idnits 2.17.1 draft-huang-ipv6cp-options-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5072, but the abstract doesn't seem to mention this, which it should. 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. (Using the creation date from RFC5072, updated by this document, for RFC5378 checks: 2004-06-03) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 3, 2010) is 5189 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) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Huang 3 Internet-Draft AT&T Labs 4 Updates: 5072 (if approved) February 3, 2010 5 Intended status: Standards Track 6 Expires: August 7, 2010 8 IPv6CP Options for PPP Host Configuration 9 draft-huang-ipv6cp-options-00 11 Abstract 13 The Softwire Hub and Spoke Framework document outlines three steps 14 for the Softwire Initiator (SI) and PPP peer of the Softwire 15 Concentrator (SC) over IPv4 connectivity to be fully configured for 16 IPv6 once the PPP session has been established. For the same 17 function over IPv6 connectivity, however, only one additional step is 18 needed. This is because IPv6CP only defines the Interface-Identifier 19 option. This document defines additional host configuration options 20 for IPv6CP so that the operational model of IPCP is extended to 21 IPv6CP to reduce requirements on the SI and SC. 23 Status of this Memo 25 This Internet-Draft is submitted to IETF in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF), its areas, and its working groups. Note that 30 other groups may also distribute working documents as Internet- 31 Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt. 41 The list of Internet-Draft Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html. 44 This Internet-Draft will expire on August 7, 2010. 46 Copyright Notice 48 Copyright (c) 2010 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 65 2. IPv6CP Configuration Options . . . . . . . . . . . . . . . . . 3 66 2.1. Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2.2. Prefix-Length . . . . . . . . . . . . . . . . . . . . . . 4 68 2.3. IPv6-Address . . . . . . . . . . . . . . . . . . . . . . . 5 69 2.4. Default-Gateway-Address . . . . . . . . . . . . . . . . . 6 70 2.5. Primary-DNS-Address . . . . . . . . . . . . . . . . . . . 7 71 2.6. Secondary-DNS-Address . . . . . . . . . . . . . . . . . . 7 72 2.7. Delegated-Prefix . . . . . . . . . . . . . . . . . . . . . 8 73 2.8. Delegated-Prefix-Length . . . . . . . . . . . . . . . . . 9 74 3. Security Considerations . . . . . . . . . . . . . . . . . . . 10 75 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 76 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 77 6. Normative References . . . . . . . . . . . . . . . . . . . . . 10 78 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 80 1. Introduction 82 The Softwire Hub and Spoke framework document [RFC5571] outlines 83 three steps for the Softwire Initiator (SI) and PPP peer of the 84 Softwire Concentrator (SC) over IPv4 connectivity to be fully 85 configured for IPv6 once the PPP session has been established. For 86 the same function over IPv6 connectivity, however, only one 87 additional step is needed. This is because IPv6CP [RFC5072] only 88 defines the Interface-Identifier option. This document defines 89 additional host configuration options for IPv6CP so that the 90 operational model of IPCP is extended to IPv6CP to reduce 91 requirements on the SI and SC. 93 Other use cases where IPv6CP can completely configure the PPP 94 endpoint is the traditional VPN concentrator space, where the 95 concentrator assigns all IP configuration parameters to the VPN 96 client for IPv4. 98 1.1. Requirements Language 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119 [RFC2119]. 104 2. IPv6CP Configuration Options 106 IPv6CP [RFC5072]defines the Interface-Identifier configuration 107 option. Successful negotiation of the Interface-Identifier allows 108 further configuration parameters via Stateless Autoconfiguration. 110 The following IPv6CP options are defined in this document. Up-to- 111 date values of the IPv6CP Option Type field are specified in the 112 online database of "Assigned Numbers" maintained by IANA. 114 2.1. Prefix 116 This option and Prefix-Length provide the IPv6 prefix information to 117 the device. 119 0 1 2 3 120 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 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | Type | Length | Prefix (msb) 123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 124 Prefix (cont) 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 ... ... 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 Prefix (lsb) | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 Type 133 2 135 Length 137 18 139 Prefix 141 The IPv6 prefix that should be used on the link to construct the 142 globally unique IPv6 address. 144 Default 146 None 148 2.2. Prefix-Length 150 This option and Prefix provide the IPv6 prefix information to the 151 device. 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 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | Type | Length |Prefix-Length | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 Type 161 3 163 Length 165 3 167 Prefix-Length 169 The length of the IPv6 prefix that should be used on the link to 170 construct the globally unique IPv6 address. 172 Default 174 None 176 2.3. IPv6-Address 178 This option provides the IPv6 address to be configured on the PPP 179 peer for the PPP link. This is an alternative for the IPv6 address 180 assignment/generation process where the gateway/SC completely 181 controls the configuration of the PPP peer. 183 0 1 2 3 184 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 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | Type | Length | IPv6-Address (msb) 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 IPv6-Address (cont) 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 ... ... 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 192 IPv6-Address (lsb) | 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 Type 197 4 199 Length 201 18 203 IPv6-Address 205 The IPv6 address assigned to the PPP peer to use on this link. 207 Default 209 None 211 2.4. Default-Gateway-Address 213 This option provides the IPv6 address of the default gateway on the 214 link. 216 0 1 2 3 217 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 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 | Type | Length | Default-Gateway-Address (msb) 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 Default-Gateway-Address (cont) 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 ... ... 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 Default-Gateway-Address (lsb) | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 Type 230 5 232 Length 234 18 236 Default-Gateway-Address 238 The IPv6 address of the default gateway on this link. 240 Default 242 None 244 2.5. Primary-DNS-Address 246 This option provides the IPv6 address of the primary DNS server that 247 should be configured on the PPP peer. 249 0 1 2 3 250 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 251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 252 | Type | Length | Primary-DNS-Address (msb) 253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 254 Primary-DNS-Address (cont) 255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 ... ... 257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 Primary-DNS-Address (lsb) | 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 Type 263 6 265 Length 267 18 269 Primary-DNS-Address 271 The IPv6 address of the primary DNS server. 273 Default 275 None 277 2.6. Secondary-DNS-Address 279 This option provides the IPv6 address of the secondary DNS server 280 that should be configured on the PPP peer. 282 0 1 2 3 283 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 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 | Type | Length | Secondary-DNS-Address (msb) 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 Secondary-DNS-Address (cont) 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 ... ... 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 Secondary-DNS-Address (lsb) | 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 Type 296 7 298 Length 300 18 302 Secondary-DNS-Address 304 The IPv6 address of the secondary DNS server. 306 Default 308 None 310 2.7. Delegated-Prefix 312 This option and Delegated-Prefix-Length provide information on the 313 IPv6 prefix delegated to the device. 315 0 1 2 3 316 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 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | Type | Length | Delegated-Prefix (msb) 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 Delegated-Prefix (cont) 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 ... ... 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 Delegated-Prefix (lsb) | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 327 Type 329 8 331 Length 333 18 335 Delegated-Prefix 337 The IPv6 prefix delegated by the gateway/SC to the device. 339 Default 341 None 343 2.8. Delegated-Prefix-Length 345 This option and Delegated-Prefix provide the information on the IPv6 346 prefix delegated by the gateway/SC to the device. 348 0 1 2 3 349 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 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | Type | Length |Deleg-Pref-Leng| 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 Type 356 9 358 Length 360 3 362 Delegated-Prefix-Length 364 The length of the IPv6 prefix delegated by the gateway/SC to the 365 device 367 Default 369 None 371 3. Security Considerations 373 No new security concerns raise out of this document. 375 4. IANA Considerations 377 IANA is requested to assign values 2 through 9 for the Type field for 378 the IPv6CP configuration options specified in this document. 380 5. Acknowledgements 382 Placeholder 384 6. Normative References 386 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 387 Requirement Levels", BCP 14, RFC 2119, March 1997. 389 [RFC5072] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over 390 PPP", RFC 5072, September 2007. 392 [RFC5571] Storer, B., Pignataro, C., Dos Santos, M., Stevant, B., 393 Toutain, L., and J. Tremblay, "Softwire Hub and Spoke 394 Deployment Framework with Layer Two Tunneling Protocol 395 Version 2 (L2TPv2)", RFC 5571, June 2009. 397 Author's Address 399 Jerry Huang 400 AT&T Labs 401 4513 Western Avenue, Ofc 1741 402 Lisle, IL 60532 403 US 405 Phone: +1 630 719 4389 406 Email: jhuang1@att.com