Internet Engineering Task Force Jie. Hu Internet-Draft China Telecom Intended status: Standards Track Jacni. Qin Expires: April 20, 2011 Liquan. Yuan ZTE Glen. Zorn Network Zen October 17, 2010 PPP IPv6 Control Protocol Extensions draft-hu-pppext-ipv6cp-extensions-00 Abstract The IPv6 Control Protocol (IPv6CP) is one of Network Control Protocols(NCPs) that are defined by the Point-to-Point Protocol(PPP) for establishing and configuring different network protocols. This document extends the IPv6CP for negotiating and configuring IPv6 network parameters over PPP links, including IPv6 address, IPv6 prefix, primary and alternative DNS server addresses. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on April 20, 2011. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the 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 Hu, et al. Expires April 20, 2011 [Page 1] Internet-Draft IPv6CP Extensions October 2010 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 Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Hu, et al. Expires April 20, 2011 [Page 2] Internet-Draft IPv6CP Extensions October 2010 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2. IPv6CP Configuration Options . . . . . . . . . . . . . . . . . 4 2.1. IPv6-Address . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. IPv6-Prefix . . . . . . . . . . . . . . . . . . . . . . . 6 2.3. Primary DNS Server IPv6 Address . . . . . . . . . . . . . 7 2.4. Alternative DNS Server IPv6 Address . . . . . . . . . . . 8 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 6.1. Normative References . . . . . . . . . . . . . . . . . . . 10 6.2. Informative References . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Hu, et al. Expires April 20, 2011 [Page 3] Internet-Draft IPv6CP Extensions October 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. To respond to the requirements specified by [draft-hu-pppext-ipv6cp-requirements-00] and guarantee the negotiation of essential parameters needed for establishing a basic IPv6 connectivity over PPP links, this document extends the IPv6CP defining the negotiation of IPv6 address, IPv6 Prefix, primary and alternative DNS server addresses. Please note that the prefix negotiated here should be used by the local node(usually a Residential Gateway) as an address pool for allocating addresses to hosts on the attached networks. This document combines serveral drafts: [I-D.qin-pppext-ipv6-addr- pref] [I-D.ietf-pppext-ipv6-dns-addr] [I-D.huang-ipv6cp-options] 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. IPv6CP Configuration Options The IPv6-Address configuration option, type TBD1, 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 TBD2, provides a method of obtaining the prefix to be used by the local end of the PPP link as the address pool. The two name server address configuration options, TBD3 and TBD4, provide a method of obtaining the addresses of DNS servers on the remote IPv6 network. For implementational convenience, these options are designed to be identical in format and behavior to options which are already present. 2.1. IPv6-Address Hu, et al. Expires April 20, 2011 [Page 4] Internet-Draft IPv6CP Extensions October 2010 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. 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 TBD1 Length 18 IPv6-Address Hu, et al. Expires April 20, 2011 [Page 5] Internet-Draft IPv6CP Extensions October 2010 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. 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 TBD2 Hu, et al. Expires April 20, 2011 [Page 6] Internet-Draft IPv6CP Extensions October 2010 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 No IPv6 prefix is assigned. 2.3. Primary DNS Server IPv6 Address Description This Configuration Option defines a method for negotiating with the remote peer the IPv6 address of the primary DNS server to be used on the local end of the link. If the local peer requests an invalid server address (which it will typically do intentionally) the remote peer specifies the address by Naking this option, and returning the IPv6 address of a valid DNS server. By default, no primary DNS address is provided. A summary of the Primary DNS IPv6 Address Configuration Option format is shown below. The fields are transmitted from left to right. 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 | Primary-DNS-IPv6-Addr | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Hu, et al. Expires April 20, 2011 [Page 7] Internet-Draft IPv6CP Extensions October 2010 | Primary-DNS-IPv6-Addr (cont.) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Primary-DNS-IPv6-Addr (cont.) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Primary-DNS-IPv6-Addr (cont.) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Primary-DNS-IPV6-Addr | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type TBD3 Length 18 Primary-DNS-IPv6-Addr The sixteen octet Primary-DNS-Addr is the address (in network byte order) of the primary DNS server to be used by the local peer. If all sixteen octets are set to zero, it indicates an explicit request that the peer provide the address information in a Config-Nak packet. Default No address is provided. 2.4. Alternative DNS Server IPv6 Address Hu, et al. Expires April 20, 2011 [Page 8] Internet-Draft IPv6CP Extensions October 2010 Description This Configuration Option defines a method for negotiating with the remote peer the IPv6 address of an alternate DNS server to be used on the local end of the link. If the local peer requests an invalid server address (which it will typically do intentionally) the remote peer specifies the address by Naking this option, and returning the IPv6 address of a valid DNS server. By default, no alternative DNS address is provided. A summary of the Alternative DNS Server IPv6 Address Configuration Option format is shown below. The fields are transmitted from left to right. 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 | Alt-DNS-IPv6-Addr | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Alt-DNS-IPv6-Address (cont.) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Alt-DNS-IPv6-Address (cont.) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Alt-DNS-IPv6-Address (cont.) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Alt-DNS-IPv6-Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type TBD4 Length 18 Alt-DNS-IPv6-Address The sixteen octet Secondary-DNS-IPv6-Address is the IPv6 address (in network byte order) of the secondary DNS server to be used by the local peer. If all sixteen octets are set to zero, it indicates an explicit request that the peer provide the address information in a Config-Nak packet. Default No address is provided. Hu, et al. Expires April 20, 2011 [Page 9] Internet-Draft IPv6CP Extensions October 2010 3. Acknowledgements This document combines serveral drafts: [I-D.qin-pppext-ipv6-addr- pref] [I-D.ietf-pppext-ipv6-dns-addr] [I-D.huang-ipv6cp-options] 4. IANA Considerations IANA is requested to assign values for the Type field of the IPv6CP Configuration Options specified in this document. 5. Security Considerations No new security concerns raised out of this document. 6. References 6.1. Normative References [I-D.huang-ipv6cp-options] Huang, J., "IPv6CP Options for PPP Host Configuration", draft-huang-ipv6cp-options-00 (work in progress), February 2010. [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. [I-D.qin-pppext-ipv6-addr-pref] Li, Y., Qin, J., and L. Yuan, "PPP IPv6 Control Protocol Extensions for Address and Prefix", draft-qin-pppext-ipv6-addr-pref-00 (work in progress), February 2010. [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. Hu, et al. Expires April 20, 2011 [Page 10] Internet-Draft IPv6CP Extensions October 2010 6.2. Informative References [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, July 2003. Authors' Addresses Jie Hu China Telecom No.118, Xizhimennei Beijing, 100035 China Phone: +86 10 58552808 Email: huj@ctbri.com.cn Jacni Qin ZTE Shanghai, China Phone: +86 1391 8619 913 Email: jacniq@gmail.com Liquan Yuan ZTE Shanghai, China Phone: +86 21 6889 5515 Email: ylq@zte.com.cn Glen Zorn Network Zen Seattle, Washington, USA Phone: Email: gwz@net-zen.net Hu, et al. Expires April 20, 2011 [Page 11]