[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06

  Network Working Group                                  S. Daniel Park
  Internet Draft                                                 P. Kim
  Expires : September 2004                          Samsung Electronics
                                                             March 2004
  
  
  
  
              DHCP Option for Configuring IPv6-over-IPv4 Tunnels
                     <draft-daniel-dhc-ipv6in4-opt-02.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 (2004).  All Rights Reserved.
  
  
  Abstract
  
     This document provides a mechanism by which the DHCPv4 servers can
     provide information about the configured IPv6-over-IPv4 tunnel
     end-point.  The IPv4/IPv6 dual-stack nodes can use this
     information to set up a configured tunnel to the tunnel end-point
     to obtain IPv6 connectivity.
  
  
  
  Park, Kim                  Expires: August 2004               [Page 1]


  Internet Draft       CTEP Option for IP6over4 Tunnel         March 2004
  
  
  
  Table of Contents
  
     1.  Introduction.................................................2
     2.  Requirements.................................................2
     3.  Configured Tunnel End Point Option...........................2
     4.  Multiple Tunnel End Point Considerations.....................3
     5.  Security Considerations......................................4
     6.  IANA Considerations..........................................4
     7.  References...................................................4
         7.1  Normative References....................................4
         7.2  Informative Reference...................................4
     8.  Authors' Addresses...........................................5
     9.  Acknowledgements.............................................5
  
  
  1. Introduction
  
     In the initial deployment of IPv6, the IPv6 nodes may need to
     communicate with the other IPv6 nodes via IPv4 tunnel service. The
     connectivity can be obtained by setting up an IPv6-over-IPv4
     configured tunnel between a client and a tunnel router.
  
     This document defines a new option by which the DHCPv4 [1] server
     can notify the client with the list of end-points of the possible
     configured tunnels.
  
     Particularly, this mechanism is useful where the ISP is providing
     the IPv6 services but is doing it using tunneling over IPv4 to avoid
     upgrading all their infrastructure to support IPv6 on day one.
  
  
  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. Configured Tunnel End Point Option
  
     This option specifies the configured tunnel end-point that client
     should use when discovering the IPv4 address of the ISP's tunnel
     router somehow via the Dynamic Host Configuration Protocol.
  
     Once the IPv4 address has been learned, it is configured as the
     tunnel end-point for the configured IPv6-over-IPv4 tunnel.
  
  
  Park, Kim                 Expires: September 2004             [Page 2]


  Internet Draft       CTEP Option for IP6over4 Tunnel         March 2004
  
  
  
  
     The format of the Configured Tunnel End Point Option is shown as
     below;
  
     The code for this option is TBD.  The length of this option is 4.
  
          Code            Length             CTEP Order in Sequence
      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  |     Len       |           CTEP Addr1          |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |        CTEP Addr 1            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  
  
     In the above diagram, CTEP Addr is 32-bit integers corresponding to
     DHCP options which specify the IP address of different configured
     tunnel end-point.
  
     As described in [4], the dual node received CTEP option MUST store
     the tunnel end-point address and this address is used as destination
     address for the encapsulating IPv4 header.
  
     The determination of which packets to tunnel is usually made by
     routing information on the encapsulator.  This is usually done via a
     routing table, which directs packets based on their destination
     address using the prefix mask and match technique.  For more
     information, refer to section 4. Configured Tunneling in [4].
  
  
  4. Multiple Tunnel End Point Considerations
  
     For the simple configured tunnel, one tunnel end-point is generally
     used and it assumes that all the networks will be reached through
     the same end-point.  In this case, one CTEP Addr field in the CTEP
     option is used for configured tunnel service.
  
     The list of end-points can be installed as the default routes and
     the routes will be tried in a round robin fashion if the IPv6 host
     load-sharing is honored [5].  Instead there can be specific default
     routes for the different destination.
  
     Generally, there may not be a need for installing multiple
     configured tunnel end-points unless administrator wants two for
     redundancy purposes.  It is out of scope of this draft.
  
  
  Park, Kim                 Expires: September 2004             [Page 3]


  Internet Draft       CTEP Option for IP6over4 Tunnel         March 2004
  
  
  
  
  
  5. Security Considerations
  
     A rouge DHCP server can issue invalid or incorrect configured tunnel
     end-point.  This may cause denial of service due to unreachability
     or makes the client to reach incorrect destination.
  
     The latter has very severe security issues as the tunnel end-point
     is on-the-path towards all the IPv6 destinations, and can trivially
     act as a man-in-the-middle attacker.
  
  
  6. IANA Considerations
  
     IANA is requested to an assign value for the Configured Tunnel End
     Point option code in accordance with RFC 2939 [3].
  
     Option Nam         Value     Described in
     OPTION_CTE          TBD        Section 3.
  
  
  7. References
  
  7.1 Normative References
  
     [1]   Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
           Bucknell University, March 1997.
  
     [2]   Bradner, S., "Key words for use in RFCs to Indicate
           Requirement Levels", BCP 14, RFC 2119, March 1997.
  
     [3]   Droms, R.,"Procedures and IANA Guidelines for Definition of
           New DHCP Options and Message Types", RFC 2939, September 2000.
  
  
  7.2 Informative Reference
  
     [4]   Nordmark, E. and Gilligan, R.E., "Basic Transition Mechanisms
           for IPv6 Hosts and Routers", RFC 2893, August 2000.
  
     [5]   Hinden B. and Thaler D., "IPv6 Host to Router Load Sharing",
           Internet-Draft (work in progress), January 2004.
  
  
  
  
  
  Park, Kim                 Expires: September 2004             [Page 4]


  Internet Draft       CTEP Option for IP6over4 Tunnel         March 2004
  
  
  
  8. Authors' Addresses
  
     Soohong Daniel Park
     Mobile Platform Laboratory
     Samsung Electronics.
     Suwon
     Korea
  
     Phone: +81 31 200 4508
     Email: soohong.park@samsung.com
  
  
     Pyungsoo Kim
     Mobile Platform Laboratory
     Samsung Electronics.
     Suwon
     Korea
  
     Phone: +81 31 200 4635
     Email: kimps@samsung.com
  
  
  9. Acknowledgements
  
     Special thanks to Pekka Savola, Vijayabhaskar A K, Eric Nordmark and
     Alain Durand for their many valuable revisions and comments.  In
     particular, Pekka Savola kindly clarified the multiple tunnel end
     point considerations with his good experience as well.
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  Park, Kim                 Expires: September 2004             [Page 5]


  Internet Draft       CTEP Option for IP6over4 Tunnel         March 2004
  
  
  
  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
  
     Copyright (C) The Internet Society (2004).  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.
  
     This document and the information contained herein is provided on an
     "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
  
  
  Park, Kim                 Expires: September 2004             [Page 6]


  Internet Draft       CTEP Option for IP6over4 Tunnel         March 2004
  
  
  
     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.
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  Park, Kim                 Expires: September 2004             [Page 7]
  

Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/