[Search] [txt|pdf|bibtex] [Tracker] [Email] [Nits]

Versions: 00                                                            
Internet Engineering Task Force                                    Y. Li
Internet-Draft                                             China Telecom
Intended status: Standards Track                                  J. Qin
Expires: July 5, 2010                                            L. Yuan
                                                                     ZTE
                                                            January 2010


      PPP IPv6 Control Protocol Extensions for Address and Prefix
                   draft-qin-pppext-ipv6-addr-pref-00

Abstract

   The IPv6 Control Protocol (IPv6CP) is a NCP that allows for the
   negotiation of parameters for an IPv6 interface over PPP.

   This document defines the IPv6 address and prefix configuration
   options that can be negotiated through the IPv6CP.

   The major part of the text in this document is taken from the
   previous RFCs.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 July 5, 2010.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the



Li, et al.                Expires July 5, 2010                  [Page 1]


Internet-Draft               ipv6-addr-pref                 January 2010


   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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the BSD License.


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 3
   2.  Additional IPv6CP Configuration Options . . . . . . . . . . . . 3
     2.1.  IPv6-Address  . . . . . . . . . . . . . . . . . . . . . . . 4
     2.2.  IPv6-Prefix . . . . . . . . . . . . . . . . . . . . . . . . 5
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     5.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     5.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7

























Li, et al.                Expires July 5, 2010                  [Page 2]


Internet-Draft               ipv6-addr-pref                 January 2010


1.  Introduction

   The point-to-point protocol provides a standard method for
   transporting network-layer protocol datagrams over point-to-point
   links.  It also defines an extensible Link Control Protocol (LCP),
   and a family of Network Control protocols (NCPs) for establishing and
   configuring different network-layer protocols.

   This document extends the NCP for configuring the IPv6 over PPP,
   defining the negotiation of IPv6 address and IPv6 Prefix.  The prefix
   negotiated by the means here should be used by the local node(usually
   a Residential Gateway) for allocating addresses to hosts on the
   attached networks.

   Notes: As in IPv4 networks, PPP(PPPoE) will still be an important
   mechanism for connecting broadband access users of IPv6.  To make it
   consistent in the way of configuring network parameters and simplify
   the implementations, it may be reasonable to extend the Configuration
   Options needed which is the mature way for PPP rather than involving
   additional mechanisms.

   In addition to this document, There is an expired WG item,
   [I-D.ietf-pppext-ipv6-dns-addr] that needs to be reevaluated.

1.1.  Requirements Language

   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 RFC 2119 [RFC2119].


2.  Additional IPv6CP Configuration Options

   The IPv6-Address configuration option, type 'X'(TBD), provides a
   method of obtaining the IPv6 address to be used by the local end of
   the PPP link.

   The IPv6-prefix configuration option, type 'Y'(TBD), provides a
   method of obtaining the prefix to be used by the local end of the PPP
   link for the address pool.

   For implementational convenience, these options are designed to be
   identical in format and behavior to options which are already
   present.







Li, et al.                Expires July 5, 2010                  [Page 3]


Internet-Draft               ipv6-addr-pref                 January 2010


2.1.  IPv6-Address

   Description

   This Configuration Option provides a way to negotiate the IPv6
   address to be used on the local end of the link.  It allows the
   sender of the Configure-Request to state which IPv6-address is
   desired, or to request that the peer provide the information. the
   peer can provide this information by NAKing the option, and returning
   a valid IPv6-address.

   If negotiation about the remote IPv6-address is required, and the
   peer did not provide the option in its Configure-Request, the option
   should be appended to a Configure-NAK.  The value of the IPv6-address
   given must be acceptable as the remote IPv6-address, or indicate a
   request that the peer provide the information.

   By default, no IPv6 address is assigned.

   A summary of the IPv6-address Configuration Option format is shown
   below.  The field are transimitted from left to right.






























Li, et al.                Expires July 5, 2010                  [Page 4]


