draft-ietf-manet-nhdp-optimization-03.txt   draft-ietf-manet-nhdp-optimization-04.txt 
Mobile Ad hoc Networking (MANET) C. Dearlove Mobile Ad hoc Networking (MANET) C. Dearlove
Internet-Draft BAE Systems ATC Internet-Draft BAE Systems ATC
Updates: 6130, 7181 T. Clausen Updates: 6130, 7181 T. Clausen
(if approved) LIX, Ecole Polytechnique (if approved) LIX, Ecole Polytechnique
Intended status: Standards Track September 5, 2014 Intended status: Standards Track January 23, 2015
Expires: March 9, 2015 Expires: July 27, 2015
An Optimization for the MANET Neighborhood Discovery Protocol (NHDP) An Optimization for the MANET Neighborhood Discovery Protocol (NHDP)
draft-ietf-manet-nhdp-optimization-03 draft-ietf-manet-nhdp-optimization-04
Abstract Abstract
The link quality mechanism of the MANET Neighborhood Discovery The link quality mechanism of the MANET Neighborhood Discovery
Protocol (NHDP) enables "ignoring" some 1-hop neighbors if the Protocol (NHDP) enables "ignoring" some 1-hop neighbors if the
measured link quality from that 1-hop neighbor is below an acceptable measured link quality from that 1-hop neighbor is below an acceptable
threshold, while still retaining the corresponding link information threshold, while still retaining the corresponding link information
as acquired from HELLO message exchange. This allows immediate as acquired from HELLO message exchange. This allows immediate
reinstatement of the 1-hop neighbor if the link quality later reinstatement of the 1-hop neighbor if the link quality later
improves sufficiently. improves sufficiently.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
However it specifies that if a link from a symmetric 1-hop neighbor However it specifies that if a link from a symmetric 1-hop neighbor
ceases being symmetric, including while "ignored" as described above, ceases being symmetric, including while "ignored" as described above,
then corresponding symmetric 2-hop neighbors are removed. This may then corresponding symmetric 2-hop neighbors are removed. This may
lead to symmetric 2-hop neighborhood information being permanently lead to symmetric 2-hop neighborhood information being permanently
removed (until further HELLO messages are received) if the link removed (until further HELLO messages are received) if the link
quality of a symmetric 1-hop neighbor drops below the acceptable quality of a symmetric 1-hop neighbor drops below the acceptable
threshold, even if only for a moment. threshold, even if only for a moment.
This specification updates RFC6130 "Mobile Ad Hoc Network (MANET) This specification updates RFC6130 "Mobile Ad Hoc Network (MANET)
Neighborhood Discovery Protocol (NHDP)", and RFC7181 "The Optimized Neighborhood Discovery Protocol (NHDP)", and RFC7181 "The Optimized
Link State Routing Protocol version 2 (OLSRv2)" to permit retaining, Link State Routing Protocol version 2 (OLSRv2)" to permit, as an
but ignoring, symmetric 2-hop information when the link quality from option, retaining, but ignoring, symmetric 2-hop information when the
the corresponding 1-hop neighbor drops below the acceptable link quality from the corresponding 1-hop neighbor drops below the
threshold. This allows immediate reinstatement of the symmetric acceptable threshold. This allows immediate reinstatement of the
2-hop neighbor if the link quality later improves sufficiently, thus symmetric 2-hop neighbor if the link quality later improves
making the symmetric 2-hop neighborhood more "robust". sufficiently, thus making the symmetric 2-hop neighborhood more
"robust".
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 9, 2015. This Internet-Draft will expire on July 27, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 5, line 35 skipping to change at page 5, line 35
this specification is simply permissive, as it allows retaining this specification is simply permissive, as it allows retaining
information which otherwise would have been removed, but does not use information which otherwise would have been removed, but does not use
that information except when it could have been used by [RFC6130]. that information except when it could have been used by [RFC6130].
This can, in some cases, ensure that the symmetric 2-hop neighborhood This can, in some cases, ensure that the symmetric 2-hop neighborhood
is more robust against temporary link quality changes, and is more robust against temporary link quality changes, and
consequently yield a more stable network. The only other consequence consequently yield a more stable network. The only other consequence
of this optimization is that state for some otherwise expired 2-Hop of this optimization is that state for some otherwise expired 2-Hop
Tuples may be maintained for longer. Tuples may be maintained for longer.
This specification also updates [RFC7181]. This could be avoided by This specification also updates [RFC7181]. This could have been
simply noting that this specification describes how the updates to avoided by this specification describing how the updates to [RFC6130]
[RFC6130] may be handled so as to be invisible to any other protocol may be handled so as to be invisible to any other protocol using it.
using it. However as it is known that some implementations of However, as it is known that some implementations of [RFC7181] are
[RFC7181] are not independent of the implementation of [RFC6130] that not independent of the implementation of [RFC6130] that they use, it
they use, it is useful to indicate the direct impact on [RFC7181]. is useful to indicate the direct impact on [RFC7181].
A router that implements the optimization described in this A router that implements the optimization described in this
specification will interoperate successfully with routers that specification will interoperate successfully with routers that
implement [RFC6130], but do not implement this optimization. implement [RFC6130], but do not implement this optimization.
4. Changes to NHDP 4. Changes to NHDP
The following changes are made to [RFC6130] if using this The following changes are made to [RFC6130] if using this
specification. Note that while this specification is OPTIONAL, if specification. Note that while this specification is OPTIONAL, if
any of these changes are made then all of these changes MUST be made. any of these changes are made then all of these changes MUST be made.
 End of changes. 6 change blocks. 
17 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/