| 1 |
<pre>Internet Engineering Task Force (IETF) P. Eronen |
| 2 |
Request for Comments: 5739 Nokia |
| 3 |
Category: Experimental J. Laganier |
| 4 |
ISSN: 2070-1721 QUALCOMM, Inc. |
| 5 |
C. Madson |
| 6 |
Cisco Systems |
| 7 |
February 2010 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)</span> |
| 11 |
|
| 12 |
Abstract |
| 13 |
|
| 14 |
When Internet Key Exchange Protocol version 2 (IKEv2) is used for |
| 15 |
remote VPN access (client to VPN gateway), the gateway assigns the |
| 16 |
client an IP address from the internal network using IKEv2 |
| 17 |
configuration payloads. The configuration payloads specified in <a href="./rfc4306">RFC</a> |
| 18 |
<a href="./rfc4306">4306</a> work well for IPv4 but make it difficult to use certain features |
| 19 |
of IPv6. This document specifies new configuration attributes for |
| 20 |
IKEv2 that allows the VPN gateway to assign IPv6 prefixes to clients, |
| 21 |
enabling all features of IPv6 to be used with the client-gateway |
| 22 |
"virtual link". |
| 23 |
|
| 24 |
Status of This Memo |
| 25 |
|
| 26 |
This document is not an Internet Standards Track specification; it is |
| 27 |
published for examination, experimental implementation, and |
| 28 |
evaluation. |
| 29 |
|
| 30 |
This document defines an Experimental Protocol for the Internet |
| 31 |
community. This document is a product of the Internet Engineering |
| 32 |
Task Force (IETF). It represents the consensus of the IETF |
| 33 |
community. It has received public review and has been approved for |
| 34 |
publication by the Internet Engineering Steering Group (IESG). Not |
| 35 |
all documents approved by the IESG are a candidate for any level of |
| 36 |
Internet Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 37 |
|
| 38 |
Information about the current status of this document, any errata, |
| 39 |
and how to provide feedback on it may be obtained at |
| 40 |
<a href="http://www.rfc-editor.org/info/rfc5739">http://www.rfc-editor.org/info/rfc5739</a>. |
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Eronen, et al. Experimental [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2010 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
This document may contain material from IETF Documents or IETF |
| 73 |
Contributions published or made publicly available before November |
| 74 |
10, 2008. The person(s) controlling the copyright in some of this |
| 75 |
material may not have granted the IETF Trust the right to allow |
| 76 |
modifications of such material outside the IETF Standards Process. |
| 77 |
Without obtaining an adequate license from the person(s) controlling |
| 78 |
the copyright in such materials, this document may not be modified |
| 79 |
outside the IETF Standards Process, and derivative works of it may |
| 80 |
not be created outside the IETF Standards Process, except to format |
| 81 |
it for publication as an RFC or to translate it into languages other |
| 82 |
than English. |
| 83 |
|
| 84 |
|
| 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">Eronen, et al. Experimental [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction and Problem Statement ..............................<a href="#page-4">4</a> |
| 116 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-5">5</a> |
| 117 |
<a href="#section-3">3</a>. Current Limitations and Goals ...................................<a href="#page-6">6</a> |
| 118 |
<a href="#section-3.1">3.1</a>. Multiple Prefixes ..........................................<a href="#page-6">6</a> |
| 119 |
<a href="#section-3.2">3.2</a>. Link-Local Addresses .......................................<a href="#page-6">6</a> |
| 120 |
<a href="#section-3.3">3.3</a>. Interface Identifier Selection .............................<a href="#page-7">7</a> |
| 121 |
<a href="#section-3.4">3.4</a>. Sharing VPN Access .........................................<a href="#page-7">7</a> |
| 122 |
<a href="#section-3.5">3.5</a>. General Goals ..............................................<a href="#page-8">8</a> |
| 123 |
<a href="#section-3.6">3.6</a>. Non-Goals ..................................................<a href="#page-8">8</a> |
| 124 |
<a href="#section-3.7">3.7</a>. Additional Information .....................................<a href="#page-9">9</a> |
| 125 |
<a href="#section-4">4</a>. Solution Details ................................................<a href="#page-9">9</a> |
| 126 |
<a href="#section-4.1">4.1</a>. Initial Exchanges ..........................................<a href="#page-9">9</a> |
| 127 |
<a href="#section-4.2">4.2</a>. Reauthentication ..........................................<a href="#page-11">11</a> |
| 128 |
<a href="#section-4.3">4.3</a>. Creating CHILD_SAs ........................................<a href="#page-11">11</a> |
| 129 |
<a href="#section-4.4">4.4</a>. Relationship to Neighbor Discovery ........................<a href="#page-12">12</a> |
| 130 |
<a href="#section-4.5">4.5</a>. Relationship to Existing IKEv2 Payloads ...................<a href="#page-13">13</a> |
| 131 |
<a href="#section-5">5</a>. Payload Formats ................................................<a href="#page-13">13</a> |
| 132 |
<a href="#section-5.1">5.1</a>. INTERNAL_IP6_LINK Configuration Attribute .................<a href="#page-13">13</a> |
| 133 |
<a href="#section-5.2">5.2</a>. INTERNAL_IP6_PREFIX Configuration Attribute ...............<a href="#page-14">14</a> |
| 134 |
<a href="#section-5.3">5.3</a>. LINK_ID Notify Payload ....................................<a href="#page-14">14</a> |
| 135 |
<a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-15">15</a> |
| 136 |
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-15">15</a> |
| 137 |
<a href="#section-8">8</a>. Acknowledgments ................................................<a href="#page-15">15</a> |
| 138 |
<a href="#section-9">9</a>. References .....................................................<a href="#page-16">16</a> |
| 139 |
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-16">16</a> |
| 140 |
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-16">16</a> |
| 141 |
<a href="#appendix-A">Appendix A</a>. Design Rationale (Non-Normative) ...................<a href="#page-19">19</a> |
| 142 |
<a href="#appendix-A.1">A.1</a>. Link Model ................................................<a href="#page-20">20</a> |
| 143 |
<a href="#appendix-A.2">A.2</a>. Distributing Prefix Information ...........................<a href="#page-20">20</a> |
| 144 |
<a href="#appendix-A.3">A.3</a>. Unique Address Allocation .................................<a href="#page-21">21</a> |
| 145 |
<a href="#appendix-A.4">A.4</a>. Layer 3 Access Control ....................................<a href="#page-21">21</a> |
| 146 |
<a href="#appendix-A.5">A.5</a>. Other Considerations ......................................<a href="#page-22">22</a> |
| 147 |
<a href="#appendix-A.6">A.6</a>. Alternative Solution Sketches .............................<a href="#page-24">24</a> |
| 148 |
<a href="#appendix-A.6.1">A.6.1</a>. Version -00 Sketch ..................................<a href="#page-24">24</a> |
| 149 |
<a href="#appendix-A.6.2">A.6.2</a>. Router Aggregation Sketch #1 ..........................<a href="#page-25">25</a> |
| 150 |
<a href="#appendix-A.6.3">A.6.3</a>. Router Aggregation Sketch #2 ..........................<a href="#page-27">27</a> |
| 151 |
<a href="#appendix-A.6.4">A.6.4</a>. IPv4-Like Sketch ....................................<a href="#page-28">28</a> |
| 152 |
<a href="#appendix-A.6.5">A.6.5</a>. Sketch Based on <a href="./rfc3456">RFC 3456</a> ..............................<a href="#page-30">30</a> |
| 153 |
<a href="#appendix-B">Appendix B</a>. Evaluation (Non-Normative) .........................<a href="#page-31">31</a> |
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Eronen, et al. Experimental [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction and Problem Statement</span> |
| 170 |
|
| 171 |
In typical remote access VPN use (client to VPN gateway), the client |
| 172 |
needs an IP address in the network protected by the security gateway. |
| 173 |
IKEv2 includes a feature called "configuration payloads" that allows |
| 174 |
the gateway to dynamically assign a temporary address to the client |
| 175 |
[<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>]. |
| 176 |
|
| 177 |
For IPv4, the message exchange would look as follows: |
| 178 |
|
| 179 |
Client Gateway |
| 180 |
-------- --------- |
| 181 |
|
| 182 |
HDR(IKE_SA_INIT), SAi1, KEi, Ni --> |
| 183 |
|
| 184 |
<-- HDR(IKE_SA_INIT), SAr1, KEr, Nr, [CERTREQ] |
| 185 |
|
| 186 |
HDR(IKE_AUTH), |
| 187 |
SK { IDi, CERT, [CERTREQ], AUTH, [IDr], |
| 188 |
CP(CFG_REQUEST) = |
| 189 |
{ INTERNAL_IP4_ADDRESS(), |
| 190 |
INTERNAL_IP4_DNS() }, SAi2, |
| 191 |
TSi = (0, 0-65535, 0.0.0.0-255.255.255.255), |
| 192 |
TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) } --> |
| 193 |
|
| 194 |
<-- HDR(IKE_AUTH), |
| 195 |
SK { IDr, CERT, AUTH, |
| 196 |
CP(CFG_REPLY) = |
| 197 |
{ INTERNAL_IP4_ADDRESS(192.0.2.234), |
| 198 |
INTERNAL_IP4_DNS(198.51.100.33) }, |
| 199 |
SAr2, |
| 200 |
TSi = (0, 0-65535, 192.0.2.234-192.0.2.234), |
| 201 |
TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) } |
| 202 |
|
| 203 |
Figure 1: IPv4 Configuration |
| 204 |
|
| 205 |
The IPv4 case has been implemented by various vendors and, in |
| 206 |
general, works well. IKEv2 also defines almost identical |
| 207 |
configuration payloads for IPv6: |
| 208 |
|
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Eronen, et al. Experimental [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 223 |
|
| 224 |
|
| 225 |
Client Gateway |
| 226 |
-------- --------- |
| 227 |
|
| 228 |
HDR(IKE_AUTH), |
| 229 |
SK { IDi, CERT, [CERTREQ], AUTH, [IDr], |
| 230 |
CP(CFG_REQUEST) = |
| 231 |
{ INTERNAL_IP6_ADDRESS(), |
| 232 |
INTERNAL_IP6_DNS() }, SAi2, |
| 233 |
TSi = (0, 0-65535, |
| 234 |
0:0:0:0:0:0:0:0 - |
| 235 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF), |
| 236 |
TSr = (0, |
| 237 |
0-65535, 0:0:0:0:0:0:0:0 - |
| 238 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) } --> |
| 239 |
|
| 240 |
<-- HDR(IKE_AUTH), |
| 241 |
SK { IDr, CERT, AUTH, |
| 242 |
CP(CFG_REPLY) = |
| 243 |
{ INTERNAL_IP6_ADDRESS(2001:DB8:0:1:2:3:4:5, |
| 244 |
64), |
| 245 |
INTERNAL_IP6_DNS(2001:DB8:9:8:7:6:5:4) }, |
| 246 |
SAr2, |
| 247 |
TSi = (0, 0-65535, |
| 248 |
2001:DB8:0:1:2:3:4:5 - |
| 249 |
2001:DB8:0:1:2:3:4:5), |
| 250 |
TSr = (0, 0-65535, |
| 251 |
0:0:0:0:0:0:0:0 - |
| 252 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) } |
| 253 |
|
| 254 |
Figure 2: IPv6 Configuration |
| 255 |
|
| 256 |
In other words, IPv6 is basically treated as IPv4 with larger |
| 257 |
addresses. As noted in [<a href="./rfc4718" title=""IKEv2 Clarifications and Implementation Guidelines"">RFC4718</a>], this does not fully follow the |
| 258 |
"normal IPv6 way of doing things", and it complicates or prevents |
| 259 |
using certain features of IPv6. <a href="#section-3">Section 3</a> describes the limitations |
| 260 |
in detail. |
| 261 |
|
| 262 |
This document specifies new configuration attributes for IKEv2 that |
| 263 |
allows the VPN gateway to assign IPv6 prefixes to clients, enabling |
| 264 |
all features of IPv6 to be used with the client-gateway "virtual |
| 265 |
link". |
| 266 |
|
| 267 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 268 |
|
| 269 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 270 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 271 |
document are to be interpreted as described in [<a href="#ref-KEYWORDS" title=""Key words for use in RFCs to Indicate Requirement Levels"">KEYWORDS</a>]. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Eronen, et al. Experimental [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 279 |
|
| 280 |
|
| 281 |
When messages containing IKEv2 payloads are described, optional |
| 282 |
payloads are shown in brackets (for instance, "[FOO]"); a plus sign |
| 283 |
indicates that a payload can be repeated one or more times (for |
| 284 |
instance, "FOO+"). |
| 285 |
|
| 286 |
This document uses the term "virtual interface" when describing how |
| 287 |
the client uses the IPv6 address(es) assigned by the gateway. While |
| 288 |
existing IPsec documents do not use this term, it is not a new |
| 289 |
concept. In order to use the address assigned by the VPN gateway, |
| 290 |
current VPN clients already create a local "virtual interface", as |
| 291 |
only addresses assigned to interfaces can be used, e.g., as source |
| 292 |
addresses for TCP connections. Note that this definition of |
| 293 |
"interface" is not necessarily identical with what some particular |
| 294 |
implementations call "interface". |
| 295 |
|
| 296 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Current Limitations and Goals</span> |
| 297 |
|
| 298 |
This section describes the limitations of the current IPv6 |
| 299 |
configuration mechanism and requirements for the new solution. |
| 300 |
|
| 301 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Multiple Prefixes</span> |
| 302 |
|
| 303 |
In Figure 2, only a single IPv6 address (from a single prefix) is |
| 304 |
assigned. The specification does allow the client to include |
| 305 |
multiple INTERNAL_IP6_ADDRESS attributes in its request, but the |
| 306 |
gateway cannot assign more addresses than the client requested. |
| 307 |
|
| 308 |
Multiple prefixes are useful for site renumbering, host-based site |
| 309 |
multihoming [<a href="#ref-SHIM6" title=""Shim6: Level 3 Multihoming Shim Protocol for IPv6"">SHIM6</a>], and unique local IPv6 addresses [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>]. In |
| 310 |
all of these cases, the gateway has better information on how many |
| 311 |
different addresses (from different prefixes) the client should be |
| 312 |
assigned. |
| 313 |
|
| 314 |
The solution should support assigning addresses from multiple |
| 315 |
prefixes, without requiring the client to know beforehand how many |
| 316 |
prefixes are needed. |
| 317 |
|
| 318 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Link-Local Addresses</span> |
| 319 |
|
| 320 |
The IPv6 addressing architecture [<a href="#ref-IPv6Addr" title=""IP Version 6 Addressing Architecture"">IPv6Addr</a>] specifies that "IPv6 |
| 321 |
addresses of all types are assigned to interfaces, not nodes. [..] |
| 322 |
All interfaces are required to have at least one Link-Local unicast |
| 323 |
address". |
| 324 |
|
| 325 |
Currently, the virtual interface created by IKEv2 configuration |
| 326 |
payloads does not have link-local addresses. This violates the |
| 327 |
requirements in [<a href="#ref-IPv6Addr" title=""IP Version 6 Addressing Architecture"">IPv6Addr</a>] and prevents the use of protocols that |
| 328 |
require link-local addresses, such as [<a href="#ref-MLDv2" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">MLDv2</a>] and [<a href="#ref-DHCPv6" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">DHCPv6</a>]. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Eronen, et al. Experimental [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 335 |
|
| 336 |
|
| 337 |
The solution should assign link-local addresses to the virtual |
| 338 |
interfaces and allow them to be used for protocols between the VPN |
| 339 |
client and gateway. |
| 340 |
|
| 341 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Interface Identifier Selection</span> |
| 342 |
|
| 343 |
In the message exchange shown in Figure 2, the gateway chooses the |
| 344 |
interface ID used by the client. It is also possible for the client |
| 345 |
to request a specific interface ID; the gateway then chooses the |
| 346 |
prefix part. |
| 347 |
|
| 348 |
This approach complicates the use of Cryptographically Generated |
| 349 |
Addresses (CGAs) [<a href="#ref-CGA" title=""Cryptographically Generated Addresses (CGA)"">CGA</a>]. With CGAs, the interface ID cannot be |
| 350 |
calculated before the prefix is known. The client could first obtain |
| 351 |
a non-CGA address to determine the prefix and then send a separate |
| 352 |
CFG_REQUEST to obtain a CGA address with the same prefix. However, |
| 353 |
this approach requires that the IKEv2 software component provide an |
| 354 |
interface to the component managing CGAs; an ugly implementation |
| 355 |
dependency that would be best avoided. |
| 356 |
|
| 357 |
Similar concerns apply to other cases where the client has some |
| 358 |
interest in what interface ID is being used, such as Hash-Based |
| 359 |
Addresses [<a href="#ref-HBA" title=""Hash-Based Addresses (HBA)"">HBA</a>] and privacy addresses [<a href="./rfc4941" title=""Privacy Extensions for Stateless Address Autoconfiguration in IPv6"">RFC4941</a>]. |
| 360 |
|
| 361 |
Without CGAs and HBAs, VPN clients are not able to fully use IPv6 |
| 362 |
features such as [<a href="#ref-SHIM6" title=""Shim6: Level 3 Multihoming Shim Protocol for IPv6"">SHIM6</a>] or enhanced Mobile IPv6 route optimization |
| 363 |
[<a href="./rfc4866" title=""Enhanced Route Optimization for Mobile IPv6"">RFC4866</a>]. |
| 364 |
|
| 365 |
The solution should allow the VPN client to easily obtain several |
| 366 |
addresses from a given prefix, where the interface IDs are selected |
| 367 |
by the client and may depend on the prefix. |
| 368 |
|
| 369 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Sharing VPN Access</span> |
| 370 |
|
| 371 |
Some VPN clients may want to share the VPN connection with other |
| 372 |
devices (e.g., from a cell phone to a laptop or vice versa) via some |
| 373 |
local area network connection (such as Wireless LAN or Bluetooth), if |
| 374 |
allowed by the security policy. |
| 375 |
|
| 376 |
Quite obviously, sharing of VPN access requires more than one address |
| 377 |
(unless NAT is used). However, the current model where each address |
| 378 |
is requested separately is probably complex to integrate with a local |
| 379 |
area network that uses stateless address autoconfiguration |
| 380 |
[<a href="#ref-AUTOCONF" title=""IPv6 Stateless Address Autoconfiguration"">AUTOCONF</a>]. Thus, obtaining a whole prefix for the VPN client and |
| 381 |
advertising that to the local link (something resembling [<a href="#ref-NDProxy" title=""Neighbor Discovery Proxies (ND Proxy)"">NDProxy</a>]) |
| 382 |
would be preferable. With DHCPv6 prefix delegation [<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>], even |
| 383 |
[<a href="#ref-NDProxy" title=""Neighbor Discovery Proxies (ND Proxy)"">NDProxy</a>] and associated multi-link subnet issues would be avoided. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Eronen, et al. Experimental [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 391 |
|
| 392 |
|
| 393 |
The solution should support sharing the VPN access over a local area |
| 394 |
network connection when the other hosts are using stateless address |
| 395 |
autoconfiguration. |
| 396 |
|
| 397 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. General Goals</span> |
| 398 |
|
| 399 |
o The solution should avoid periodic messages over the VPN tunnel. |
| 400 |
|
| 401 |
o Reauthentication should work, where the client can start a new IKE |
| 402 |
Security Association (SA) and continue using the same addresses as |
| 403 |
before. |
| 404 |
|
| 405 |
o There should be compatibility with other IPsec uses. Configuring |
| 406 |
a virtual IPv6 link (with addresses assigned in IKEv2) should not |
| 407 |
prevent the same peers from using IPsec/IKEv2 for other uses (with |
| 408 |
other addresses). In particular, the peers may have Security |
| 409 |
Policy Database (SPD) entries and Peer Authorization Database |
| 410 |
(PAD) Child SA Authorization Data entries that are not related to |
| 411 |
the virtual link; when a CHILD_SA is created, it should be |
| 412 |
unambiguous which entries are used. |
| 413 |
|
| 414 |
o There should be compatibility with current IPv6 configuration. |
| 415 |
Although the current IPv6 mechanism is not widely implemented, new |
| 416 |
solutions should not preclude its use (e.g., by defining |
| 417 |
incompatible semantics for the existing payloads). |
| 418 |
|
| 419 |
o The solution should have clean implementation dependencies. In |
| 420 |
particular, it should not require significant modifications to the |
| 421 |
core IPv6 stack (typically part of the operating system) or |
| 422 |
require the IKEv2 implementor to re-implement parts of the IPv6 |
| 423 |
stack (e.g., to have access or control to functionality that is |
| 424 |
currently not exposed by interfaces of the IPv6 stack). |
| 425 |
|
| 426 |
o Re-use existing mechanisms as much as possible, as described in |
| 427 |
[<a href="#ref-IPConfig" title=""Principles of Internet Host Configuration"">IPConfig</a>]. <a href="#appendix-A">Appendix A</a> describes the rationale of why this |
| 428 |
document nevertheless uses IKEv2 configuration payloads for |
| 429 |
configuring the addresses. However, <a href="#section-4.1">Section 4.1</a> recommends using |
| 430 |
a DHCPv6 Information-Request message for obtaining other |
| 431 |
configuration information (such as DNS server addresses). |
| 432 |
|
| 433 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Non-Goals</span> |
| 434 |
|
| 435 |
Mobile IPv6 already defines how it interacts with IPsec/IKEv2 |
| 436 |
[<a href="./rfc4877" title=""Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture"">RFC4877</a>], and the intent of this document is not to change that |
| 437 |
interaction in any way. |
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Eronen, et al. Experimental [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Additional Information</span> |
| 450 |
|
| 451 |
If the VPN client is assigned IPv6 address(es) from prefix(es) that |
| 452 |
are shared with other VPN clients, this results in some kind of |
| 453 |
multi-link subnet. [<a href="#ref-Multilink" title=""Multi-Link Subnet Issues"">Multilink</a>] describes issues associated with |
| 454 |
multi-link subnets and recommends that they be avoided. |
| 455 |
|
| 456 |
The original 3GPP specifications for IPv6 assigned a single IPv6 |
| 457 |
address to each mobile phone, resembling current IKEv2 payloads. |
| 458 |
[<a href="./rfc3314" title=""Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards"">RFC3314</a>] describes the problems with this approach and caused 3GPP |
| 459 |
to change the specifications to assign unique /64 prefix(es) for each |
| 460 |
phone. |
| 461 |
|
| 462 |
Due to similar concerns, the IEEE 802.16 IPv6 Convergence Sublayer |
| 463 |
[<a href="./rfc5121" title=""Transmission of IPv6 via the IPv6 Convergence Sublayer over IEEE 802.16 Networks"">RFC5121</a>] and Proxy Mobile IPv6 [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] also assign unique |
| 464 |
prefixes. |
| 465 |
|
| 466 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Solution Details</span> |
| 467 |
|
| 468 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Initial Exchanges</span> |
| 469 |
|
| 470 |
During IKE_AUTH, the client sends a new configuration attribute, |
| 471 |
INTERNAL_IP6_LINK, which requests a virtual link to be configured. |
| 472 |
The attribute contains the client's interface ID for the link-local |
| 473 |
address (other addresses may use other interface IDs). Typically, |
| 474 |
the client would also ask for the DHCPv6 server address; this is used |
| 475 |
only for configuration (such as DNS server addresses), not address |
| 476 |
assignment. |
| 477 |
|
| 478 |
CP(CFG_REQUEST) = |
| 479 |
{ INTERNAL_IP6_LINK(Client's Link-Local Interface ID) |
| 480 |
INTERNAL_IP6_DHCP() } |
| 481 |
TSi = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 482 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 483 |
TSr = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 484 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) --> |
| 485 |
|
| 486 |
If the client has sent the INTERNAL_IP6_LINK configuration attribute, |
| 487 |
the VPN gateway SHOULD ignore any INTERNAL_IP6_ADDRESS configuration |
| 488 |
attribute present in the request. |
| 489 |
|
| 490 |
The VPN gateway MUST choose for itself a link-local interface |
| 491 |
identifier different than the client's, i.e., accept the link-local |
| 492 |
interface identifier proposed by the client. In case the VPN gateway |
| 493 |
cannot accept the link-local interface identifier the client |
| 494 |
proposed, the VPN gateway MUST fail the IPv6 address assignment by |
| 495 |
including a NOTIFY payload with the INTERNAL_ADDRESS_FAILURE message. |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Eronen, et al. Experimental [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 503 |
|
| 504 |
|
| 505 |
The VPN gateway then replies with an INTERNAL_IP6_LINK configuration |
| 506 |
attribute that contains the IKEv2 Link ID (an identifier selected by |
| 507 |
the VPN gateway, treated as an opaque octet string by the client -- |
| 508 |
this will be used for reauthentication and CREATE_CHILD_SA messages), |
| 509 |
the gateway's link-local interface identifier, and zero or more |
| 510 |
INTERNAL_IP6_PREFIX attributes. The traffic selectors proposed by |
| 511 |
the initiator are also narrowed to contain only the assigned prefixes |
| 512 |
and the client link-local address (FE80::<Client's Interface ID>) |
| 513 |
identifier. |
| 514 |
|
| 515 |
CP(CFG_REPLY) = |
| 516 |
{ INTERNAL_IP6_LINK(Gateway's Link-Local Interface ID, |
| 517 |
IKEv2 Link ID) |
| 518 |
INTERNAL_IP6_PREFIX(Prefix1/64), |
| 519 |
[INTERNAL_IP6_PREFIX(Prefix2/64),...], |
| 520 |
INTERNAL_IP6_DHCP(Address) } |
| 521 |
TSi = ((0, 0-65535, |
| 522 |
FE80::<Client's Interface ID> - |
| 523 |
FE80::<Client's Interface ID>) |
| 524 |
(0, 0-65535, |
| 525 |
Prefix1::0 - |
| 526 |
Prefix1::FFFF:FFFF:FFFF:FFFF), |
| 527 |
[(0, 0-65535, |
| 528 |
Prefix2::0 - |
| 529 |
Prefix2::FFFF:FFFF:FFFF:FFFF), ...]) |
| 530 |
TSr = (0, 0-65535, |
| 531 |
0:0:0:0:0:0:0:0 - |
| 532 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 533 |
|
| 534 |
At this point, the client can configure its link-local address |
| 535 |
(FE80::<Client's Interface ID>) and other non-link-local unicast |
| 536 |
addresses from the assigned prefixes (with any proper interface |
| 537 |
identifier [<a href="#ref-IPv6Addr" title=""IP Version 6 Addressing Architecture"">IPv6Addr</a>]). The VPN gateway MUST NOT simultaneously |
| 538 |
assign the same prefixes to any other client and MUST NOT itself |
| 539 |
configure addresses from these prefixes. Thus, the client does not |
| 540 |
have to perform Duplicate Address Detection (DAD). (This approach is |
| 541 |
based on [<a href="#ref-IPv6PPP" title=""IP Version 6 over PPP"">IPv6PPP</a>].) |
| 542 |
|
| 543 |
The prefixes remain valid through the lifetime of the IKE SA (and its |
| 544 |
continuations via rekeying). If the VPN gateway needs to remove a |
| 545 |
prefix it has previously assigned, or assign a new prefix, it can do |
| 546 |
so with reauthentication (either starting reauthentication itself or |
| 547 |
requesting the client to reauthenticate using [<a href="./rfc4478" title=""Repeated Authentication in Internet Key Exchange (IKEv2) Protocol"">RFC4478</a>]). |
| 548 |
|
| 549 |
The client also contacts the DHCPv6 server. This is the RECOMMENDED |
| 550 |
way to obtain additional configuration parameters (such as DNS server |
| 551 |
addresses), as it allows easier extensibility and more options (such |
| 552 |
as the domain search list for DNS). |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Eronen, et al. Experimental [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Reauthentication</span> |
| 562 |
|
| 563 |
When the client performs reauthentication (and wants to continue |
| 564 |
using the same "virtual link"), it includes the IKEv2 Link ID given |
| 565 |
by the gateway in the INTERNAL_IP6_LINK attribute. |
| 566 |
|
| 567 |
CP(CFG_REQUEST) = |
| 568 |
{ INTERNAL_IP6_LINK(Client's Link Local Interface ID, |
| 569 |
IKEv2 Link ID) |
| 570 |
INTERNAL_IP6_DHCP() } |
| 571 |
TSi = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 572 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 573 |
TSr = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 574 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) --> |
| 575 |
|
| 576 |
At this point, the gateway MUST verify that the client is indeed |
| 577 |
allowed to use the link identified by the IKEv2 Link ID. The same |
| 578 |
situation occurs in [<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>] when the client wants to continue using |
| 579 |
the same IPv4 address with the INTERNAL_IP4_ADDRESS configuration |
| 580 |
attribute. Typically, the gateway would use the Link ID to look up |
| 581 |
relevant local state and compare the authenticated peer identity of |
| 582 |
the IKE_SA with the local state. |
| 583 |
|
| 584 |
If the client is allowed to continue using this link, the gateway |
| 585 |
replies (see <a href="#section-4.1">Section 4.1</a>) with the same gateway's link-local |
| 586 |
interface ID and IKEv2 Link ID as used earlier and sends the IPv6 |
| 587 |
prefix(es) associated with this link. Usually, the IPv6 prefix(es) |
| 588 |
will also be the same as earlier, but this is not required. |
| 589 |
|
| 590 |
If the client is not allowed to continue using this link, the gateway |
| 591 |
treats it as a request for a new virtual link, selects a different |
| 592 |
IKEv2 Link ID value, and replies as in <a href="#section-4.1">Section 4.1</a>. |
| 593 |
|
| 594 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Creating CHILD_SAs</span> |
| 595 |
|
| 596 |
When a CHILD_SA is created, the peers need to determine which SPD |
| 597 |
entries and PAD Child SA Authorization Data entries are used for this |
| 598 |
CHILD_SA. In the basic client-to-VPN-gateway uses, the situation is |
| 599 |
simple: all the matching SPD entries and Child SA Authorization Data |
| 600 |
entries are related to the "virtual link" between the VPN client and |
| 601 |
the VPN gateway. However, if the same peers are also using IPsec/ |
| 602 |
IKEv2 for other uses (with addresses not assigned inside IKEv2), they |
| 603 |
would also have SPD entries and PAD Child SA Authorization Data that |
| 604 |
is not related to the virtual link. |
| 605 |
|
| 606 |
If one of the peers requests a CHILD_SA and proposes traffic |
| 607 |
selectors covering everything (like in Figure 2), should those be |
| 608 |
narrowed to the prefixes configured with INTERNAL_IP6_PREFIX or to |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Eronen, et al. Experimental [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 615 |
|
| 616 |
|
| 617 |
the other SPD/PAD entries? While some kind of heuristics are |
| 618 |
possible (see <a href="#appendix-A">Appendix A</a> for discussion), this document specifies an |
| 619 |
explicit solution: |
| 620 |
|
| 621 |
The peers MUST include a LINK_ID notification, containing the IKEv2 |
| 622 |
Link ID, in all CREATE_CHILD_SA requests (including rekeys) that are |
| 623 |
related to the virtual link. The LINK_ID notification is not |
| 624 |
included in the CREATE_CHILD_SA response or when doing IKE_SA |
| 625 |
rekeying. |
| 626 |
|
| 627 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Relationship to Neighbor Discovery</span> |
| 628 |
|
| 629 |
Neighbor Discovery [<a href="#ref-IPv6ND" title=""Neighbor Discovery for IP version 6 (IPv6)"">IPv6ND</a>] specifies the following mechanisms: |
| 630 |
|
| 631 |
Router Discovery, Prefix Discovery, Parameter Discovery, and address |
| 632 |
autoconfiguration are not used, as the necessary functionality is |
| 633 |
implemented in IKEv2. |
| 634 |
|
| 635 |
Address Resolution, Next-hop Determination, and Redirect are not |
| 636 |
used, as the virtual link does not have link-layer addresses and is a |
| 637 |
point-to-point link. |
| 638 |
|
| 639 |
Neighbor Unreachability Detection could be used but is a bit |
| 640 |
redundant given IKEv2 Dead Peer Detection. |
| 641 |
|
| 642 |
Duplicate Address Detection is not needed because this is a point-to- |
| 643 |
point link, where the VPN gateway does not assign any addresses from |
| 644 |
the global unicast prefixes, and the link-local interface identifier |
| 645 |
is negotiated separately. |
| 646 |
|
| 647 |
Duplicate Address Detection is not needed for global unicast |
| 648 |
addresses formed from the global unicast prefix(es) configured as |
| 649 |
part of the IKEv2 exchange, because this is a point-to-point link, |
| 650 |
where the VPN gateway does not assign any addresses from the global |
| 651 |
unicast prefixes. Duplicate Address Detection may be needed for |
| 652 |
link-local addresses, e.g., when the client configures a link-local |
| 653 |
address as per [<a href="./rfc4941" title=""Privacy Extensions for Stateless Address Autoconfiguration in IPv6"">RFC4941</a>]. |
| 654 |
|
| 655 |
Thus, Duplicate Address Detection MAY be skipped for global unicast |
| 656 |
addresses formed from the global unicast prefix(es) configured as |
| 657 |
part of the IKEv2 exchange. However, Duplicate Address Detection for |
| 658 |
link-local unicast addresses MUST be performed as required per some |
| 659 |
other specifications, e.g., [<a href="./rfc4941" title=""Privacy Extensions for Stateless Address Autoconfiguration in IPv6"">RFC4941</a>]. |
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Eronen, et al. Experimental [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Relationship to Existing IKEv2 Payloads</span> |
| 674 |
|
| 675 |
The mechanism described in this document is not intended to be used |
| 676 |
at the same time as the existing INTERNAL_IP6_ADDRESS attribute. For |
| 677 |
compatibility with gateways implementing only INTERNAL_IP6_ADDRESS, |
| 678 |
the VPN client MAY include attributes for both mechanisms in |
| 679 |
CFG_REQUEST. The capabilities and preferences of the VPN gateway |
| 680 |
will then determine which is used. |
| 681 |
|
| 682 |
All other attributes except INTERNAL_IP6_ADDRESS (and |
| 683 |
INTENAL_ADDRESS_EXPIRY) from [<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>] remain valid, including the |
| 684 |
somewhat confusingly named INTERNAL_IP6_SUBNET (see <a href="./rfc4718#section-6.3">Section 6.3 of |
| 685 |
[RFC4718]</a> for discussion). |
| 686 |
|
| 687 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Payload Formats</span> |
| 688 |
|
| 689 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. INTERNAL_IP6_LINK Configuration Attribute</span> |
| 690 |
|
| 691 |
The INTERNAL_IP6_LINK configuration attribute is formatted as |
| 692 |
follows: |
| 693 |
|
| 694 |
1 2 3 |
| 695 |
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 |
| 696 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 697 |
!R| Attribute Type ! Length | |
| 698 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 699 |
| Link-Local | |
| 700 |
| Interface ID | |
| 701 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 702 |
| | |
| 703 |
~ IKEv2 Link ID ~ |
| 704 |
| | |
| 705 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 706 |
|
| 707 |
o Reserved (1 bit) - See [<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>]. |
| 708 |
|
| 709 |
o Attribute Type (15 bits) - INTERNAL_IP6_LINK (17). |
| 710 |
|
| 711 |
o Length (2 octets) - Length in octets of the Value field (Link- |
| 712 |
Local Interface ID and IKEv2 Link ID); 8 or more. |
| 713 |
|
| 714 |
o Link-Local Interface ID (8 octets) - The Interface ID used for |
| 715 |
link-local address (by the party that sent this attribute). |
| 716 |
|
| 717 |
o IKEv2 Link ID (variable length) - The Link ID (may be empty when |
| 718 |
the client does not yet know the Link ID). The Link ID is |
| 719 |
selected by the VPN gateway and is treated as an opaque octet |
| 720 |
string by the client. |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Eronen, et al. Experimental [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. INTERNAL_IP6_PREFIX Configuration Attribute</span> |
| 730 |
|
| 731 |
The INTERNAL_IP6_PREFIX configuration attribute is formatted as |
| 732 |
follows: |
| 733 |
|
| 734 |
1 2 3 |
| 735 |
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 |
| 736 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 737 |
!R| Attribute Type ! Length | |
| 738 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 739 |
| | |
| 740 |
| Prefix | |
| 741 |
| | |
| 742 |
| | |
| 743 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 744 |
| Prefix Length | |
| 745 |
+-+-+-+-+-+-+-+-+ |
| 746 |
|
| 747 |
o Reserved (1 bit) - See [<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>]. |
| 748 |
|
| 749 |
o Attribute Type (15 bits) - INTERNAL_IP6_PREFIX (18). |
| 750 |
|
| 751 |
o Length (2 octets) - Length in octets of the Value field; in this |
| 752 |
case, 17. |
| 753 |
|
| 754 |
o Prefix (16 octets) - An IPv6 prefix assigned to the virtual link. |
| 755 |
The low-order bits of the prefix field that are not part of the |
| 756 |
prefix MUST be set to zero by the sender and MUST be ignored by |
| 757 |
the receiver. |
| 758 |
|
| 759 |
o Prefix Length (1 octet) - The length of the prefix in bits; |
| 760 |
usually 64. |
| 761 |
|
| 762 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. LINK_ID Notify Payload</span> |
| 763 |
|
| 764 |
The LINK_ID notification is included in CREATE_CHILD_SA requests to |
| 765 |
indicate that the SA being created is related to the virtual link. |
| 766 |
If this notification is not included, the CREATE_CHILD_SA requests |
| 767 |
are related to the real interface. |
| 768 |
|
| 769 |
The Notify Message Type for LINK_ID is 16414. The Protocol ID and |
| 770 |
SPI Size fields are set to zero. The data associated with this |
| 771 |
notification is the IKEv2 Link ID returned in the INTERNAL_IP6_LINK |
| 772 |
configuration attribute. |
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Eronen, et al. Experimental [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 786 |
|
| 787 |
This document defines two new IKEv2 configuration attributes, whose |
| 788 |
values have been allocated from the "IKEv2 Configuration Payload |
| 789 |
Attribute Types" namespace [<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>]: |
| 790 |
|
| 791 |
Multi- |
| 792 |
Value Attribute Type Valued Length Reference |
| 793 |
------ ---------------------- ------ ------------- --------- |
| 794 |
17 INTERNAL_IP6_LINK NO 8 or more [<a href="./rfc5739">RFC5739</a>] |
| 795 |
18 INTERNAL_IP6_PREFIX YES 17 octets [<a href="./rfc5739">RFC5739</a>] |
| 796 |
|
| 797 |
This document also defines one new IKEv2 notification, whose value |
| 798 |
has been allocated from the "IKEv2 Notify Message Types - Status |
| 799 |
Types" namespace [<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>]: |
| 800 |
|
| 801 |
Value Notify Messages - Status Types Reference |
| 802 |
------ ------------------------------- --------- |
| 803 |
16414 LINK_ID [<a href="./rfc5739">RFC5739</a>] |
| 804 |
|
| 805 |
This document does not create any new namespaces to be maintained by |
| 806 |
IANA. |
| 807 |
|
| 808 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 809 |
|
| 810 |
Since this document is an extension to IKEv2, the security |
| 811 |
considerations in [<a href="#ref-IKEv2" title=""Internet Key Exchange (IKEv2) Protocol"">IKEv2</a>] apply here as well. |
| 812 |
|
| 813 |
The mechanism described in this document assigns each client a unique |
| 814 |
prefix, which makes using randomized interface identifiers [<a href="./rfc4941" title=""Privacy Extensions for Stateless Address Autoconfiguration in IPv6"">RFC4941</a>] |
| 815 |
ineffective from a privacy point of view: the client is still |
| 816 |
uniquely identified by the prefix. In some environments, it may be |
| 817 |
preferable to assign a VPN client the same prefix each time a VPN |
| 818 |
connection is established; other environments may prefer assigning a |
| 819 |
different prefix every time for privacy reasons. (This is basically |
| 820 |
a similar trade-off as in Mobile IPv6 -- using the same Home Address |
| 821 |
forever is simpler than changing it often, but has privacy |
| 822 |
implications.) |
| 823 |
|
| 824 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgments</span> |
| 825 |
|
| 826 |
The authors would like to thank Patrick Irwin, Tero Kivinen, Chinh |
| 827 |
Nguyen, Mohan Parthasarathy, Yaron Sheffer, Hemant Singh, Dave |
| 828 |
Thaler, Yinghzhe Wu, and Fan Zhao for their valuable comments. |
| 829 |
|
| 830 |
Many of the challenges associated with IPsec-protected "virtual |
| 831 |
interfaces" have been identified before, for example, in the context |
| 832 |
of protecting IPv6-in-IPv4 tunnels with IPsec [<a href="./rfc4891" title=""Using IPsec to Secure IPv6-in-IPv4 Tunnels"">RFC4891</a>], Provider |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Eronen, et al. Experimental [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 839 |
|
| 840 |
|
| 841 |
Provisioned VPNs ([<a href="#ref-VLINK" title=""Framework for IPsec Protected Virtual Links for PPVPNs"">VLINK</a>], [<a href="./rfc3884" title=""Use of IPsec Transport Mode for Dynamic Routing"">RFC3884</a>]), and Mobile IPv6 [<a href="./rfc4877" title=""Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture"">RFC4877</a>]. |
| 842 |
Some of the limitations of assigning a single IPv6 address were |
| 843 |
identified in [<a href="./rfc3314" title=""Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards"">RFC3314</a>]. |
| 844 |
|
| 845 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 846 |
|
| 847 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span> |
| 848 |
|
| 849 |
[<a id="ref-IKEv2">IKEv2</a>] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", |
| 850 |
<a href="./rfc4306">RFC 4306</a>, December 2005. |
| 851 |
|
| 852 |
[<a id="ref-IPv6Addr">IPv6Addr</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing |
| 853 |
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006. |
| 854 |
|
| 855 |
[<a id="ref-KEYWORDS">KEYWORDS</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 856 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 857 |
|
| 858 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span> |
| 859 |
|
| 860 |
[<a id="ref-AUTOCONF">AUTOCONF</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless |
| 861 |
Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, September 2007. |
| 862 |
|
| 863 |
[<a id="ref-CGA">CGA</a>] Aura, T., "Cryptographically Generated Addresses (CGA)", |
| 864 |
<a href="./rfc3972">RFC 3972</a>, March 2006. |
| 865 |
|
| 866 |
[<a id="ref-DHCPv6">DHCPv6</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., |
| 867 |
and M. Carney, "Dynamic Host Configuration Protocol for |
| 868 |
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003. |
| 869 |
|
| 870 |
[<a id="ref-HBA">HBA</a>] Bagnulo, M., "Hash-Based Addresses (HBA)", <a href="./rfc5535">RFC 5535</a>, |
| 871 |
June 2009. |
| 872 |
|
| 873 |
[<a id="ref-IPConfig">IPConfig</a>] Aboba, B., Thaler, D., Andersson, L., and S. Cheshire, |
| 874 |
"Principles of Internet Host Configuration", <a href="./rfc5505">RFC 5505</a>, |
| 875 |
May 2009. |
| 876 |
|
| 877 |
[<a id="ref-IPv6ND">IPv6ND</a>] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, |
| 878 |
"Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>, |
| 879 |
September 2007. |
| 880 |
|
| 881 |
[<a id="ref-IPv6PPP">IPv6PPP</a>] Varada, S., Haskins, D., and E. Allen, "IP Version 6 |
| 882 |
over PPP", <a href="./rfc5072">RFC 5072</a>, September 2007. |
| 883 |
|
| 884 |
[<a id="ref-MLDv2">MLDv2</a>] Vida, R. and L. Costa, "Multicast Listener Discovery |
| 885 |
Version 2 (MLDv2) for IPv6", <a href="./rfc3810">RFC 3810</a>, June 2004. |
| 886 |
|
| 887 |
[<a id="ref-MOBIKE">MOBIKE</a>] Eronen, P., "IKEv2 Mobility and Multihoming Protocol |
| 888 |
(MOBIKE)", <a href="./rfc4555">RFC 4555</a>, June 2006. |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Eronen, et al. Experimental [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 895 |
|
| 896 |
|
| 897 |
[<a id="ref-Multilink">Multilink</a>] Thaler, D., "Multi-Link Subnet Issues", <a href="./rfc4903">RFC 4903</a>, |
| 898 |
June 2007. |
| 899 |
|
| 900 |
[<a id="ref-NDProxy">NDProxy</a>] Thaler, D., Talwar, M., and C. Patel, "Neighbor |
| 901 |
Discovery Proxies (ND Proxy)", <a href="./rfc4389">RFC 4389</a>, April 2006. |
| 902 |
|
| 903 |
[<a id="ref-RFC3314">RFC3314</a>] Wasserman, M., "Recommendations for IPv6 in Third |
| 904 |
Generation Partnership Project (3GPP) Standards", |
| 905 |
<a href="./rfc3314">RFC 3314</a>, September 2002. |
| 906 |
|
| 907 |
[<a id="ref-RFC3456">RFC3456</a>] Patel, B., Aboba, B., Kelly, S., and V. Gupta, "Dynamic |
| 908 |
Host Configuration Protocol (DHCPv4) Configuration of |
| 909 |
IPsec Tunnel Mode", <a href="./rfc3456">RFC 3456</a>, January 2003. |
| 910 |
|
| 911 |
[<a id="ref-RFC3633">RFC3633</a>] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic |
| 912 |
Host Configuration Protocol (DHCP) version 6", <a href="./rfc3633">RFC 3633</a>, |
| 913 |
December 2003. |
| 914 |
|
| 915 |
[<a id="ref-RFC3884">RFC3884</a>] Touch, J., Eggert, L., and Y. Wang, "Use of IPsec |
| 916 |
Transport Mode for Dynamic Routing", <a href="./rfc3884">RFC 3884</a>, |
| 917 |
September 2004. |
| 918 |
|
| 919 |
[<a id="ref-RFC4193">RFC4193</a>] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast |
| 920 |
Addresses", <a href="./rfc4193">RFC 4193</a>, October 2005. |
| 921 |
|
| 922 |
[<a id="ref-RFC4478">RFC4478</a>] Nir, Y., "Repeated Authentication in Internet Key |
| 923 |
Exchange (IKEv2) Protocol", <a href="./rfc4478">RFC 4478</a>, April 2006. |
| 924 |
|
| 925 |
[<a id="ref-RFC4718">RFC4718</a>] Eronen, P. and P. Hoffman, "IKEv2 Clarifications and |
| 926 |
Implementation Guidelines", <a href="./rfc4718">RFC 4718</a>, October 2006. |
| 927 |
|
| 928 |
[<a id="ref-RFC4866">RFC4866</a>] Arkko, J., Vogt, C., and W. Haddad, "Enhanced Route |
| 929 |
Optimization for Mobile IPv6", <a href="./rfc4866">RFC 4866</a>, May 2007. |
| 930 |
|
| 931 |
[<a id="ref-RFC4877">RFC4877</a>] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation |
| 932 |
with IKEv2 and the Revised IPsec Architecture", |
| 933 |
<a href="./rfc4877">RFC 4877</a>, April 2007. |
| 934 |
|
| 935 |
[<a id="ref-RFC4891">RFC4891</a>] Graveman, R., Parthasarathy, M., Savola, P., and H. |
| 936 |
Tschofenig, "Using IPsec to Secure IPv6-in-IPv4 |
| 937 |
Tunnels", <a href="./rfc4891">RFC 4891</a>, May 2007. |
| 938 |
|
| 939 |
[<a id="ref-RFC4941">RFC4941</a>] Narten, T., Draves, R., and S. Krishnan, "Privacy |
| 940 |
Extensions for Stateless Address Autoconfiguration in |
| 941 |
IPv6", <a href="./rfc4941">RFC 4941</a>, September 2007. |
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Eronen, et al. Experimental [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 951 |
|
| 952 |
|
| 953 |
[<a id="ref-RFC5121">RFC5121</a>] Patil, B., Xia, F., Sarikaya, B., Choi, JH., and S. |
| 954 |
Madanapalli, "Transmission of IPv6 via the IPv6 |
| 955 |
Convergence Sublayer over IEEE 802.16 Networks", |
| 956 |
<a href="./rfc5121">RFC 5121</a>, February 2008. |
| 957 |
|
| 958 |
[<a id="ref-RFC5213">RFC5213</a>] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, |
| 959 |
K., and B. Patil, "Proxy Mobile IPv6", <a href="./rfc5213">RFC 5213</a>, |
| 960 |
August 2008. |
| 961 |
|
| 962 |
[<a id="ref-SHIM6">SHIM6</a>] Nordmark, E. and M. Bagnulo, "Shim6: Level 3 Multihoming |
| 963 |
Shim Protocol for IPv6", <a href="./rfc5533">RFC 5533</a>, June 2009. |
| 964 |
|
| 965 |
[<a id="ref-VLINK">VLINK</a>] Duffy, M., "Framework for IPsec Protected Virtual Links |
| 966 |
for PPVPNs", Work in Progress, October 2002. |
| 967 |
|
| 968 |
|
| 969 |
|
| 970 |
|
| 971 |
|
| 972 |
|
| 973 |
|
| 974 |
|
| 975 |
|
| 976 |
|
| 977 |
|
| 978 |
|
| 979 |
|
| 980 |
|
| 981 |
|
| 982 |
|
| 983 |
|
| 984 |
|
| 985 |
|
| 986 |
|
| 987 |
|
| 988 |
|
| 989 |
|
| 990 |
|
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Eronen, et al. Experimental [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Design Rationale (Non-Normative)</span> |
| 1010 |
|
| 1011 |
This appendix describes some of the reasons why the solution in |
| 1012 |
<a href="#section-4">Section 4</a> was selected and lists some alternative designs that were |
| 1013 |
considered but were ultimately rejected. |
| 1014 |
|
| 1015 |
Assigning a new IPv6 address to the client creates a new "virtual |
| 1016 |
IPv6 interface" and "virtual link" between the client and the |
| 1017 |
gateway. We will assume that the virtual link has the following |
| 1018 |
properties: |
| 1019 |
|
| 1020 |
o The link and its interfaces are created and destroyed by the IKEv2 |
| 1021 |
process. |
| 1022 |
|
| 1023 |
o The link is not an IPsec SA; at any time, there can be zero or |
| 1024 |
more IPsec SAs covering traffic on this link. |
| 1025 |
|
| 1026 |
o The link is not a single IKE SA; to support reauthentication, it |
| 1027 |
must be possible to identify the same link in another IKE SA. |
| 1028 |
|
| 1029 |
o Not all IPsec-protected traffic between the peers is necessarily |
| 1030 |
related to the virtual link (although in the simplest VPN client- |
| 1031 |
to-gateway scenario, it will be). |
| 1032 |
|
| 1033 |
Given these assumptions and the goals described in <a href="#section-3">Section 3</a>, it |
| 1034 |
seems that the most important design choices to be made are the |
| 1035 |
following: |
| 1036 |
|
| 1037 |
o What link/subnet model is used; in other words, how relationships |
| 1038 |
between VPN clients, IPv6 subnet prefixes, and link-local traffic |
| 1039 |
(especially link-local multicast) are organized. |
| 1040 |
|
| 1041 |
o How information about the IPv6 prefix(es) is distributed from the |
| 1042 |
gateway to the clients. |
| 1043 |
|
| 1044 |
o How to ensure unique IPv6 addresses for each client and keep |
| 1045 |
forwarding state up-to-date accordingly. |
| 1046 |
|
| 1047 |
o How layer 3 access control is done; in other words, where the |
| 1048 |
mechanisms for preventing address spoofing by clients are placed |
| 1049 |
architecturally. |
| 1050 |
|
| 1051 |
Each of these is discussed next in turn. |
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Eronen, et al. Experimental [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. Link Model</span> |
| 1066 |
|
| 1067 |
There are at least three main choices for how to organize the |
| 1068 |
relationships between VPN clients, IPv6 subnet prefixes, and link- |
| 1069 |
local traffic: |
| 1070 |
|
| 1071 |
o Point-to-point link model: each VPN client is assigned one or more |
| 1072 |
IPv6 prefixes. These prefixes are not shared with other clients, |
| 1073 |
and there is no link-local traffic between different VPN clients |
| 1074 |
connected to the same gateway. |
| 1075 |
|
| 1076 |
o Multi-access link model: multiple VPN clients share the same IPv6 |
| 1077 |
prefix. Link-local multicast packets sent by one VPN client will |
| 1078 |
be received by other VPN clients (VPN gateway will forward the |
| 1079 |
packets, possibly with Multicast Listener Discovery (MLD) snooping |
| 1080 |
to remove unnecessary packets). |
| 1081 |
|
| 1082 |
o "Router aggregation" link model: one form of "multi-link" subnet |
| 1083 |
[<a href="#ref-Multilink" title=""Multi-Link Subnet Issues"">Multilink</a>] where multiple VPN clients share the same IPv6 prefix. |
| 1084 |
Link-local multicast will not be received by other VPN clients. |
| 1085 |
|
| 1086 |
In the multi-access link model, VPN clients who are idle (i.e., not |
| 1087 |
currently sending or receiving application traffic) could receive |
| 1088 |
significant amounts of multicast packets from other clients |
| 1089 |
(depending on how many other clients are connected). This is |
| 1090 |
especially undesirable when the clients are battery-powered such as a |
| 1091 |
PDA that keeps the VPN connection to corporate intranet active 24/7. |
| 1092 |
For this reason, using the multi-access link model was rejected. |
| 1093 |
|
| 1094 |
The configuration attributes specified in <a href="#section-4">Section 4</a> use the point-to- |
| 1095 |
point link model. |
| 1096 |
|
| 1097 |
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Distributing Prefix Information</span> |
| 1098 |
|
| 1099 |
Some types of addresses, such as CGAs, require knowledge about the |
| 1100 |
prefix before an address can be generated. The prefix information |
| 1101 |
could be distributed to clients in the following ways: |
| 1102 |
|
| 1103 |
o IKEv2 messages (configuration payloads) |
| 1104 |
|
| 1105 |
o Router Advertisement messages (sent over the IPsec tunnel) |
| 1106 |
|
| 1107 |
o DHCPv6 messages (sent over the IPsec tunnel) |
| 1108 |
|
| 1109 |
In <a href="#section-4">Section 4</a>, the prefix information is distributed in IKEv2 |
| 1110 |
messages. |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Eronen, et al. Experimental [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. Unique Address Allocation</span> |
| 1122 |
|
| 1123 |
In the "multi-access" and "router aggregation" link models (where a |
| 1124 |
single IPv6 prefix is shared between multiple VPN clients), |
| 1125 |
mechanisms are needed to ensure that one VPN client does not use an |
| 1126 |
address already used by some other client. Also, the VPN gateway has |
| 1127 |
to know which client is using which addresses in order to correctly |
| 1128 |
forward traffic. |
| 1129 |
|
| 1130 |
The main choices seem to be the following: |
| 1131 |
|
| 1132 |
o Clients receive the address(es) they are allowed to use in IKEv2 |
| 1133 |
messages (configuration payloads). In this case, keeping track of |
| 1134 |
which client is using which address is trivial. |
| 1135 |
|
| 1136 |
o Clients receive the address(es) they are allowed to use in DHCPv6 |
| 1137 |
messages sent over the IPsec tunnel. In case the DHCPv6 server is |
| 1138 |
not integrated with the VPN gateway, the gateway may need to work |
| 1139 |
as a relay agent to keep track of which client is using which |
| 1140 |
address (and update its forwarding state accordingly). |
| 1141 |
|
| 1142 |
o Clients can use stateless address autoconfiguration to configure |
| 1143 |
addresses and perform Duplicate Address Detection (DAD). This is |
| 1144 |
easy to do in a multi-access link model and can be made to work |
| 1145 |
with a router aggregation link model if the VPN gateway traps |
| 1146 |
Neighbor Solicitation (NS) messages and spoofs Neighbor |
| 1147 |
Advertisement (NA) replies. The gateway keeps track of which |
| 1148 |
client is using which address (and updates its forwarding state |
| 1149 |
accordingly) by trapping these NS/NA messages. |
| 1150 |
|
| 1151 |
In the point-to-point link model, the client can simply use any |
| 1152 |
address from the prefix, and the VPN gateway only needs to know which |
| 1153 |
client is using which prefix in order to forward packets correctly. |
| 1154 |
|
| 1155 |
<span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>. Layer 3 Access Control</span> |
| 1156 |
|
| 1157 |
It is almost always desirable to prevent one VPN client from sending |
| 1158 |
packets with a source address that is used by another VPN client. In |
| 1159 |
order to correctly forward packets destined to clients, the VPN |
| 1160 |
gateway obviously has to know which client is using which address; |
| 1161 |
the question is therefore where, architecturally, the mechanisms for |
| 1162 |
ingress filtering are placed. |
| 1163 |
|
| 1164 |
o Layer 3 access control could be enforced by IPsec Security |
| 1165 |
Association Database (SAD) / SPD; the addresses/prefixes assigned |
| 1166 |
to a VPN client would be reflected in the traffic selectors used |
| 1167 |
in IPsec Security Association and Security Policy Database |
| 1168 |
entries, as negotiated in IKEv2. |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Eronen, et al. Experimental [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
o The ingress filtering capability could be placed outside IPsec; |
| 1178 |
the traffic selectors in SAD/SPD entries would cover traffic that |
| 1179 |
would be dropped later by ingress filtering. |
| 1180 |
|
| 1181 |
The former approach is used by the current IPv4 solution and the |
| 1182 |
mechanism specified in <a href="#section-4">Section 4</a>. |
| 1183 |
|
| 1184 |
<span class="h3"><a class="selflink" id="appendix-A.5" href="#appendix-A.5">A.5</a>. Other Considerations</span> |
| 1185 |
|
| 1186 |
VPN gateway state |
| 1187 |
|
| 1188 |
In some combinations of design choices, the amount of state |
| 1189 |
information required in the VPN gateway depends not only on the |
| 1190 |
number of clients but also on the number of addresses used by one |
| 1191 |
client. With privacy addresses and potentially some uses of |
| 1192 |
Cryptographically Generated Addresses (CGAs), a single client |
| 1193 |
could have a large number of different addresses (especially if |
| 1194 |
different privacy addresses are used with different destinations). |
| 1195 |
|
| 1196 |
Virtual link identifier |
| 1197 |
|
| 1198 |
Reauthentication requires a way to uniquely identify the virtual |
| 1199 |
link when a second IKE SA is created. Some possible alternatives |
| 1200 |
are the IKE Security Parameter Indexes (SPIs) of the IKE SA where |
| 1201 |
the virtual link was "created" (assuming we can't have multiple |
| 1202 |
virtual links within the same IKE SA), a new identifier assigned |
| 1203 |
when the link is created, or any unique prefix or address that |
| 1204 |
remains assigned to the link for its entire lifetime. <a href="#section-4">Section 4</a> |
| 1205 |
specifies that the gateway assigns a new IKEv2 Link ID when the |
| 1206 |
link is created. The client treats the Link ID as an opaque octet |
| 1207 |
string; the gateway uses it to identify relevant local state when |
| 1208 |
reauthentication is done. |
| 1209 |
|
| 1210 |
Note that the link is not uniquely identified by the IKE peer |
| 1211 |
identities (because IDi is often a user identity that can be used |
| 1212 |
on multiple hosts at the same time) or the outer IP addresses of |
| 1213 |
the peers (due to NAT Traversal and [<a href="#ref-MOBIKE" title=""IKEv2 Mobility and Multihoming Protocol (MOBIKE)"">MOBIKE</a>]). |
| 1214 |
|
| 1215 |
|
| 1216 |
|
| 1217 |
|
| 1218 |
|
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Eronen, et al. Experimental [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
Prefix lifetime |
| 1234 |
|
| 1235 |
Prefixes could remain valid either for the lifetime of the IKE SA, |
| 1236 |
until explicitly cancelled, or for an explicitly specified time. |
| 1237 |
In <a href="#section-4">Section 4</a>, the prefixes remain valid for the lifetime of the |
| 1238 |
IKE SA (and its continuations via rekeying but not via |
| 1239 |
reauthentication). If necessary, the VPN gateway can thus add or |
| 1240 |
remove prefixes by triggering reauthentication. It is assumed |
| 1241 |
that adding or removing prefixes is a relatively rare situation, |
| 1242 |
and thus this document does not specify more complex solutions |
| 1243 |
(such as explicit prefix lifetimes or use of CFG_SET/CFG_ACK). |
| 1244 |
|
| 1245 |
Compatibility with other IPsec uses |
| 1246 |
|
| 1247 |
Compatibility with other IPsec uses probably requires that when a |
| 1248 |
CHILD_SA is created, both peers can determine whether the CHILD_SA |
| 1249 |
applies to the virtual interface (at the end of the virtual link) |
| 1250 |
or the real interfaces over which IKEv2 messages are being sent. |
| 1251 |
This is required to select the correct SPD to be used for traffic- |
| 1252 |
selector narrowing and SA authorization in general. |
| 1253 |
|
| 1254 |
One straight-forward solution is to add an extra payload to |
| 1255 |
CREATE_CHILD_SA requests, containing the virtual link identifier. |
| 1256 |
Requests not containing this payload would refer to the real link |
| 1257 |
(over which IKEv2 messages are being sent). |
| 1258 |
|
| 1259 |
Another solution is to require that the peer requesting a CHILD_SA |
| 1260 |
proposes traffic selectors that identify the link. For example, |
| 1261 |
if TSi includes the peer's "outer" IP address, it's probably |
| 1262 |
related to the real interface, not the virtual one. Or if TSi |
| 1263 |
includes any of the prefixes assigned by the gateway (or the link- |
| 1264 |
local or multicast prefix), it is probably related to the virtual |
| 1265 |
interface. |
| 1266 |
|
| 1267 |
These heuristics can work in many situations but have proved |
| 1268 |
inadequate in the context of IPv6-in-IPv4 tunnels [<a href="./rfc4891" title=""Using IPsec to Secure IPv6-in-IPv4 Tunnels"">RFC4891</a>], |
| 1269 |
Provider Provisioned VPNs ([<a href="#ref-VLINK" title=""Framework for IPsec Protected Virtual Links for PPVPNs"">VLINK</a>], [<a href="./rfc3884" title=""Use of IPsec Transport Mode for Dynamic Routing"">RFC3884</a>]), and Mobile IPv6 |
| 1270 |
[<a href="./rfc4877" title=""Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture"">RFC4877</a>]. Thus, <a href="#section-4">Section 4</a> includes the virtual link identifier |
| 1271 |
in all CREATE_CHILD_SA requests that apply to the virtual |
| 1272 |
interface. |
| 1273 |
|
| 1274 |
Example of other IPsec uses: |
| 1275 |
|
| 1276 |
If a VPN gateway receives a CREATE_CHILD_SA request associated |
| 1277 |
with a physical Ethernet interface, requesting an SA for |
| 1278 |
(TSi=FE80::something, dst=*), it would typically reject the |
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Eronen, et al. Experimental [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
request (or, in other words, narrow it to an empty set) because it |
| 1290 |
doesn't have SPD/PAD entries that would allow [email protected] |
| 1291 |
to request such CHILD_SAs. |
| 1292 |
|
| 1293 |
(However, it might have SPD/PAD entries that would allow |
| 1294 |
"neighboring-router.example.com" to create such SAs to protect, |
| 1295 |
for example, some routing protocol that uses link-local |
| 1296 |
addresses.) |
| 1297 |
|
| 1298 |
However, the virtual interface created when [email protected] |
| 1299 |
authenticated and sent INTERNAL_IP6_LINK would have a different |
| 1300 |
SPD/PAD, which would allow [email protected] to create this SA. |
| 1301 |
|
| 1302 |
<span class="h3"><a class="selflink" id="appendix-A.6" href="#appendix-A.6">A.6</a>. Alternative Solution Sketches</span> |
| 1303 |
|
| 1304 |
<span class="h4"><a class="selflink" id="appendix-A.6.1" href="#appendix-A.6.1">A.6.1</a>. Version -00 Sketch</span> |
| 1305 |
|
| 1306 |
The -00 version of this document contained the following solution |
| 1307 |
sketch, which is basically a combination of (1) a point-to-point link |
| 1308 |
model, (2) prefix information distributed in Neighbor Advertisements, |
| 1309 |
and (3) access control enforced outside IPsec. |
| 1310 |
|
| 1311 |
1. During IKE_AUTH, the client sends a new configuration attribute, |
| 1312 |
INTERNAL_IP6_LINK, which requests a virtual link to be created. |
| 1313 |
The attribute contains the client's interface ID for the link- |
| 1314 |
local address (other addresses may use other interface IDs). |
| 1315 |
|
| 1316 |
CP(CFG_REQUEST) = |
| 1317 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID) } |
| 1318 |
TSi = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1319 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1320 |
TSr = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1321 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) --> |
| 1322 |
|
| 1323 |
The VPN gateway replies with its own link-local interface ID (which |
| 1324 |
has to be different from the client's) and an IKEv2 Link ID (which |
| 1325 |
will be used for reauthentication). |
| 1326 |
|
| 1327 |
CP(CFG_REPLY) = |
| 1328 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID, IKEv2 Link ID) } |
| 1329 |
TSi = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1330 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1331 |
TSr = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1332 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1333 |
|
| 1334 |
At this point, both peers configure the virtual interface with the |
| 1335 |
link-local addresses. |
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Eronen, et al. Experimental [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
2. The next step is IPv6 stateless address autoconfiguration, that |
| 1346 |
is, Router Solicitation and Router Advertisement messages sent |
| 1347 |
over the IPsec SA. |
| 1348 |
|
| 1349 |
ESP(Router Solicitation: |
| 1350 |
src=::, |
| 1351 |
dst=FF02:0:0:0:0:0:0:2) --> |
| 1352 |
|
| 1353 |
<-- ESP(Router Advertisement: |
| 1354 |
src=FE80::<Gateway's Interface ID> |
| 1355 |
dst=FF02:0:0:0:0:0:0:1, |
| 1356 |
Prefix1, [Prefix2...]) |
| 1357 |
|
| 1358 |
After receiving the Router Advertisement, the client can configure |
| 1359 |
unicast addresses from the advertised prefixes, using any proper |
| 1360 |
interface ID. The VPN gateway does not simultaneously assign the |
| 1361 |
same prefixes to any other client and does not itself configure |
| 1362 |
addresses from these prefixes. Thus, the client does not have to |
| 1363 |
perform Duplicate Address Detection (DAD). |
| 1364 |
|
| 1365 |
3. Reauthentication works basically the same way as in <a href="#section-4">Section 4</a>; |
| 1366 |
the client includes the IKEv2 Link ID in the INTERNAL_IP6_LINK |
| 1367 |
attribute. |
| 1368 |
|
| 1369 |
4. Creating and rekeying IPsec SAs works basically the same way as |
| 1370 |
in <a href="#section-4.3">Section 4.3</a>; the client includes the IKEv2 Link ID in those |
| 1371 |
CHILD_SA requests that are related to the virtual link. |
| 1372 |
|
| 1373 |
Comments: This was changed in the -01 version of this document based |
| 1374 |
on feedback from VPN vendors; while the solution looks nice on paper, |
| 1375 |
it is claimed to be unnecessarily complex to implement when the IKE |
| 1376 |
implementation and IPv6 stack are from different companies. |
| 1377 |
Furthermore, enforcing access control outside IPsec is a significant |
| 1378 |
architectural change compared to current IPv4 solutions. |
| 1379 |
|
| 1380 |
<span class="h4"><a class="selflink" id="appendix-A.6.2" href="#appendix-A.6.2">A.6.2</a>. Router Aggregation Sketch #1</span> |
| 1381 |
|
| 1382 |
Hemant Singh helped sketch the following solution during the IETF 70 |
| 1383 |
meeting in Vancouver. It combines (1) the router aggregation link |
| 1384 |
model, (2) prefix information distributed in IKEv2 messages, (3) |
| 1385 |
unique address allocation with stateless address autoconfiguration |
| 1386 |
(with VPN gateway trapping NS messages and spoofing NA replies), and |
| 1387 |
(4) access control enforced (partly) outside IPsec. |
| 1388 |
|
| 1389 |
1. During IKE_AUTH, the client sends a new configuration attribute, |
| 1390 |
INTERNAL_IP6_LINK, which requests a virtual link to be created. |
| 1391 |
The attribute contains the client's interface ID for the link- |
| 1392 |
local address (other addresses may use other interface IDs). |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Eronen, et al. Experimental [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
CP(CFG_REQUEST) = |
| 1402 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID) } |
| 1403 |
TSi = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1404 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1405 |
TSr = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1406 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) --> |
| 1407 |
|
| 1408 |
The VPN gateway replies with its own Link-Local Interface ID (which |
| 1409 |
has to be different from the client's), an IKEv2 Link ID (which will |
| 1410 |
be used for reauthentication and CREATE_CHILD_SA messages), and zero |
| 1411 |
or more INTERNAL_IP6_PREFIX attributes. The traffic selectors |
| 1412 |
proposed by the initiator are also narrowed to contain only the |
| 1413 |
assigned prefixes (and the link-local prefix). |
| 1414 |
|
| 1415 |
CP(CFG_REPLY) = |
| 1416 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID, IKEv2 Link ID), |
| 1417 |
INTERNAL_IP6_PREFIX(Prefix1/64), |
| 1418 |
[INTERNAL_IP6_PREFIX(Prefix2/64),...] } |
| 1419 |
TSi = ((0, 0-65535, |
| 1420 |
FE80::<Client's Interface ID> - |
| 1421 |
FE80::<Client's Interface ID>) |
| 1422 |
(0, 0-65535, |
| 1423 |
Prefix1::0 - |
| 1424 |
Prefix1::FFFF:FFFF:FFFF:FFFF), |
| 1425 |
[(0, 0-65535, |
| 1426 |
Prefix2::0 - |
| 1427 |
Prefix2::FFFF:FFFF:FFFF:FFFF), ...]) |
| 1428 |
TSr = (0, 0-65535, |
| 1429 |
0:0:0:0:0:0:0:0 - |
| 1430 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1431 |
|
| 1432 |
2. The client now configures tentative unicast addresses from the |
| 1433 |
prefixes given by the gateway, and performs Duplicate Address |
| 1434 |
Detection (DAD) for them. |
| 1435 |
|
| 1436 |
The Neighbor Solicitation messages are processed by the VPN |
| 1437 |
gateway; if the target address is already in use by some other |
| 1438 |
VPN client, the gateway replies with a Neighbor Advertisement. |
| 1439 |
If the target address is not already in use, the VPN gateway |
| 1440 |
notes that it is now being used by this client and updates its |
| 1441 |
forwarding state accordingly. |
| 1442 |
|
| 1443 |
|
| 1444 |
|
| 1445 |
|
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Eronen, et al. Experimental [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
Comments: The main disadvantages of this solution are non-standard |
| 1458 |
processing of NS messages (which are used to update the gateway's |
| 1459 |
forwarding state), and performing access control partly outside |
| 1460 |
IPsec. |
| 1461 |
|
| 1462 |
<span class="h4"><a class="selflink" id="appendix-A.6.3" href="#appendix-A.6.3">A.6.3</a>. Router Aggregation Sketch #2</span> |
| 1463 |
|
| 1464 |
This is basically similar to the version -00 sketch described above |
| 1465 |
but uses the router aggregation link model. In other words, it |
| 1466 |
combines (1) the router aggregation link model, (2) prefix |
| 1467 |
information distributed in Neighbor Advertisements, (3) unique |
| 1468 |
address allocation with stateless address autoconfiguration (with the |
| 1469 |
VPN gateway trapping NS messages and spoofing NA replies), and (4) |
| 1470 |
access control enforced outside IPsec. |
| 1471 |
|
| 1472 |
1. During IKE_AUTH, the client sends a new configuration attribute, |
| 1473 |
INTERNAL_IP6_LINK, which requests a virtual link to be created. |
| 1474 |
The attribute contains the client's interface ID for the link- |
| 1475 |
local address (other addresses may use other interface IDs). |
| 1476 |
|
| 1477 |
CP(CFG_REQUEST) = |
| 1478 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID) } |
| 1479 |
TSi = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1480 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1481 |
TSr = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1482 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) --> |
| 1483 |
|
| 1484 |
The VPN gateway replies with its own Link-Local Interface ID (which |
| 1485 |
has to be different from the client's) and an IKEv2 Link ID (which |
| 1486 |
will be used for reauthentication). |
| 1487 |
|
| 1488 |
CP(CFG_REPLY) = |
| 1489 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID, IKEv2 Link ID) } |
| 1490 |
TSi = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1491 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1492 |
TSr = (0, 0-65535, 0:0:0:0:0:0:0:0 - |
| 1493 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1494 |
|
| 1495 |
At this point, both peers configure the virtual interface with the |
| 1496 |
link-local addresses. |
| 1497 |
|
| 1498 |
2. The next step is IPv6 stateless address autoconfiguration, that |
| 1499 |
is, Router Solicitation and Router Advertisement messages sent |
| 1500 |
over the IPsec SA. |
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Eronen, et al. Experimental [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
ESP(Router Solicitation: |
| 1514 |
src=::, |
| 1515 |
dst=FF02:0:0:0:0:0:0:2) --> |
| 1516 |
|
| 1517 |
<-- ESP(Router Advertisement: |
| 1518 |
src=FE80::<Gateway's Interface ID> |
| 1519 |
dst=FF02:0:0:0:0:0:0:1, |
| 1520 |
Prefix1, [Prefix2...]) |
| 1521 |
|
| 1522 |
3. The client now configures tentative unicast addresses from the |
| 1523 |
prefixes given by the gateway and performs Duplicate Address |
| 1524 |
Detection (DAD) for them. |
| 1525 |
|
| 1526 |
The Neighbor Solicitation messages are processed by the VPN |
| 1527 |
gateway; if the target address is already in use by some other |
| 1528 |
VPN client, the gateway replies with a Neighbor Advertisement. |
| 1529 |
If the target address is not already in use, the VPN gateway |
| 1530 |
notes that it is now being used by this client and updates its |
| 1531 |
forwarding state accordingly. |
| 1532 |
|
| 1533 |
Comments: The main disadvantages of this solution are non-standard |
| 1534 |
processing of NS messages (which are used to update the gateway's |
| 1535 |
forwarding state) and performing access control outside IPsec. |
| 1536 |
|
| 1537 |
<span class="h4"><a class="selflink" id="appendix-A.6.4" href="#appendix-A.6.4">A.6.4</a>. IPv4-Like Sketch</span> |
| 1538 |
|
| 1539 |
This sketch resembles the current IPv4 configuration payloads and |
| 1540 |
combines (1) the router aggregation link model, (2) prefix |
| 1541 |
information distributed in IKEv2 messages, (3) unique address |
| 1542 |
allocation with IKEv2 messages, and (4) access control enforced by |
| 1543 |
IPsec SAD/SPD. |
| 1544 |
|
| 1545 |
1. During IKE_AUTH, the client sends a new configuration attribute, |
| 1546 |
INTERNAL_IP6_LINK, which requests a virtual link to be created. |
| 1547 |
The attribute contains the client's interface ID for the link- |
| 1548 |
local address (other addresses may use other interface IDs). |
| 1549 |
|
| 1550 |
CP(CFG_REQUEST) = |
| 1551 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID) } |
| 1552 |
TSi = (0, 0-65535, |
| 1553 |
0:0:0:0:0:0:0:0 - |
| 1554 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1555 |
TSr = (0, 0-65535, |
| 1556 |
0:0:0:0:0:0:0:0 - |
| 1557 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) --> |
| 1558 |
|
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Eronen, et al. Experimental [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
The VPN gateway replies with its own Link-Local Interface ID (which |
| 1570 |
has to be different from the client's), an IKEv2 Link ID (which will |
| 1571 |
be used for reauthentication and CREATE_CHILD_SA messages), and zero |
| 1572 |
or more INTERNAL_IP6_ADDRESS2 attributes. Each attribute contains |
| 1573 |
one address from a particular prefix. |
| 1574 |
|
| 1575 |
CP(CFG_REPLY) = |
| 1576 |
{ INTERNAL_IP6_LINK(Link-Local Interface ID, IKEv2 Link ID), |
| 1577 |
INTERNAL_IP6_ADDRESS2(Prefix1+Client's Interface ID1), |
| 1578 |
[INTERNAL_IP6_ADDRESS2(Prefix2+Client's Interface ID2),...], |
| 1579 |
TSi = ((0, 0-65535, |
| 1580 |
FE80::<Client's Link-Local Interface ID> - |
| 1581 |
FE80::<Client's Link-Local Interface ID>) |
| 1582 |
(0, 0-65535, |
| 1583 |
Prefix1::<Client's Interface ID1> - |
| 1584 |
Prefix1::<Client's Interface ID1>), |
| 1585 |
[(0, 0-65535, |
| 1586 |
Prefix2::<Client's Interface ID2> - |
| 1587 |
Prefix2::<Client's Interface ID2>), ...]) |
| 1588 |
TSr = (0, 0-65535, |
| 1589 |
0:0:0:0:0:0:0:0 - |
| 1590 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1591 |
|
| 1592 |
Since the VPN gateway keeps track of address uniqueness, there is no |
| 1593 |
need to perform Duplicate Address Detection. |
| 1594 |
|
| 1595 |
2. If the client wants additional addresses later (for example, with |
| 1596 |
a specific interface ID), it requests them in a separate |
| 1597 |
CREATE_CHILD_SA exchange. For example: |
| 1598 |
|
| 1599 |
CP(CFG_REQUEST) = |
| 1600 |
{ INTERNAL_IP6_ADDRESS2(Prefix1+Client's Interface ID3) } |
| 1601 |
TSi = (0, 0-65535, |
| 1602 |
Prefix1::0 - |
| 1603 |
Prefix1::FFFF:FFFF:FFFF:FFFF>), |
| 1604 |
TSr = (0, 0-65535, |
| 1605 |
0:0:0:0:0:0:0:0 - |
| 1606 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) --> |
| 1607 |
|
| 1608 |
If the requested address is not currently in use by some other |
| 1609 |
client, the VPN gateway simply returns the same address and the |
| 1610 |
appropriately narrowed traffic selectors. |
| 1611 |
|
| 1612 |
|
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Eronen, et al. Experimental [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
CP(CFG_REQUEST) = |
| 1626 |
{ INTERNAL_IP6_ADDRESS2(Prefix1+Client's Interface ID3) } |
| 1627 |
TSi = ((0, 0-65535, |
| 1628 |
Prefix1::<Client's Interface ID3> - |
| 1629 |
Prefix1::<Client's Interface ID3>), |
| 1630 |
TSr = (0, 0-65535, |
| 1631 |
0:0:0:0:0:0:0:0 - |
| 1632 |
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF) |
| 1633 |
|
| 1634 |
Comments: The main advantage of this solution is that it's quite |
| 1635 |
close to the current IPv4 way of doing things. By adding explicit |
| 1636 |
link creation (with Link ID for reauthentication/SPD selection and |
| 1637 |
link-local addresses) and slightly changing the semantics (and also |
| 1638 |
name) of the INTERNAL_IP6_ADDRESS attribute (which can return more |
| 1639 |
attributes than was asked), we get much of the needed functionality. |
| 1640 |
|
| 1641 |
The biggest disadvantages are probably potentially complex |
| 1642 |
implementation dependency for interface ID selection (see |
| 1643 |
<a href="#section-3.3">Section 3.3</a>) and the multi-link subnet model. |
| 1644 |
|
| 1645 |
<span class="h4"><a class="selflink" id="appendix-A.6.5" href="#appendix-A.6.5">A.6.5</a>. Sketch Based on <a href="./rfc3456">RFC 3456</a></span> |
| 1646 |
|
| 1647 |
For completeness: a solution modeled after [<a href="./rfc3456" title=""Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode"">RFC3456</a>] would combine |
| 1648 |
(1) the router aggregation link model, (2) prefix information |
| 1649 |
distribution and unique address allocation with DHCPv6, and (3) |
| 1650 |
access control enforced by IPsec SAD/SPD. |
| 1651 |
|
| 1652 |
|
| 1653 |
|
| 1654 |
|
| 1655 |
|
| 1656 |
|
| 1657 |
|
| 1658 |
|
| 1659 |
|
| 1660 |
|
| 1661 |
|
| 1662 |
|
| 1663 |
|
| 1664 |
|
| 1665 |
|
| 1666 |
|
| 1667 |
|
| 1668 |
|
| 1669 |
|
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Eronen, et al. Experimental [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Evaluation (Non-Normative)</span> |
| 1682 |
|
| 1683 |
<a href="#section-3">Section 3</a> describes the goals and requirements for IPv6 configuration |
| 1684 |
in IKEv2. This appendix briefly summarizes how the solution |
| 1685 |
specified in Sections <a href="#section-4">4</a> and <a href="#section-5">5</a> meets these goals. |
| 1686 |
|
| 1687 |
o (3.1) Assigning addresses from multiple prefixes is supported, |
| 1688 |
without requiring the client to know beforehand how many prefixes |
| 1689 |
are needed. |
| 1690 |
|
| 1691 |
o (3.2) Link-local addresses are assigned and can be used for |
| 1692 |
protocols between the VPN client and gateway. |
| 1693 |
|
| 1694 |
o (3.3) The entire prefix is assigned to a single client, so the |
| 1695 |
client can freely select any number of interface IDs (which may |
| 1696 |
depend on the prefix). |
| 1697 |
|
| 1698 |
o (3.4) This document does not specify how the VPN client would |
| 1699 |
share the VPN connection with other devices. However, since the |
| 1700 |
entire prefix is assigned to a single client, the client could |
| 1701 |
further assign addresses from it without requiring coordination |
| 1702 |
with the VPN gateway. |
| 1703 |
|
| 1704 |
o (3.5) The solution does not add any new periodic messages over the |
| 1705 |
VPN tunnel. |
| 1706 |
|
| 1707 |
o (3.5) Reauthentication works (see <a href="#section-4.2">Section 4.2</a>). |
| 1708 |
|
| 1709 |
o (3.5) The solution is compatible with other IPsec uses since the |
| 1710 |
LINK_ID notification makes it unambiguous which CHILD_SAs are |
| 1711 |
related to the virtual link and which are not (see Sections <a href="#section-4.3">4.3</a> |
| 1712 |
and 5.3). |
| 1713 |
|
| 1714 |
o (3.5) The new mechanisms do not prevent the VPN client and/or |
| 1715 |
gateway from implementing the INTERNAL_IP6_ADDRESS configuration |
| 1716 |
attribute as well; however, the two mechanisms are not intended to |
| 1717 |
be used simultaneously (see <a href="#section-4.5">Section 4.5</a>). |
| 1718 |
|
| 1719 |
o (3.5) Implementation dependencies are, obviously, implementation |
| 1720 |
dependent (and their cleanliness somewhat subjective). Possible |
| 1721 |
drawbacks of some alternative solutions are discussed in |
| 1722 |
<a href="#appendix-A.6">Appendix A.6</a>. |
| 1723 |
|
| 1724 |
o (3.5) The mechanism for configuring the prefixes (configuration |
| 1725 |
payloads) is specific to IKEv2, for reasons described in |
| 1726 |
<a href="#appendix-A">Appendix A</a>. However, <a href="#section-4.1">Section 4.1</a> recommends using DHCPv6 |
| 1727 |
Information-Request message for obtaining other configuration |
| 1728 |
information (such as DNS server addresses). |
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Eronen, et al. Experimental [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc5739">RFC 5739</a> IPv6 Configuration in IKEv2 February 2010</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
Authors' Addresses |
| 1738 |
|
| 1739 |
Pasi Eronen |
| 1740 |
Nokia Research Center |
| 1741 |
P.O. Box 407 |
| 1742 |
FIN-00045 Nokia Group |
| 1743 |
Finland |
| 1744 |
|
| 1745 |
EMail: [email protected] |
| 1746 |
|
| 1747 |
|
| 1748 |
Julien Laganier |
| 1749 |
QUALCOMM Incorporated |
| 1750 |
5775 Morehouse Drive |
| 1751 |
San Diego, CA 92121 |
| 1752 |
USA |
| 1753 |
|
| 1754 |
Phone: +1 858 658 3538 |
| 1755 |
EMail: [email protected] |
| 1756 |
|
| 1757 |
|
| 1758 |
Cheryl Madson |
| 1759 |
Cisco Systems, Inc. |
| 1760 |
510 MacCarthy Drive |
| 1761 |
Milpitas, CA |
| 1762 |
USA |
| 1763 |
|
| 1764 |
EMail: [email protected] |
| 1765 |
|
| 1766 |
|
| 1767 |
|
| 1768 |
|
| 1769 |
|
| 1770 |
|
| 1771 |
|
| 1772 |
|
| 1773 |
|
| 1774 |
|
| 1775 |
|
| 1776 |
|
| 1777 |
|
| 1778 |
|
| 1779 |
|
| 1780 |
|
| 1781 |
|
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
Eronen, et al. Experimental [Page 32] |
| 1789 |
</pre> |