draft-ietf-dhc-dhcpv6-ctep-opt-01.txt   draft-ietf-dhc-dhcpv6-ctep-opt-02.txt 
Network Working Group S. Daniel Park Network Working Group S. Daniel Park
Internet-Draft Samsung Electronics Internet-Draft SAMSUNG Electronics
Expires : 26 September 2004 A.K. Vijayabhaskar Expires: April 22, 2006 A. Vijayabhaskar
Hewlett-Packard HP
27 March 2004 October 22, 2005
Configured Tunnel End Point Option for DHCPv6 Configured Tunnel End Point Option for DHCPv6
draft-ietf-dhc-dhcpv6-ctep-opt-01.txt draft-ietf-dhc-dhcpv6-ctep-opt-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, each author represents that any
all provisions of Section 10 of RFC2026. 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
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
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
at any time. It is inappropriate to use Internet-Drafts as time. It is inappropriate to use Internet-Drafts as reference
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 22, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
For the newly deployed IPv6 networks to interoperate with vastly For the newly deployed IPv6 networks to interoperate with vastly
deployed IPv4 networks, various transition mechanisms had been deployed IPv4 networks, various transition mechanisms had been
proposed. One such mechanism is configured tunnels. This document proposed. One such mechanism is configured tunnels. This document
provides a mechanism by which the DHCPv6 servers can provide provides a tunnel discovery mechanism by which the DHCPv6 servers can
information about the various configured tunnel end points to reach provide information about the available configured tunnel end points
the IPv6 nodes which are separated by IPv4 networks. to reach the IPv6 nodes which are separated by IPv4 networks.
1. Introduction 1. Introduction
In the initial deployment of IPv6, the IPv6 nodes may need to In the initial deployment of IPv6, the IPv6 nodes may need to
communicate with the other IPv6 nodes via IPv4 networks. Configured communicate with the other IPv6 nodes via IPv4 networks. Configured
tunnels [3] provide a way to encapsulate the IPv6 packets in IPv4 tunnels [RFC4213] provide a way to encapsulate the IPv6 packets in
packets and tunnel them in the IPv4 network. IPv4 packets and tunnel them in the IPv4 network.
This document defines a new option called Configured Tunnel End This document defines a new option called Configured Tunnel End Point
Point by which the DHCPv6 [1] server can notify the client with the by which the DHCPv6 [RFC3315] server can notify the client with the
list of end point of the configured tunnels to the various IPv6 list of end point of the configured tunnels to the various IPv6
networks separated by the IPv4 networks. networks separated by the IPv4 networks.
2. Background 2. Background
Configured Tunnel described in this document is a simple and Configured Tunnel described in this document is a simple and
temporary mechanism which allows isolated IPv6 networks or hosts, temporary mechanism which allows isolated IPv6 networks or hosts,
attached to a legacy IPv4 network which has no native IPv6 attached to a legacy IPv4 network which has no native IPv6
connectivity, to communicate with other such IPv6 networks or hosts connectivity, to communicate with other such IPv6 networks or hosts
with manual configuration. The configured tunnel end-point received with manual configuration. The configured tunnel end-point received
from the DHCPv6 server is not used for IPv6 connectivity as long as from the DHCPv6 server is not used for IPv6 connectivity as long as
IPv6 networks or hosts are communicating with other IPv6 networks or IPv6 networks or hosts are communicating with other IPv6 networks or
hosts via IPv6 network which has native IPv6 connectivity and only hosts via IPv6 network which has native IPv6 connectivity and only
available when communicating with other IPv6 networks or hosts via available when communicating with other IPv6 networks or hosts via
IPv4 networks. IPv4 networks.
In this scenario, 6to4 [4] can be a possible alternative instead of In this scenario, 6to4 [RFC3056] can be a possible alternative
configured tunnel and does not require IPv4-compatible IPv6 instead of configured tunnel.
addresses or configured tunnels.
As indicated in [4], the mechanisms are intended as a start-up As indicated in [RFC3056], the mechanisms are intended as a start-up
transition tool used during the period of co-existence of IPv4 and transition tool used during the period of co-existence of IPv4 and
IPv6. It is not intended as a permanent solution. IPv6. It is not intended as a permanent solution.
3. Requirements 3. Requirements
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document, are to be interpreted as described in RFC 2119 [2] document are to be interpreted as described in [RFC2119].
4. Terminology 4. Terminology
This document uses terminology specific to IPv6 and DHCPv6 as This document uses terminology specific to IPv6 and DHCPv6 as defined
defined in "Terminology" section of the DHCPv6 specification [1]. in "Terminology" section of the DHCPv6 specification [RFC3315].
5. Configured Tunnel End Point Option 5. Configured Tunnel End Point Option
The Configured Tunnel End Point Option gives the information to the The Configured Tunnel End Point Option gives the information to the
clients about the Configured Tunnel End Point [3] to be contacted clients about the Configured Tunnel End Point [RFC4213] to be
for reaching the nodes in the various IPv6 networks which are contacted for reaching the nodes in the various IPv6 networks which
separated by IPv4 networks. The clients are expected to install are separated by IPv4 networks. The clients are expected to install
these routes in their machines. these routes in their machines.
The format of the Configured Tunnel End Point Option is as shown The format of the Configured Tunnel End Point Option is as shown
below: below:
0 1 2 3 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 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_CTEP | option-len | | OPTION_CTEP | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| prefix-len | | | prefix-len | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| | | |
| Destination Prefix (16 bytes) |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+ |
| Configured TEP Address (16 bytes) | | Configured TEP Address (16 bytes) |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | prefix-len | | | |... (if multiple tunnels are in use)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Destination Prefix (16 bytes) |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Configured TEP Address (16 bytes) |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_CTEP (TBD)
option-len: Total length of the prefix-len, Destination Prefix and option-code: OPTION_CTEP (TBD)
Configured Tunnel Address lists in octets; It should be
a multiple of 33.
prefix-len: prefix length of the Destination Prefix option-len: Total length of the prefix-len, Configured Tunnel Address
lists in octets; It should be a multiple of 17.
Destination Prefix: An IPv6 Prefix; prefix-len: prefix length of this Configured TEP Address in bits.
Configured TEP Address: IPv6 Address of the Configured TEP. This Configured TEP Address: IPv6 Address of the Configured TEP.
address is a IPv4-compatible IPv6 address.
The clients are expected to install the routes identified by the The clients are expected to install the routes identified by the
tuples <Destination Prefix/prefix-len, Configured TEP Address> once tuples (prefix-len, Configured TEP Address) once they receive this
they receive this option from the server. option from the server.
6. Appearance of this option 6. Appearance of this option
The Configured Tunnel End Point Option MUST NOT appear in other The Configured Tunnel End Point Option MUST NOT appear in other than
than the following messages: Solicit, Advertise, Request, Renew, the following messages: Solicit, Advertise, Request, Renew, Rebind,
Rebind, Information-Request and Reply. Information-Request and Reply.
The option numbers of Configured Tunnel End Point option MAY appear The option numbers of Configured Tunnel End Point option MAY appear
in the Option Request Option [1] in the following messages: Solicit, in the Option Request Option [RFC3315] in the following messages:
Request, Renew, Rebind, Information-Request and Reconfigure. Solicit, Request, Renew, Rebind, Information-Request and Reconfigure.
7. Security Considerations 7. multiple Tunnel End Point Considerations
For the simple tunnel discovery, one tunnel endpoint is generally
used and it assumes that all the networks will be reached through the
same endpoint. In this case, one Configured TEP field in the TEP
option is used for configured tunnel service.
The list of endpoints can be installed if the IPv6 host load-sharing
is honored, but there may not be a need for installing multiple
configured tunnel endpoints unless administrator wants two for
redundancy purposes. It is beyond scope of this document.
8. Security Considerations
The Configured Tunnel End Point Option may be used by an intruder The Configured Tunnel End Point Option may be used by an intruder
DHCPv6 server to provide invalid or incorrect configured tunnel end DHCPv6 server to provide invalid or incorrect configured tunnel end
point. This makes the client unable to reach its destination IPv6 point. This makes the client unable to reach its destination IPv6
node or to reach incorrect destination. The latter one has very node or to reach incorrect destination. The latter one has very
severe security issues as IPv6 destination is spoofed here. severe security issues as IPv6 destination is spoofed here.
To avoid attacks through this option, the DHCPv6 client SHOULD use To avoid attacks through this option, the DHCPv6 client SHOULD use
authenticated DHCP (see section "Authentication of DHCP messages" in authenticated DHCP (see section "Authentication of DHCP messages" in
the DHCPv6 specification [1]). the DHCPv6 specification [RFC3315]).
8. IANA Considerations 9. IANA Considerations
IANA is requested to assign an option code to the following options IANA is requested to assign an option code to the following options
from the option-code space defined in "DHCPv6 Options" section of from the option-code space defined in "DHCPv6 Options" section of the
the DHCPv6 specification [1]. DHCPv6 specification [RFC3315].
Option Name Value Described in Option Name Value Described in
OPTION_CTEP TBD Section 4
9. References OPTION_CTEP TBD Section 4
9.1 Normative References 10. References
[1] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and 10.1 Normative References
R.Droms (ed.), "Dynamic Host Configuration Protocol for IPv6
(DHCPv6)", RFC 3315, July 2003.
[2] 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.
9.2 Informative References [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C. and
M. Carney, "Dynamic Host Configuration Protocol for IPv6
(DHCPv6)", RFC 3315, July 2003.
[3] Gilligan, R, Nordmark, E., "Transition Mechanisms for IPv6 10.2 Informative References
Hosts and Routers", RFC 2893, August 2000.
[4] Carpenter, B., Moore K., "Connection of IPv6 Domains via IPv4 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains
Clouds", RFC 3056, February 2001. via IPv4 Clouds", RFC 3056, February 2001.
[RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms
for IPv6 Hosts and Routers", RFC 4213, October 2005.
Authors' Addresses Authors' Addresses
Soohong Daniel Park Soohong Daniel Park
Mobile Platform Laboratory SAMSUNG Electronics
Samsung Electronics. 416 Maetan-3dong, Yeongtong-gu
Suwon Suwon-si, Gyeonggi-do 442-742
Korea KOREA
Phone: +81-31-200-4508 Phone: +82 31 200 4635
E-Mail: soohong.park@samsung.com EMail: soohong.park@samsung.com
Vijayabhaskar A K Vijayabhaskar A K
Hewlett-Packard STSD-I Hewlett-Packard
29, Cunningham Road 29, Cunningham Road
Bangalore - 560052 Bangalore 560052
India INDIA
Phone: +91-80-2053085
E-Mail: vijayak@india.hp.com
Acknowledgements
Thanks to the DHC Working Group for their time and input into the Phone: +91 80 205308582
specification. In particular, thanks to Pekka Savola, Bernie Volz, EMail: vijayak@india.hp.com
Ralph Droms, Margaret Wasserman for their valuable comments on this
work.
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made Copies of IPR disclosures made to the IETF Secretariat and any
to obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification attempt made to obtain a general license or permission for the use of
can be obtained from the IETF Secretariat. 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 The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
are included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright Statement
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2005). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
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.
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. 50 change blocks. 
140 lines changed or deleted 118 lines changed or added

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