< draft-ietf-manet-dymo-16.txt   draft-ietf-manet-dymo-17.txt >
Mobile Ad hoc Networks Working I. Chakeres Mobile Ad hoc Networks Working I. Chakeres
Group CenGen Group CenGen
Internet-Draft C. Perkins Internet-Draft C. Perkins
Intended status: Standards Track WiChorus Intended status: Standards Track WiChorus
Expires: June 8, 2009 December 5, 2008 Expires: September 9, 2009 March 8, 2009
Dynamic MANET On-demand (DYMO) Routing Dynamic MANET On-demand (DYMO) Routing
draft-ietf-manet-dymo-16 draft-ietf-manet-dymo-17
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 8, 2009. This Internet-Draft will expire on September 9, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
The Dynamic MANET On-demand (DYMO) routing protocol is intended for The Dynamic MANET On-demand (DYMO) routing protocol is intended for
use by mobile routers in wireless, multihop networks. DYMO use by mobile routers in wireless, multihop networks. DYMO
determines unicast routes among DYMO routers within the network in an determines unicast routes among DYMO routers within the network in an
on-demand fashion, offering improved convergence in dynamic on-demand fashion, offering improved convergence in dynamic
topologies. topologies.
Table of Contents Table of Contents
skipping to change at page 2, line 34 skipping to change at page 2, line 37
5.2.2. Creating or Updating a Route Table Entry with 5.2.2. Creating or Updating a Route Table Entry with
Received Superior Routing Information . . . . . . . . 17 Received Superior Routing Information . . . . . . . . 17
5.2.3. Route Table Entry Timeouts . . . . . . . . . . . . . . 18 5.2.3. Route Table Entry Timeouts . . . . . . . . . . . . . . 18
5.3. Routing Messages . . . . . . . . . . . . . . . . . . . . . 18 5.3. Routing Messages . . . . . . . . . . . . . . . . . . . . . 18
5.3.1. RREQ Creation . . . . . . . . . . . . . . . . . . . . 18 5.3.1. RREQ Creation . . . . . . . . . . . . . . . . . . . . 18
5.3.2. RREP Creation . . . . . . . . . . . . . . . . . . . . 19 5.3.2. RREP Creation . . . . . . . . . . . . . . . . . . . . 19
5.3.3. Intermediate DYMO Router RREP Creation . . . . . . . . 20 5.3.3. Intermediate DYMO Router RREP Creation . . . . . . . . 20
5.3.4. RM Processing . . . . . . . . . . . . . . . . . . . . 21 5.3.4. RM Processing . . . . . . . . . . . . . . . . . . . . 21
5.3.5. Adding Additional Routing Information to a RM . . . . 24 5.3.5. Adding Additional Routing Information to a RM . . . . 24
5.4. Route Discovery . . . . . . . . . . . . . . . . . . . . . 25 5.4. Route Discovery . . . . . . . . . . . . . . . . . . . . . 25
5.5. Route Maintenance . . . . . . . . . . . . . . . . . . . . 25 5.5. Route Maintenance . . . . . . . . . . . . . . . . . . . . 26
5.5.1. Active Link Monitoring . . . . . . . . . . . . . . . . 26 5.5.1. Active Link Monitoring . . . . . . . . . . . . . . . . 26
5.5.2. Updating Route Lifetimes During Packet Forwarding . . 26 5.5.2. Updating Route Lifetimes During Packet Forwarding . . 26
5.5.3. RERR Generation . . . . . . . . . . . . . . . . . . . 27 5.5.3. RERR Generation . . . . . . . . . . . . . . . . . . . 27
5.5.4. RERR Processing . . . . . . . . . . . . . . . . . . . 27 5.5.4. RERR Processing . . . . . . . . . . . . . . . . . . . 28
5.6. Unknown Message & TLV Types . . . . . . . . . . . . . . . 29 5.6. DYMO Identifier (DID) . . . . . . . . . . . . . . . . . . 29
5.7. Advertising Network Addresses . . . . . . . . . . . . . . 29 5.7. Unknown Message & TLV Types . . . . . . . . . . . . . . . 29
5.8. Simple Internet Attachment . . . . . . . . . . . . . . . . 29 5.8. Advertising Network Addresses . . . . . . . . . . . . . . 30
5.9. Multiple Interfaces . . . . . . . . . . . . . . . . . . . 31 5.9. Simple Internet Attachment . . . . . . . . . . . . . . . . 30
5.10. DYMO Control Packet/Message Generation Limits . . . . . . 31 5.10. Multiple Interfaces . . . . . . . . . . . . . . . . . . . 31
6. Configuration Parameters and Other Administrative Options . . 31 5.11. DYMO Control Packet/Message Generation Limits . . . . . . 31
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 6. Configuration Parameters and Other Administrative Options . . 32
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
7.1. DYMO Message Type Specification . . . . . . . . . . . . . 33 7.1. DYMO Message Type Specification . . . . . . . . . . . . . 33
7.2. Packet and Message TLV Type Specification . . . . . . . . 33 7.2. Packet and Message TLV Type Specification . . . . . . . . 33
7.3. Address Block TLV Specification . . . . . . . . . . . . . 34 7.3. Address Block TLV Specification . . . . . . . . . . . . . 34
8. Security Considerations . . . . . . . . . . . . . . . . . . . 34 8. Security Considerations . . . . . . . . . . . . . . . . . . . 35
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 35 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 35
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 36
10.1. Normative References . . . . . . . . . . . . . . . . . . . 35 10.1. Normative References . . . . . . . . . . . . . . . . . . . 36
10.2. Informative References . . . . . . . . . . . . . . . . . . 36 10.2. Informative References . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37
Intellectual Property and Copyright Statements . . . . . . . . . . 38
1. Overview 1. Overview
The Dynamic MANET On-demand (DYMO) routing protocol enables reactive, The Dynamic MANET On-demand (DYMO) routing protocol enables reactive,
multihop unicast routing among participating DYMO routers. The basic multihop unicast routing among participating DYMO routers. The basic
operations of the DYMO protocol are route discovery and route operations of the DYMO protocol are route discovery and route
maintenance. maintenance.
During route discovery, the originator's DYMO router initiates During route discovery, the originator's DYMO router initiates
dissemination of a Route Request (RREQ) throughout the network to dissemination of a Route Request (RREQ) throughout the network to
skipping to change at page 6, line 19 skipping to change at page 6, line 19
routers may form an adjacency based several different pieces of routers may form an adjacency based several different pieces of
information or protocols; for example, exchange of DYMO routing information or protocols; for example, exchange of DYMO routing
messages, other protocols (e.g. NDP [RFC4861] or NHDP messages, other protocols (e.g. NDP [RFC4861] or NHDP
[I-D.ietf-manet-nhdp]), or manual configuration. [I-D.ietf-manet-nhdp]), or manual configuration.
Distance (Dist) Distance (Dist)
A metric of the distance a message or piece of information has A metric of the distance a message or piece of information has
traversed. The minimum value of distance is the number of IP hops traversed. The minimum value of distance is the number of IP hops
traversed. The maximum value is 65,535. traversed. The maximum value is 65,535.
DYMO Identifier (DID)
A DID is maintained by each DYMO routing protocol instance
(ThisNode.DID), and the default value is zero (0). Each routing
message is tagged with its associated DID (MsgTLV.DID), unless
zero (0). Upon receipt of DYMO protocol message a DYMO routing
protocol instance SHOULD only process messages with a matching DID
value.
DYMO Sequence Number (SeqNum) DYMO Sequence Number (SeqNum)
A DYMO Sequence Number is maintained by each DYMO router. This A DYMO Sequence Number is maintained by each DYMO router. This
sequence number is used by other DYMO routers to identify the sequence number is used by other DYMO routers to identify the
temporal order of routing information generated and ensure loop- temporal order of routing information generated and ensure loop-
free routes. free routes.
Forwarding Route Forwarding Route
A route that is used to forward data packets. Forwarding routes A route that is used to forward data packets. Forwarding routes
are generally maintained in a forwarding information base (FIB) or are generally maintained in a forwarding information base (FIB) or
the kernel forwarding/routing table. the kernel forwarding/routing table.
skipping to change at page 19, line 43 skipping to change at page 19, line 43
For RREQ, the MsgHdr.HopLimit MAY be set in accordance with an For RREQ, the MsgHdr.HopLimit MAY be set in accordance with an
expanding ring search as described in [RFC3561] to limit the RREQ expanding ring search as described in [RFC3561] to limit the RREQ
propagation to a subset of the local network and possibly reduce propagation to a subset of the local network and possibly reduce
route discovery overhead. route discovery overhead.
The IP.DestinationAddress for multicast RREQ is set to LL-MANET- The IP.DestinationAddress for multicast RREQ is set to LL-MANET-
ROUTERS. The IP.DestinationAddress for unicast RREQ is set to the ROUTERS. The IP.DestinationAddress for unicast RREQ is set to the
NextHopAddress. NextHopAddress.
Each DYMO routing protocol message SHOULD contain ThisNode.DID's
value in a message TLV (MsgTLV.DID). If ThisNode.DID value is zero
(0) it MAY be omitted.
5.3.2. RREP Creation 5.3.2. RREP Creation
First, the AddBlk.TargetNode.Address is added to the RREP. The First, the AddBlk.TargetNode.Address is added to the RREP. The
TargetNode is the ultimate destination of this RREP; the RREQ TargetNode is the ultimate destination of this RREP; the RREQ
OrigNode.Address. OrigNode.Address.
Next, AddBlk.OrigNode.Address and prefix are added to the RREP. The Next, AddBlk.OrigNode.Address and prefix are added to the RREP. The
AddBlk.OrigNode.Address is the RREQ TargetNode.Address. The AddBlk.OrigNode.Address is the RREQ TargetNode.Address. The
AddBlk.OrigNode.Address MUST be a unicast IP address. ThisNode AddBlk.OrigNode.Address MUST be a unicast IP address. ThisNode
SHOULD advertise the largest known prefix containing SHOULD advertise the largest known prefix containing
skipping to change at page 20, line 41 skipping to change at page 20, line 45
to a number greater than zero (0) and less than 65,535. The Distance to a number greater than zero (0) and less than 65,535. The Distance
value will influence judgment of the routing information value will influence judgment of the routing information
(Section 5.2.1) against known information at other DYMO routers that (Section 5.2.1) against known information at other DYMO routers that
process this RM. process this RM.
The MsgHdr.HopLimit is set to MSG_HOPLIMIT. The MsgHdr.HopLimit is set to MSG_HOPLIMIT.
The IP.DestinationAddress for RREP is set to the IP address of the The IP.DestinationAddress for RREP is set to the IP address of the
Route.NextHopAddress for the route to the RREP TargetNode. Route.NextHopAddress for the route to the RREP TargetNode.
Each DYMO routing protocol message SHOULD contain ThisNode.DID's
value in a message TLV (MsgTLV.DID). If ThisNode.DID value is zero
(0) it MAY be omitted.
5.3.3. Intermediate DYMO Router RREP Creation 5.3.3. Intermediate DYMO Router RREP Creation
Sometimes a DYMO router other than the TargetNode's DYMO router (call Sometimes a DYMO router other than the TargetNode's DYMO router (call
it an "intermediate DYMO router") has routing information that can it an "intermediate DYMO router") has routing information that can
satisfy an incoming RREQ. An intermediate DYMO router can issue a satisfy an incoming RREQ. An intermediate DYMO router can issue a
intermediate DYMO router RREP on behalf of the TargetNode's DYMO intermediate DYMO router RREP on behalf of the TargetNode's DYMO
router. router.
Before creating a intermediate DYMO router RREP, OwnSeqNum SHOULD be Before creating a intermediate DYMO router RREP, OwnSeqNum SHOULD be
incremented by one (1) according to the rules specified in incremented by one (1) according to the rules specified in
skipping to change at page 21, line 25 skipping to change at page 21, line 32
The Intermediate DYMO router SHOULD also issue a RREP to the RREQ The Intermediate DYMO router SHOULD also issue a RREP to the RREQ
TargetNode, so that the RREQ TargetNode receives routing information TargetNode, so that the RREQ TargetNode receives routing information
on how to reach the RREQ OrigNode. on how to reach the RREQ OrigNode.
When an intermediate DYMO router creates this RREP, it sends a RREP When an intermediate DYMO router creates this RREP, it sends a RREP
to the RREQ TargetNode with additional routing information (Address, to the RREQ TargetNode with additional routing information (Address,
Prefix, SeqNum, Dist, etc.) about the RREQ OrigNode. Prefix, SeqNum, Dist, etc.) about the RREQ OrigNode.
5.3.4. RM Processing 5.3.4. RM Processing
First, ThisNode decides whether to process this message. ThisNode First, ThisNode decides whether to process this message. If the
MAY selectively process messages based upon information in the message contains a MsgTLV.DID it SHOULD match ThisNode.DID's value.
message. ThisNode SHOULD only process messages from adjacent DYMO If the message does not contain a MsgTLV.DID it is assumed to be zero
routers. If ThisNode chooses not to process this message, the (0) and SHOULD be discarded if ThisNode.DID's value is not zero (0).
message is discarded and further processing stopped.
Next, ThisNode MAY selectively process messages based upon
information in the message. ThisNode SHOULD only process messages
from adjacent DYMO routers. If ThisNode chooses not to process this
message, the message is discarded and further processing stopped.
ThisNode checks if the AddBlk.OrigNode.Address is a valid multihop- ThisNode checks if the AddBlk.OrigNode.Address is a valid multihop-
capable (e.g. site or global scope) unicast IP address. If the capable (e.g. site or global scope) unicast IP address. If the
address is not a valid unicast IP address, the messages is discarded address is not a valid unicast IP address, the messages is discarded
and further processing stopped. and further processing stopped.
ThisNode also checks whether AddBlk.OrigNode.Address is an address ThisNode also checks whether AddBlk.OrigNode.Address is an address
handled by this DYMO router. If this node is the originating DYMO handled by this DYMO router. If this node is the originating DYMO
router, the RM is dropped. router, the RM is dropped.
skipping to change at page 24, line 25 skipping to change at page 24, line 36
control message sending or packet forwarding. This type of advanced control message sending or packet forwarding. This type of advanced
behavior is not defined in this specification. behavior is not defined in this specification.
5.3.5. Adding Additional Routing Information to a RM 5.3.5. Adding Additional Routing Information to a RM
Appending routing information can alleviate route discovery attempts Appending routing information can alleviate route discovery attempts
to the nodes whose information is included, if other DYMO routers use to the nodes whose information is included, if other DYMO routers use
this information to update their routing tables. this information to update their routing tables.
DYMO routers can append routing information to a RM. This option DYMO routers can append routing information to a RM. This option
should be administratively configurable or intelligently controlled. should be administratively configurable or intelligently controlled.o
Prior to appending an address controlled by this DYMO router to a RM, Prior to appending an address controlled by this DYMO router to a RM,
ThisNode MAY increment its OwnSeqNum as defined in Section 5.1.2. If ThisNode MAY increment its OwnSeqNum as defined in Section 5.1.2. If
OwnSeqNum is not incremented the appended routing information might OwnSeqNum is not incremented the appended routing information might
not be considered superior, when received by nodes with existing not be considered superior, when received by nodes with existing
routing information. Incrementation of the sequence number when routing information. Incrementation of the sequence number when
appending information to an RM in transit should be administratively appending information to an RM in transit should be administratively
configurable or intelligently controlled. configurable or intelligently controlled.
If an address controlled by this DYMO router includes ThisNode.Dist, If an address controlled by this DYMO router includes ThisNode.Dist,
skipping to change at page 27, line 34 skipping to change at page 27, line 41
The SeqNum if known SHOULD also be included. Appending The SeqNum if known SHOULD also be included. Appending
UnreachableNode information notifies each processing node of UnreachableNode information notifies each processing node of
additional routes that are no longer available. This option SHOULD additional routes that are no longer available. This option SHOULD
be administratively configurable or intelligently controlled. be administratively configurable or intelligently controlled.
If SeqNum information is not known or not included in the RERR, all If SeqNum information is not known or not included in the RERR, all
nodes processing the RERR will assume their routing information nodes processing the RERR will assume their routing information
associated with the UnreachableNode is no longer valid and flag those associated with the UnreachableNode is no longer valid and flag those
routes as broken. routes as broken.
Each DYMO routing protocol message SHOULD contain ThisNode.DID's
value in a message TLV (MsgTLV.DID). If ThisNode.DID value is zero
(0) it MAY be omitted.
A multicast RERR is sent to the IP.DestinationAddress LL-MANET- A multicast RERR is sent to the IP.DestinationAddress LL-MANET-
ROUTERS [I-D.ietf-manet-iana]. Sending the RERR to the LL-MANET- ROUTERS [I-D.ietf-manet-iana]. Sending the RERR to the LL-MANET-
ROUTERS address notifies all nearby DYMO routers that might depend on ROUTERS address notifies all nearby DYMO routers that might depend on
the now broken link. If the RERR is unicast, the the now broken link. If the RERR is unicast, the
IP.DestinationAddress is set to the NextHopAddress. IP.DestinationAddress is set to the NextHopAddress.
At this point, the packet or message that forced generation of this At this point, the packet or message that forced generation of this
RERR SHOULD be discarded. RERR SHOULD be discarded.
5.5.4. RERR Processing 5.5.4. RERR Processing
First, ThisNode decides whether to process this message. ThisNode First, ThisNode decides whether to process this message. If the
MAY selectively process messages based upon information in the message contains a MsgTLV.DID it SHOULD match ThisNode.DID's value.
message. ThisNode MAY choose to only process messages from adjacent If the message does not contain a MsgTLV.DID it is assumed to be zero
DYMO routers. If ThisNode chooses not to process this message, the (0) and SHOULD be discarded if ThisNode.DID's value is not zero (0).
message is discarded and further processing stopped.
Next, ThisNode MAY selectively process messages based upon
information in the message. ThisNode MAY choose to only process
messages from adjacent DYMO routers. If ThisNode chooses not to
process this message, the message is discarded and further processing
stopped.
When a DYMO router processes a RERR, it processes each When a DYMO router processes a RERR, it processes each
UnreachableNode's information. The processing DYMO router removes UnreachableNode's information. The processing DYMO router removes
the forwarding route, unsets the Route.Forwarding flag, sets the the forwarding route, unsets the Route.Forwarding flag, sets the
Route.Broken flag, and a timer for ROUTE_DELETE is set to Route.Broken flag, and a timer for ROUTE_DELETE is set to
ROUTE_DELETE_TIMEOUT for each UnreachableNode.Address found using ROUTE_DELETE_TIMEOUT for each UnreachableNode.Address found using
longest prefix matching that meet all of the following conditions: longest prefix matching that meet all of the following conditions:
1. The UnreachableNode.Address is a multihop-capable unicast IP 1. The UnreachableNode.Address is a multihop-capable unicast IP
address. address.
skipping to change at page 29, line 7 skipping to change at page 29, line 24
If processing continues, the MsgHdr.HopLimit is decremented by one If processing continues, the MsgHdr.HopLimit is decremented by one
(1). Further, if this RERR's new MsgHdr.HopLimit is greater than one (1). Further, if this RERR's new MsgHdr.HopLimit is greater than one
(1) and at least one unreachable node address remains in the RERR, (1) and at least one unreachable node address remains in the RERR,
then the updated RERR SHOULD be sent. then the updated RERR SHOULD be sent.
A multicast RERR is sent to the IP.DestinationAddress LL-MANET- A multicast RERR is sent to the IP.DestinationAddress LL-MANET-
ROUTERS [I-D.ietf-manet-iana]. If the RERR is unicast, the ROUTERS [I-D.ietf-manet-iana]. If the RERR is unicast, the
IP.DestinationAddress is set to the NextHopAddress. IP.DestinationAddress is set to the NextHopAddress.
5.6. Unknown Message & TLV Types 5.6. DYMO Identifier (DID)
Each DYMO routing protocol instance MUST have an associated DYMO
Identifier (DID). The default value is zero (0). The DID value
should be administratively configured.
Each DYMO routing protocol message sent SHOULD contain its associated
DID in a message TLV. If the DID value is zero (0) it MAY be
omitted.
Upon receipt of DYMO protocol message a DYMO routing protocol
instance SHOULD only process messages with a DID (MsgTLV.DID) value
matching its own DID (ThisNode.DID).
The DID allows multiple DYMO routing protocol instances to operate
over the same links and same node independently.
The DID fulfills a function similar to OSPF Instance ID [RFC2740]
[I-D.ietf-ospf-multi-instance], OSPF Area ID [RFC2328] [RFC2740],
and/or the MANET_ID TLV [I-D.chakeres-manet-manetid].
5.7. Unknown Message & TLV Types
If a message with an unknown type is received, the message is If a message with an unknown type is received, the message is
discarded. discarded.
For processing of messages that contain unknown TLV types, operation For processing of messages that contain unknown TLV types, operation
should be administratively controlled. should be administratively controlled.
5.7. Advertising Network Addresses 5.8. Advertising Network Addresses
DYMO routers advertise specify the prefix length for each advertised DYMO routers advertise specify the prefix length for each advertised
address. Any nodes (other than the advertising DYMO router) within address. Any nodes (other than the advertising DYMO router) within
the advertised prefix MUST NOT participate in the DYMO protocol the advertised prefix MUST NOT participate in the DYMO protocol
directly. For example, A.B.C.1 with a prefix length of 24 indicates directly. For example, A.B.C.1 with a prefix length of 24 indicates
all nodes with the matching A.B.C.X are reachable through the DYMO all nodes with the matching A.B.C.X are reachable through the DYMO
router with address A.B.C.1. router with address A.B.C.1.
5.8. Simple Internet Attachment 5.9. Simple Internet Attachment
Simple Internet attachment consists of a stub network of MANET Simple Internet attachment consists of a stub network of MANET
routers connected to the Internet via a single Internet DYMO router routers connected to the Internet via a single Internet DYMO router
(IDR). The Internet may be connected via multiple DYMO routers, but (IDR). The Internet may be connected via multiple DYMO routers, but
such behavior is not specified in this document. such behavior is not specified in this document.
The IDR is responsible for responding to RREQs for DYMO routers on The IDR is responsible for responding to RREQs for DYMO routers on
behalf of TargetNodes on the Internet, as well as delivering packets behalf of TargetNodes on the Internet, as well as delivering packets
to destinations on the Internet. to destinations on the Internet.
skipping to change at page 31, line 6 skipping to change at page 31, line 26
for properly responding to RREQ on behalf of the Internet for properly responding to RREQ on behalf of the Internet
destinations, and maintaining their associated sequence number(s). destinations, and maintaining their associated sequence number(s).
For an IDR and other DYMO routers that maintain the sequence number For an IDR and other DYMO routers that maintain the sequence number
on behalf of other nodes, these routers MUST know the IP addresses on behalf of other nodes, these routers MUST know the IP addresses
for which they MUST generate DYMO messages and maintain OwnSeqNum. for which they MUST generate DYMO messages and maintain OwnSeqNum.
Likewise, they MUST be capable of advertising an address within the Likewise, they MUST be capable of advertising an address within the
same prefix as these IP addresses. Alternatively, they may behave as same prefix as these IP addresses. Alternatively, they may behave as
a proxy on behalf of Internet destinations. a proxy on behalf of Internet destinations.
5.9. Multiple Interfaces 5.10. Multiple Interfaces
DYMO may be used with multiple interfaces; therefore, the particular DYMO may be used with multiple interfaces; therefore, the particular
interface over which packets arrive MUST be known whenever a packet interface over which packets arrive MUST be known whenever a packet
is received. Whenever a new route is created, the interface through is received. Whenever a new route is created, the interface through
which the Route.Address can be reached is also recorded in the route which the Route.Address can be reached is also recorded in the route
table entry. table entry.
When multiple interfaces are available, a node transmitting a When multiple interfaces are available, a node transmitting a
multicast packet with IP.DestinationAddress set to LL-MANET-ROUTERS multicast packet with IP.DestinationAddress set to LL-MANET-ROUTERS
SHOULD send the packet on all interfaces that have been configured SHOULD send the packet on all interfaces that have been configured
for DYMO operation. for DYMO operation.
Similarly, DYMO routers should subscribe to LL-MANET-ROUTERS on all Similarly, DYMO routers should subscribe to LL-MANET-ROUTERS on all
their DYMO interfaces. their DYMO interfaces.
5.10. DYMO Control Packet/Message Generation Limits 5.11. DYMO Control Packet/Message Generation Limits
To ensure predictable control overhead, DYMO router's rate of packet/ To ensure predictable control overhead, DYMO router's rate of packet/
message generation SHOULD be limited. The rate and algorithm for message generation SHOULD be limited. The rate and algorithm for
limiting messages is left to the implementor and should be limiting messages is left to the implementor and should be
administratively configurable or intelligently controlled. DYMO administratively configurable or intelligently controlled. DYMO
control messages SHOULD be discarded in the following order of control messages SHOULD be discarded in the following order of
preferences RREQ, RREP, and finally RERR. preferences RREQ, RREP, and finally RERR.
6. Configuration Parameters and Other Administrative Options 6. Configuration Parameters and Other Administrative Options
skipping to change at page 34, line 12 skipping to change at page 34, line 32
Table 5 Table 5
7.3. Address Block TLV Specification 7.3. Address Block TLV Specification
Address Block TLV Types Address Block TLV Types
+---------------+--------------+--------+---------------------------+ +---------------+--------------+--------+---------------------------+
| Name | Type | Length | Value | | Name | Type | Length | Value |
+---------------+--------------+--------+---------------------------+ +---------------+--------------+--------+---------------------------+
| DYMOSeqNum | 10 - TBD | up to | The DYMO sequence num | | DYMO | 9 - TBD | DID | ThisNode.DID's value. |
| | | 2 | associated with this | | Identifier | | length | More information can be |
| | | octets | address. The sequence | | (DID) | | | found in Section 5.6 |
| DYMO Sequence | 10 - TBD | up to | The DYMO sequence num |
| Number | | 2 | associated with this |
| (DYMOSeqNum) | | octets | address. The sequence |
| | | | number may be the last | | | | | number may be the last |
| | | | known sequence number. | | | | | known sequence number. |
| Distance | 11 - TBD | up to | A metric of the distance | | Distance | 11 - TBD | up to | A metric of the distance |
| | | 2 | traversed by the | | | | 2 | traversed by the |
| | | octets | information associated | | | | octets | information associated |
| | | | with this address. | | | | | with this address. |
| VALIDITY_TIME | TBD | | The maximum amount of | | VALIDITY_TIME | TBD | | The maximum amount of |
| - AKA MaxAge | [I-D.ietf-ma | | time that information can | | - AKA MaxAge | [I-D.ietf-ma | | time that information can |
| | n et-timetlv | | be maintained before | | | n et-timetlv | | be maintained before |
| | ] | | being deleted. The | | | ] | | being deleted. The |
skipping to change at page 36, line 19 skipping to change at page 36, line 41
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., and C. [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., and C.
Pignataro, "The Generalized TTL Security Mechanism Pignataro, "The Generalized TTL Security Mechanism
(GTSM)", RFC 5082, October 2007. (GTSM)", RFC 5082, October 2007.
10.2. Informative References 10.2. Informative References
[I-D.chakeres-manet-manetid]
Chakeres, I., "MANET_ID TLV",
draft-chakeres-manet-manetid-03 (work in progress),
February 2008.
[I-D.ietf-manet-nhdp] [I-D.ietf-manet-nhdp]
Clausen, T., Dearlove, C., and J. Dean, "MANET Clausen, T., Dearlove, C., and J. Dean, "MANET
Neighborhood Discovery Protocol (NHDP)", Neighborhood Discovery Protocol (NHDP)",
draft-ietf-manet-nhdp-07 (work in progress), July 2008. draft-ietf-manet-nhdp-07 (work in progress), July 2008.
[I-D.ietf-ospf-multi-instance]
Lindem, A., Roy, A., and S. Mirtorabi, "OSPF Multi-
Instance Extensions", draft-ietf-ospf-multi-instance-00
(work in progress), February 2009.
[Perkins99] [Perkins99]
Perkins, C. and E. Belding-Royer, "Ad hoc On-Demand Perkins, C. and E. Belding-Royer, "Ad hoc On-Demand
Distance Vector (AODV) Routing", Proceedings of the 2nd Distance Vector (AODV) Routing", Proceedings of the 2nd
IEEE Workshop on Mobile Computing Systems and IEEE Workshop on Mobile Computing Systems and
Applications, New Orleans, LA, pp. 90-100, February 1999. Applications, New Orleans, LA, pp. 90-100, February 1999.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
RFC 2740, December 1999.
[RFC3561] Perkins, C., Belding-Royer, E., and S. Das, "Ad hoc On- [RFC3561] Perkins, C., Belding-Royer, E., and S. Das, "Ad hoc On-
Demand Distance Vector (AODV) Routing", RFC 3561, Demand Distance Vector (AODV) Routing", RFC 3561,
July 2003. July 2003.
[RFC4728] Johnson, D., Hu, Y., and D. Maltz, "The Dynamic Source [RFC4728] Johnson, D., Hu, Y., and D. Maltz, "The Dynamic Source
Routing Protocol (DSR) for Mobile Ad Hoc Networks for Routing Protocol (DSR) for Mobile Ad Hoc Networks for
IPv4", RFC 4728, February 2007. IPv4", RFC 4728, February 2007.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
skipping to change at page 37, line 15 skipping to change at page 38, line 4
Authors' Addresses Authors' Addresses
Ian D Chakeres Ian D Chakeres
CenGen CenGen
9250 Bendix Road North 9250 Bendix Road North
Columbia, Maryland 21045 Columbia, Maryland 21045
USA USA
Email: ian.chakeres@gmail.com Email: ian.chakeres@gmail.com
URI: http://www.ianchak.com/ URI: http://www.ianchak.com/
Charles E. Perkins Charles E. Perkins
WiChorus Inc. WiChorus Inc.
3590 North First Street, Suite 300 3590 North First Street, Suite 300
San Jose, CA 95134 San Jose, CA 95134
USA USA
Phone: +1-408-421-1172 Phone: +1-408-421-1172
Email: charliep@computer.org Email: charliep@computer.org
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 27 change blocks. 
41 lines changed or deleted 117 lines changed or added

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