Debian Codegraph @

rfc6911.html

raw
1 <pre>Internet Engineering Task Force (IETF) W. Dec, Ed.
2 Request for Comments: 6911 Cisco Systems, Inc.
3 Category: Standards Track B. Sarikaya
4 ISSN: 2070-1721 Huawei USA
5 G. Zorn, Ed.
6 Network Zen
7 D. Miles
8 Google
9 B. Lourdelet
10 Juniper Networks
11 April 2013
12
13
14 <span class="h1">RADIUS Attributes for IPv6 Access Networks</span>
15
16 Abstract
17
18 This document specifies additional IPv6 RADIUS Attributes useful in
19 residential broadband network deployments. The Attributes, which are
20 used for authorization and accounting, enable assignment of a host
21 IPv6 address and an IPv6 DNS server address via DHCPv6, assignment of
22 an IPv6 route announced via router advertisement, assignment of a
23 named IPv6 delegated prefix pool, and assignment of a named IPv6 pool
24 for host DHCPv6 addressing.
25
26 Status of This Memo
27
28 This is an Internet Standards Track document.
29
30 This document is a product of the Internet Engineering Task Force
31 (IETF). It represents the consensus of the IETF community. It has
32 received public review and has been approved for publication by the
33 Internet Engineering Steering Group (IESG). Further information on
34 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
35
36 Information about the current status of this document, any errata,
37 and how to provide feedback on it may be obtained at
38 <a href="http://www.rfc-editor.org/info/rfc6911">http://www.rfc-editor.org/info/rfc6911</a>.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Dec, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2013 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 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-1.1">1.1</a>. Requirements Language . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
76 <a href="#section-2">2</a>. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
77 <a href="#section-2.1">2.1</a>. IPv6 Address Assignment . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
78 <a href="#section-2.2">2.2</a>. DNS Servers . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
79 <a href="#section-2.3">2.3</a>. IPv6 Route Information . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
80 <a href="#section-2.4">2.4</a>. Delegated IPv6 Prefix Pool . . . . . . . . . . . . . . . <a href="#page-6">6</a>
81 <a href="#section-2.5">2.5</a>. Stateful IPv6 Address Pool . . . . . . . . . . . . . . . <a href="#page-6">6</a>
82 <a href="#section-3">3</a>. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
83 <a href="#section-3.1">3.1</a>. Framed-IPv6-Address . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
84 <a href="#section-3.2">3.2</a>. DNS-Server-IPv6-Address . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
85 <a href="#section-3.3">3.3</a>. Route-IPv6-Information . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
86 <a href="#section-3.4">3.4</a>. Delegated-IPv6-Prefix-Pool . . . . . . . . . . . . . . . <a href="#page-10">10</a>
87 <a href="#section-3.5">3.5</a>. Stateful-IPv6-Address-Pool . . . . . . . . . . . . . . . <a href="#page-11">11</a>
88 <a href="#section-3.6">3.6</a>. Table of Attributes . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
89 <a href="#section-4">4</a>. Diameter Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
90 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
91 <a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
92 <a href="#section-7">7</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
93 <a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
94 <a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
95 <a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Dec, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 This document specifies additional RADIUS Attributes used to support
116 configuration of DHCPv6 and/or ICMPv6 Router Advertisement (RA)
117 parameters on a per-user basis. The Attributes, which complement
118 those defined in [<a href="./rfc3162" title="&quot;RADIUS and IPv6&quot;">RFC3162</a>] and [<a href="./rfc4818" title="&quot;RADIUS Delegated-IPv6-Prefix Attribute&quot;">RFC4818</a>], support the following:
119
120 o The assignment of specific IPv6 addresses to hosts via DHCPv6.
121
122 o The assignment of an IPv6 DNS server address, via DHCPv6 or Router
123 Advertisement [<a href="./rfc6106" title="&quot;IPv6 Router Advertisement Options for DNS Configuration&quot;">RFC6106</a>].
124
125 o The configuration of more specific routes to be announced to the
126 user via the Route Information Option defined in <a href="./rfc4191#section-2.3">[RFC4191],
127 Section&nbsp;2.3</a>.
128
129 o The assignment of a named delegated prefix pool for use with "IPv6
130 Prefix Options for Dynamic Host Configuration Protocol (DHCP)
131 version 6" [<a href="./rfc3633" title="&quot;IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6&quot;">RFC3633</a>].
132
133 o The assignment of a named stateful address pool for use with
134 DHCPv6 stateful address assignment [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>].
135
136 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
137
138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
140 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
141
142 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Deployment Scenarios</span>
143
144 The extensions in this document are intended to be applicable across
145 a wide variety of network access scenarios in which RADIUS is
146 involved. One such typical network scenario is illustrated in Figure
147 1. It is composed of an IP Routing Residential Gateway (RG) or host;
148 a Layer 2 Access Node (AN), e.g., a Digital Subscriber Line Access
149 Multiplexer (DSLAM); an IP Network Access Server (NAS) (incorporating
150 an Authentication, Authorization, and Accounting (AAA) client); and a
151 AAA server.
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Dec, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
167
168
169 +-----+
170 | AAA |
171 | |
172 +--+--+
173 ^
174 .
175 .(RADIUS)
176 .
177 v
178 +------+ +---+---+
179 +------+ | | | |
180 | RG/ +-------| AN +-----------+----------+ NAS |
181 | host | | | | |
182 +------+ (DSL) +------+ (Ethernet) +-------+
183
184 Figure 1
185
186 In the depicted scenario, the NAS may utilize an IP address
187 configuration protocol (e.g., DHCPv6) to handle address assignment to
188 RGs/hosts. The RADIUS server authenticates each RG/host and returns
189 the Attributes used for authorization and accounting. These
190 Attributes can include a host's IPv6 address, a DNS server address,
191 and a set of IPv6 routes to be advertised via any suitable protocol,
192 e.g., ICMPv6 (Neighbor Discovery). The name of a prefix pool to be
193 used for DHCPv6 Prefix Delegation or the name of an address pool to
194 be used for DHCPv6 address assignment can also be Attributes provided
195 to the NAS by the RADIUS AAA server.
196
197 The following subsections discuss how these Attributes are used in
198 more detail.
199
200 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. IPv6 Address Assignment</span>
201
202 DHCPv6 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] provides a mechanism to assign one or more non-
203 temporary IPv6 addresses to hosts. To provide a DHCPv6 server
204 residing on a NAS with one or more IPv6 addresses to be assigned,
205 this document specifies the Framed-IPv6-Address Attribute
206 (<a href="#section-3.1">Section 3.1</a>).
207
208 While [<a href="./rfc3162" title="&quot;RADIUS and IPv6&quot;">RFC3162</a>] permits the specification of an IPv6 address via the
209 combination of the Framed-Interface-Id and Framed-IPv6-Prefix
210 Attributes, this separation is more natural for use with PPP's IPv6
211 Control Protocol than it is for use with DHCPv6, and the use of a
212 single IPv6 address Attribute makes for easier processing of
213 accounting records.
214
215
216
217
218
219
220 <span class="grey">Dec, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
223
224
225 Because DHCPv6 can be deployed on the same network as ICMPv6
226 stateless address autoconfiguration (SLAAC) [<a href="./rfc4862" title="&quot;IPv6 Stateless Address Autoconfiguration&quot;">RFC4862</a>], it is possible
227 that the NAS will require both stateful and stateless configuration
228 information. Therefore, it is possible for the Framed-IPv6-Address,
229 Framed-IPv6-Prefix, and Framed-Interface-Id Attributes [<a href="./rfc3162" title="&quot;RADIUS and IPv6&quot;">RFC3162</a>] to
230 be included within the same packet. To avoid ambiguity in this case,
231 the Framed-IPv6-Address Attribute is intended for authorization and
232 accounting of DHCPv6-assigned addresses, and the Framed-IPv6-Prefix
233 and Framed-Interface-Id Attributes are used for authorization and
234 accounting of addresses assigned via SLAAC.
235
236 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. DNS Servers</span>
237
238 DHCPv6 provides an option for configuring a host with the IPv6
239 address of a DNS server. The IPv6 address of a DNS server can also
240 be conveyed to the host using ICMPv6 with Router Advertisements, via
241 the Recursive DNS Server Option [<a href="./rfc6106" title="&quot;IPv6 Router Advertisement Options for DNS Configuration&quot;">RFC6106</a>]. To provide the NAS with
242 the IPv6 address of one or more DNS servers, this document specifies
243 the DNS-Server-IPv6-Address Attribute (<a href="#section-3.2">Section 3.2</a>).
244
245 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IPv6 Route Information</span>
246
247 The IPv6 Route Information Option [<a href="./rfc4191" title="&quot;Default Router Preferences and More-Specific Routes&quot;">RFC4191</a>], is intended to be used
248 to inform a host connected to the NAS that a specific route is
249 reachable via any given NAS.
250
251 This document specifies the Route-IPv6-Information Attribute
252 (<a href="#section-3.3">Section 3.3</a>) that allows the AAA server to provision the
253 announcement by the NAS of a specific Route Information Option to an
254 accessing host. The NAS may advertise this route using the method
255 defined in <a href="./rfc4191">RFC 4191</a> or other equivalent methods. Any other
256 information, such as preference or lifetime values, that is to be
257 present in the actual announcement using a given method is assumed to
258 be determined by the NAS using means not specified by this document
259 (e.g., local configuration on the NAS).
260
261 While the Framed-IPv6-Prefix Attribute (<a href="./rfc3162#section-2.3">[RFC3162], Section&nbsp;2.3</a>)
262 allows the route to be advertised in an RA, it cannot be used to
263 configure more specific routes. While the Framed-IPv6-Route
264 Attribute (<a href="./rfc3162#section-2.5">[RFC3162], Section&nbsp;2.5</a>) causes the route to be configured
265 on the NAS and potentially to be announced via an IP routing
266 protocol, depending on the value of Framed-Routing, it does not
267 result in the route being announced in an RA.
268
269
270
271
272
273
274
275
276 <span class="grey">Dec, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
279
280
281 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Delegated IPv6 Prefix Pool</span>
282
283 DHCPv6 Prefix Delegation (DHCPv6-PD) [<a href="./rfc3633" title="&quot;IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6&quot;">RFC3633</a>] involves a delegating
284 router selecting a prefix and delegating it on a temporary basis to a
285 requesting router. The delegating router may implement a number of
286 strategies as to how it chooses what prefix is to be delegated to a
287 requesting router, one of them being the use of a local named prefix
288 pool. The Delegated-IPv6-Prefix-Pool Attribute (<a href="#section-3.4">Section 3.4</a>) allows
289 the RADIUS server to convey a prefix pool name to a NAS that is
290 hosting a DHCPv6-PD server and that is acting as a delegating router.
291
292 Because DHCPv6 Prefix Delegation can be used with SLAAC on the same
293 network, it is possible for the Delegated-IPv6-Prefix-Pool and
294 Framed-IPv6-Pool Attributes to be included within the same packet.
295 To avoid ambiguity in this scenario, use of the Delegated-IPv6-
296 Prefix-Pool Attribute should be restricted to authorization and
297 accounting of prefix pools used in DHCPv6 Prefix Delegation, and the
298 Framed-IPv6-Pool Attribute should be used for authorization and
299 accounting of prefix pools used in SLAAC.
300
301 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Stateful IPv6 Address Pool</span>
302
303 DHCPv6 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] provides a mechanism to assign one or more non-
304 temporary IPv6 addresses to hosts. <a href="#section-3.1">Section 3.1</a> introduces the
305 Framed-IPv6-Address Attribute to be used to provide a DHCPv6 server
306 residing on a NAS with one or more IPv6 addresses to be assigned to
307 the clients. An alternative way to achieve a similar result is for
308 the NAS to select the IPv6 address to be assigned from an address
309 pool configured for this purpose on the NAS. This document specifies
310 the Stateful-IPv6-Address-Pool Attribute (<a href="#section-3.5">Section 3.5</a>) to allow the
311 RADIUS server to convey a pool name to be used for such stateful
312 DHCPv6-based addressing and for any subsequent accounting.
313
314 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Attributes</span>
315
316 The fields shown in the diagrams below are transmitted from left to
317 right.
318
319 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Framed-IPv6-Address</span>
320
321 The Framed-IPv6-Address Attribute indicates an IPv6 address that is
322 assigned to the NAS-facing interface of the RG/host. It MAY be used
323 in Access-Accept packets and MAY appear multiple times. It MAY be
324 used in an Access-Request packet as a hint by the NAS to the RADIUS
325 server that it would prefer this IPv6 address, but the RADIUS server
326 is not required to honor the hint. Because it is assumed that the
327
328
329
330
331
332 <span class="grey">Dec, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
335
336
337 NAS will add a route corresponding to the address, it is not
338 necessary for the RADIUS server to also send a host Framed-IPv6-Route
339 Attribute for the same address.
340
341 This Attribute can be used by a DHCPv6 process on the NAS to assign a
342 unique IPv6 address to the RG/host.
343
344 A summary of the Framed-IPv6-Address Attribute format is shown below.
345 The format of the Address field is identical to that of the
346 corresponding field in the NAS-IPv6-Address Attribute [<a href="./rfc3162" title="&quot;RADIUS and IPv6&quot;">RFC3162</a>].
347
348 0 1 2 3
349 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
350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
351 | Type | Length | Address
352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
353 Address (cont)
354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
355 Address (cont)
356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
357 Address (cont)
358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
359 Address (cont) |
360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
361
362 Type
363
364 168 for Framed-IPv6-Address
365
366 Length
367
368 18
369
370 Address
371
372 A 128-bit IPv6 address.
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Dec, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
391
392
393 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. DNS-Server-IPv6-Address</span>
394
395 The DNS-Server-IPv6-Address Attribute contains the IPv6 address of a
396 DNS server. This Attribute MAY be included multiple times in Access-
397 Accept packets when the intention is for a NAS to announce more than
398 one DNS server address to an RG/host. The Attribute MAY be used in
399 an Access-Request packet as a hint by the NAS to the RADIUS server
400 regarding the DNS IPv6 address, but the RADIUS server is not required
401 to honor the hint.
402
403 The content of this Attribute can be copied to an instance of the
404 DHCPv6 DNS Recursive Name Server Option [<a href="./rfc3646" title="&quot;DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3646</a>] or to an IPv6
405 Router Advertisement Recursive DNS Server Option [<a href="./rfc6106" title="&quot;IPv6 Router Advertisement Options for DNS Configuration&quot;">RFC6106</a>]. If more
406 than one DNS-Server-IPv6-Address Attribute is present in the Access-
407 Accept packet, the addresses from the Attributes SHOULD be copied in
408 the same order as received.
409
410 A summary of the DNS-Server-IPv6-Address Attribute format is given
411 below. The format of the Address field is the same as that of the
412 corresponding field in the NAS-IPv6-Address Attribute [<a href="./rfc3162" title="&quot;RADIUS and IPv6&quot;">RFC3162</a>].
413
414 0 1 2 3
415 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
416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
417 | Type | Length | Address
418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
419 Address (cont)
420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
421 Address (cont)
422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
423 Address (cont)
424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
425 Address (cont) |
426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
427
428 Type
429
430 169 for DNS-Server-IPv6-Address
431
432 Length
433
434 18
435
436 Address
437
438 The 128-bit IPv6 address of a DNS server.
439
440
441
442
443
444 <span class="grey">Dec, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
447
448
449 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Route-IPv6-Information</span>
450
451 The Route-IPv6-Information Attribute specifies a prefix (and
452 corresponding route) for the user on the NAS, which is to be
453 announced using the Route Information Option defined in "Default
454 Router Preferences and More Specific Routes" <a href="./rfc4191#section-2.3">[RFC4191], Section&nbsp;2.3</a>.
455 It is used in the Access-Accept packet and can appear multiple times.
456 It MAY be used in an Access-Request packet as a hint by the NAS to
457 the RADIUS server, but the RADIUS server is not required to honor the
458 hint. The Route-IPv6-Information Attribute format is depicted below.
459 The format of the prefix is as per [<a href="./rfc3162" title="&quot;RADIUS and IPv6&quot;">RFC3162</a>].
460
461 0 1 2 3
462 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
463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
464 | Type | Length | Reserved | Prefix-Length |
465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
466 | |
467 . Prefix (variable) .
468 . .
469 | |
470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
471
472 Type
473
474 170 for Route-IPv6-Information
475
476 Length
477
478 Length, in bytes. At least 4 and no larger than 20; typically, 12
479 or less.
480
481 Prefix Length
482
483 8-bit unsigned integer. The number of leading bits in the prefix
484 that are valid. The value can range from 0 to 128. The prefix
485 field is 0, 8, or 16 octets depending on Length.
486
487 Prefix
488
489 Variable-length field containing an IP prefix. The prefix length
490 field contains the number of valid leading bits in the prefix.
491 The bits in the prefix after the prefix length, if any, are
492 reserved and MUST be initialized to zero.
493
494
495
496
497
498
499
500 <span class="grey">Dec, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
503
504
505 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Delegated-IPv6-Prefix-Pool</span>
506
507 The Delegated-IPv6-Prefix-Pool Attribute contains the name of an
508 assigned pool that SHOULD be used to select an IPv6 delegated prefix
509 for the user on the NAS. If a NAS does not support prefix pools, the
510 NAS MUST ignore this Attribute. It MAY be used in an Access-Request
511 packet as a hint by the NAS to the RADIUS server regarding the pool,
512 but the RADIUS server is not required to honor the hint.
513
514 A summary of the Delegated-IPv6-Prefix-Pool Attribute format is shown
515 below.
516
517 0 1 2
518 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
520 | Type | Length | String...
521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
522
523 Type
524
525 171 for Delegated-IPv6-Prefix-Pool
526
527 Length
528
529 Length, in bytes. At least 3.
530
531 String
532
533 The string field contains the name of an assigned IPv6 prefix pool
534 configured on the NAS. The field is not NULL (hexadecimal 00)
535 terminated.
536
537 Note: The string data type is as documented in [<a href="./rfc6158" title="&quot;RADIUS Design Guidelines&quot;">RFC6158</a>] and carries
538 binary data that is external to the RADIUS protocol, e.g., the name
539 of a pool of prefixes configured on the NAS.
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Dec, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
559
560
561 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Stateful-IPv6-Address-Pool</span>
562
563 The Stateful-IPv6-Address-Pool Attribute contains the name of an
564 assigned pool that SHOULD be used to select an IPv6 address for the
565 user on the NAS. If a NAS does not support address pools, the NAS
566 MUST ignore this Attribute. A summary of the Stateful-IPv6-Address-
567 Pool Attribute format is shown below. It MAY be used in an Access-
568 Request packet as a hint by the NAS to the RADIUS server regarding
569 the pool, but the RADIUS server is not required to honor the hint.
570
571 0 1 2
572 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
573 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
574 | Type | Length | String...
575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
576
577 Type
578
579 172 for Stateful-IPv6-Address-Pool
580
581 Length
582
583 Length, in bytes. At least 3.
584
585 String
586
587 The string field contains the name of an assigned IPv6 stateful
588 address pool configured on the NAS. The field is not NULL
589 (hexadecimal 00) terminated.
590
591 Note: The string data type is as documented in [<a href="./rfc6158" title="&quot;RADIUS Design Guidelines&quot;">RFC6158</a>] and carries
592 binary data that is external to the RADIUS protocol, e.g., the name
593 of a pool of addresses configured on the NAS.
594
595 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Table of Attributes</span>
596
597 The following table provides a guide to which Attributes may be found
598 in which kinds of packets, and in what quantity. The optional
599 inclusion of the options in Access Request messages is intended to
600 allow for a NAS to provide the RADIUS server with a hint of the
601 Attributes in advance of user authentication, which may be useful in
602 cases in which a user reconnects or has a static address. The server
603 is under no obligation to honor such hints.
604
605
606
607
608
609
610
611
612 <span class="grey">Dec, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
615
616
617 Request Accept Reject Challenge Accounting # Attribute
618 Request
619 0+ 0+ 0 0 0+ 168 Framed-IPv6-Address
620 0+ 0+ 0 0 0+ 169 DNS-Server-IPv6-Address
621 0+ 0+ 0 0 0+ 170 Route-IPv6-Information
622 0+ 0+ 0 0 0+ 171 Delegated-IPv6-Prefix-Pool
623 0+ 0+ 0 0 0+ 172 Stateful-IPv6-Address-Pool
624
625 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Diameter Considerations</span>
626
627 Given that the Attributes defined in this document are allocated from
628 the standard RADIUS type space (see <a href="#section-6">Section 6</a>), no special handling
629 is required by Diameter entities.
630
631 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
632
633 This document specifies additional IPv6 RADIUS Attributes useful in
634 residential broadband network deployments. In such networks, the
635 RADIUS protocol may run either over IPv4 or over IPv6, and known
636 security vulnerabilities of the RADIUS protocol, e.g., [<a href="#ref-SECI" title="&quot;An Analysis of the RADIUS Authentication Protocol&quot;">SECI</a>], apply
637 to the Attributes defined in this document. A trust relationship
638 between a NAS and RADIUS server is expected to be in place, with
639 communication optionally secured by IPsec or Transport Layer Security
640 (TLS) [<a href="./rfc6614" title="&quot;Transport Layer Security (TLS) Encryption for RADIUS&quot;">RFC6614</a>].
641
642 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
643
644 IANA has assigned five new RADIUS Attribute types in the "Radius
645 Attribute Types" registry (currently located at
646 <a href="http://www.iana.org/assignments/radius-types">http://www.iana.org/assignments/radius-types</a>) for the following
647 Attributes:
648
649 o Framed-IPv6-Address
650
651 o DNS-Server-IPv6-Address
652
653 o Route-IPv6-Information
654
655 o Delegated-IPv6-Prefix-Pool
656
657 o Stateful-IPv6-Address-Pool
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Dec, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
671
672
673 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
674
675 The authors would like to thank Bernard Aboba, Benoit Claise, Peter
676 Deacon, Alan DeKok, Ralph Droms, Brian Haberman, Alfred Hines,
677 Stephen Farrell, Jouni Korhonen, Roberta Maglione, Pete Resnick, Mark
678 Smith, and Leaf Yeh for their help and comments in reviewing this
679 document.
680
681 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
682
683 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
684
685 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
686 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
687
688 [<a id="ref-RFC4862">RFC4862</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
689 Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, September 2007.
690
691 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
692
693 [<a id="ref-RFC3162">RFC3162</a>] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", <a href="./rfc3162">RFC</a>
694 <a href="./rfc3162">3162</a>, August 2001.
695
696 [<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
697 and M. Carney, "Dynamic Host Configuration Protocol for
698 IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
699
700 [<a id="ref-RFC3633">RFC3633</a>] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
701 Host Configuration Protocol (DHCP) version 6", <a href="./rfc3633">RFC 3633</a>,
702 December 2003.
703
704 [<a id="ref-RFC3646">RFC3646</a>] Droms, R., "DNS Configuration options for Dynamic Host
705 Configuration Protocol for IPv6 (DHCPv6)", <a href="./rfc3646">RFC 3646</a>,
706 December 2003.
707
708 [<a id="ref-RFC4191">RFC4191</a>] Draves, R. and D. Thaler, "Default Router Preferences and
709 More-Specific Routes", <a href="./rfc4191">RFC 4191</a>, November 2005.
710
711 [<a id="ref-RFC4818">RFC4818</a>] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix
712 Attribute", <a href="./rfc4818">RFC 4818</a>, April 2007.
713
714 [<a id="ref-RFC6106">RFC6106</a>] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli,
715 "IPv6 Router Advertisement Options for DNS Configuration",
716 <a href="./rfc6106">RFC 6106</a>, November 2010.
717
718 [<a id="ref-RFC6158">RFC6158</a>] DeKok, A. and G. Weber, "RADIUS Design Guidelines", <a href="https://www.rfc-editor.org/bcp/bcp158">BCP</a>
719 <a href="https://www.rfc-editor.org/bcp/bcp158">158</a>, <a href="./rfc6158">RFC 6158</a>, March 2011.
720
721
722
723
724 <span class="grey">Dec, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
727
728
729 [<a id="ref-RFC6614">RFC6614</a>] Winter, S., McCauley, M., Venaas, S., and K. Wierenga,
730 "Transport Layer Security (TLS) Encryption for RADIUS",
731 <a href="./rfc6614">RFC 6614</a>, May 2012.
732
733 [<a id="ref-SECI">SECI</a>] Hill, J., "An Analysis of the RADIUS Authentication
734 Protocol", November 2001, &lt;<a href="http://regul.uni-mb.si/~meolic/ptk-seminarske/radius.pdf">http://regul.uni-mb.si/~meolic/</a>
735 <a href="http://regul.uni-mb.si/~meolic/ptk-seminarske/radius.pdf">ptk-seminarske/radius.pdf</a>&gt;.
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780 <span class="grey">Dec, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6911">RFC 6911</a> RADIUS IPv6 Access April 2013</span>
783
784
785 Authors' Addresses
786
787 Wojciech Dec (editor)
788 Cisco Systems, Inc.
789 Haarlerbergweg 13-19
790 Amsterdam, Noord-Holland 1101 CH
791 Netherlands
792
793 EMail: [email protected]
794
795
796 Behcet Sarikaya
797 Huawei USA
798 1700 Alma Drive, Suite 500
799 Plano, TX
800 US
801
802 Phone: +1 972-509-5599
803 EMail: [email protected]
804
805
806 Glen Zorn (editor)
807 Network Zen
808 227/358 Thanon Sanphawut
809 Bang Na, Bangkok 10260
810 Thailand
811
812 Phone: +66 (0) 8-1000-4155
813 EMail: [email protected]
814
815
816 David Miles
817 Google
818
819 EMail: [email protected]
820
821
822 Benoit Lourdelet
823 Juniper Networks
824 France
825
826 EMail: [email protected]
827
828
829
830
831
832
833
834
835
836 Dec, et al. Standards Track [Page 15]
837 </pre>