Internet-Draft               ipv6-addr-pref                 January 2010


       Configuration-Option: IPv6-Address

       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 2
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Type      |    Length     |         IPv6-Address
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                               IPv6-Address (cont)
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                               IPv6-Address (cont)
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                               IPv6-Address (cont)
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                 IPv6-Address          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Type

       'X'

       Length

       18

       IPv6-Address

       The sixteen octet IPv6-Address is the desired local address of
       the sender of a Configure-Request. If all sixteen octects are
       set to zero, it indicates a request that the peer provide the
       IP-Address information.

       Default

       No IPv6 address is assigned.

2.2.  IPv6-Prefix

   Description

   This Configuration Option provides a way to negotiate the IPv6 prefix
   to be used on local end(usually a Router or Residential Gateway) of
   the link for further allocating addresses to hosts on the attached
   networks.  It allows the sender of the Configure-Request to state
   which IPv6 prefix is desired, or to request that the peer provide the
   information.  The peer can provide this information by NAKing the
   option, and returning a valid IPv6 prefix.

   By default, no IPv6 prefix is assigned.



Li, et al.                Expires July 5, 2010                  [Page 5]


Internet-Draft               ipv6-addr-pref                 January 2010


   A summary of the IPv6-Prefix Configuration Option format is shown
   below.  The field are transimitted from left to right.


       Configuration-Option: IPv6-Prefix

       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 2
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Type      |    Length     | Prefix-Length |  IPv6-Prefix  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                               IPv6-Prefix (cont)
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                               IPv6-Prefix (cont)
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                               IPv6-Prefix (cont)
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                          IPv6-Prefix                  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Type

       'Y'

       Length

       19


       Prefix-Length

       This field is one octet and indicates the available length of the
       prefix in the IPv6-Prefix field.

       IPv6-Prefix

       The IPv6-Prefix field associated with the Prefix-length field is
       the desired prefix of the sender of a Configure-Request. If all
       sixteen octects are set to zero, it indicates a request that
       the peer provide the prefix information and the length required
       is indicated in the Prefix-Length field.

       The fixed sixteen octet space is used no matter what exactly the
       available prefix length is.


       Default




Li, et al.                Expires July 5, 2010                  [Page 6]


Internet-Draft               ipv6-addr-pref                 January 2010


       No IPv6 prefix is assigned.


3.  IANA Considerations

   TBD.


4.  Security Considerations

   Security issues are not discussed in this document.


5.  References

5.1.  Normative References

   [RFC1661]  Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,
              RFC 1661, July 1994.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC5072]  S.Varada, Haskins, D., and E. Allen, "IP Version 6 over
              PPP", RFC 5072, September 2007.

5.2.  Informative References

   [I-D.ietf-pppext-ipv6-dns-addr]
              Hiller, T. and G. Zorn, "PPP IPV6 Control Protocol
              Extensions for DNS Server Addresses",
              draft-ietf-pppext-ipv6-dns-addr-03 (work in progress),
              June 2003.

   [RFC1332]  McGregor, G., "The PPP Internet Protocol Control Protocol
              (IPCP)", RFC 1332, May 1992.

   [RFC5172]  Varada, S., "Negotiation for IPv6 Datagram Compression
              Using IPv6 Control Protocol", RFC 5172, March 2008.












Li, et al.                Expires July 5, 2010                  [Page 7]


Internet-Draft               ipv6-addr-pref                 January 2010


Authors' Addresses

   Yangchun Li
   China Telecom
   109 West Zhongshan Ave
   Guangzhou,   510630
   China

   Phone: +86 20 3863 9479
   Email: liyc@gsta.com


   Jacni Qin
   ZTE
   Shanghai,
   China

   Phone: +86 1391 861 9913
   Email: jacniq@gmail.com


   Liquan Yuan
   ZTE
   Shanghai,
   China

   Phone: +86 1352 460 6672
   Email: ylq@zte.com.cn























Li, et al.                Expires July 5, 2010                  [Page 8]