AUTOCONF Working Group Sanghyun Ahn
Internet Draft University of Seoul
Expires: January 4, 2011 Yujin Lim
University of Suwon
July 3, 2010
MANET Address Configurtion using Address Pool
draft-ahn-autoconf-addresspool-01.txt
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, except to format it
for publication as an RFC or to translate it into languages other
than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 4, 2011.
Copyright Notice
Copyright (c) 2010 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 (http://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Ahn, et al. Expires January 4, 2011 [Page 1]
Internet-Draft MANET Address Configuration using Address Pool July 2010
Abstract
This document describes an address configuration mechanism based on
the concept of address pool allocation in the connected MANET.
The Internet gateway acts as a DHCP (Dynamic Host Configuration
Protocol) server and assigns not a single address but a part of its
address pool to an address requesting node and, then, the node can
assign a part of its own address pool to its neighbor nodes.
By doing this, the address allocation procedure can be expedited.
Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Address Pool based MANET Address Configuration . . . . . . . . 3
5. Message Format . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1 Address Pool Release Request (APRR) message . . . . . . . 4
5.2 Address Pool Release Reply (APRP) message . . . . . . . . 4
5.3 DHCP Options . . . . . . . . . . . . . . . . . . . . . . 5
6. Other Considerations . . . . . . . . . . . . . . . . . . . . . 5
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Ahn, et al. Expires January 4, 2011 [Page 2]
Internet-Draft MANET Address Configuration using Address Pool July 2010
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Introduction
The MANET can be classified into the standalone MANET and the
connected MANET [1]. The conntected MANET allows a MANET node to
communicate with global Internet nodes via the Internet gateway
(IGW). In order for a MANET node to communicate with a node in the
external global Internet, the MANET node has to obtain a globally
unique IP address. In the wireless multi-hop communication
environment, the mechanism using the IGW as the centralized DHCP
(Dynamic Host Configuration Protocol) [2] server is not desirable
since it may incur long address allocation delay.
In this draft, we describe an address configuration mechanism that
allows stable and fast global IP address allocation based on the DHCP
mechanism in the connected MANET. In the proposed scheme, the IGW
acts as a DHCP server and allocates a part of its address pool to
an address requesting node. Now, the node with the allocated address
pool can act a DHCP server and allocate a part of its address pool
to the other address requesting nodes.
3. Terminology
Address Pool A range of addresses starting from LOW to HIGH.
4. Address Pool based MANET Address Configuration
The IGW periodically broadcasts Router Advertisement (RA) messages to
the entire MANET and the MANET node receiving the RA message can
request for addresses to the IGW by unicasting a DHCP_Request [2]
message. Any intermediate node receiving the DHCP_Request message
intercepts the message and allocates a part of its address pool in
lieu of the IGW if its address pool is big enough to allocate by
unicasting a DHCP_Reply message to the address requesting node.
Otherwise, it forwards the DHCP_Request message to the IGW. Once the
IGW receives the DHCP_Request message, the IGW allocates a part of
its address pool to the addres requesting node by sending a
DHCP_Reply message.
The node with the allocated address pool assigns one address to its
interface and keeps the rest of its address pool for later
Ahn, et al. Expires January 4, 2011 [Page 3]
Internet-Draft MANET Address Configuration using Address Pool July 2010
allocation to other MANET nodes requesting addresses.
In order to avoid the renewal of the allocated address pool, the
valid-lifetime field in the DHCP_Reply message is set to
'0xffffffff' (that is, infinite use of the address pool). If the size
of the address pool of the IGW reaches below a pre-specified
threshold, the IGW broadcasts an Address Pool Release Request (APRR)
message to the entire MANET. The MANET node receiving the APRR
message sends an Address Pool Release Reply (APRP) message to let
the IGW know those addresses already being used or assigned by the
APRP message sent node.
5. Message Format
5.1 Address Pool Release Request (APRR) message
This message is broadcast by the IGW to the entire MANET in order to
request for the list of addresses used by MANET nodes.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OPTION_ADDPOOL_RELEASE_REQUEST(24)| option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| APRR-options |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5.2 Address Pool Release Reply (APRP) message
This message is unicast by a MANET node to the IGW in order to give
the list of addresses used by the MANET node.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OPTION_ADDPOOL_RELEASE_REPLY(24)| option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| used address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| APRP-options |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Ahn, et al. Expires January 4, 2011 [Page 4]
Internet-Draft MANET Address Configuration using Address Pool July 2010
5.3 DHCP options
The OPTION_ADDRSS_POOL_REQUEST option is defined to allow a MANET
node to request for an address pool to the DHCP server. This option
is included in the DHCP_Request message [2] as shown in the
following figure.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_ORD(6) | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|OPTION_ADDRESS_POOL_REQUEST(21)| requested-option-code-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The OPTION_IAADDPOOL option is defined to allow the DHCP server to
to allocate an address pool to the address pool request MANET node.
This option is included in the DHCP_Reply message [2] as shown in
the following figure.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_IAADDPOOL(22) | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| lowest IPv6 address(LOW) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| highest IPv6 address(HIGH) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| preferred-lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| valid-lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IA_ADDPOOL-options |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6. Other Considerations
TBD.
Ahn, et al. Expires January 4, 2011 [Page 5]
Internet-Draft MANET Address Configuration using Address Pool July 2010
References
[1] E. Baccelli, "Address Autoconfiguration for MANET: Terminology
and Problem Statement," draft-ietf-autoconf-statement-04.txt,
Feb. 2008.
[2] R. Droms, J. Bound, B. Volz, T. Lemon, C. Perkins and M. Carnery,
"Dynamic Host Configuration Protocol for IPv6(DHCPv6)," RFC 3315,
July 2003.
Authors' Addresses
Sanghyun Ahn
University of Seoul
90, Cheonnong-dong, Tongdaemun-gu
Seoul 130-743
Korea
Email: ahn@uos.ac.kr
Yujin Lim
University of Suwon
San 2-2, Wau-ri, Bongdam-eup
Hwaseong-si, Gyeonggi-do, 445-743
Korea
Email: yujin@suwon.ac.kr
Ahn, et al. Expires January 4, 2011 [Page 6]