< draft-ietf-autoconf-manetarch-06.txt   draft-ietf-autoconf-manetarch-07.txt >
MANET Autoconfiguration (AUTOCONF) I. Chakeres MANET Autoconfiguration (AUTOCONF) I. Chakeres
Internet-Draft Motorola Internet-Draft Motorola
Intended status: Informational J. Macker Intended status: Informational J. Macker
Expires: April 5, 2008 Naval Research Laboratory Expires: May 11, 2008 Naval Research Laboratory
T. Clausen T. Clausen
LIX, Ecole Polytechnique LIX, Ecole Polytechnique
October 3, 2007 November 8, 2007
Mobile Ad hoc Network Architecture Mobile Ad hoc Network Architecture
draft-ietf-autoconf-manetarch-06 draft-ietf-autoconf-manetarch-07
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes 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. 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
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 April 5, 2008. This Internet-Draft will expire on May 11, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document discusses Mobile Ad hoc NETworks (MANETs). It presents This document discusses Mobile Ad hoc NETworks (MANETs). It presents
the initial motivation for MANET and describes unaccustomed the initial motivation for MANET and describes unaccustomed
characteristics and challenges. It also defines a MANET, other MANET characteristics and challenges. It also defines a MANET, other MANET
skipping to change at page 3, line 29 skipping to change at page 3, line 29
This document is meant to complement [RFC2501] in describing and This document is meant to complement [RFC2501] in describing and
defining MANET. defining MANET.
2. Terminology 2. Terminology
Owing to the fact that a MANET, as described in this document, is an Owing to the fact that a MANET, as described in this document, is an
instance of an IP network, much of the terminology employed in this instance of an IP network, much of the terminology employed in this
document is borrowed from existing documents. Some of the documents document is borrowed from existing documents. Some of the documents
that contain relevant terminology are [RFC1812], [RFC2328], that contain relevant terminology are [RFC1812], [RFC2328],
[RFC2453], [RFC2460], [RFC2461], [RFC4291], [RFC3753], and [RFC4903]. [RFC2453], [RFC2460], [RFC4861], [RFC4291], [RFC3753], and [RFC4903].
In some cases the terminology is slightly abbreviated or rephrased; In some cases the terminology is slightly abbreviated or rephrased;
although, every effort made to retain the meanings. Borrowed although, every effort made to retain the meanings. Borrowed
terminology is provided in Section 2.1 with the intent of providing a terminology is provided in Section 2.1 with the intent of providing a
complete discussion of MANETs using coherent terminology. MANET complete discussion of MANETs using coherent terminology. MANET
specific terminology is provided in Section 2.2. specific terminology is provided in Section 2.2.
2.1. Borrowed Terminology 2.1. Borrowed Terminology
This document employs the following definitions: This document employs the following definitions:
skipping to change at page 8, line 20 skipping to change at page 8, line 20
and development. and development.
4.1. Qualities - Wireless, Mobile, Ad hoc 4.1. Qualities - Wireless, Mobile, Ad hoc
In MANETs several qualities impact protocol design. The most In MANETs several qualities impact protocol design. The most
fundamental qualities are wireless interface characteristics, fundamental qualities are wireless interface characteristics,
mobility, and ad hoc interaction. mobility, and ad hoc interaction.
Wireless interfaces often exhibit more challenging characteristics Wireless interfaces often exhibit more challenging characteristics
when compared to wired interfaces. Many protocols (e.g., IPv6 when compared to wired interfaces. Many protocols (e.g., IPv6
neighbor discovery [RFC2461]) were not designed to operate in neighbor discovery [RFC4861]) were not designed to operate in
wireless networks with asymmetric reachability. Wireless interfaces wireless networks with asymmetric reachability. Wireless interfaces
may also exhibit very dynamic time varying performance (e.g., packet may also exhibit very dynamic time varying performance (e.g., packet
loss, data rate), and the factors have a significant impact on local loss, data rate), and the factors have a significant impact on local
communication. communication.
Mobility can also exacerbate communication issues, making it more Mobility can also exacerbate communication issues, making it more
challenging to attain, establish, and maintain network relationships challenging to attain, establish, and maintain network relationships
between nodes. between nodes.
Ad hoc networking further compounds problems by allowing nodes to Ad hoc networking further compounds problems by allowing nodes to
skipping to change at page 9, line 48 skipping to change at page 9, line 48
Defining the process of determining neighboring MANET routers' Defining the process of determining neighboring MANET routers'
existence, continued existence, and loss of existence is a existence, continued existence, and loss of existence is a
fundamental challenge in MANETs. Relationships with neighboring fundamental challenge in MANETs. Relationships with neighboring
MANET routers are hard to define due to the MANET interface MANET routers are hard to define due to the MANET interface
characteristics. characteristics.
Historically, two nodes are either neighbors or not neighbors and Historically, two nodes are either neighbors or not neighbors and
several simple mechanisms have been used to determine neighbor several simple mechanisms have been used to determine neighbor
relationships: single packet reception, acceptable loss rates, and relationships: single packet reception, acceptable loss rates, and
simple handshakes. [RFC2461], for example, employs an initial simple handshakes. [RFC4861], for example, employs an initial
exchange of messages to determine neighborship or absence thereof. exchange of messages to determine neighborship or absence thereof.
In networks with MANET interface the types of neighbor relationships In networks with MANET interface the types of neighbor relationships
expand, as do the mechanisms to detect and maintain the state of such expand, as do the mechanisms to detect and maintain the state of such
relationships. relationships.
Wireless network interfaces may exhibit unidirectional communication. Wireless network interfaces may exhibit unidirectional communication.
Dynamic wireless networks may also experience significant time Dynamic wireless networks may also experience significant time
varying packet delivery between the same pair of wireless network varying packet delivery between the same pair of wireless network
interfaces, so simple loss rates may not be sufficient to define a interfaces, so simple loss rates may not be sufficient to define a
neighbor relationship. Similarly, as nodes (and, hence, interfaces) neighbor relationship. Similarly, as nodes (and, hence, interfaces)
skipping to change at page 12, line 23 skipping to change at page 12, line 23
This configuration implies that, from the point of view of these This configuration implies that, from the point of view of these
nodes and the applications running on them, they are not exposed to nodes and the applications running on them, they are not exposed to
the specific characteristics of MANET interfaces. the specific characteristics of MANET interfaces.
A MANET router can be delegated zero or more prefixes. For example, A MANET router can be delegated zero or more prefixes. For example,
if a MANET router is delegated a prefix p::, then subnet prefixes if a MANET router is delegated a prefix p::, then subnet prefixes
derived from this prefix (e.g, p:1::/64, p:2::/64, ...) may be derived from this prefix (e.g, p:1::/64, p:2::/64, ...) may be
assigned to the MANET routers' non-MANET interfaces(s), and nodes on assigned to the MANET routers' non-MANET interfaces(s), and nodes on
these interfaces may be assigned addresses from within this prefix, these interfaces may be assigned addresses from within this prefix,
and configured with this prefix according to the address and configured with this prefix according to the address
autoconfiguration mechanisms governing these interfaces ([RFC2461] autoconfiguration mechanisms governing these interfaces ([RFC4861]
and [RFC2462]). This concept is illustrated in Figure 6. and [RFC4862]). This concept is illustrated in Figure 6.
MANET interfaces are specifically *NOT* configured with this prefix. MANET interfaces are specifically *NOT* configured with this prefix.
The configuration of these MANET interfaces is detailed in The configuration of these MANET interfaces is detailed in
Section 5.2. Section 5.2.
MANET <~~~~~~+~~~~~~> MANET <~~~~~~+~~~~~~>
Interface | Delegated Interface | Delegated
| Prefix | Prefix
''''''''''''''''''''' ========== ''''''''''''''''''''' ==========
' MANET ' <=== P::/62 = ' MANET ' <=== P::/62 =
' Router ' ========== ' Router ' ==========
''''''''' : ' Assigned ''''''''' : ' Assigned
: ' : ' Prefix : ' : ' Prefix
: ' +--------+' ============ : '++--------+' ============
============ : ' |Loopback|' <=== P:1::/64 = : '|Loopback |' <=== P:1::/64 =
= : = : ' +--------+' ============ ============ : '|P:1::L/64|' ============
= : = : '+---------+'
= Other = : ''''''''''''' Assigned = Other = : ''''''''''''' Assigned
=Interfaces= : Prefix =Interfaces= : Prefix
============ : ============ ============ : ============
+......+......+ <=== P:2::/64 = +...+...........+ <=== P:2::/64 =
: : ============ : : ============
+-+-+ +-+-+ +------+--+ +--+------+
| N | * * * | N | |P:2::1/64| * * * |P:2::K/64|
+---+ +---+ +---------+ +---------+
P:2::1 P:2::K
Figure 6: MANET Router and Prefixes Example Figure 6: MANET Router and Prefixes Example
5.2. MANET Interface Configuration 5.2. MANET Interface Configuration
MANET interface specific behaviors are exclusively exposed to the MANET interface specific behaviors are exclusively exposed to the
MANET routers. These behaviors may include asymmetric reachability, MANET routers. These behaviors may include asymmetric reachability,
semi-broadcast interfaces, fuzzy MANET router neighbor relationships, semi-broadcast interfaces, fuzzy MANET router neighbor relationships,
changing MANET membership, rapid topology dynamics, etc. changing MANET membership, rapid topology dynamics, etc.
The following characteristics deserve particular mention, since they The following characteristics deserve particular mention, since they
skipping to change at page 17, line 45 skipping to change at page 17, line 45
Discussions and developments concepts and architectural issues have Discussions and developments concepts and architectural issues have
evolved over many years of discussion of related work within the evolved over many years of discussion of related work within the
MANET WG. There are obviously many people that have contributed to MANET WG. There are obviously many people that have contributed to
past discussions and related draft documents within the WG that have past discussions and related draft documents within the WG that have
influenced the development of these concepts that deserve influenced the development of these concepts that deserve
acknowledgment. The authors would like to thank all contributors to acknowledgment. The authors would like to thank all contributors to
the MANET and AUTOCONF WG efforts and those that have helped in the the MANET and AUTOCONF WG efforts and those that have helped in the
review and content process. review and content process.
While not entirely complete the authors would like to in particular While not entirely complete the authors would like to in particular
thank the following individuals for exhaustive discussions and thank the following individuals for extensive discussions and
valuable contributions: valuable contributions:
Jari Arkko Jari Arkko
Emmanuel Baccelli Emmanuel Baccelli
Alan Cullen Alan Cullen
Justin Dean Justin Dean
Christopher Dearlove Christopher Dearlove
skipping to change at page 18, line 49 skipping to change at page 18, line 49
RFC 1812, June 1995. RFC 1812, June 1995.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453, [RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453,
November 1998. November 1998.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor
Discovery for IP Version 6 (IPv6)", RFC 2461,
December 1998.
[RFC2462] Thomson, S. and T. Narten, "IPv6 Stateless Address
Autoconfiguration", RFC 2462, December 1998.
[RFC2501] Corson, M. and J. Macker, "Mobile Ad hoc Networking [RFC2501] Corson, M. and J. Macker, "Mobile Ad hoc Networking
(MANET): Routing Protocol Performance Issues and (MANET): Routing Protocol Performance Issues and
Evaluation Considerations", RFC 2501, January 1999. Evaluation Considerations", RFC 2501, January 1999.
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", [RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004. RFC 3753, June 2004.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007.
[RFC4903] Thaler, D., "Multi-Link Subnet Issues", RFC 4903, [RFC4903] Thaler, D., "Multi-Link Subnet Issues", RFC 4903,
June 2007. June 2007.
Authors' Addresses Authors' Addresses
Ian D Chakeres Ian D Chakeres
Motorola Motorola
Bagmane Tech Park Bagmane Tech Park
66/1, Plot 5, CV Raman Nagar 66/1, Plot 5, CV Raman Nagar
Bangalore, Karnataka 560093 Bangalore, Karnataka 560093
 End of changes. 13 change blocks. 
27 lines changed or deleted 26 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/