idnits 2.17.1 draft-guo-softwire-6rd-ipv6-config-02.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 abstract seems to contain references ([RFC3315], [RFC5969]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 14, 2011) is 4763 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 3736 (Obsoleted by RFC 8415) == Outdated reference: A later version (-18) exists of draft-ietf-mboned-auto-multicast-10 Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 softwires WG X. Xu 3 Internet-Draft D. Guo 4 Intended status: Informational Huawei Technologies 5 Expires: September 15, 2011 O. Troan 6 W. Townsley 7 Cisco 8 March 14, 2011 10 IPv6 Host Configuration in 6rd 11 draft-guo-softwire-6rd-ipv6-config-02.txt 13 Abstract 15 The 6rd [RFC5969] linktype does not support IPv6 link-local 16 addressing, multicast and 6rd nodes are off-link from each other. 17 The host configuration protocol DHCPv6 [RFC3315] relies on link-local 18 addressing and multicast to function. This document specifies how 19 DHCPv6 can be used across a 6rd link. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 15, 2011. 38 Copyright Notice 40 Copyright (c) 2011 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 1. Introduction 55 IPv6 rapid deployment on IPv4 infrastructures (6rd) [RFC5969] enables 56 a service provider to rapidly deploy IPv6 service to residential 57 sites via stateless tunneling across its existing IPv4 network. 59 With 6rd, a 6rd CE can provide address assignments to hosts on the 60 LAN side, but there is no provision for providing other configuration 61 information to hosts on the LAN. 63 If only DNS configuration is required on IPv6-only hosts, DNS Proxy 64 [RFC5625] mechanism implemented on the 6rd CE would be enough. 65 Otherwise, stateless DHCPv6 [RFC3736] SHOULD be supported in 6rd for 66 IPv6 hosts to obtain other configuration information besides DNS. 68 As specified in the DHCPv6 specification [RFC3315], "...The client 69 MUST use a link-local address assigned to the interface for which it 70 is requesting configuration information as the source address in the 71 header of the IP datagram." A DHCPv6 client uses the 72 All_DHCP_Servers_or_Relays IPv6 multicast address as the destination 73 address of requests it sends. Link-local addresses are not supported 74 on 6rd links. 6rd as described in [RFC5969] does not support 75 multicast. 77 This document describes how DHCPv6 service can be provided across a 78 6rd link. 80 2. Conventions 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in RFC 2119 [RFC2119]. 86 3. DHCPv6 over 6rd links 88 There are two problems to be solved with regards to providing DHCPv6 89 service over a 6rd link: 90 o A DHCPv6 client uses an IPv6 link-local address as the source 91 address when requesting configuration information [RFC3315]. 92 Link-local addressing is not supported on an 6rd link. 94 o A DHCPv6 client sends a request to the 95 All_DHCP_Relay_Agent_and_Servers multicast address. 6rd as 96 specified in [RFC5969] does not support IPv6 multicast. 98 The first problem can be solved by changing the DHCPv6 protocol to 99 allow for a global address to be used as the source address in 100 requests. Another solution that does not require protocol changes, 101 is to send DHCPv6 requests via a local DHCPv6 relay on the 6rd CE. 103 The 6rd CE MUST support a local DHCPv6 client and relay. The DHCPv6 104 client running on the 6rd CE's virtual tunnel interface MUST send 105 DHCPv6 messages through a local DHCPv6 relay that encapsulates the 106 client message and forwards it to a DHCPv6 server or relay using one 107 of the 6rd CE's global unicast addresses as the source address. 109 The 6rd CE DHCPv6 relay agent SHOULD use the 6rd BR IPv6 anycast 110 address as the destination address, section 20 of [RFC3315]. If the 111 6rd link supports multicast [I-D.ietf-mboned-auto-multicast] the 6rd 112 CE DHCPv6 relay MAY use the All_DHCP_Servers [RFC3315] as the 113 destination address of Relay-forward messages. 115 The 6rd BRs in the 6rd domain must be configured as DHCPv6 relays or 116 servers on their 6rd virtual interfaces. 118 The 6rd CE SHOULD behave according to 119 [I-D.ietf-v6ops-ipv6-cpe-router]. In particular it operates a DHCPv6 120 client on the WAN side (6rd virtual) interface and as a DHCPv6 server 121 on the LAN-side interface(s). 123 4. IANA Considerations 125 This specification does not require any IANA actions. 127 5. Security Considerations 129 There are no new security considerations pertaining to this document. 131 6. Acknowledgements 133 7. References 134 7.1. Normative References 136 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 137 Requirement Levels", BCP 14, RFC 2119, March 1997. 139 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 140 and M. Carney, "Dynamic Host Configuration Protocol for 141 IPv6 (DHCPv6)", RFC 3315, July 2003. 143 [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol 144 (DHCP) Service for IPv6", RFC 3736, April 2004. 146 [RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4 147 Infrastructures (6rd) -- Protocol Specification", 148 RFC 5969, August 2010. 150 7.2. Informative References 152 [I-D.ietf-mboned-auto-multicast] 153 Thaler, D., Talwar, M., Aggarwal, A., Vicisano, L., and T. 154 Pusateri, "Automatic IP Multicast Without Explicit Tunnels 155 (AMT)", draft-ietf-mboned-auto-multicast-10 (work in 156 progress), March 2010. 158 [I-D.ietf-v6ops-ipv6-cpe-router] 159 Singh, H., Beebee, W., Donley, C., Stark, B., and O. 160 Troan, "Basic Requirements for IPv6 Customer Edge 161 Routers", draft-ietf-v6ops-ipv6-cpe-router-09 (work in 162 progress), December 2010. 164 [RFC5625] Bellis, R., "DNS Proxy Implementation Guidelines", 165 BCP 152, RFC 5625, August 2009. 167 Authors' Addresses 169 Xiaohu Xu 170 Huawei Technologies 171 No.3 Xinxi Rd., Shang-Di Information Industry Base 172 Beijing, Hai-Dian District 100085 173 P.R. China 175 Phone: +86 10 82882573 176 Email: xuxh@huawei.com 177 Dayong Guo 178 Huawei Technologies 179 No.3 Xinxi Rd., Shang-Di Information Industry Base 180 Beijing, Hai-Dian District 100085 181 P.R. China 183 Phone: +86-10-82882578 184 Email: guoseu@huawei.com 186 Ole Troan 187 Cisco 188 Oslo, 189 Norway 191 Email: ot@cisco.com 193 Mark Townsley 194 Cisco 195 Paris, 196 France 198 Email: mark@townsley.net