draft-ietf-dhc-mipadvert-opt-00.txt   draft-ietf-dhc-mipadvert-opt-01.txt 
Internet Engineering Task Force H. Levkowetz DHC Working Group H. Levkowetz
Internet-Draft ipUnplugged Internet-Draft ipUnplugged
Expires: April 24, 2003 October 24, 2002 Expires: March 31, 2004 Oct 2003
DHCP Option for Mobile IP Mobility Agents DHCP Option for Mobile IP Mobility Agents
<draft-ietf-dhc-mipadvert-opt-00.txt> draft-ietf-dhc-mipadvert-opt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- 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://
http://www.ietf.org/ietf/1id-abstracts.txt. 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 24, 2003. This Internet-Draft will expire on March 31, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document defines a new Dynamic Host Configuration Protocol This document defines a new Dynamic Host Configuration Protocol
(DHCP) option with suboptions. One suboption is passed from the DHCP (DHCP) option with suboptions. One suboption is passed from the DHCP
Server to the DHCP Client to announce the presence of one or more Server to the DHCP Client to announce the presence of one or more
Mobile IP Mobility Agents. For each announced Mobility Agent, Mobile IP Mobility Agents. For each announced Mobility Agent,
information is provided which is the same as that of the Mobile IP information is provided which is the same as that of the Mobile IP
Agent Advertisement extension to ICMP Router Advertisements. There Agent Advertisement extension to ICMP Router Advertisements. There is
is also one suboption which may be used by a DHCP client to provide also one suboption which may be used by a DHCP client to provide
identity information to the DHCP server. identity information to the DHCP server.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements terminology . . . . . . . . . . . . . . . . . . . 3 2. Requirements terminology . . . . . . . . . . . . . . . . . . . 3
3. Mobility Agent Information Option . . . . . . . . . . . . . . 3 3. Mobility Agent Information Option . . . . . . . . . . . . . . 3
3.1 Mobility Agent Information Option Definition . . . . . . . . . 3 3.1 Mobility Agent Information Option Definition . . . . . . 3
3.2 Network Access Identifier Sub-Option . . . . . . . . . . . . . 4 3.2 Network Access Identifier Sub-Option . . . . . . . . . . 4
3.3 Mobility Agent Announcement Sub-Option . . . . . . . . . . . . 4 3.3 Mobility Agent Announcement Sub-Option . . . . . . . . . 4
4. Mobility Agent Option Usage . . . . . . . . . . . . . . . . . 7 4. Mobility Agent Option Usage . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
Normative References . . . . . . . . . . . . . . . . . . . . . 7 Normative References . . . . . . . . . . . . . . . . . . . . . 7
Informative References . . . . . . . . . . . . . . . . . . . . 8 Informative References . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . 9
1. Introduction 1. Introduction
There already exists a DHCP option to announce Mobile IP Home Agent There already exists a DHCP option to announce Mobile IP Home Agent
addresses, described in RFC 2132 [2]. There is, however, no option addresses, described in RFC 2132 [2]. There is, however, no option
available to announce Mobile IP Foreign Agents. available to announce Mobile IP Foreign Agents.
Announcement of available Mobile IP Mobility Agents by means of DHCP Announcement of available Mobile IP Mobility Agents by means of DHCP
provides possibilities for selective and individual assignment of provides possibilities for selective and individual assignment of
Mobility Agents to Mobile Nodes. This in turn makes load-sharing and Mobility Agents to Mobile Nodes. This in turn makes load-sharing and
skipping to change at page 3, line 31 skipping to change at page 3, line 31
document are to be interpreted as described in RFC 2119 [8]. document are to be interpreted as described in RFC 2119 [8].
The Mobile IP related terminology used in this document is described The Mobile IP related terminology used in this document is described
in RFC 3220 [5]. in RFC 3220 [5].
3. Mobility Agent Information Option 3. Mobility Agent Information Option
3.1 Mobility Agent Information Option Definition 3.1 Mobility Agent Information Option Definition
This document defines a new DHCP Option called the Mobility Agent This document defines a new DHCP Option called the Mobility Agent
Option. It is a "container" option for specific agent- supplied sub- Option. It is a "container" option for specific agent- supplied
options. The format of the Mobility Agent option is: sub-options. The format of the Mobility Agent option is:
Code Len Mobility Agent Information Field Code Len Mobility Agent Information Field
+-------+------+------+------+------+------+--...-+------+ +-------+------+------+------+------+------+--...-+------+
| TBD | N | a1 | a2 | a3 | a4 | | aN | | TBD | N | a1 | a2 | a3 | a4 | | aN |
+-------+------+------+------+------+------+--...-+------+ +-------+------+------+------+------+------+--...-+------+
The length N gives the total number of octets in the Mobility Agent The length N gives the total number of octets in the Mobility Agent
Field. The Mobility Agent Information field consists of a sequence Field. The Mobility Agent Information field consists of a sequence
of SubOpt/Length/Value tuples for each sub-option, encoded in the of SubOpt/Length/Value tuples for each sub-option, encoded in the
following manner: following manner:
skipping to change at page 5, line 38 skipping to change at page 5, line 38
| Registration Lifetime |R|B|H|F|M|G|r|T| reserved | | Registration Lifetime |R|B|H|F|M|G|r|T| reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| zero or more care-of addresses | | zero or more care-of addresses |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option code Option code
DHCP_MIP_OPTION (to be assigned by IANA) DHCP_MIP_OPTION (to be assigned by IANA)
Length Length
Length in bytes of this option, not including the Option code Length in bytes of this option, not including the Option code and
and Length bytes. Length bytes.
Agent IP Address Agent IP Address
The address trough which the Mobile Node may reach the The address trough which the Mobile Node may reach the announced
announced Mobility Agent in order to do a Mobile IP Mobility Agent in order to do a Mobile IP registration.
registration.
Type Type
16. This is the same value as for the type field in a Mobility 16. This is the same value as for the type field in a Mobility
Agent Advertisement Extension as described in RFC 3220 [5]. If Agent Advertisement Extension as described in RFC 3220 [5]. If
other Mobility Agent Advertisement Extensions are defined in other Mobility Agent Advertisement Extensions are defined in the
the future, this field will make it possible to differentiate future, this field will make it possible to differentiate between
between them without using new DHCP option numbers. them without using new DHCP option numbers.
Reserved-0 Reserved-0
Sent as zero; required to be zero on reception for the option Sent as zero; required to be zero on reception for the option
described in this document. described in this document.
Adv-Length Adv-Length
(6 + 4*N), where 6 accounts for the number of bytes in the (6 + 4*N), where 6 accounts for the number of bytes in the
Sequence Number, Registration Lifetime, flags, and reserved Sequence Number, Registration Lifetime, flags, and reserved
fields, and N is the number of care-of addresses advertised for fields, and N is the number of care-of addresses advertised for
the Mobility Agent. the Mobility Agent.
Sequence Number Sequence Number
The count of Mobility Agent DHCP announcements made since the The count of Mobility Agent DHCP announcements made since the DHCP
DHCP server was initialized (RFC 3220, Section 2.3.2 [5]). server was initialized (RFC 3220, Section 2.3.2 [5]).
Registration Lifetime Registration Lifetime
The longest lifetime (measured in seconds) that this agent is The longest lifetime (measured in seconds) that this agent is
willing to accept in any Registration Request. A value of willing to accept in any Registration Request. A value of 0xffff
0xffff indicates infinity. indicates infinity.
R R
Registration required. Registration with this foreign agent Registration required. Registration with this foreign agent (or
(or another foreign agent listed in this DHCP option) is another foreign agent listed in this DHCP option) is required even
required even when using a co-located care-of address. when using a co-located care-of address.
B B
Busy. The foreign agent will not accept registrations from Busy. The foreign agent will not accept registrations from
additional mobile nodes. additional mobile nodes.
H H
Home agent. This agent offers service as a home agent on the Home agent. This agent offers service as a home agent on the link
link on which this mobility agent announcement is sent. on which this mobility agent announcement is sent.
F F
Foreign agent. This agent offers service as a foreign agent on Foreign agent. This agent offers service as a foreign agent on
the link on which this mobility agent announcement is sent. the link on which this mobility agent announcement is sent.
M M
Minimal encapsulation. This agent implements receiving Minimal encapsulation. This agent implements receiving tunneled
tunneled datagrams that use minimal encapsulation [7]. datagrams that use minimal encapsulation [7].
G G
GRE encapsulation. This agent implements receiving tunneled GRE encapsulation. This agent implements receiving tunneled
datagrams that use GRE encapsulation [6]. datagrams that use GRE encapsulation [6].
r r
Sent as zero; ignored on reception. SHOULD NOT be allocated Sent as zero; ignored on reception. SHOULD NOT be allocated for
for any other uses. any other uses.
T T
Foreign agent supports reverse tunneling [11]. Foreign agent supports reverse tunneling [11].
reserved reserved
Sent as zero; ignored on reception. Sent as zero; ignored on reception.
Care-of Address(es) Care-of Address(es)
The foreign agent care-of address(es) provided by this foreign The foreign agent care-of address(es) provided by this foreign
agent. An DHCP Mobility Agent Announcement MUST include at agent. An DHCP Mobility Agent Announcement MUST include at least
least one care-of address if the 'F' bit is set. The number of one care-of address if the 'F' bit is set. The number of care-of
care-of addresses present is determined by the Length field in addresses present is determined by the Length field in the
the Extension. Extension.
4. Mobility Agent Option Usage 4. Mobility Agent Option Usage
The requesting and sending of this option follows the rules for DHCP The requesting and sending of this option follows the rules for DHCP
options in RFC 2131 [1] options in RFC 2131 [1]
5. Security Considerations 5. Security Considerations
DHCP provides an authentication mechanism, as described in RFC 3118 DHCP provides an authentication mechanism, as described in RFC 3118
[4], which may be used if authentication is required before offering [4], which may be used if authentication is required before offering
skipping to change at page 9, line 5 skipping to change at page 9, line 5
Henrik Levkowetz Henrik Levkowetz
ipUnplugged AB ipUnplugged AB
Arenavagen 33 Arenavagen 33
Stockholm S-121 28 Stockholm S-121 28
SWEDEN SWEDEN
Phone: +46 8 725 9513 Phone: +46 8 725 9513
EMail: henrik@levkowetz.com EMail: henrik@levkowetz.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property 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; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/