1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
|
<pre>Internet Engineering Task Force (IETF) D. Guo
Request for Comments: 6930 S. Jiang, Ed.
Category: Standards Track Huawei Technologies Co., Ltd
ISSN: 2070-1721 R. Despres
RD-IPtech
R. Maglione
Cisco Systems
April 2013
<span class="h1">RADIUS Attribute for IPv6 Rapid Deployment</span>
<span class="h1">on IPv4 Infrastructures (6rd)</span>
Abstract
The IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) provides both
IPv4 and IPv6 connectivity services simultaneously during the
IPv4/IPv6 coexistence period. The Dynamic Host Configuration
Protocol (DHCP) 6rd option has been defined to configure the 6rd
Customer Edge (CE). However, in many networks, the configuration
information may be stored in the Authentication Authorization and
Accounting (AAA) servers, while user configuration is mainly acquired
from a Broadband Network Gateway (BNG) through the DHCP protocol.
This document defines a Remote Authentication Dial-In User Service
(RADIUS) attribute that carries 6rd configuration information from
the AAA server to BNGs.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6930">http://www.rfc-editor.org/info/rfc6930</a>.
<span class="grey">Guo, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. IPv6 6rd Configuration with RADIUS ..............................<a href="#page-4">4</a>
<a href="#section-4">4</a>. Attributes ......................................................<a href="#page-6">6</a>
<a href="#section-4.1">4.1</a>. IPv6-6rd-Configuration Attribute ...........................<a href="#page-6">6</a>
<a href="#section-4.2">4.2</a>. Table of Attributes ........................................<a href="#page-9">9</a>
<a href="#section-5">5</a>. Diameter Considerations .........................................<a href="#page-9">9</a>
<a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-9">9</a>
<a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-10">10</a>
<a href="#section-8">8</a>. Acknowledgments ................................................<a href="#page-10">10</a>
<a href="#section-9">9</a>. References .....................................................<a href="#page-10">10</a>
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-10">10</a>
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-11">11</a>
<span class="grey">Guo, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Recently, providers have started to deploy IPv6 and to consider
transition to IPv6. The IPv6 Rapid Deployment (6rd) [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>]
provides both IPv4 and IPv6 connectivity services simultaneously
during the IPv4/IPv6 coexistence period. 6rd is used to provide IPv6
connectivity service through legacy IPv4-only infrastructure. 6rd
uses the Dynamic Host Configuration Protocol (DHCP) [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>], and
the 6rd Customer Edge (CE) uses the DHCP 6rd option [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>] to
discover a 6rd Border Relay and to configure an IPv6 prefix and
address.
In many networks, user-configuration information is managed by
Authentication, Authorization, and Accounting (AAA) servers. The
Remote Authentication Dial-In User Service (RADIUS) protocol
[<a href="./rfc2865" title=""Remote Authentication Dial In User Service (RADIUS)"">RFC2865</a>] is usually used by AAA servers to communicate with network
elements. In a fixed-line broadband network, the Broadband Network
Gateways (BNGs) act as the access gateway for users. The BNGs are
assumed to embed a DHCP server function that allows them to handle
locally any DHCP requests issued by hosts.
Since the 6rd configuration information is stored in AAA servers, and
user configuration is mainly through DHCP between BNGs and hosts/CEs,
new RADIUS attributes are needed to propagate the information from
AAA servers to BNGs.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
The terms 6rd Customer Edge (6rd CE) and 6rd Border Relay (BR) are
defined in [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>]. "MAC" stands for Media Access Control.
<span class="grey">Guo, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IPv6 6rd Configuration with RADIUS</span>
Figure 1 illustrates how DHCP and the RADIUS protocol cooperate to
provide 6rd CE with 6rd configuration information.
6rd CE BNG AAA Server
| | |
|-------DHCPDISCOVER------>| |
|(Parameter Request w/ 6rd option) |
| |--Access-Request(6rd Attr)-->|
| | |
| |<--Access-Accept(6rd Attr)---|
|<-------DHCPOFFER---------| |
| (6rd option) | |
| | |
DHCP RADIUS
Figure 1: The Cooperation between DHCP and RADIUS
When Combined with RADIUS Authentication
The BNG acts as a client of RADIUS and as a DHCP server. First, the
6rd CE MAY initiate a DHCPDISCOVER message that includes a Parameter
Request option (55) [<a href="./rfc2132" title=""DHCP Options and BOOTP Vendor Extensions"">RFC2132</a>] with the 6rd option [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>]. When
the BNG receives the DHCPDISCOVER, it SHOULD initiate a RADIUS
Access- Request message to the RADIUS server. In that message,
- the User-Name attribute (1) SHOULD be filled by the 6rd CE MAC
address, and
- the User-Password attribute (2) SHOULD be filled by the shared 6rd
password that has been preconfigured on the DHCP server.
The BNG requests authentication, as defined in [<a href="./rfc2865" title=""Remote Authentication Dial In User Service (RADIUS)"">RFC2865</a>], with the
IPv6-6rd-Configuration attribute (<a href="#section-4.1">Section 4.1</a>) in the desired
attribute list. If the authentication request is approved by the AAA
server, an Access-Accept message MUST be acknowledged with the
IPv6-6rd-Configuration attribute. Then, the BNG SHOULD respond to
the 6rd CE with a DHCPOFFER message, which contains a DHCP 6rd
option. The recommended format of the MAC address is as defined in
Calling-Station-Id (<a href="./rfc3580#section-3.20">[RFC3580], Section 3.20</a>) without the SSID
(Service Set Identifier) portion.
Figure 2 describes another scenario -- later re-authorization -- in
which the authorization operation is not coupled with authentication.
Authorization relevant to 6rd is done independently after the
authentication process.
<span class="grey">Guo, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
6rd CE BNG AAA Server
| | |
|--------DHCPREQUEST------>| |
|(Parameter Request w/ 6rd option) |
| |--Access-Request(6rd Attr)-->|
| | |
| |<--Access-Accept(6rd Attr)---|
| | |
|<---------DHCPACK---------| |
| (6rd option) | |
| | |
DHCP RADIUS
Figure 2: The Cooperation between DHCP and RADIUS
When Decoupled from RADIUS Authentication
In this scenario, the Access-Request packet SHOULD contain a Service-
Type attribute (6) with the value Authorize Only (17); thus,
according to [<a href="./rfc5080" title=""Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested Fixes"">RFC5080</a>], the Access-Request packet MUST contain a
State attribute that it obtains from the previous authentication
process.
In both above-mentioned scenarios, Message-Authenticator (type 80)
[<a href="./rfc2865" title=""Remote Authentication Dial In User Service (RADIUS)"">RFC2865</a>] SHOULD be used to protect both Access-Request and Access-
Accept messages.
After receiving the IPv6-6rd-Configuration attribute in the initial
Access-Accept, the BNG SHOULD store the received 6rd configuration
parameters locally. When the 6rd CE sends a DHCP Request message to
request an extension of the lifetime for the assigned address, the
BNG does not have to initiate a new Access-Request towards the AAA
server to request the 6rd configuration parameters. The BNG could
retrieve the previously stored 6rd configuration parameters and use
them in its reply.
If the BNG does not receive the IPv6-6rd-Configuration attribute in
the Access-Accept, it MAY fall back to a preconfigured default 6rd
configuration, if any. If the BNG does not have any preconfigured
default 6rd configuration or if the BNG receives an Access-Reject,
the tunnel cannot be established.
As specified in <a href="./rfc2131#section-4.4.5">[RFC2131], Section 4.4.5</a> ("Reacquisition and
expiration"), if the DHCP server to which the DHCP Request message
was sent at time T1 has not responded by time T2 (typically
0.375*duration_of_lease after T1), the 6rd CE (the DHCP client)
SHOULD enter the REBINDING state and attempt to contact any server.
<span class="grey">Guo, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
In this situation, the secondary BNG receiving the new DHCP message
MUST initiate a new Access-Request towards the AAA server. The
secondary BNG MAY include the IPv6-6rd-Configuration attribute in its
Access-Request.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Attributes</span>
This section defines the IPv6-6rd-Configuration attribute that is
used in both above-mentioned scenarios. The attribute design follows
[<a href="./rfc6158" title=""RADIUS Design Guidelines"">RFC6158</a>] and refers to [<a href="./rfc6929" title=""Remote Authentication Dial-In User Service (RADIUS) Protocol Extensions"">RFC6929</a>].
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. IPv6-6rd-Configuration Attribute</span>
The specification requires that multiple IPv4 addresses are
associated with one IPv6 prefix. Given that RADIUS currently has no
recommended way of grouping multiple attributes, the design below
appears to be a reasonable compromise. The IPv6-6rd-Configuration
attribute is structured as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | SubType1 | SubLen1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4MaskLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType2 | SubLen2 | Reserved | 6rdPrefixLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ 6rdPrefix +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType3 | SubLen3 | 6rdBRIPv4Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 6rdBRIPv4Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
173
<span class="grey">Guo, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
Length
28 + n*6 (the length of the entire attribute in octets, where n
is the number of BR IPv4 addresses and minimum n is 1)
SubType1
1 (SubType number, for the IPv4 Mask Length suboption)
SubLen1
6 (the length of the IPv4 Mask Length suboption)
IPv4MaskLen
The number of high-order bits that are identical across all CE
IPv4 addresses within a given 6rd domain. This may be any
value between 0 and 32. Any value greater than 32 is invalid.
Since <a href="./rfc6158#appendix-A.2.1">[RFC6158], Appendix A.2.1</a>, has forbidden 8-bit fields, a
32-bit field is used here.
SubType2
2 (SubType number for the 6rd prefix suboption)
SubLen2
20 (the length of the 6rd prefix suboption)
Reserved
Set to all 0 for now. Reserved for future use. To be
compatible with other IPv6 prefix attributes in the RADIUS
protocol, the bits MUST be set to zero by the sender and MUST
be ignored by the receiver.
6rdPrefixLen
The IPv6 Prefix length of the Service Provider's 6rd IPv6
prefix in number of bits. The 6rdPrefixLen MUST be less than
or equal to 128.
6rdPrefix
The Service Provider's 6rd IPv6 prefix represented as a
16-octet IPv6 address. The bits after the 6rdPrefixlen number
of bits in the prefix SHOULD be set to zero.
<span class="grey">Guo, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
SubType3
3 (SubType number, for the 6rd Border Relay IPv4 address
suboption)
SubLen3
6 (the length of the 6rd Border Relay IPv4 address suboption)
6rdBRIPv4Address
One or more IPv4 addresses of the 6rd Border Relay(s) for a
given 6rd domain. The maximum RADIUS attribute length of 255
octets results in a limit of 37 IPv4 addresses.
Since the subtypes have values, they can appear in any order. If
multiple 6rdBRIPv4Address (subtype 3) appear, they are RECOMMENDED to
be placed together.
The IPv6-6rd-Configuration attribute is normally used in Access-
Accept messages. It MAY be used in Access-Request packets as a hint
to the RADIUS server; for example, if the BNG is preconfigured with a
default 6rd configuration, these parameters MAY be inserted in the
attribute. The RADIUS server MAY ignore the hint sent by the BNG,
and it MAY assign different 6rd parameters.
If the BNG includes the IPv6-6rd-Configuration attribute, but the AAA
server does not recognize it, this attribute MUST be ignored by the
AAA server.
If the BNG does not receive the IPv6-6rd-Configuration attribute in
the Access-Accept, it MAY fallback to a preconfigured default 6rd
configuration, if any. If the BNG does not have any preconfigured
default 6rd configuration, the 6rd tunnel cannot be established.
If the BNG is pre-provisioned with a default 6rd configuration and
the 6rd configuration received in Access-Accept is different from the
configured default, then the 6rd configuration received in the
Access-Accept message MUST be used for the session.
If the BNG cannot support the received 6rd configuration for any
reason, the tunnel SHOULD NOT be established.
<span class="grey">Guo, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Table of Attributes</span>
The following table adds to the one in <a href="./rfc2865#section-5.44">[RFC2865], Section 5.44</a>,
providing a guide to the quantity of IPv6-6rd-Configuration
attributes that may be found in each kind of packet.
Request Accept Reject Challenge Accounting # Attribute
Request
0-1 0-1 0 0 0-1 173 IPv6-6rd-
Configuration
0-1 0-1 0 0 0-1 1 User-Name
0-1 0 0 0 0-1 2 User-Password
0-1 0-1 0 0 0-1 6 Service-Type
0-1 0-1 0-1 0-1 0-1 80 Message-Authenticator
The following key defines the meanings of the above table entries.
0 This attribute MUST NOT be present in packet.
0+ Zero or more instances of this attribute MAY be present in
packet.
0-1 Zero or one instance of this attribute MAY be present in
packet.
1 Exactly one instance of this attribute MUST be present in
packet.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Diameter Considerations</span>
This attribute is usable within either RADIUS or Diameter [<a href="./rfc6733" title=""Diameter Base Protocol"">RFC6733</a>].
Since the attribute defined in this document has been allocated from
the standard RADIUS type space, no special handling is required by
Diameter entities.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
In 6rd scenarios, both CE and BNG are within a provider network,
which can be considered as a closed network and a lower-threat
environment. A similar consideration can be applied to the RADIUS
message exchange between the BNG and the AAA server.
In 6rd scenarios, the RADIUS protocol is run over IPv4. Known
security vulnerabilities of the RADIUS protocol are discussed in
[<a href="./rfc2607" title=""Proxy Chaining and Policy Implementation in Roaming"">RFC2607</a>], [<a href="./rfc2865" title=""Remote Authentication Dial In User Service (RADIUS)"">RFC2865</a>], and [<a href="./rfc2869" title=""RADIUS Extensions"">RFC2869</a>]. Use of IPsec [<a href="./rfc4301" title=""Security Architecture for the Internet Protocol"">RFC4301</a>] for
providing security when RADIUS is carried in IPv6 is discussed in
[<a href="./rfc3162" title=""RADIUS and IPv6"">RFC3162</a>].
<span class="grey">Guo, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
To get unauthorized 6rd configuration information, a malicious user
may use MAC address spoofing and/or a dictionary attack on the shared
6rd password that has been preconfigured on the DHCP server. The
relevant security issues have been considered in <a href="./rfc5969#section-12">Section 12 of
[RFC5969]</a>.
Security issues that may arise specifically between the 6rd CE and
BNG are discussed in [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>]. Furthermore, generic DHCP security
mechanisms can be applied to DHCP intercommunication between 6rd CE
and BNG.
Security considerations for the Diameter protocol are discussed in
[<a href="./rfc6733" title=""Diameter Base Protocol"">RFC6733</a>].
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
Per this document, IANA has assigned one new RADIUS Attribute Type in
the "Radius Types" registry (currently located at
<a href="http://www.iana.org/assignments/radius-types">http://www.iana.org/assignments/radius-types</a>) for the following
attribute:
IPv6-6rd-Configuration (173)
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgments</span>
The authors would like to thank Alan DeKok, Yong Cui, Leaf Yeh, Sean
Turner, Joseph Salowey, Glen Zorn, Dave Nelson, Bernard Aboba, Benoit
Claise, Barry Lieba, Stephen Farrell, Adrian Farrel, Ralph Droms, and
other members of the SOFTWIRE WG, RADEXT WG, AAA Doctors, and
Security Directorate for valuable comments.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC</a>
<a href="./rfc2131">2131</a>, March 1997.
[<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
[<a id="ref-RFC2865">RFC2865</a>] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", <a href="./rfc2865">RFC</a>
<a href="./rfc2865">2865</a>, June 2000.
<span class="grey">Guo, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
[<a id="ref-RFC3162">RFC3162</a>] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", <a href="./rfc3162">RFC</a>
<a href="./rfc3162">3162</a>, August 2001.
[<a id="ref-RFC4301">RFC4301</a>] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", <a href="./rfc4301">RFC 4301</a>, December 2005.
[<a id="ref-RFC5080">RFC5080</a>] Nelson, D. and A. DeKok, "Common Remote Authentication
Dial In User Service (RADIUS) Implementation Issues and
Suggested Fixes", <a href="./rfc5080">RFC 5080</a>, December 2007.
[<a id="ref-RFC5969">RFC5969</a>] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4
Infrastructures (6rd) -- Protocol Specification", <a href="./rfc5969">RFC</a>
<a href="./rfc5969">5969</a>, August 2010.
[<a id="ref-RFC6158">RFC6158</a>] DeKok, A., Ed., and G. Weber, "RADIUS Design Guidelines",
<a href="https://www.rfc-editor.org/bcp/bcp158">BCP 158</a>, <a href="./rfc6158">RFC 6158</a>, March 2011.
[<a id="ref-RFC6733">RFC6733</a>] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", <a href="./rfc6733">RFC 6733</a>, October 2012.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-RFC2607">RFC2607</a>] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
Implementation in Roaming", <a href="./rfc2607">RFC 2607</a>, June 1999.
[<a id="ref-RFC2869">RFC2869</a>] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", <a href="./rfc2869">RFC 2869</a>, June 2000.
[<a id="ref-RFC3580">RFC3580</a>] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese,
"IEEE 802.1X Remote Authentication Dial In User Service
(RADIUS) Usage Guidelines", <a href="./rfc3580">RFC 3580</a>, September 2003.
[<a id="ref-RFC6929">RFC6929</a>] DeKok, A. and A. Lior, "Remote Authentication Dial-In User
Service (RADIUS) Protocol Extensions", <a href="./rfc6929">RFC 6929</a>, April
2013.
<span class="grey">Guo, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6930">RFC 6930</a> RADIUS for 6rd April 2013</span>
Authors' Addresses
Dayong Guo
Huawei Technologies Co., Ltd
Q14 Huawei Campus, 156 BeiQi Road,
ZhongGuan Cun, Hai-Dian District, Beijing 100095
P.R. China
EMail: guoseu@huawei.com
Sheng Jiang (Editor)
Huawei Technologies Co., Ltd
Q14 Huawei Campus, 156 BeiQi Road,
ZhongGuan Cun, Hai-Dian District, Beijing 100095
P.R. China
EMail: jiangsheng@huawei.com
Remi Despres
RD-IPtech
3 rue du President Wilson
Levallois
France
EMail: despres.remi@laposte.net
Roberta Maglione
Cisco Systems
181 Bay Street
Toronto, ON
M5J 2T3
Canada
EMail: robmgl@cisco.com
Guo, et al. Standards Track [Page 12]
</pre>
|
