idnits 2.17.1 draft-hu-pppext-ipv6cp-extensions-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 17, 2010) is 4941 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.qin-pppext-ipv6-addr-pref' is defined on line 376, but no explicit reference was found in the text == Unused Reference: 'RFC1661' is defined on line 382, but no explicit reference was found in the text == Unused Reference: 'RFC5072' is defined on line 388, but no explicit reference was found in the text == Unused Reference: 'RFC3552' is defined on line 393, but no explicit reference was found in the text -- Possible downref: Normative reference to a draft: ref. 'I-D.huang-ipv6cp-options' -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-pppext-ipv6-dns-addr' Summary: 0 errors (**), 0 flaws (~~), 7 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Jie. Hu 3 Internet-Draft China Telecom 4 Intended status: Standards Track Jacni. Qin 5 Expires: April 20, 2011 Liquan. Yuan 6 ZTE 7 Glen. Zorn 8 Network Zen 9 October 17, 2010 11 PPP IPv6 Control Protocol Extensions 12 draft-hu-pppext-ipv6cp-extensions-00 14 Abstract 16 The IPv6 Control Protocol (IPv6CP) is one of Network Control 17 Protocols(NCPs) that are defined by the Point-to-Point Protocol(PPP) 18 for establishing and configuring different network protocols. 20 This document extends the IPv6CP for negotiating and configuring IPv6 21 network parameters over PPP links, including IPv6 address, IPv6 22 prefix, primary and alternative DNS server addresses. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on April 20, 2011. 41 Copyright Notice 43 Copyright (c) 2010 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 This document may contain material from IETF Documents or IETF 57 Contributions published or made publicly available before November 58 10, 2008. The person(s) controlling the copyright in some of this 59 material may not have granted the IETF Trust the right to allow 60 modifications of such material outside the IETF Standards Process. 61 Without obtaining an adequate license from the person(s) controlling 62 the copyright in such materials, this document may not be modified 63 outside the IETF Standards Process, and derivative works of it may 64 not be created outside the IETF Standards Process, except to format 65 it for publication as an RFC or to translate it into languages other 66 than English. 68 Table of Contents 70 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 72 2. IPv6CP Configuration Options . . . . . . . . . . . . . . . . . 4 73 2.1. IPv6-Address . . . . . . . . . . . . . . . . . . . . . . . 4 74 2.2. IPv6-Prefix . . . . . . . . . . . . . . . . . . . . . . . 6 75 2.3. Primary DNS Server IPv6 Address . . . . . . . . . . . . . 7 76 2.4. Alternative DNS Server IPv6 Address . . . . . . . . . . . 8 77 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 78 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 79 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 80 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 81 6.1. Normative References . . . . . . . . . . . . . . . . . . . 10 82 6.2. Informative References . . . . . . . . . . . . . . . . . . 11 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 85 1. Introduction 87 The point-to-point protocol provides a standard method for 88 transporting network-layer protocol datagrams over point-to-point 89 links. It also defines an extensible Link Control Protocol (LCP), 90 and a family of Network Control protocols (NCPs) for establishing and 91 configuring different network-layer protocols. 93 To respond to the requirements specified by 94 [draft-hu-pppext-ipv6cp-requirements-00] and guarantee the 95 negotiation of essential parameters needed for establishing a basic 96 IPv6 connectivity over PPP links, this document extends the IPv6CP 97 defining the negotiation of IPv6 address, IPv6 Prefix, primary and 98 alternative DNS server addresses. Please note that the prefix 99 negotiated here should be used by the local node(usually a 100 Residential Gateway) as an address pool for allocating addresses to 101 hosts on the attached networks. 103 This document combines serveral drafts: [I-D.qin-pppext-ipv6-addr- 104 pref] [I-D.ietf-pppext-ipv6-dns-addr] [I-D.huang-ipv6cp-options] 106 1.1. Requirements Language 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in RFC 2119 [RFC2119]. 112 2. IPv6CP Configuration Options 114 The IPv6-Address configuration option, type TBD1, provides a method 115 of obtaining the IPv6 address to be used by the local end of the PPP 116 link. 118 The IPv6-prefix configuration option, type TBD2, provides a method of 119 obtaining the prefix to be used by the local end of the PPP link as 120 the address pool. 122 The two name server address configuration options, TBD3 and TBD4, 123 provide a method of obtaining the addresses of DNS servers on the 124 remote IPv6 network. 126 For implementational convenience, these options are designed to be 127 identical in format and behavior to options which are already 128 present. 130 2.1. IPv6-Address 131 Description 133 This Configuration Option provides a way to negotiate the IPv6 134 address to be used on the local end of the link. It allows the 135 sender of the Configure-Request to state which IPv6-address is 136 desired, or to request that the peer provide the information. the 137 peer can provide this information by NAKing the option, and returning 138 a valid IPv6-address. 140 If negotiation about the remote IPv6-address is required, and the 141 peer did not provide the option in its Configure-Request, the option 142 should be appended to a Configure-NAK. The value of the IPv6-address 143 given must be acceptable as the remote IPv6-address, or indicate a 144 request that the peer provide the information. 146 By default, no IPv6 address is assigned. 148 A summary of the IPv6-address Configuration Option format is shown 149 below. The field are transimitted from left to right. 151 Configuration-Option: IPv6-Address 153 0 1 2 3 154 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 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | Type | Length | IPv6-Address 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 IPv6-Address (cont.) 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 IPv6-Address (cont.) 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 IPv6-Address (cont.) 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 IPv6-Address | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 Type 169 TBD1 171 Length 173 18 175 IPv6-Address 176 The sixteen octet IPv6-Address is the desired local address of 177 the sender of a Configure-Request. If all sixteen octects are 178 set to zero, it indicates a request that the peer provide the 179 IP-Address information. 181 Default 183 No IPv6 address is assigned. 185 2.2. IPv6-Prefix 187 Description 189 This Configuration Option provides a way to negotiate the IPv6 prefix 190 to be used on local end(usually a Router or Residential Gateway) of 191 the link for further allocating addresses to hosts on the attached 192 networks. It allows the sender of the Configure-Request to state 193 which IPv6 prefix is desired, or to request that the peer provide the 194 information. The peer can provide this information by NAKing the 195 option, and returning a valid IPv6 prefix. 197 By default, no IPv6 prefix is assigned. 199 A summary of the IPv6-Prefix Configuration Option format is shown 200 below. The field are transimitted from left to right. 202 Configuration-Option: IPv6-Prefix 204 0 1 2 3 205 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 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | Type | Length | Prefix-Length | IPv6-Prefix | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 IPv6-Prefix (cont.) 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 IPv6-Prefix (cont.) 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 IPv6-Prefix (cont.) 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 IPv6-Prefix | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 Type 220 TBD2 222 Length 224 19 226 Prefix-Length 228 This field is one octet and indicates the available length of the 229 prefix in the IPv6-Prefix field. 231 IPv6-Prefix 233 The IPv6-Prefix field associated with the Prefix-length field is 234 the desired prefix of the sender of a Configure-Request. If all 235 sixteen octects are set to zero, it indicates a request that 236 the peer provide the prefix information and the length required 237 is indicated in the Prefix-Length field. 239 The fixed sixteen octet space is used no matter what exactly the 240 available prefix length is. 242 Default 244 No IPv6 prefix is assigned. 246 2.3. Primary DNS Server IPv6 Address 248 Description 250 This Configuration Option defines a method for negotiating with 251 the remote peer the IPv6 address of the primary DNS server to be 252 used on the local end of the link. If the local peer requests an 253 invalid server address (which it will typically do intentionally) 254 the remote peer specifies the address by Naking this option, and 255 returning the IPv6 address of a valid DNS server. 257 By default, no primary DNS address is provided. 259 A summary of the Primary DNS IPv6 Address Configuration Option 260 format is shown below. The fields are transmitted from left to 261 right. 263 0 1 2 3 264 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 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 | Type | Length | Primary-DNS-IPv6-Addr | 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | Primary-DNS-IPv6-Addr (cont.) 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | Primary-DNS-IPv6-Addr (cont.) 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 | Primary-DNS-IPv6-Addr (cont.) 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 | Primary-DNS-IPV6-Addr | 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 Type 279 TBD3 281 Length 283 18 285 Primary-DNS-IPv6-Addr 287 The sixteen octet Primary-DNS-Addr is the address (in network 288 byte order) of the primary DNS server to be used by the local 289 peer. If all sixteen octets are set to zero, it indicates an 290 explicit request that the peer provide the address information in 291 a Config-Nak packet. 293 Default 295 No address is provided. 297 2.4. Alternative DNS Server IPv6 Address 298 Description 300 This Configuration Option defines a method for negotiating with 301 the remote peer the IPv6 address of an alternate DNS server to be 302 used on the local end of the link. If the local peer requests an 303 invalid server address (which it will typically do intentionally) 304 the remote peer specifies the address by Naking this option, and 305 returning the IPv6 address of a valid DNS server. 307 By default, no alternative DNS address is provided. 309 A summary of the Alternative DNS Server IPv6 Address 310 Configuration Option format is shown below. The fields are 311 transmitted from left to right. 313 0 1 2 3 314 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 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | Type | Length | Alt-DNS-IPv6-Addr | 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | Alt-DNS-IPv6-Address (cont.) 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 | Alt-DNS-IPv6-Address (cont.) 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 | Alt-DNS-IPv6-Address (cont.) 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 | Alt-DNS-IPv6-Address | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 327 Type 329 TBD4 331 Length 333 18 335 Alt-DNS-IPv6-Address 337 The sixteen octet Secondary-DNS-IPv6-Address is the IPv6 address 338 (in network byte order) of the secondary DNS server to be used 339 by the local peer. If all sixteen octets are set to zero, it 340 indicates an explicit request that the peer provide the address 341 information in a Config-Nak packet. 343 Default 345 No address is provided. 347 3. Acknowledgements 349 This document combines serveral drafts: [I-D.qin-pppext-ipv6-addr- 350 pref] [I-D.ietf-pppext-ipv6-dns-addr] [I-D.huang-ipv6cp-options] 352 4. IANA Considerations 354 IANA is requested to assign values for the Type field of the IPv6CP 355 Configuration Options specified in this document. 357 5. Security Considerations 359 No new security concerns raised out of this document. 361 6. References 363 6.1. Normative References 365 [I-D.huang-ipv6cp-options] 366 Huang, J., "IPv6CP Options for PPP Host Configuration", 367 draft-huang-ipv6cp-options-00 (work in progress), 368 February 2010. 370 [I-D.ietf-pppext-ipv6-dns-addr] 371 Hiller, T. and G. Zorn, "PPP IPV6 Control Protocol 372 Extensions for DNS Server Addresses", 373 draft-ietf-pppext-ipv6-dns-addr-03 (work in progress), 374 June 2003. 376 [I-D.qin-pppext-ipv6-addr-pref] 377 Li, Y., Qin, J., and L. Yuan, "PPP IPv6 Control Protocol 378 Extensions for Address and Prefix", 379 draft-qin-pppext-ipv6-addr-pref-00 (work in progress), 380 February 2010. 382 [RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, 383 RFC 1661, July 1994. 385 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 386 Requirement Levels", BCP 14, RFC 2119, March 1997. 388 [RFC5072] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over 389 PPP", RFC 5072, September 2007. 391 6.2. Informative References 393 [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC 394 Text on Security Considerations", BCP 72, RFC 3552, 395 July 2003. 397 Authors' Addresses 399 Jie Hu 400 China Telecom 401 No.118, Xizhimennei 402 Beijing, 100035 403 China 405 Phone: +86 10 58552808 406 Email: huj@ctbri.com.cn 408 Jacni Qin 409 ZTE 410 Shanghai, 411 China 413 Phone: +86 1391 8619 913 414 Email: jacniq@gmail.com 416 Liquan Yuan 417 ZTE 418 Shanghai, 419 China 421 Phone: +86 21 6889 5515 422 Email: ylq@zte.com.cn 424 Glen Zorn 425 Network Zen 426 Seattle, Washington, 427 USA 429 Phone: 430 Email: gwz@net-zen.net