draft-ietf-manet-nhdp-13.txt   draft-ietf-manet-nhdp-14.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet-Draft LIX, Ecole Polytechnique Internet-Draft LIX, Ecole Polytechnique
Intended status: Standards Track C. Dearlove Intended status: Standards Track C. Dearlove
Expires: January 13, 2011 BAE Systems ATC Expires: January 13, 2011 BAE Systems ATC
J. Dean J. Dean
Naval Research Laboratory Naval Research Laboratory
The OLSRv2 Design Team The OLSRv2 Design Team
MANET Working Group MANET Working Group
July 12, 2010 July 12, 2010
Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP) Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)
draft-ietf-manet-nhdp-13 draft-ietf-manet-nhdp-14
Abstract Abstract
This document describes a 1-hop and symmetric 2-hop neighborhood This document describes a 1-hop and symmetric 2-hop neighborhood
discovery protocol (NHDP) for mobile ad hoc networks (MANETs). discovery protocol (NHDP) for mobile ad hoc networks (MANETs).
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.
skipping to change at page 15, line 40 skipping to change at page 15, line 40
o As a response to a change in the router itself, or its 1-hop o As a response to a change in the router itself, or its 1-hop
neighborhood, for example on first becoming active or in response neighborhood, for example on first becoming active or in response
to a new, lost, or changed status link. to a new, lost, or changed status link.
o In a combination of these proactive and responsive mechanisms. o In a combination of these proactive and responsive mechanisms.
Jittering of HELLO message generation and transmission SHOULD be used Jittering of HELLO message generation and transmission SHOULD be used
as described in Section 11.2, unless the medium access control as described in Section 11.2, unless the medium access control
mechanism in use prevents any simultaneous transmissions by mechanism in use prevents any simultaneous transmissions by
potentially interefering routers. potentially interfering routers.
HELLO messages MAY be scheduled independently for each MANET HELLO messages MAY be scheduled independently for each MANET
interface, or, interface parameters permitting, using the same interface, or, interface parameters permitting, using the same
schedule for all MANET interfaces of a router. schedule for all MANET interfaces of a router.
4.3.2. HELLO Message Content 4.3.2. HELLO Message Content
The content of a HELLO message MUST satisfy the following: The content of a HELLO message MUST satisfy the following:
o A HELLO message MUST contain all of the network addresses in the o A HELLO message MUST contain all of the network addresses in the
skipping to change at page 16, line 40 skipping to change at page 16, line 40
whether that information has been sent in the interval of length whether that information has been sent in the interval of length
REFRESH_INTERVAL up to the current time. Instead, the router MUST REFRESH_INTERVAL up to the current time. Instead, the router MUST
consider the interval of length REFRESH_INTERVAL that will end at consider the interval of length REFRESH_INTERVAL that will end at
the latest possible time at which the next HELLO message will be the latest possible time at which the next HELLO message will be
sent on this MANET interface. (Normally, this will be sent on this MANET interface. (Normally, this will be
HELLO_INTERVAL past the current time, but MAY be earlier if this HELLO_INTERVAL past the current time, but MAY be earlier if this
router elects to divide its neighbor information among more than router elects to divide its neighbor information among more than
one HELLO message in order to reduce the size of its HELLO one HELLO message in order to reduce the size of its HELLO
messages.) All neighbor information MUST be sent in this messages.) All neighbor information MUST be sent in this
interval, i.e., the router MUST ensure that this HELLO message interval, i.e., the router MUST ensure that this HELLO message
includes all neighbour information that has not already been includes all neighbor information that has not already been
included in any HELLO messages sent since the start of this included in any HELLO messages sent since the start of this
interval (normally the current time - (REFRESH_INTERVAL - interval (normally the current time - (REFRESH_INTERVAL -
HELLO_INTERVAL)). HELLO_INTERVAL)).
o A HELLO message MUST include exactly one VALIDITY_TIME Message o A HELLO message MUST include exactly one VALIDITY_TIME Message
TLV, as specified in [RFC5497], that indicates the length of time TLV, as specified in [RFC5497], that indicates the length of time
for which the message content is to be considered valid, and is for which the message content is to be considered valid, and is
therefore to be included in the receiving router's Interface therefore to be included in the receiving router's Interface
Information Base. Information Base.
skipping to change at page 18, line 9 skipping to change at page 18, line 9
router to determine that a given link is too unstable to even router to determine that a given link is too unstable to even
consider for use. It is specifically not a link metric nor a consider for use. It is specifically not a link metric nor a
substitute for one. substitute for one.
Link quality information is only used locally and is not used in Link quality information is only used locally and is not used in
signaling. Routers may interoperate whether they are using the same, signaling. Routers may interoperate whether they are using the same,
different, or no, link quality information. Link quality information different, or no, link quality information. Link quality information
is thus not equivalent to a link metric. is thus not equivalent to a link metric.
Link quality information is defined in this specification as a Link quality information is defined in this specification as a
normalised, dimensionless, value in the interval zero to one, normalized, dimensionless, value in the interval zero to one,
inclusive, where the greater the value, the better the link quality. inclusive, where the greater the value, the better the link quality.
See Section 14 for further details. See Section 14 for further details.
5. Protocol Parameters and Constants 5. Protocol Parameters and Constants
The parameters and constants used in this specification are described The parameters and constants used in this specification are described
in this section. in this section.
5.1. Protocol and Port Numbers 5.1. Protocol and Port Numbers
skipping to change at page 21, line 24 skipping to change at page 21, line 24
L_HOLD_TIME MAY be set to zero, if accelerated information removal L_HOLD_TIME MAY be set to zero, if accelerated information removal
is not required. is not required.
H_HOLD_TIME - is used as the Value in the VALIDITY_TIME Message TLV H_HOLD_TIME - is used as the Value in the VALIDITY_TIME Message TLV
included in all HELLO messages on this MANET interface. It is included in all HELLO messages on this MANET interface. It is
then used by each router receiving such a HELLO message to then used by each router receiving such a HELLO message to
indicate the validity of the information taken from that HELLO indicate the validity of the information taken from that HELLO
message and recorded in the receiving router's Information Bases. message and recorded in the receiving router's Information Bases.
Note that as each item of neighbor information is included in HELLO Note that as each item of neighbor information is included in HELLO
messages within an interval of length REFRESH~_INTERVAL, contrainst messages within an interval of length REFRESH_INTERVAL, constraints
on H_HOLD_TIME are based on REFRESH_INTERVAL, not on HELLO_INTERVAL. on H_HOLD_TIME are based on REFRESH_INTERVAL, not on HELLO_INTERVAL.
The following constraints apply to these interface parameters: The following constraints apply to these interface parameters:
o L_HOLD_TIME >= 0 o L_HOLD_TIME >= 0
o H_HOLD_TIME >= REFRESH_INTERVAL o H_HOLD_TIME >= REFRESH_INTERVAL
o If HELLO messages can be lost then both parameters SHOULD be o If HELLO messages can be lost then both parameters SHOULD be
significantly greater than REFRESH_INTERVAL. significantly greater than REFRESH_INTERVAL.
skipping to change at page 36, line 46 skipping to change at page 36, line 46
included or excluded from each HELLO message. Each such Address included or excluded from each HELLO message. Each such Address
Block TLV MUST be included associated with the address object Block TLV MUST be included associated with the address object
representation of that network address in a HELLO message sent on representation of that network address in a HELLO message sent on
that MANET interface in every interval of length equal to that MANET that MANET interface in every interval of length equal to that MANET
interface's parameter REFRESH_INTERVAL. Address Block TLVs interface's parameter REFRESH_INTERVAL. Address Block TLVs
associated with the same address object included in the same HELLO associated with the same address object included in the same HELLO
message MAY be applied to the same or different copies of that message MAY be applied to the same or different copies of that
address object. address object.
An implementation of this protocol MAY limit the information included An implementation of this protocol MAY limit the information included
in each HELLO message, for example to acommodate smaller MTU sizes. in each HELLO message, for example to accommodate smaller MTU sizes.
HELLO messages remain constrained by the above requirements, in HELLO messages remain constrained by the above requirements, in
particular that all local interface information MUST be included in particular that all local interface information MUST be included in
all HELLO messages, and that all neighbor information MUST be sent all HELLO messages, and that all neighbor information MUST be sent
within each interval of length REFRESH_INTERVAL. This neighbor within each interval of length REFRESH_INTERVAL. This neighbor
information MAY, however, be sent in the same or in different HELLO information MAY, however, be sent in the same or in different HELLO
messages. messages.
11.2. HELLO Message Transmission 11.2. HELLO Message Transmission
HELLO messages are transmitted in the format specified by [RFC5444]. HELLO messages are transmitted in the format specified by [RFC5444].
skipping to change at page 48, line 5 skipping to change at page 48, line 5
Link quality is a mechanism whereby a router MAY take considerations Link quality is a mechanism whereby a router MAY take considerations
other than message exchange into account for determining when a link other than message exchange into account for determining when a link
is and is not a candidate for being considered as HEARD or SYMMETRIC. is and is not a candidate for being considered as HEARD or SYMMETRIC.
As such, it is a "link admission" mechanism. As such, it is a "link admission" mechanism.
Link quality information for a link is generated (e.g., through Link quality information for a link is generated (e.g., through
access to signal to noise ratio, packet loss rate, or other access to signal to noise ratio, packet loss rate, or other
information from the link layer) and used only locally, i.e., is not information from the link layer) and used only locally, i.e., is not
included in signaling, and routers may interoperate whether they are included in signaling, and routers may interoperate whether they are
using the same, different, or no, link quality information. Link using the same, different, or no, link quality information. Link
quality information is specified as a normalised, dimensionless quality information is specified as a normalized, dimensionless
figure in the interval zero to one, inclusive, a higher value figure in the interval zero to one, inclusive, a higher value
indicating a better link quality. indicating a better link quality.
For deployments where no link quality is used, the considerations in For deployments where no link quality is used, the considerations in
Section 14.1 apply. For deployments where link quality is used, the Section 14.1 apply. For deployments where link quality is used, the
general principles of link quality usage are described in general principles of link quality usage are described in
Section 14.2. Section 14.3 and Section 14.4 detail link quality Section 14.2. Section 14.3 and Section 14.4 detail link quality
functioning. functioning.
14.1. Deployment Without Link Quality 14.1. Deployment Without Link Quality
skipping to change at page 50, line 4 skipping to change at page 50, line 4
corresponding Link Tuple is modified by: corresponding Link Tuple is modified by:
1. If L_lost = false, then: 1. If L_lost = false, then:
o L_lost := true; o L_lost := true;
o L_time := min(L_time, current time + L_HOLD_TIME). o L_time := min(L_time, current time + L_HOLD_TIME).
As a result of this processing, the L_STATUS of a Link Tuple may As a result of this processing, the L_STATUS of a Link Tuple may
change. In this case, the processing actions corresponding to this change. In this case, the processing actions corresponding to this
change, as specified in in Section 13, MUST also be taken. change, as specified in Section 13, MUST also be taken.
If L_quality for a link is updated based on HELLO message reception, If L_quality for a link is updated based on HELLO message reception,
or on reception of a packet including a HELLO message, then L_quality or on reception of a packet including a HELLO message, then L_quality
MUST be updated prior to the HELLO message processing described in MUST be updated prior to the HELLO message processing described in
Section 12. (If the receipt of the HELLO message, or the packet Section 12. (If the receipt of the HELLO message, or the packet
containing it, creates the Link Tuple, then the Link Tuple MUST be containing it, creates the Link Tuple, then the Link Tuple MUST be
created with the appropriately updated L_quality value, rather than created with the appropriately updated L_quality value, rather than
with L_quality := INITIAL_QUALITY.) with L_quality := INITIAL_QUALITY.)
14.4. Updating Link Quality 14.4. Updating Link Quality
 End of changes. 8 change blocks. 
8 lines changed or deleted 8 lines changed or added

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