idnits 2.17.1 draft-freedman-pppext-ipv6-6rd-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 : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 153: '...s number of bits MUST be removed from ...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 25, 2011) is 4653 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3633 (Obsoleted by RFC 8415) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force D. Freedman 3 Internet-Draft Claranet 4 Intended status: Informational M. Townsley 5 Expires: January 26, 2012 Cisco 6 July 25, 2011 8 IPv6 6RD IPCP configuration option for PPP 9 draft-freedman-pppext-ipv6-6rd-00 11 Abstract 13 The Point-to-Point Protocol (PPP) (RFC1661) provides a standard 14 method for transporting multi-protocol datagrams over point-to-point 15 links. PPP defines an extensible Link Control Protocol and a family 16 of Network Control Protocols (NCPs) for establishing and configuring 17 different network-layer protocols. 19 This document extends the NCP for establishing and configuring the 20 Internet Protocol over PPP (RFC1332), defining the negotiation of 6RD 21 (RFC5969) Border Relay (BR) addresses. While the authors believe one 22 could use DHCP INFORM (RFC2131) to obtain the necessary 6RD 23 parameters, this is simply an alternative which allows reuse of an 24 existing PPP-based configuration infrastructure. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on January 26, 2012. 43 Copyright Notice 45 Copyright (c) 2011 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3. 6RD IPCP configuration option . . . . . . . . . . . . . . . . 5 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 64 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 65 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 66 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 67 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10 68 7.2. Informational References . . . . . . . . . . . . . . . . . 10 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 71 1. Introduction 73 PPP [RFC1661], and PPPoE [RFC2516], remains a common way for a 74 residential broadband end user to obtain configuration. In such 75 deployments, no DHCP [RFC2131], infrastructure may be in place and IP 76 configuration is solely obtained from RADIUS [RFC2865] servers and 77 network equipment via IPCP [RFC1332]. The PPP IPCP option presents 78 configuration information to the local peer such that it may join a 79 6RD [RFC5969] domain. 81 2. Terminology 83 6RD IPv6 Prefix 85 An IPv6 prefix selected by the service provider for use by a 6RD 86 domain. There is exactly one 6RD IPv6 prefix for a given 6RD 87 domain. An SP may deploy 6RD with a single 6RD domain or multiple 88 6RD domains. 90 6RD Delegated Prefix 92 The IPv6 prefix calculated by the local peer for use within the 93 customer site by combining the 6RD prefix and the local peer IPv4 94 address obtained via IPv4 configuration methods. This prefix can 95 be considered logically equivalent to a DHCPv6 IPv6 delegated 96 prefix [RFC3633]. 98 6RD Domain 100 A service provider may deploy 6RD with a single 6RD domain, or may 101 utilize multiple 6RD domains. Each domain requires a seperate 6RD 102 IPv6 prefix. 104 6RD Border Relay (BR) 106 A 6RD-enabled router managed by the service provider at the edge 107 of a 6RD domain. A Border Relay router provides an endpoint for 108 the 6RD IPv6 in IPv4 tunnel. A 6RD BR may also be referred to 109 simply as a "BR" within the context of 6RD. 111 6RD BR address 113 The IPv4 address of the 6RD Border Relay for a given 6RD domain. 114 This IPv4 address is used by the local peer to send packets to a 115 BR in order to reach IPv6 destinations outside of the 6RD domain. 117 3. 6RD IPCP configuration option 119 Description: 121 This Configuration Option provides a method for informing the 122 local peer of the configuration parameters required for the 6RD 123 domain available for the peer to join. 125 0 1 2 3 126 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 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 | type | length |V4Prefix-Length|V6Prefix-Length| 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | 6RD BR Address (4 octets) | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | | 133 | 6RD IPv6 Prefix | 134 | (variable, up to 16 octets) | 135 | | 136 | | 137 | | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 Figure 1 142 Type: 144 TBA 146 Length: 148 The total length of the IPCP option, in octets 150 V4Prefix-Length 152 Prefix length of the common part of the encoded IPv4 address in 153 number of bits. This number of bits MUST be removed from leftmost 154 of the IPv4 address when generating the 6RD Delegated Prefix. For 155 example, if this value is 8, 24 bits of the subscriber IPv4 prefix 156 will be used when creating the IPv6 Delegated Prefix, determining 157 the destination IPv4 encapsulation address, etc. If the value is 158 0, then the whole 32 bits of the IPv4 address is used in the 159 encoding. 161 V6Prefix-Length 163 IPv6 Prefix length of the 6RD IPv6 prefix in number of bits. 165 6RD BR Address 167 The IPv4 address of the 6RD Relay (may be anycast) 169 6RD IPv6 prefix 171 The service provider's 6RD IPv6 prefix represented as a 16-octet 172 IPv6 address. 174 Default: 176 By default, no fields are populated 178 4. IANA Considerations 180 This memo requires an IPCP option number assignment. 182 5. Security Considerations 184 This memo does not present any security considerations, it is assumed 185 that the remote peer is trusted and therefore the parameters of the 186 6RD domain are to be trusted. 188 6. Acknowledgements 190 This memo is based on existing work [I-D.townsley-ipv6-6rd] which 191 describes possible provisioning of 6RD configuration parameters. 193 7. References 195 7.1. Normative References 197 [RFC1332] McGregor, G., "The PPP Internet Protocol Control Protocol 198 (IPCP)", RFC 1332, May 1992. 200 [RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, 201 RFC 1661, July 1994. 203 [RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D., 204 and R. Wheeler, "A Method for Transmitting PPP Over 205 Ethernet (PPPoE)", RFC 2516, February 1999. 207 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 208 Host Configuration Protocol (DHCP) version 6", RFC 3633, 209 December 2003. 211 [RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4 212 Infrastructures (6rd) -- Protocol Specification", 213 RFC 5969, August 2010. 215 7.2. Informational References 217 [I-D.townsley-ipv6-6rd] 218 Townsley, M. and O. Troan, "IPv6 via IPv4 Service Provider 219 Networks", draft-townsley-ipv6-6rd-01 (work in progress), 220 July 2009. 222 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 223 RFC 2131, March 1997. 225 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 226 "Remote Authentication Dial In User Service (RADIUS)", 227 RFC 2865, June 2000. 229 Authors' Addresses 231 David Freedman 232 Claranet 233 London 234 UK 236 Phone: +44 20 7685 8000 237 Email: david.freedman@uk.clara.net 239 Mark Townsley 240 Cisco Systems 241 Paris 242 France 244 Phone: +33 15 804 3483 245 Email: mark@townsley.net