Internet DRAFT - draft-daniel-dhc-dhcpv6-ctep-opt
draft-daniel-dhc-dhcpv6-ctep-opt
Network Working Group S. Daniel Park
Internet-Draft SAMSUNG Electronics
Expires : June 2004 A.K. Vijayabhaskar
Hewlett-Packard
December 2003
Configured Tunnel End Point Option for DHCPv6
draft-daniel-dhc-dhcpv6-ctep-opt-01.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
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.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
For the newly deployed IPv6 networks to interoperate with vastly
deployed IPv4 networks, various transition mechanisms had been
proposed. One such mechanism is configured tunnels. This document
provides a mechanism by which the DHCPv6 servers can provide
information about the various configured tunnel end points to reach
the IPv6 nodes which are separated by IPv4 networks.
Park, Vijay Expires June 2004 [Page 1]
Internet-Draft CTEP Option for DHCPv6 December 2003
1. Introduction
In the initial deployment of IPv6, the IPv6 nodes may need to
communicate with the other IPv6 nodes via IPv4 networks. Configured
tunnels [3] provide a way to encapsulate the IPv6 packets in IPv4
packets and tunnel them in the IPv4 network.
This document defines a new option called Configured Tunnel End
Point by which the DHCPv6 [1] server can notify the client with the
list of end point of the configured tunnels to the various IPv6
networks separated by the IPv4 networks.
2. Requirements
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in RFC 2119 [2]
3. Terminology
This document uses terminology specific to IPv6 and DHCPv6 as
defined in "Terminology" section of the DHCPv6 specification [1].
4. Configured Tunnel End Point Option
The Configured Tunnel End Point Option gives the information to the
clients about the Configured Tunnel End Point [3] to be contacted
for reaching the nodes in the various IPv6 networks which are
separated by IPv4 networks. The clients are expected to install
these routes in their machines.
The format of the Configured Tunnel End Point Option is as shown
below:
Park, Vijay Expires June 2004 [Page 2]
Internet-Draft CTEP Option for DHCPv6 December 2003
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_CTEP | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| prefix-len | |
+-+-+-+-+-+-+-+-+-+ |
| |
| Destination Prefix (16 bytes) |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+ |
| Configured TEP Address (16 bytes) |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | prefix-len | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| 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
Configured Tunnel Address lists in octets; It should be
a multiple of 33.
prefix-len: prefix length of the Destination Prefix
Destination Prefix: IPv6 Prefix;
Configured TEP Address: IPv6 Address of the Configured TEP.
The clients are expected to install the routes identified by the
tuples <Destination Prefix/prefix-len, Configured TEP Address> once
they receive this option from the server.
Park, Vijay Expires June 2004 [Page 3]
Internet-Draft CTEP Option for DHCPv6 December 2003
5. Appearance of this option
The Configured Tunnel End Point Option MUST NOT appear in other
than the following messages: Solicit, Advertise, Request, Renew,
Rebind, Information-Request and Reply.
The option numbers of Configured Tunnel End Point option MAY appear
in the Option Request Option [1] in the following messages: Solicit,
Request, Renew, Rebind, Information-Request and Reconfigure.
6. Security Considerations
The Configured Tunnel End Point Option may be used by an intruder
DHCPv6 server to provide invalid or incorrect configured tunnel end
point. This makes the client unable to reach its destination IPv6
node or to reach incorrect destination. The latter one has very
severe security issues as IPv6 destination is spoofed here.
To avoid attacks through this option, the DHCPv6 client SHOULD use
authenticated DHCP (see section "Authentication of DHCP messages" in
the DHCPv6 specification [1]).
7. IANA Considerations
IANA is requested to assign an option code to the following options
from the option-code space defined in "DHCPv6 Options" section of
the DHCPv6 specification [1].
Option Name Value Described in
OPTION_CTEP TBD Section 4
8. References
8.1 Normative References
[1] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and
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 Requirement
Levels", BCP 14, RFC 2119, March 1997.
Park, Vijay Expires June 2004 [Page 4]
Internet-Draft CTEP Option for DHCPv6 December 2003
8.2 Informative References
[3] R. Gilligan, E. Nordmark, "Transition Mechanisms for IPv6
Hosts and Routers", RFC 2893, August 2000.
9. Authors' Addresses
Soohong Daniel Park
Mobile Platform Laboratory, SAMSUNG Electronics.
416. Maetan-Dong, Paldal-Gu,
Suwon, Gyeonggi-Do
Korea
Phone: +81-31-200-4508
E-Mail: soohong.park@samsung.com
Vijayabhaskar A K
Hewlett-Packard STSD-I
29, Cunningham Road
Bangalore - 560052
India
Phone: +91-80-2053085
E-Mail: vijayak@india.hp.com
Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
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
revoked by the Internet Society or its successors or assigns.
Park, Vijay Expires June 2004 [Page 5]
Internet-Draft CTEP Option for DHCPv6 December 2003
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society. Thanks to the DHC Working Group for their time
and input into the specification. In particular, thanks to Pekka
Savola, Bernie Volz, Ralph Droms, for their valuable comments on
this work.
Park, Vijay Expires June 2004 [Page 6]
