idnits 2.17.1 draft-cui-dhc-dhcp4o6-active-leasequery-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 an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The abstract seems to contain references ([RFC7341]), 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 (October 26, 2014) is 3467 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2132' is defined on line 221, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-dhc-dhcpv4-active-leasequery' is defined on line 252, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-softwire-lw4over6' is defined on line 263, but no explicit reference was found in the text == Outdated reference: A later version (-04) exists of draft-ietf-dhc-dhcpv6-active-leasequery-01 ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) == Outdated reference: A later version (-07) exists of draft-fsc-softwire-dhcp4o6-saddr-opt-01 == Outdated reference: A later version (-07) exists of draft-ietf-dhc-dhcpv4-active-leasequery-01 == Outdated reference: A later version (-09) exists of draft-ietf-dhc-dynamic-shared-v4allocation-02 == Outdated reference: A later version (-13) exists of draft-ietf-softwire-lw4over6-11 Summary: 3 errors (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 dhc Working Group Y. Cui 3 Internet-Draft Z. Liu 4 Intended status: Informational C. Liu 5 Expires: April 29, 2015 Tsinghua University 6 October 26, 2014 8 DHCP4o6 Active Leasequery 9 draft-cui-dhc-dhcp4o6-active-leasequery-00 11 Abstract 13 As networks migrate towards IPv6, some entities still have the 14 requirement for IPv4 configuration. DHCPv4 over DHCPv6 [RFC7341] 15 provides a mechanism for obtaining IPv4 configuration information 16 dynamically in IPv6 networks. DHCPv4/DHCPv6 Active Leasequery allows 17 a client to get real-time DHCP address binding information data via 18 TCP. This document describes an extension of DHCPv6 Active 19 Leasequery to provide an mechanism to getting real-time DHCPv4 over 20 DHCPv6 lease information. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on April 29, 2015. 39 Copyright Notice 41 Copyright (c) 2014 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 61 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 63 6.2. Informative References . . . . . . . . . . . . . . . . . 6 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 The DHCPv6 Leasequery [RFC5007] extends the basic DHCPv6 capability 69 [RFC3315] to allow an external entity to query a DHCPv6 server to 70 recover individual lease state information about a particular IPv6 71 address or client in near real-time. The DHCPv6 Bulk Leasequery 72 [RFC5460] extends DHCPv6 Leasequery [RFC5007] that allows an external 73 entity to query a DHCPv6 server for bulk transfer of lease 74 information via TCP. The Active Leasequery allows an entity not 75 directly participated in DHCPv6 client-server transactions and caches 76 the current DHCPv6 lease state in real-time.And for DHCPv4, there are 77 also similar protocols for DHCPv4 lease. [RFC4388] [RFC6926] 79 As networks migrate towards IPv6, hosts in some IPv6 network also 80 need DHCPv4 configuration using DHCPv4 over DHCPv6[RFC7341]. The 81 lease information in DHCPv4 over DHCPv6 (i.e. DHCP4o6 lease 82 information) contains DHCPv4 lease information (including IPv4 83 address and other DHCPv4 options) in DHCPv4 messages, and stateless 84 DHCPv6 options in DHCPV4-QUERY/DHCPV4-RESPONSE messages. The 85 capability of additional DHCPv6 options makes it different from 86 original DHCPv4 [RFC2131]. One example usage is in Lightweight 87 4over6 dynamic provisioning: A client (lwB4) chooses its IPv6 tunnel 88 source address and puts it into a DHCPv6 option 89 (OPTION_DHCP4O6_SADDR) [I-D.fsc-softwire-dhcp4o6-saddr-opt] to tell 90 the provisioning system. The tuple of client (lease IPv4 address, 91 port set, IPv6 tunnel source address)is then used to create a binding 92 entry in lwAFTR. 94 In the case that a requestor wants to get both DHCPv4 lease 95 information and DHCPv6 lease information of the same client, it can 96 run DHCPv4 Active Leasequery and DHCPv6 Active Leasequery separately, 97 using the same client identifier to associate them together. 98 However, it doesn't work for a requestor getting DHCP4o6 lease 99 information because there's no DUID or any other DHCPv6 identifiers 100 in DHCPV4-QUERY/DHCPV4-RESPONSE messages, thus the DHCPv6 options can 101 only be associated with the DHCPv4 lease. A requestor asking for 102 DHCP4o6 lease must get the DHCPv6 options along with the DHCPv4 lease 103 information. 105 However, the DHCPv4 Active Leasequery mechanism doesn't support 106 providing DHCPv6 options, and the DHCPv6 Active Leasequery mechanism 107 doesn't support providing DHCPv4 lease information. This document 108 describes an extension of DHCPv6 Active Leasequery, naming the 109 DHCP4o6 Active Leasequery, to allow an entity get the mixed DHCPv4 110 over DHCPv6 lease information in real-time in IPv6 network. 112 2. Terminology 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 116 document are to be interpreted as described in [RFC2119]. 118 3. Solution 120 The DHCP4o6 Active Leasequery mechanism is modeled on the existing 121 DHCPv4 over DHCPv6 protocol in [RFC7341], which combine DHCPv4 Active 122 Leasequery and DHCPv6 Active Leasequery to providing real-time DHCPv4 123 lease and related DHCPv6 lease information in IPv6 network. The 124 DHCP4o6 Active Leasequery requestors and DHCP4o6 servers communicate 125 with each other using DHCPv6 Active Leasequery which contains DHCPv4 126 Message Option defined in [RFC7341]. 128 DHCPv4 Message Option defined in [RFC7341] contains the DHCPv4 129 message sent by the DHCP client or server. In DHCP4o6 Active 130 Leasequery scenario, DHCPv4 Message Option contains the DHCPv4 Active 131 Leasequery message sent by requestor and DHCP4o6 server. 133 DHCP4o6 Leasequery requestor SHOULD obtain necessary IPv6 134 configuration and have the DHCP4o6 server IPv6 address available via 135 configuration or some other means, and that it has unicast IPv6 136 reachability to the DHCP4o6 server. 138 DHCP4o6 Leasequery requestor creates a TCP connection to DHCP4o6 139 server as defined [I-D.ietf-dhc-dhcpv6-active-leasequery]. After 140 establishing a connection, requestor sends a DHCPv6 ACTIVELEASEQUERY 141 message with a DHCPv4 Message Option in it to query for DHCPv4 over 142 DHCPv6 lease information. The DHCPv4 Message Option encapsulates the 143 DHCPv4 DHCPACTIVELEASEQUERY message to describe the query for a 144 DHCPv4 lease. And the related DHCPv6 options will be queried in 145 DHCPv6 query-options. The requestor MUST NOT put more than one 146 DHCPv4 Message Option into a single DHCPv6 ACTIVELEASEQUERY message. 148 When received the DHCPv6 ACTIVELEASEQUERY message, DHCP4o6 server 149 SHOULD address the DHCPv4 DHCPACTIVELEASEQUERY message in the DHCPv4 150 Message Option and the related DHCPv6 query in DHCPv6 query-options. 151 DHCP4o6 server will reply with DHCPv6 LEASEQUERY-REPLY message/ 152 LEASEQUERY-DATA message. When the server update DHCPv4 lease or 153 related DHCPv6 information, it will generate a response to 154 requestors. In response, the server sends updates of DHCPv4 over 155 DHCPv6 lease information in the DHCPv6 LEASEQUERY-DATA message. The 156 DHCPv4 lease sent to the requestor using DHCPv4 DHCPLEASEACTIVE or 157 DHCPLEASEUNASSIGNED message which will be encapsulated in DHCPv4 158 Message Option. The related DHCPv6 options will be carried in the 159 DHCPv6 OPTION_CLIENT_DATA option. 161 4. Use Case 163 As the method described above, it will provide the requestor with 164 related DHCPv4 lease and DHCPv6 information of a DHCP client in real- 165 time. It MAY be used in many cases. We will describe the using for 166 Lightweight 4over6 [I-D.ietf-softwire-lw4over6]as an example. 168 In Lightweight 4over6, lwAFTR need the binding IPv6 address for the 169 mapping table. lwAFTR can work as a DHCP4o6 Active Leasequery 170 requestor to get real-time DHCPv4 lease and related DHCPv6 171 information. lwAFTR need all lwB4's IPv4 address, PSID, IPv6 address 172 to make the maaping table for the tunnel. So, lwAFTR will send the 173 DHCPv6 ACTIVELEASEQUERY message with DHCPv4 Message Option to query 174 for DHCPv4 lease and related DHCPv6 lease information of a DHCP 175 client. DHCPv4 ACTIVELEASEQUERY message in the DHCPv4 Message Option 176 SHOULD contains the primary query as Query for All Configured IP 177 addresses. And the Parameter Request List option in DHCPv4 178 ACTIVELEASEQUERY message SHOULD contains the DHCPv4 Port Parameters 179 option defined in [I-D.ietf-dhc-dynamic-shared-v4allocation]. And in 180 the OPTION_LQ_QUERY option in DHCPv6 ACTIVELEASEQUERY message, the 181 DHCPv6 OPTION_ORO option MUST contains the DHCPv4 over DHCPv6 Source 182 address option defined in [I-D.fsc-softwire-dhcp4o6-saddr-opt]. 184 DHCP4o6 server configure the lwB4s with DHCPv4 lease, and get the 185 binding IPv6 address during the process. As defined in [RFC7341], 186 DHCP4o6 client query for DHCP4o6 server's address during DHCPv6 187 interaction. After receiving DHCP4o6 server's address, DHCP4o6 188 client will query for IPv4 address from DHCP4o6 server. At the same 189 time, DHCP4o6 client MAY negotiate the binding IPv6 address with 190 DHCP4o6 server, and DHCP4o6 server can record the binding IPv6 191 address as defined in [I-D.fsc-softwire-dhcp4o6-saddr-opt]. When 192 DHCP4o6 server received DHCPv6 ACTIVELEASEQUERY message from lwAFTR, 193 it SHOULD reply with the DHCPv6 LEASEQUERY-REPLY/LEASEQUERY-DATA 194 message which contains the CPEs' IPv4 address, PSID, IPv6 address and 195 other information in the following time if there is update of DHCPv4 196 lease or DHCPv6 lease. 198 In other cases, DHCP4o6 server MAY get more DHCPv6 information or 199 even the whole DHCPv6 lease by some means, it can provide more 200 information to the requestors. 202 5. Security Considerations 204 To be continue 206 6. References 208 6.1. Normative References 210 [I-D.ietf-dhc-dhcpv6-active-leasequery] 211 Dushyant, D., Kinnear, K., and D. Kukrety, "DHCPv6 Active 212 Leasequery", draft-ietf-dhc-dhcpv6-active-leasequery-01 213 (work in progress), March 2014. 215 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 216 Requirement Levels", BCP 14, RFC 2119, March 1997. 218 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 219 2131, March 1997. 221 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 222 Extensions", RFC 2132, March 1997. 224 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 225 and M. Carney, "Dynamic Host Configuration Protocol for 226 IPv6 (DHCPv6)", RFC 3315, July 2003. 228 [RFC4388] Woundy, R. and K. Kinnear, "Dynamic Host Configuration 229 Protocol (DHCP) Leasequery", RFC 4388, February 2006. 231 [RFC5007] Brzozowski, J., Kinnear, K., Volz, B., and S. Zeng, 232 "DHCPv6 Leasequery", RFC 5007, September 2007. 234 [RFC5460] Stapp, M., "DHCPv6 Bulk Leasequery", RFC 5460, February 235 2009. 237 [RFC6926] Kinnear, K., Stapp, M., Desetti, R., Joshi, B., Russell, 238 N., Kurapati, P., and B. Volz, "DHCPv4 Bulk Leasequery", 239 RFC 6926, April 2013. 241 [RFC7341] Sun, Q., Cui, Y., Siodelski, M., Krishnan, S., and I. 242 Farrer, "DHCPv4-over-DHCPv6 (DHCP 4o6) Transport", RFC 243 7341, August 2014. 245 6.2. Informative References 247 [I-D.fsc-softwire-dhcp4o6-saddr-opt] 248 Farrer, I., Sun, Q., and Y. Cui, "DHCPv4 over DHCPv6 249 Source Address Option", draft-fsc-softwire-dhcp4o6-saddr- 250 opt-01 (work in progress), September 2014. 252 [I-D.ietf-dhc-dhcpv4-active-leasequery] 253 Kinnear, K., Stapp, M., Volz, B., and N. Russell, "Active 254 DHCPv4 Lease Query", draft-ietf-dhc-dhcpv4-active- 255 leasequery-01 (work in progress), June 2014. 257 [I-D.ietf-dhc-dynamic-shared-v4allocation] 258 Cui, Y., Qiong, Q., Farrer, I., Lee, Y., Sun, Q., and M. 259 Boucadair, "Dynamic Allocation of Shared IPv4 Addresses", 260 draft-ietf-dhc-dynamic-shared-v4allocation-02 (work in 261 progress), September 2014. 263 [I-D.ietf-softwire-lw4over6] 264 Cui, Y., Qiong, Q., Boucadair, M., Tsou, T., Lee, Y., and 265 I. Farrer, "Lightweight 4over6: An Extension to the DS- 266 Lite Architecture", draft-ietf-softwire-lw4over6-11 (work 267 in progress), October 2014. 269 Authors' Addresses 271 Yong Cui 272 Tsinghua University 273 Beijing 100084 274 P.R.China 276 Phone: +86-10-6260-3059 277 Email: yong@csnet1.cs.tsinghua.edu.cn 279 ZiLong Liu 280 Tsinghua University 281 Beijing 100084 282 P.R.China 284 Phone: +86-10-6278-5822 285 Email: liuzilong8266@126.com 286 Cong Liu 287 Tsinghua University 288 Beijing 100084 289 P.R.China 291 Phone: +86-10-6278-5822 292 Email: gnocuil@gmail.com