| 1 |
<pre>Internet Engineering Task Force (IETF) I. Farrer |
| 2 |
Request for Comments: 8539 Deutsche Telekom AG |
| 3 |
Updates: <a href="./rfc7598">7598</a> Q. Sun |
| 4 |
Category: Standards Track Y. Cui |
| 5 |
ISSN: 2070-1721 L. Sun |
| 6 |
Tsinghua University |
| 7 |
March 2019 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Softwire Provisioning Using DHCPv4 over DHCPv6</span> |
| 11 |
|
| 12 |
Abstract |
| 13 |
|
| 14 |
DHCPv4 over DHCPv6 (<a href="./rfc7341">RFC 7341</a>) is a mechanism for dynamically |
| 15 |
configuring IPv4 for use as an over-the-top service in an IPv6-only |
| 16 |
network. Softwires are an example of such a service. For DHCPv4 |
| 17 |
over DHCPv6 (DHCP 4o6) to function with some IPv4-over-IPv6 softwire |
| 18 |
mechanisms and deployment scenarios (e.g., <a href="./rfc7596">RFC 7596</a> or <a href="./rfc7597">RFC 7597</a>), the |
| 19 |
operator needs to know the IPv6 address that the client will use as |
| 20 |
the source of an IPv4-in-IPv6 softwire tunnel. This address, in |
| 21 |
conjunction with the client's IPv4 address, and (in some deployments) |
| 22 |
the Port Set ID are used to create a binding table entry in the |
| 23 |
operator's softwire tunnel concentrator. This memo defines a DHCPv6 |
| 24 |
option to convey IPv6 parameters for establishing the softwire tunnel |
| 25 |
and a DHCPv4 option (to be used only with DHCP 4o6) to communicate |
| 26 |
the source tunnel IPv6 address between the DHCP 4o6 client and |
| 27 |
server. It is designed to work in conjunction with the IPv4 address |
| 28 |
allocation process. |
| 29 |
|
| 30 |
"DHCPv6 Options for Configuration of Softwire Address and Port-Mapped |
| 31 |
Clients" (<a href="./rfc7598">RFC 7598</a>) describes a deterministic DHCPv6-based mechanism |
| 32 |
for provisioning softwires. This document updates <a href="./rfc7598">RFC 7598</a>, allowing |
| 33 |
OPTION_S46_BR (90) to be enumerated in the DHCPv6 client's Option |
| 34 |
Request Option (ORO) request and to appear directly within subsequent |
| 35 |
messages sent by the DHCPv6 server. |
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Farrer, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 55 |
|
| 56 |
|
| 57 |
Status of This Memo |
| 58 |
|
| 59 |
This is an Internet Standards Track document. |
| 60 |
|
| 61 |
This document is a product of the Internet Engineering Task Force |
| 62 |
(IETF). It represents the consensus of the IETF community. It has |
| 63 |
received public review and has been approved for publication by the |
| 64 |
Internet Engineering Steering Group (IESG). Further information on |
| 65 |
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 66 |
|
| 67 |
Information about the current status of this document, any errata, |
| 68 |
and how to provide feedback on it may be obtained at |
| 69 |
<a href="https://www.rfc-editor.org/info/rfc8539">https://www.rfc-editor.org/info/rfc8539</a>. |
| 70 |
|
| 71 |
Copyright Notice |
| 72 |
|
| 73 |
Copyright (c) 2019 IETF Trust and the persons identified as the |
| 74 |
document authors. All rights reserved. |
| 75 |
|
| 76 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 77 |
Provisions Relating to IETF Documents |
| 78 |
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of |
| 79 |
publication of this document. Please review these documents |
| 80 |
carefully, as they describe your rights and restrictions with respect |
| 81 |
to this document. Code Components extracted from this document must |
| 82 |
include Simplified BSD License text as described in Section 4.e of |
| 83 |
the Trust Legal Provisions and are provided without warranty as |
| 84 |
described in the Simplified BSD License. |
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Farrer, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 116 |
<a href="#section-2">2</a>. Applicability . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 117 |
<a href="#section-3">3</a>. Requirements Language . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 118 |
<a href="#section-4">4</a>. Solution Overview . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 119 |
4.1. Updating <a href="./rfc7598">RFC 7598</a> to Permit the Reuse of |
| 120 |
OPTION_S46_BR (90) . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 121 |
<a href="#section-5">5</a>. DHCP 4o6 IPv6/IPv4 Binding Message Flow . . . . . . . . . . . <a href="#page-6">6</a> |
| 122 |
<a href="#section-6">6</a>. DHCP Options . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 123 |
<a href="#section-6.1">6.1</a>. DHCPv6 Softwire Source Binding Prefix Hint Option . . . . <a href="#page-7">7</a> |
| 124 |
<a href="#section-6.2">6.2</a>. DHCP 4o6 Softwire Source Address Option . . . . . . . . . <a href="#page-8">8</a> |
| 125 |
<a href="#section-7">7</a>. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 126 |
<a href="#section-7.1">7.1</a>. Client Initialization . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 127 |
7.2. Renewing or Rebinding the IPv4 Address Lease and |
| 128 |
Softwire Source Address . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 129 |
<a href="#section-7.2.1">7.2.1</a>. Changing the Bound IPv6 Softwire Source Address . . . <a href="#page-10">10</a> |
| 130 |
7.3. Releasing the IPv4 Address Lease and Softwire |
| 131 |
Source Address . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 132 |
<a href="#section-7.4">7.4</a>. OPTION_S46_BIND_IPV6_PREFIX Validation Behavior . . . . . <a href="#page-11">11</a> |
| 133 |
<a href="#section-7.5">7.5</a>. Client and Server Softwire Source Address Mismatch . . . <a href="#page-11">11</a> |
| 134 |
<a href="#section-7.6">7.6</a>. Use with Dynamic, Shared IPv4 Addresses . . . . . . . . . <a href="#page-12">12</a> |
| 135 |
<a href="#section-8">8</a>. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a> |
| 136 |
<a href="#section-8.1">8.1</a>. Changing the Bound IPv6 Source Address . . . . . . . . . <a href="#page-12">12</a> |
| 137 |
8.2. Handling Conflicts between Clients' Bound IPv6 Source |
| 138 |
Addresses . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a> |
| 139 |
<a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 140 |
<a href="#section-9.1">9.1</a>. Client Privacy Considerations . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 141 |
<a href="#section-10">10</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 142 |
<a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a> |
| 143 |
<a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a> |
| 144 |
<a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 145 |
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 146 |
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a> |
| 147 |
|
| 148 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 149 |
|
| 150 |
Deterministic IPv4-over-IPv6 transition technologies require that |
| 151 |
elements be preconfigured with binding rules for routing traffic to |
| 152 |
clients. This places a constraint on the choice of address used as |
| 153 |
the client's softwire source address: it must use a predetermined |
| 154 |
prefix, which is usually configured on the home gateway device. |
| 155 |
[<a href="./rfc7598" title=""DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"">RFC7598</a>] describes a DHCPv6-based mechanism for provisioning such |
| 156 |
deterministic softwires. |
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Farrer, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 167 |
|
| 168 |
|
| 169 |
A dynamic provisioning model, such as using DHCPv4 over DHCPv6 (DHCP |
| 170 |
4o6) [<a href="./rfc7341" title=""DHCPv4-over-DHCPv6 (DHCP 4o6) Transport"">RFC7341</a>], allows much more flexibility in the location of the |
| 171 |
IPv4-over-IPv6 softwire source address. In this model, the IPv6 |
| 172 |
address is dynamically communicated back to the service provider, |
| 173 |
allowing the corresponding softwire configuration to be created in |
| 174 |
the border relay (BR). |
| 175 |
|
| 176 |
The DHCP 4o6 client and softwire client could be run on end devices |
| 177 |
attached to a network segment using any routable IPv6 prefix |
| 178 |
allocated to an end user, located anywhere within an arbitrary home |
| 179 |
network topology. Dynamic allocation also helps to optimize IPv4 |
| 180 |
resource usage, because only clients that are actively renewing their |
| 181 |
IPv4 lease hold on to the address. |
| 182 |
|
| 183 |
This document describes a mechanism for dynamically provisioning |
| 184 |
softwires created using DHCP 4o6, including provisioning the client |
| 185 |
with the address of the softwire BR and informing the service |
| 186 |
provider of a client's binding between the dynamically allocated IPv4 |
| 187 |
address and Port Set ID and the IPv6 address that the softwire |
| 188 |
initiator will use for accessing IPv4-over-IPv6 services. |
| 189 |
|
| 190 |
The mechanism operates alongside the DHCP 4o6 message flows to |
| 191 |
communicate the binding information over the IPv6-only network. The |
| 192 |
DHCP 4o6 server provides a single point in the network that holds the |
| 193 |
current client binding information. The service provider can then |
| 194 |
use this binding information to provision other functional elements, |
| 195 |
such as the BR(s). |
| 196 |
|
| 197 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Applicability</span> |
| 198 |
|
| 199 |
The mechanism described in this document is only suitable for use for |
| 200 |
provisioning softwire clients via DHCP 4o6. The options described |
| 201 |
here are only applicable within the DHCP 4o6 message-exchange |
| 202 |
process. Current softwire technologies suitable for extending to |
| 203 |
incorporate DHCP 4o6 with dynamic IPv4 address leasing include |
| 204 |
[<a href="./rfc7597" title=""Mapping of Address and Port with Encapsulation (MAP-E)"">RFC7597</a>] and [<a href="./rfc7596" title=""Lightweight 4over6: An Extension to the Dual- Stack Lite Architecture"">RFC7596</a>]. |
| 205 |
|
| 206 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Requirements Language</span> |
| 207 |
|
| 208 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 209 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and |
| 210 |
"OPTIONAL" in this document are to be interpreted as described in |
| 211 |
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all |
| 212 |
capitals, as shown here. |
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Farrer, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Solution Overview</span> |
| 226 |
|
| 227 |
In order to provision a softwire, both IPv6 and IPv4 configurations |
| 228 |
need to be passed to the client. To map this to the DHCP 4o6 |
| 229 |
configuration process, the IPv6 configuration is carried in DHCPv6 |
| 230 |
options [<a href="./rfc8415" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC8415</a>], carried inside the DHCPv6 message DHCPV4-RESPONSE |
| 231 |
(21) sent by the server. OPTION_S46_BR (90) is used to provision the |
| 232 |
remote IPv6 address for the softwire BR (see <a href="#section-4.1">Section 4.1</a>). |
| 233 |
OPTION_S46_BIND_IPV6_PREFIX (137) is optionally sent by the DHCP 4o6 |
| 234 |
server to indicate to the client a preferred IPv6 prefix for binding |
| 235 |
the received IPv4 configuration and sourcing tunnel traffic. This |
| 236 |
may be necessary if there are multiple IPv6 prefixes in use in the |
| 237 |
customer network (e.g., Unique Local Addresses (ULAs)) or if the |
| 238 |
specific IPv4-over-IPv6 transition mechanism requires the use of a |
| 239 |
particular prefix for any reason. |
| 240 |
|
| 241 |
IPv4 configuration is carried in DHCPv4 messages [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] (inside |
| 242 |
the DHCP 4o6 option OPTION_DHCPV4_MSG (87)) using the mechanism |
| 243 |
described in [<a href="./rfc7341" title=""DHCPv4-over-DHCPv6 (DHCP 4o6) Transport"">RFC7341</a>]. |
| 244 |
|
| 245 |
In order for the client to communicate the softwire source address, a |
| 246 |
new DHCPv4 option OPTION_DHCP4O6_S46_SADDR (109) is defined in this |
| 247 |
document. This is included in DHCPREQUEST messages sent by the |
| 248 |
client and is stored by the server for the lifetime of the IPv4 |
| 249 |
address lease. |
| 250 |
|
| 251 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Updating <a href="./rfc7598">RFC 7598</a> to Permit the Reuse of OPTION_S46_BR (90)</span> |
| 252 |
|
| 253 |
<a href="./rfc7598#section-4.2">Section 4.2 of [RFC7598]</a> defines option OPTION_S46_BR (90) for |
| 254 |
communicating remote softwire BR IPv6 address(es) to a client, but it |
| 255 |
mandates that the option can only be used when encapsulated within |
| 256 |
one of the softwire container options: OPTION_S46_CONT_MAPE (94) or |
| 257 |
OPTION_S46_CONT_LW (96). From <a href="./rfc7598#section-3">Section 3 of [RFC7598]</a>: |
| 258 |
|
| 259 |
Softwire46 DHCPv6 clients that receive provisioning options that |
| 260 |
are not encapsulated in container options MUST silently ignore |
| 261 |
these options. |
| 262 |
|
| 263 |
This document updates [<a href="./rfc7598" title=""DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"">RFC7598</a>], removing this restriction for |
| 264 |
OPTION_S46_BR (90), allowing it to be enumerated in the client's ORO |
| 265 |
request and appear directly within subsequent messages sent by the |
| 266 |
DHCPv6 server. |
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Farrer, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. DHCP 4o6 IPv6/IPv4 Binding Message Flow</span> |
| 282 |
|
| 283 |
Figure 1 shows the relevant extensions to the successful DHCP 4o6 |
| 284 |
IPv4 allocation client/server message flow for the softwire source |
| 285 |
address function. The full process, including error handling, is |
| 286 |
described in <a href="#section-7">Section 7</a>. |
| 287 |
|
| 288 |
In each step, the DHCPv6 portion of the message and any relevant |
| 289 |
option is shown above the arrow. The DHCP 4o6 content of the message |
| 290 |
and its relevant options are below the arrow. All the DHCPv4 |
| 291 |
messages are encapsulated in DHCPV4-QUERY (20) or DHCPV4-RESPONSE |
| 292 |
(21) messages. Where relevant, the necessary options and their |
| 293 |
contents are shown. |
| 294 |
|
| 295 |
DHCP 4o6 DHCP 4o6 |
| 296 |
Client Server |
| 297 |
| | |
| 298 |
| DHCPv6 - DHCPV4-QUERY message containing | |
| 299 |
| OPTION_ORO (6) listing (90, 137) | |
| 300 |
Step 1 |----------------------------------------------------->| |
| 301 |
| DHCPv4 - DHCPDISCOVER message | |
| 302 |
| | |
| 303 |
| | |
| 304 |
| DHCPv6 - DHCPV4-RESPONSE message containing | |
| 305 |
| OPTION_S46_BR(90), OPTION_S46_BIND_IPV6_PREFIX(137) | |
| 306 |
| (bind-ipv6-prefix with service provider's | |
| 307 |
| preferred prefix) | |
| 308 |
Step 2 |<-----------------------------------------------------| |
| 309 |
| DHCPv4 - DHCPOFFER message | |
| 310 |
| containing an available IPv4 address | |
| 311 |
| | |
| 312 |
| DHCPv6 - DHCPV4-QUERY message | |
| 313 |
Step 3 |----------------------------------------------------->| |
| 314 |
| DHCPv4 - DHCPREQUEST message containing the | |
| 315 |
| requested IPv4 address and OPTION_DHCP4O6_S46_SADDR | |
| 316 |
| (softwire-ipv6-src-address with client's bound | |
| 317 |
| IPv6 softwire source address) | |
| 318 |
| | |
| 319 |
| | |
| 320 |
| DHCPv6 - DHCPV4-RESPONSE message | |
| 321 |
Step 4 |<-----------------------------------------------------| |
| 322 |
| DHCPv4 - DHCPACK message containing | |
| 323 |
| the leased IPv4 address and OPTION_DHCP4O6_S46_SADDR | |
| 324 |
| (softwire-ipv6-src-address with client's bound | |
| 325 |
| IPv6 softwire source address) | |
| 326 |
| | |
| 327 |
|
| 328 |
Figure 1: IPv6/IPv4 Binding Message Flow |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Farrer, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 335 |
|
| 336 |
|
| 337 |
Step 1 The client constructs a DHCPv6 "DHCPV4-QUERY (20)" message. |
| 338 |
This message contains two options: DHCPv6 OPTION_ORO (6) and |
| 339 |
OPTION_DHCPV4_MSG (87). OPTION_ORO lists "90" |
| 340 |
(OPTION_S46_BR) and "137" (OPTION_S46_BIND_IPV6_PREFIX). |
| 341 |
OPTION_DHCPV4_MSG contains a DHCPv4 DHCPDISCOVER message. |
| 342 |
|
| 343 |
Step 2 The server responds with a DHCPv6 "DHCPV4-RESPONSE (21)" |
| 344 |
message. This message contains an OPTION_S46_BR (90) |
| 345 |
containing the IPv6 address of the BR for the client's |
| 346 |
softwire configuration. The message may also optionally |
| 347 |
contain OPTION_S46_BIND_IPV6_PREFIX (137). OPTION_DHCPV4_MSG |
| 348 |
contains a DHCPv4 DHCPOFFER message. The DHCPv4 message |
| 349 |
contains an available IPv4 address. |
| 350 |
|
| 351 |
Step 3 The client sends a DHCPv6 "DHCPV4-QUERY (20)" message |
| 352 |
containing a DHCPv4 DHCPREQUEST message with the requested |
| 353 |
IPv4 address and OPTION_DHCP4O6_S46_SADDR (109) with the IPv6 |
| 354 |
address that the client will use as its softwire source |
| 355 |
address. |
| 356 |
|
| 357 |
Step 4 The server sends a DHCPv6 "DHCPV4-RESPONSE (21)" message. |
| 358 |
OPTION_DHCPV4_MSG contains a DHCPv4 DHCPACK message with the |
| 359 |
allocated IPv4 address. OPTION_DHCP4O6_S46_SADDR with the |
| 360 |
client's bound softwire source address is included. |
| 361 |
|
| 362 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. DHCP Options</span> |
| 363 |
|
| 364 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. DHCPv6 Softwire Source Binding Prefix Hint Option</span> |
| 365 |
|
| 366 |
The format of the DHCPv6 source binding prefix hint option is as |
| 367 |
follows: |
| 368 |
|
| 369 |
0 1 2 3 |
| 370 |
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 |
| 371 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 372 |
| OPTION_S46_BIND_IPV6_PREFIX | option-length | |
| 373 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 374 |
|bindprefix6-len| | |
| 375 |
+-+-+-+-+-+-+-+-+ bind-ipv6-prefix . |
| 376 |
. (variable length) . |
| 377 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 378 |
|
| 379 |
Figure 2: Format of OPTION_S46_BIND_IPV6_PREFIX |
| 380 |
|
| 381 |
o option-code: OPTION_S46_BIND_IPV6_PREFIX (137) |
| 382 |
|
| 383 |
o option-length: 1 + length of bind-ipv6-prefix, specified in bytes. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Farrer, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 391 |
|
| 392 |
|
| 393 |
o bindprefix6-len: 8-bit field expressing the bit mask length of the |
| 394 |
IPv6 prefix specified in bind-ipv6-prefix. Valid values are 0 to |
| 395 |
128. |
| 396 |
|
| 397 |
o bind-ipv6-prefix: The IPv6 prefix indicating the preferred prefix |
| 398 |
for the client to bind the received IPv4 configuration to. The |
| 399 |
length is (bindprefix6-len + 7) / 8. The field is padded on the |
| 400 |
right with zero bits up to the next octet boundary when |
| 401 |
bind-ipv6-prefix is not evenly divisible by 8. These padding bits |
| 402 |
are ignored by the receiver (see <a href="#section-7.4">Section 7.4</a>). |
| 403 |
|
| 404 |
OPTION_S46_BIND_IPV6_PREFIX is a singleton. Servers MUST NOT send |
| 405 |
more than one instance of the OPTION_S46_BIND_IPV6_PREFIX option. |
| 406 |
|
| 407 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. DHCP 4o6 Softwire Source Address Option</span> |
| 408 |
|
| 409 |
The format of the DHCPv4 over DHCPv6 softwire source address option |
| 410 |
is as follows: |
| 411 |
|
| 412 |
0 1 |
| 413 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 |
| 414 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |
| 415 |
| option-code | option-length | |
| 416 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |
| 417 |
+ softwire-ipv6-src-address + |
| 418 |
. (128 bits) . |
| 419 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |
| 420 |
|
| 421 |
Figure 3: Format of OPTION_DHCP4O6_S46_SADDR |
| 422 |
|
| 423 |
o option-code: OPTION_DHCP4O6_S46_SADDR (109) |
| 424 |
|
| 425 |
o option-length: 16. |
| 426 |
|
| 427 |
o softwire-ipv6-src-address: 16 bytes long; the IPv6 address that is |
| 428 |
associated (either being requested for binding or currently bound) |
| 429 |
with the client's IPv4 configuration. |
| 430 |
|
| 431 |
Note: The function of OPTION_DHCP4O6_S46_SADDR may seem similar to |
| 432 |
the DHCPv4 message's "chaddr" field or the Client Identifier (61) |
| 433 |
option in that it provides a unique lower-layer address that the |
| 434 |
server can use for identifying the client. However, as both of these |
| 435 |
are required to remain constant throughout the address lease |
| 436 |
lifetime, they cannot be used with the mechanism described in this |
| 437 |
document. This is because the client may only be able to construct |
| 438 |
the IPv6 address to use as the source address after it has received |
| 439 |
the first DHCPV4-RESPONSE message from the server containing |
| 440 |
OPTION_S46_BIND_IPV6_PREFIX. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Farrer, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Client Behavior</span> |
| 450 |
|
| 451 |
A client requiring dynamic softwire configuration first enables DHCP |
| 452 |
4o6 configuration using the method described in <a href="./rfc7341#section-5">Section 5 of |
| 453 |
[RFC7341]</a>. If OPTION_DHCP4_O_DHCP6_SERVER is received in the |
| 454 |
corresponding REPLY message, the client MAY continue with the |
| 455 |
configuration process described below. |
| 456 |
|
| 457 |
Before the dynamic softwire configuration process can commence, the |
| 458 |
client MUST be configured with a suitable IPv6 prefix to be used as |
| 459 |
the local softwire endpoint. This could be obtained using DHCPv6, |
| 460 |
Router Advertisement (RA) / Prefix Information Option (PIO), or |
| 461 |
another mechanism. |
| 462 |
|
| 463 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Client Initialization</span> |
| 464 |
|
| 465 |
When constructing the initial DHCP 4o6 DHCPDISCOVER message, the |
| 466 |
client includes a DHCPv6 OPTION_ORO (6) within the options field of |
| 467 |
the DHCP-QUERY message. OPTION_ORO contains the option codes for |
| 468 |
OPTION_S46_BR (90) and OPTION_S46_BIND_IPV6_PREFIX (137). |
| 469 |
|
| 470 |
On receipt of the DHCP 4o6 server's reply (a DHCPV4-RESPONSE |
| 471 |
containing a DHCPOFFER message), the client checks the contents of |
| 472 |
the DHCPv4-RESPONSE for the presence of a valid OPTION_S46_BR option. |
| 473 |
If this option is not present, or does not contain at least one valid |
| 474 |
IPv6 address for a BR, then the client MUST discard the message, as |
| 475 |
without the address of the BR the client cannot configure the |
| 476 |
softwire and so has no interface to request IPv4 configuration for. |
| 477 |
|
| 478 |
The DHCPV4-RESPONSE message may also include |
| 479 |
OPTION_S46_BIND_IPV6_PREFIX, which is used by the operator to |
| 480 |
indicate a preferred prefix that the client should bind IPv4 |
| 481 |
configuration to. If received, the client first checks the option |
| 482 |
according to <a href="#section-7.4">Section 7.4</a>. If valid, the client uses this prefix as |
| 483 |
the "IPv6 binding prefix" and follows to the process described in |
| 484 |
<a href="./rfc7596#section-5.1">Section 5.1 of [RFC7596]</a> in order to select an active IPv6 prefix to |
| 485 |
construct the softwire. If no match is found, or the client doesn't |
| 486 |
receive OPTION_S46_BIND_IPV6_PREFIX, the client MAY select any valid |
| 487 |
IPv6 prefix (of a suitable scope) to use as the tunnel source. |
| 488 |
|
| 489 |
Once the client has selected a suitable prefix, it MAY either use an |
| 490 |
existing IPv6 address that is already configured on an interface or |
| 491 |
create a new address specifically for use as the softwire source |
| 492 |
address (e.g., using an Interface Identifier constructed as per |
| 493 |
<a href="./rfc7597#section-6">Section 6 of [RFC7597]</a>). If a new address is being created, the |
| 494 |
client MUST complete configuration of the new address, performing |
| 495 |
duplicate address detection (if required) before proceeding. |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Farrer, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 503 |
|
| 504 |
|
| 505 |
The client then constructs a DHCPV4-QUERY message containing a DHCPv4 |
| 506 |
DHCPREQUEST message. OPTION_DHCP4O6_S46_SADDR is included in the |
| 507 |
options field of the DHCPREQUEST message with the IPv6 address of its |
| 508 |
softwire source address in the softwire-ipv6-src-address field. |
| 509 |
|
| 510 |
When the client receives a DHCPv4 DHCPACK message from the server, it |
| 511 |
checks the IPv6 address in OPTION_DHCP4O6_S46_SADDR against its |
| 512 |
active softwire source address. If they match, the allocation |
| 513 |
process has concluded. If there is a discrepancy, then the process |
| 514 |
described in <a href="#section-7.5">Section 7.5</a> is followed. |
| 515 |
|
| 516 |
If the client receives a DHCPv4 DHCPNAK message from the server, then |
| 517 |
the configuration process has been unsuccessful. The client then |
| 518 |
restarts the process from Step 1 of Figure 1. |
| 519 |
|
| 520 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Renewing or Rebinding the IPv4 Address Lease and Softwire Source</span> |
| 521 |
<span class="h3"> Address</span> |
| 522 |
|
| 523 |
Whenever the client attempts to extend the lease time of the IPv4 |
| 524 |
address, OPTION_DHCP4O6_S46_SADDR with the IPv6 address of its |
| 525 |
softwire source address in the softwire-ipv6-src-address field MUST |
| 526 |
be included in the DHCPREQUEST message. |
| 527 |
|
| 528 |
<span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a>. Changing the Bound IPv6 Softwire Source Address</span> |
| 529 |
|
| 530 |
Across the lifetime of the leased IPv4 address, it is possible that |
| 531 |
the client's IPv6 address will change, e.g., if there is an IPv6 |
| 532 |
renumbering event. |
| 533 |
|
| 534 |
In this situation, the client MUST inform the server of the new |
| 535 |
address. This is done by sending a DHCPREQUEST message containing |
| 536 |
OPTION_DHCP4O6_S46_SADDR with the new IPv6 source address. |
| 537 |
|
| 538 |
When the client receives a DHCPv4 DHCPACK message from the server, it |
| 539 |
checks the IPv6 address in OPTION_DHCP4O6_S46_SADDR against its |
| 540 |
active softwire source address. If they match, the allocation |
| 541 |
process has concluded. If there is a discrepancy, then the process |
| 542 |
described in <a href="#section-7.5">Section 7.5</a> is followed. |
| 543 |
|
| 544 |
If the client receives a DHCPv4 DHCPNAK message in response from the |
| 545 |
server, then the change of the bound IPv6 softwire source address has |
| 546 |
been unsuccessful. In this case, the client MUST stop using the new |
| 547 |
IPv6 source address. The client then restarts the process from Step |
| 548 |
1 of Figure 1. |
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Farrer, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Releasing the IPv4 Address Lease and Softwire Source Address</span> |
| 562 |
|
| 563 |
When the client no longer requires the IPv4 resource, it sends a |
| 564 |
DHCPv4 DHCPRELEASE message to the server. As the options field is |
| 565 |
unused in this message type, OPTION_DHCP4O6_S46_SADDR is not |
| 566 |
included. |
| 567 |
|
| 568 |
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. OPTION_S46_BIND_IPV6_PREFIX Validation Behavior</span> |
| 569 |
|
| 570 |
On receipt of the OPTION_S46_BIND_IPV6_PREFIX option, the client |
| 571 |
makes the following validation checks: |
| 572 |
|
| 573 |
o The received bindprefix6-len value is not larger than 128. |
| 574 |
|
| 575 |
o The number of bytes received in the bind-ipv6-prefix field is |
| 576 |
consistent with the received bindprefix6-len value (calculated as |
| 577 |
described in <a href="#section-6.1">Section 6.1</a>). |
| 578 |
|
| 579 |
If either check fails, the receiver discards the invalid option and |
| 580 |
proceeds to attempt configuration as if the option had not been |
| 581 |
received. |
| 582 |
|
| 583 |
The receiver MUST only use bits from the bind-ipv6-prefix field up to |
| 584 |
the value specified in the bindprefix6-len when performing the |
| 585 |
longest prefix match. bind-ipv6-prefix bits beyond this value MUST be |
| 586 |
ignored. |
| 587 |
|
| 588 |
<span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Client and Server Softwire Source Address Mismatch</span> |
| 589 |
|
| 590 |
If the client receives a DHCPACK message with an |
| 591 |
OPTION_DHCP4O6_S46_SADDR containing an IPv6 address that differs from |
| 592 |
its active softwire source address, the client SHOULD wait for a |
| 593 |
randomized time interval and then resend the DHCPREQUEST message with |
| 594 |
the correct softwire source address. <a href="./rfc2131#section-4.1">Section 4.1 of [RFC2131]</a> |
| 595 |
describes the retransmission backoff interval process. |
| 596 |
|
| 597 |
The default minimum time for the client to attempt retransmission is |
| 598 |
60 seconds. If, after this time has expired, the client has not |
| 599 |
received a DHCPACK message with the correct bound IPv6 address, |
| 600 |
client MAY send a DHCPRELEASE message and restart the process |
| 601 |
described in <a href="#section-7">Section 7</a>. The retry interval should be configurable |
| 602 |
and aligned with any server policy defining the minimum time interval |
| 603 |
for client address updates as described in <a href="#section-8.1">Section 8.1</a>. |
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Farrer, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h3"><a class="selflink" id="section-7.6" href="#section-7.6">7.6</a>. Use with Dynamic, Shared IPv4 Addresses</span> |
| 618 |
|
| 619 |
[<a id="ref-RFC7618">RFC7618</a>] describes a mechanism for using DHCPv4 to distribute |
| 620 |
dynamic, shared IPv4 addresses to clients. The mechanism described |
| 621 |
in this document is compatible with IPv4 address sharing and can be |
| 622 |
enabled by following the process described in <a href="./rfc7618#section-6">Section 6 of [RFC7618]</a>. |
| 623 |
|
| 624 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Server Behavior</span> |
| 625 |
|
| 626 |
Beyond the normal DHCP 4o6 functionality defined in [<a href="./rfc7341" title=""DHCPv4-over-DHCPv6 (DHCP 4o6) Transport"">RFC7341</a>], the |
| 627 |
server MUST also store the IPv6 softwire source address of the client |
| 628 |
in the leasing address database, alongside the IPv4 address and |
| 629 |
client identifier. |
| 630 |
|
| 631 |
An OPTION_DHCP4O6_S46_SADDR containing the bound softwire source |
| 632 |
address MUST be sent in every DHCPACK message sent by the server. |
| 633 |
|
| 634 |
The binding entry between the client's IPv6 softwire source address |
| 635 |
and the leased IPv4 address is valid as long as the IPv4 lease |
| 636 |
remains valid. |
| 637 |
|
| 638 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Changing the Bound IPv6 Source Address</span> |
| 639 |
|
| 640 |
In the event that the server receives a DHCPREQUEST message for an |
| 641 |
active IPv4 lease containing an OPTION_DHCP4O6_S46_SADDR with an IPv6 |
| 642 |
address that differs from the address that is currently stored, the |
| 643 |
server updates the stored softwire source address with the new |
| 644 |
address supplied by the client and sends a DHCPACK message containing |
| 645 |
the updated softwire source address in OPTION_DHCP4O6_S46_SADDR. |
| 646 |
|
| 647 |
The server MAY implement a policy enforcing a minimum time interval |
| 648 |
between a client updating its softwire source IPv6 address. If a |
| 649 |
client attempts to update the softwire source IPv6 address before the |
| 650 |
minimum time has expired, the server can either silently drop the |
| 651 |
client's message or send back a DHCPACK message containing the |
| 652 |
existing IPv6 address binding in OPTION_DHCP4O6_S46_SADDR. If |
| 653 |
implemented, the default minimum client source address update |
| 654 |
interval is 60 seconds. |
| 655 |
|
| 656 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Handling Conflicts between Clients' Bound IPv6 Source Addresses</span> |
| 657 |
|
| 658 |
In order for traffic to be forwarded correctly, each customer edge's |
| 659 |
(CE's) softwire IPv6 source address must be unique. To ensure this, |
| 660 |
on receipt of every client DHCPREQUEST message containing |
| 661 |
OPTION_DHCP4O6_S46_SADDR, the DHCP 4o6 server MUST check the received |
| 662 |
IPv6 address against all existing CE source addresses stored for |
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Farrer, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 671 |
|
| 672 |
|
| 673 |
active client IPv4 leases. If there is a match for any active lease |
| 674 |
other than the lease belonging to the client sending the DHCPREQUEST, |
| 675 |
then the client's IPv6 source address MUST NOT be stored or updated. |
| 676 |
|
| 677 |
Depending on where the client and server are in the address leasing |
| 678 |
lifecycle, the DHCP 4o6 server then takes the following action: |
| 679 |
|
| 680 |
o If the DHCP 4o6 does not have a current, active IPv4 address lease |
| 681 |
for the client, then the DHCP address allocation process has not |
| 682 |
been successful. The server returns a DHCPNAK message to the |
| 683 |
client. |
| 684 |
|
| 685 |
o If the DHCP 4o6 does have a current, active IPv4 address lease, |
| 686 |
then the source address update process (see <a href="#section-8.1">Section 8.1</a>) has not |
| 687 |
been successful. The DHCP 4o6 server can either silently drop the |
| 688 |
client's message or return a DHCPACK message containing the |
| 689 |
existing IPv6 address binding in OPTION_DHCP4O6_S46_SADDR. |
| 690 |
|
| 691 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span> |
| 692 |
|
| 693 |
Security considerations that are applicable to [<a href="./rfc7341" title=""DHCPv4-over-DHCPv6 (DHCP 4o6) Transport"">RFC7341</a>] are also |
| 694 |
applicable here. |
| 695 |
|
| 696 |
A rogue client could attempt to use the mechanism described in |
| 697 |
<a href="#section-7.2.1">Section 7.2.1</a> to redirect IPv4 traffic intended for another client to |
| 698 |
itself. This would be performed by sending a DHCPREQUEST message for |
| 699 |
another client's active IPv4 lease containing the attacker's softwire |
| 700 |
IPv6 address in OPTION_DHCP4O6_S46_SADDR. |
| 701 |
|
| 702 |
For such an attack to be effective, the attacker would need to know |
| 703 |
both the client identifier and the active IPv4 address lease |
| 704 |
currently in use by another client. This could be attempted in three |
| 705 |
ways: |
| 706 |
|
| 707 |
1. One customer learning the active IPv4 address lease and client |
| 708 |
identifier of another customer via snooping the DHCP4o6 message |
| 709 |
flow between the client and server. The mechanism described in |
| 710 |
this document is intended for use in a typical ISP network |
| 711 |
topology with a dedicated Layer 2 access network per client, |
| 712 |
meaning that snooping of another client's traffic is not |
| 713 |
possible. If the access network is a shared medium, then |
| 714 |
provisioning softwire clients using dynamic DHCP4o6 as described |
| 715 |
here is NOT RECOMMENDED. |
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Farrer, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 727 |
|
| 728 |
|
| 729 |
2. Learning the active IPv4 address lease and client identifier via |
| 730 |
snooping the DHCP4o6 message flow between the client and server |
| 731 |
in the aggregation or core ISP network. In this case, the |
| 732 |
attacker requires a level of access to the ISP's infrastructure |
| 733 |
that means they can already intercept or interfere with traffic |
| 734 |
flows to the client. |
| 735 |
|
| 736 |
3. An attacker attempting to brute-force guess the IPv4 lease |
| 737 |
address and client identifier tuple. The risk of this can be |
| 738 |
reduced by using a client identifier format that is not easily |
| 739 |
guessable, e.g., by using a random-based client identifier (see |
| 740 |
<a href="./rfc7844#section-3.5">Section 3.5 of [RFC7844]</a>). |
| 741 |
|
| 742 |
An attacker could attempt to redirect existing flows to a client |
| 743 |
unable to process the traffic. This type of attack can be prevented |
| 744 |
by implementing network ingress filtering [<a href="#ref-BCP38" title=""Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing"">BCP38</a>] in conjunction with |
| 745 |
the BR source address validation processes described in <a href="./rfc7596#section-5.2">[RFC7596] |
| 746 |
Section 5.2</a> and <a href="./rfc7597#section-8.1">[RFC7597] Section 8.1</a>. |
| 747 |
|
| 748 |
A client may attempt to overload the server by sending multiple |
| 749 |
source address update messages (see <a href="#section-7.2.1">Section 7.2.1</a>) in a short time |
| 750 |
frame. This risk can be reduced by implementing a server policy |
| 751 |
enforcing a minimum time interval between client address changes, as |
| 752 |
described in <a href="#section-8.1">Section 8.1</a>. |
| 753 |
|
| 754 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Client Privacy Considerations</span> |
| 755 |
|
| 756 |
[<a id="ref-RFC7844">RFC7844</a>] describes anonymity profiles for DHCP clients. These |
| 757 |
considerations and recommendations are also applicable to clients |
| 758 |
implementing the mechanism described in this document. As DHCP 4o6 |
| 759 |
only uses DHCPv6 as a stateless transport for DHCPv4 messages, the |
| 760 |
"Anonymity Profile for DHCPv4" described in <a href="#section-3">Section 3</a> is most |
| 761 |
relevant here. |
| 762 |
|
| 763 |
In addition to the considerations given in [<a href="./rfc7844" title=""Anonymity Profiles for DHCP Clients"">RFC7844</a>], the mechanism |
| 764 |
that the client uses for constructing the interface identifier for |
| 765 |
its IPv6 softwire source address (see <a href="#section-7.1">Section 7.1</a>) could result in |
| 766 |
the device being trackable across different networks and sessions, |
| 767 |
e.g., if the client's softwire Interface Identifier (IID) is |
| 768 |
immutable. |
| 769 |
|
| 770 |
This can be mitigated by constructing the softwire source IPv6 |
| 771 |
address as per <a href="./rfc7597#section-6">Section 6 of [RFC7597]</a>. Here, the address's IID |
| 772 |
contains only the allocated IPv4 address (and port set identifier if |
| 773 |
[<a href="./rfc7618" title=""Dynamic Allocation of Shared IPv4 Addresses"">RFC7618</a>] is being used). This means no additional client |
| 774 |
information is exposed to the DHCP 4o6 server; it also means that the |
| 775 |
IID will change as the leased IPv4 address changes (e.g., between |
| 776 |
sessions when <a href="./rfc7844#section-3.5">Section 3.5 of [RFC7844]</a> is implemented). |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Farrer, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span> |
| 786 |
|
| 787 |
IANA has assigned the OPTION_S46_BIND_IPV6_PREFIX (137) option code |
| 788 |
from the DHCPv6 "Option Codes" registry maintained at |
| 789 |
<<a href="http://www.iana.org/assignments/dhcpv6-parameters">http://www.iana.org/assignments/dhcpv6-parameters</a>> as follows: |
| 790 |
|
| 791 |
Value: 137 |
| 792 |
Description: OPTION_S46_BIND_IPV6_PREFIX |
| 793 |
Client ORO: Yes |
| 794 |
Singleton Option: Yes |
| 795 |
Reference: <a href="./rfc8539">RFC 8539</a> |
| 796 |
|
| 797 |
IANA has assigned the OPTION_DHCP4O6_S46_SADDR (109) option code from |
| 798 |
the "BOOTP Vendor Extensions and DHCP Options" registry maintained at |
| 799 |
<<a href="http://www.iana.org/assignments/bootp-dhcp-parameters">http://www.iana.org/assignments/bootp-dhcp-parameters</a>> as follows: |
| 800 |
|
| 801 |
Tag: 109 |
| 802 |
Name: OPTION_DHCP4O6_S46_SADDR |
| 803 |
Data Length: 16 |
| 804 |
Meaning: DHCPv4 over DHCPv6 Softwire Source Address Option |
| 805 |
Reference: <a href="./rfc8539">RFC 8539</a> |
| 806 |
|
| 807 |
IANA has updated the entry for DHCPv6 OPTION_S46_BR (90) in the |
| 808 |
"Option Codes" registry maintained at |
| 809 |
<<a href="https://www.iana.org/assignments/dhcpv6-parameters">https://www.iana.org/assignments/dhcpv6-parameters</a>> as follows: |
| 810 |
|
| 811 |
Old Entry: |
| 812 |
|
| 813 |
Value: 90 |
| 814 |
Description: OPTION_S46_BR |
| 815 |
Client ORO: No |
| 816 |
Singleton Option: No |
| 817 |
Reference: [<a href="./rfc7598" title=""DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"">RFC7598</a>] |
| 818 |
|
| 819 |
New Entry: |
| 820 |
|
| 821 |
Value: 90 |
| 822 |
Description: OPTION_S46_BR |
| 823 |
Client ORO: Yes |
| 824 |
Singleton Option: No |
| 825 |
Reference: [<a href="./rfc7598" title=""DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"">RFC7598</a>], [<a href="./rfc8539">RFC8539</a>] |
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Farrer, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span> |
| 842 |
|
| 843 |
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span> |
| 844 |
|
| 845 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 846 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, |
| 847 |
DOI 10.17487/RFC2119, March 1997, |
| 848 |
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>. |
| 849 |
|
| 850 |
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol", |
| 851 |
<a href="./rfc2131">RFC 2131</a>, DOI 10.17487/RFC2131, March 1997, |
| 852 |
<<a href="https://www.rfc-editor.org/info/rfc2131">https://www.rfc-editor.org/info/rfc2131</a>>. |
| 853 |
|
| 854 |
[<a id="ref-RFC7341">RFC7341</a>] Sun, Q., Cui, Y., Siodelski, M., Krishnan, S., and I. |
| 855 |
Farrer, "DHCPv4-over-DHCPv6 (DHCP 4o6) Transport", |
| 856 |
<a href="./rfc7341">RFC 7341</a>, DOI 10.17487/RFC7341, August 2014, |
| 857 |
<<a href="https://www.rfc-editor.org/info/rfc7341">https://www.rfc-editor.org/info/rfc7341</a>>. |
| 858 |
|
| 859 |
[<a id="ref-RFC7598">RFC7598</a>] Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec, |
| 860 |
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for |
| 861 |
Configuration of Softwire Address and Port-Mapped |
| 862 |
Clients", <a href="./rfc7598">RFC 7598</a>, DOI 10.17487/RFC7598, July 2015, |
| 863 |
<<a href="https://www.rfc-editor.org/info/rfc7598">https://www.rfc-editor.org/info/rfc7598</a>>. |
| 864 |
|
| 865 |
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a> |
| 866 |
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174, |
| 867 |
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>. |
| 868 |
|
| 869 |
[<a id="ref-RFC8415">RFC8415</a>] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A., |
| 870 |
Richardson, M., Jiang, S., Lemon, T., and T. Winters, |
| 871 |
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", |
| 872 |
<a href="./rfc8415">RFC 8415</a>, DOI 10.17487/RFC8415, November 2018, |
| 873 |
<<a href="https://www.rfc-editor.org/info/rfc8415">https://www.rfc-editor.org/info/rfc8415</a>>. |
| 874 |
|
| 875 |
|
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Farrer, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span> |
| 898 |
|
| 899 |
[<a id="ref-BCP38">BCP38</a>] Ferguson, P. and D. Senie, "Network Ingress Filtering: |
| 900 |
Defeating Denial of Service Attacks which employ IP Source |
| 901 |
Address Spoofing", <a href="https://www.rfc-editor.org/bcp/bcp38">BCP 38</a>, <a href="./rfc2827">RFC 2827</a>, May 2000, |
| 902 |
<<a href="https://www.rfc-editor.org/info/bcp38">https://www.rfc-editor.org/info/bcp38</a>>. |
| 903 |
|
| 904 |
[<a id="ref-RFC7596">RFC7596</a>] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. |
| 905 |
Farrer, "Lightweight 4over6: An Extension to the Dual- |
| 906 |
Stack Lite Architecture", <a href="./rfc7596">RFC 7596</a>, DOI 10.17487/RFC7596, |
| 907 |
July 2015, <<a href="https://www.rfc-editor.org/info/rfc7596">https://www.rfc-editor.org/info/rfc7596</a>>. |
| 908 |
|
| 909 |
[<a id="ref-RFC7597">RFC7597</a>] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., |
| 910 |
Murakami, T., and T. Taylor, Ed., "Mapping of Address and |
| 911 |
Port with Encapsulation (MAP-E)", <a href="./rfc7597">RFC 7597</a>, |
| 912 |
DOI 10.17487/RFC7597, July 2015, |
| 913 |
<<a href="https://www.rfc-editor.org/info/rfc7597">https://www.rfc-editor.org/info/rfc7597</a>>. |
| 914 |
|
| 915 |
[<a id="ref-RFC7618">RFC7618</a>] Cui, Y., Sun, Q., Farrer, I., Lee, Y., Sun, Q., and M. |
| 916 |
Boucadair, "Dynamic Allocation of Shared IPv4 Addresses", |
| 917 |
<a href="./rfc7618">RFC 7618</a>, DOI 10.17487/RFC7618, August 2015, |
| 918 |
<<a href="https://www.rfc-editor.org/info/rfc7618">https://www.rfc-editor.org/info/rfc7618</a>>. |
| 919 |
|
| 920 |
[<a id="ref-RFC7844">RFC7844</a>] Huitema, C., Mrugalski, T., and S. Krishnan, "Anonymity |
| 921 |
Profiles for DHCP Clients", <a href="./rfc7844">RFC 7844</a>, |
| 922 |
DOI 10.17487/RFC7844, May 2016, |
| 923 |
<<a href="https://www.rfc-editor.org/info/rfc7844">https://www.rfc-editor.org/info/rfc7844</a>>. |
| 924 |
|
| 925 |
Acknowledgements |
| 926 |
|
| 927 |
The authors would like to thank Ted Lemon, Lishan Li, Tatuya Jinmei, |
| 928 |
Jonas Gorski, and Razvan Becheriu for their contributions and |
| 929 |
comments. |
| 930 |
|
| 931 |
|
| 932 |
|
| 933 |
|
| 934 |
|
| 935 |
|
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Farrer, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc8539">RFC 8539</a> Softwire Provisioning with DHCP 4o6 March 2019</span> |
| 951 |
|
| 952 |
|
| 953 |
Authors' Addresses |
| 954 |
|
| 955 |
Ian Farrer |
| 956 |
Deutsche Telekom AG |
| 957 |
Landgrabenweg 151 |
| 958 |
Bonn, NRW 53227 |
| 959 |
Germany |
| 960 |
|
| 961 |
Email: [email protected] |
| 962 |
|
| 963 |
|
| 964 |
Qi Sun |
| 965 |
Tsinghua University |
| 966 |
Beijing 100084 |
| 967 |
China |
| 968 |
|
| 969 |
Phone: +86-10-6278-5822 |
| 970 |
Email: [email protected] |
| 971 |
|
| 972 |
|
| 973 |
Yong Cui |
| 974 |
Tsinghua University |
| 975 |
Beijing 100084 |
| 976 |
China |
| 977 |
|
| 978 |
Phone: +86-10-6260-3059 |
| 979 |
Email: [email protected] |
| 980 |
|
| 981 |
|
| 982 |
Linhui Sun |
| 983 |
Tsinghua University |
| 984 |
Beijing 100084 |
| 985 |
China |
| 986 |
|
| 987 |
Phone: +86-10-6278-5822 |
| 988 |
Email: [email protected] |
| 989 |
|
| 990 |
|
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
Farrer, et al. Standards Track [Page 18] |
| 1005 |
</pre> |