draft-ietf-softwire-map-radius-19.txt   draft-ietf-softwire-map-radius-20.txt 
Softwire S. Jiang, Ed. Softwire S. Jiang, Ed.
Internet-Draft Huawei Technologies Co., Ltd Internet-Draft Huawei Technologies Co., Ltd
Intended status: Standards Track Y. Fu, Ed. Intended status: Standards Track Y. Fu, Ed.
Expires: August 15, 2019 CNNIC Expires: August 17, 2019 CNNIC
B. Liu B. Liu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
P. Deacon P. Deacon
IEA Software, Inc. IEA Software, Inc.
C. Xie C. Xie
China Telecom China Telecom
T. Li T. Li
Tsinghua University Tsinghua University
M. Boucadair, Ed. M. Boucadair, Ed.
Orange Orange
February 11, 2019 February 13, 2019
RADIUS Attributes for Address plus Port (A+P) based Softwire Mechanisms RADIUS Attributes for Address plus Port (A+P) based Softwire Mechanisms
draft-ietf-softwire-map-radius-19 draft-ietf-softwire-map-radius-20
Abstract Abstract
IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity
services over IPv6 native networks during the IPv4/IPv6 co-existence services over IPv6 native networks during the IPv4/IPv6 co-existence
period. DHCPv6 options have been defined for configuring clients for period. DHCPv6 options have been defined for configuring clients for
Lightweight 4over6, Mapping of Address and Port with Encapsulation, Lightweight 4over6, Mapping of Address and Port with Encapsulation,
and Mapping of Address and Port using Translation unicast softwire and Mapping of Address and Port using Translation unicast softwire
mechanisms, and also multicast softwires. However, in many networks, mechanisms, and also multicast softwires. However, in many networks,
configuration information is stored in an Authentication, configuration information is stored in an Authentication,
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 15, 2019. This Internet-Draft will expire on August 17, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 41 skipping to change at page 2, line 41
3. New RADIUS Attributes . . . . . . . . . . . . . . . . . . . . 6 3. New RADIUS Attributes . . . . . . . . . . . . . . . . . . . . 6
3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 7 3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 7
3.1.1. Softwire46 Attributes . . . . . . . . . . . . . . . . 8 3.1.1. Softwire46 Attributes . . . . . . . . . . . . . . . . 8
3.1.1.1. Softwire46-MAP-E Attribute . . . . . . . . . . . 10 3.1.1.1. Softwire46-MAP-E Attribute . . . . . . . . . . . 10
3.1.1.2. Softwire46-MAP-T Attribute . . . . . . . . . . . 10 3.1.1.2. Softwire46-MAP-T Attribute . . . . . . . . . . . 10
3.1.1.3. Softwire46-Lightweight-4over6 Attribute . . . . . 11 3.1.1.3. Softwire46-Lightweight-4over6 Attribute . . . . . 11
3.1.2. Softwire46 Sub-Attributes . . . . . . . . . . . . . . 11 3.1.2. Softwire46 Sub-Attributes . . . . . . . . . . . . . . 11
3.1.3. Specification of the Softwire46 Sub-Attributes . . . 12 3.1.3. Specification of the Softwire46 Sub-Attributes . . . 12
3.1.3.1. Softwire46-Rule Attribute . . . . . . . . . . . . 12 3.1.3.1. Softwire46-Rule Attribute . . . . . . . . . . . . 12
3.1.3.2. Softwire46-BR Attribute . . . . . . . . . . . . . 13 3.1.3.2. Softwire46-BR Attribute . . . . . . . . . . . . . 13
3.1.3.3. Softwire46-DMR Attribute . . . . . . . . . . . . 14 3.1.3.3. Softwire46-DMR Attribute . . . . . . . . . . . . 13
3.1.3.4. Softwire46-V4V6Bind Attribute . . . . . . . . . . 14 3.1.3.4. Softwire46-V4V6Bind Attribute . . . . . . . . . . 14
3.1.3.5. Softwire46-PORTPARAMS Attribute . . . . . . . . . 15 3.1.3.5. Softwire46-PORTPARAMS Attribute . . . . . . . . . 14
3.1.4. Sub-Attributes for Sofwtire46-Rule . . . . . . . . . 16 3.1.4. Sub-Attributes for Sofwtire46-Rule . . . . . . . . . 15
3.1.4.1. Rule-IPv6-Prefix Attribute . . . . . . . . . . . 16 3.1.4.1. Rule-IPv6-Prefix Attribute . . . . . . . . . . . 15
3.1.4.2. Rule-IPv4-Prefix Attribute . . . . . . . . . . . 17 3.1.4.2. Rule-IPv4-Prefix Attribute . . . . . . . . . . . 16
3.1.4.3. EA-Length Attribute . . . . . . . . . . . . . . . 17 3.1.4.3. EA-Length Attribute . . . . . . . . . . . . . . . 16
3.1.5. Attributes for Softwire46-v4v6Bind . . . . . . . . . 18 3.1.5. Attributes for Softwire46-v4v6Bind . . . . . . . . . 17
3.1.5.1. IPv4-address Attribute . . . . . . . . . . . . . 18 3.1.5.1. IPv4-address Attribute . . . . . . . . . . . . . 17
3.1.5.2. Bind-IPv6-Prefix Attribute . . . . . . . . . . . 18 3.1.5.2. Bind-IPv6-Prefix Attribute . . . . . . . . . . . 17
3.1.6. Attributes for S46-PORTPARAMS . . . . . . . . . . . . 19 3.1.6. Attributes for S46-PORTPARAMS . . . . . . . . . . . . 18
3.1.6.1. PSID-offset Attribute . . . . . . . . . . . . . . 19 3.1.6.1. PSID-offset Attribute . . . . . . . . . . . . . . 18
3.1.6.2. PSID-len Attribute . . . . . . . . . . . . . . . 20 3.1.6.2. PSID-len Attribute . . . . . . . . . . . . . . . 19
3.1.6.3. PSID Attribute . . . . . . . . . . . . . . . . . 20 3.1.6.3. PSID Attribute . . . . . . . . . . . . . . . . . 19
3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 21 3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 20
3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22 3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 21
3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 24 3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 23
3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 25 3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 24
3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 25 3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 24
4. A Sample Configuration Process with RADIUS . . . . . . . . . 25 4. A Sample Configuration Process with RADIUS . . . . . . . . . 24
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 28 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 27
6. Security Considerations . . . . . . . . . . . . . . . . . . . 29 6. Security Considerations . . . . . . . . . . . . . . . . . . . 28
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 29 7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 28
7.2. RADIUS Softwire46 Configuration and Multicast Attributes 30 7.2. RADIUS Softwire46 Configuration and Multicast Attributes 29
7.3. Softwire46 Mechanisms and Their Identifying Option Codes 30 7.3. Softwire46 Mechanisms and Their Identifying Option Codes 29
8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 31 8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 30
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.1. Normative References . . . . . . . . . . . . . . . . . . 33 10.1. Normative References . . . . . . . . . . . . . . . . . . 32
10.2. Informative References . . . . . . . . . . . . . . . . . 34 10.2. Informative References . . . . . . . . . . . . . . . . . 33
Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 35 Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 35
A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 35
A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings . . . 36 A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings . . . 35
A.3. OPTION_S46_DMR (91) to Softwire46-DMR . . . . . . . . . . 36 A.3. OPTION_S46_DMR (91) to Softwire46-DMR . . . . . . . . . . 35
A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind . . . . . 36 A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind . . . . . 35
A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36
A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 37 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36
A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast
Attribute Field Mappings . . . . . . . . . . . . . . . . 37 Attribute Field Mappings . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
Providers have started deploying and transitioning to IPv6. Several Providers have started deploying and transitioning to IPv6. Several
IPv4 service continuity mechanisms based on the Address plus Port IPv4 service continuity mechanisms based on the Address plus Port
(A+P) [RFC6346] have been proposed for providing unicast IPv4 over (A+P) [RFC6346] have been proposed for providing unicast IPv4 over
IPv6-only infrastructure, such as Mapping of Address and Port with IPv6-only infrastructure, such as Mapping of Address and Port with
Encapsulation (MAP-E) [RFC7597], Mapping of Address and Port using Encapsulation (MAP-E) [RFC7597], Mapping of Address and Port using
Translation (MAP-T) [RFC7599], and Lightweight 4over6 [RFC7596]. Translation (MAP-T) [RFC7599], and Lightweight 4over6 [RFC7596].
Also, [RFC8114] specifies a generic solution for the delivery of IPv4 Also, [RFC8114] specifies a generic solution for the delivery of IPv4
skipping to change at page 8, line 22 skipping to change at page 8, line 22
Extended-Type Extended-Type
TBD1 TBD1
Value Value
Contains one or more of the following attributes. Each attribute Contains one or more of the following attributes. Each attribute
type may appear at most once: type may appear at most once:
Softwire46-MAP-E Softwire46-MAP-E
For configuring MAP-E clients. For the construction of For configuring MAP-E clients. For the construction of
this attribute, Refer to Section 3.1.1.1. this attribute, efer to Section 3.1.1.1.
Softwire46-MAP-T Softwire46-MAP-T
For configuring MAP-T clients. For the construction of For configuring MAP-T clients. For the construction of
this attribute, Refer to Section 3.1.1.2. this attribute, refer to Section 3.1.1.2.
Softwire46-Lightweight-4over6 Softwire46-Lightweight-4over6
For configuring Lightweight 4over6 clients. For the For configuring Lightweight 4over6 clients. For the
construction of this attribute, Refer to Section 3.1.1.3. construction of this attribute, refer to Section 3.1.1.3.
The Softwire46-Configuration Attribute is associated with the The Softwire46-Configuration Attribute is associated with the
following identifier: 241.Extended-Type(TBD1). following identifier: 241.Extended-Type(TBD1).
3.1.1. Softwire46 Attributes 3.1.1. Softwire46 Attributes
The Softwire46 attributes can only be encapsulated in the The Softwire46 attributes can only be encapsulated in the
Softwire46-Configuration Attribute. Depending on the deployment Softwire46-Configuration Attribute. Depending on the deployment
scenario, a client might request for more than one transition scenario, a client might request for more than one transition
mechanism at a time. There MUST be at least one Softwire46 attribute mechanism at a time. There MUST be at least one Softwire46 attribute
skipping to change at page 10, line 21 skipping to change at page 10, line 21
TLV-Type TLV-Type
1 1
TLV-Length TLV-Length
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.
TLV-Value TLV-Value
Contains a set of sub-attributes, with the following requirements: Contains a set of sub-attributes, with the following requirements:
It MUST contain the Softwire46-Rule, defined in Section 3.1.3.1. It MUST contain Softwire46-Rule, defined in Section 3.1.3.1.
It MUST contain the Softwire46-BR, defined in Section 3.1.3.2. It MUST contain Softwire46-BR, defined in Section 3.1.3.2.
It MAY contain the Softwire46-PORTPARAMS, defined in It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5.
Section 3.1.3.5.
3.1.1.2. Softwire46-MAP-T Attribute 3.1.1.2. Softwire46-MAP-T Attribute
Softwire46-MAP-T attribute is designed for carrying the configuration Softwire46-MAP-T attribute is designed for carrying the configuration
information for MAP-T. The structure of Softwire46-MAP-T is shown information for MAP-T. The structure of Softwire46-MAP-T is shown
below: below:
TLV-Type TLV-Type
2 2
TLV-Length TLV-Length
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.
TLV-Value TLV-Value
Contains a set of sub-attributes, with the following requirements: Contains a set of sub-attributes, with the following requirements:
It MUST contain the Softwire46-Rule, defined in It MUST contain Softwire46-Rule, defined in Section 3.1.3.1.
Section 3.1.3.1.
It MUST contain the Softwire46-DMR, defined in It MUST contain Softwire46-DMR, defined in Section 3.1.3.3.
Section 3.1.3.3.
It MAY contain the Softwire46-PORTPARAMS, defined in It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5.
Section 3.1.3.5.
3.1.1.3. Softwire46-Lightweight-4over6 Attribute 3.1.1.3. Softwire46-Lightweight-4over6 Attribute
Softwire46-Lightweight-4over6 attribute is designed for carrying the Softwire46-Lightweight-4over6 attribute is designed for carrying the
configuration information for Lightweight 4over6. The structure of configuration information for Lightweight 4over6. The structure of
Softwire46-Lightweight-4over6 is shown below: Softwire46-Lightweight-4over6 is shown below:
TLV-Type TLV-Type
3 3
TLV-Length TLV-Length
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.
TLV-Value TLV-Value
Contains a set of sub-attributes as follows: Contains a set of sub-attributes as follows:
It MUST contain the Softwire46-BR, defined in It MUST contain Softwire46-BR, defined in Section 3.1.3.2.
Section 3.1.3.2.
It MUST contain the Softwire46-V4V6Bind, defined in It MUST contain Softwire46-V4V6Bind, defined in Section 3.1.3.4.
Section 3.1.3.4.
It MAY contain the Softwire46-PORTPARAMS, defined in It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5.
Section 3.1.3.5.
3.1.2. Softwire46 Sub-Attributes 3.1.2. Softwire46 Sub-Attributes
Table 2 shows which encapsulated sub-attributes are mandatory, Table 2 shows which encapsulated sub-attributes are mandatory,
optional, or not permitted for each defined Softwire46 attribute. optional, or not permitted for each defined Softwire46 attribute.
+-----------------------+-------+-------+--------------------+ +-----------------------+-------+-------+--------------------+
| Sub-Attributes | MAP-E | MAP-T | Lightweight 4over6 | | Sub-Attributes | MAP-E | MAP-T | Lightweight 4over6 |
+-----------------------+-------+-------+--------------------+ +-----------------------+-------+-------+--------------------+
| Softwire46-BR | 1 | 0 | 1 | | Softwire46-BR | 1 | 0 | 1 |
skipping to change at page 12, line 16 skipping to change at page 12, line 9
0+ Optional, zero or more instances of the attribute 0+ Optional, zero or more instances of the attribute
may be present. may be present.
0-1 Optional, zero or one instance of the attribute 0-1 Optional, zero or one instance of the attribute
may be present. may be present.
1 Mandatory 1 Mandatory
3.1.3. Specification of the Softwire46 Sub-Attributes 3.1.3. Specification of the Softwire46 Sub-Attributes
3.1.3.1. Softwire46-Rule Attribute 3.1.3.1. Softwire46-Rule Attribute
The Softwire46-Rule can only be encapsulated in the Softwire46-MAP-E Softwire46-Rule can only be encapsulated in Softwire46-MAP-E
(Section 3.1.1.1) or the Softwire46-MAP-T (Section 3.1.1.2). (Section 3.1.1.1) or Softwire46-MAP-T (Section 3.1.1.2). Depending
Depending on the deployment scenario, one Basic Mapping Rule (BMR) on the deployment scenario, one Basic Mapping Rule (BMR) and zero or
and zero or more Forwarding Mapping Rules (FMRs) MUST be included in more Forwarding Mapping Rules (FMRs) MUST be included in one
one Softwire46-MAP-E or Softwire46-MAP-T. Softwire46-MAP-E or Softwire46-MAP-T.
Each type of Softwire46-Rule also contains a number of sub- Each type of Softwire46-Rule also contains a number of sub-
attributes, including Rule-IPv6-Prefix, Rule-IPv4-Prefix, and EA- attributes, including Rule-IPv6-Prefix, Rule-IPv4-Prefix, and EA-
Length. The structure of the sub-attributes for the Softwire46-Rule Length. The structure of the sub-attributes for Softwire46-Rule is
is defined in Section 3.1.4. defined in Section 3.1.4.
Defining multiple TLV-types achieves the same design goals as the Defining multiple TLV-types achieves the same design goals as the
"Softwire46 Rule Flags" defined in Section 4.1 of [RFC7598]. Using "Softwire46 Rule Flags" defined in Section 4.1 of [RFC7598]. Using
TLV-type set to 4 is equivalent to setting the F-flag in the TLV-type set to 4 is equivalent to setting the F-flag in the
OPTION_S46_RULE S46 Rule Flags field. OPTION_S46_RULE S46 Rule Flags field.
TLV-Type TLV-Type
4 Basic Mapping Rule only (not to be used for forwarding) 4 Basic Mapping Rule only (not to be used for forwarding)
5 Forwarding Permitted Mapping Rule (may be used for 5 Forwarding Permitted Mapping Rule (may be used for
forwarding. Can also be a Basic Mapping Rule) forwarding. Can also be a Basic Mapping Rule)
skipping to change at page 13, line 35 skipping to change at page 13, line 7
Rule-IPv4-Prefix Rule-IPv4-Prefix
This attribute contains the IPv4 prefix for use in the MAP rule. This attribute contains the IPv4 prefix for use in the MAP rule.
Refer to Section 3.1.4.2. Refer to Section 3.1.4.2.
EA-Length EA-Length
This attribute contains the Embedded-Address (EA) bit length. This attribute contains the Embedded-Address (EA) bit length.
Refer to Section 3.1.4.1. Refer to Section 3.1.4.1.
3.1.3.2. Softwire46-BR Attribute 3.1.3.2. Softwire46-BR Attribute
The Softwire46-BR can only be encapsulated in the Softwire46-MAP-E Softwire46-BR can only be encapsulated in Softwire46-MAP-E
(Section 3.1.1.1) or Softwire46-Lightweight-4over6 (Section 3.1.1.3). (Section 3.1.1.1) or Softwire46-Lightweight-4over6 (Section 3.1.1.3).
There MUST be at least one Softwire46-BR included in each There MUST be at least one Softwire46-BR included in each
Softwire46-MAP-E or Softwire46-Lightweight-4over6. Softwire46-MAP-E or Softwire46-Lightweight-4over6.
The structure of Softwire46-BR is shown below: The structure of Softwire46-BR is shown below:
TLV-Type TLV-Type
6 6
skipping to change at page 14, line 21 skipping to change at page 13, line 31
Data Type Data Type
The attribute Softwire46-BR is of type ip6addr (Section 3.9 of The attribute Softwire46-BR is of type ip6addr (Section 3.9 of
[RFC8044]). [RFC8044]).
TLV-Value TLV-Value
br-ipv6-address. A fixed-length field of 16 octets that br-ipv6-address. A fixed-length field of 16 octets that
specifies the IPv6 address for the Softwire46 Border Relay (BR). specifies the IPv6 address for the Softwire46 Border Relay (BR).
3.1.3.3. Softwire46-DMR Attribute 3.1.3.3. Softwire46-DMR Attribute
The Softwire46-DMR may only appear in the Softwire46-MAP-T Softwire46-DMR may only appear in Softwire46-MAP-T (Section 3.1.1.2).
(Section 3.1.1.2). There MUST be exactly one Softwire46-DMR included There MUST be exactly one Softwire46-DMR included in one Softwire46-
in one Softwire46-MAP-T. MAP-T.
The structure of Softwire46-DMR is shown below: The structure of Softwire46-DMR is shown below:
TLV-Type TLV-Type
7 7
TLV-Length TLV-Length
4 + length of dmr-ipv6-prefix specified in octets. 4 + length of dmr-ipv6-prefix specified in octets.
Data Type Data Type
skipping to change at page 14, line 45 skipping to change at page 14, line 7
[RFC8044]). [RFC8044]).
TLV-Value TLV-Value
dmr-ipv6-prefix. A variable-length field specifying the IPv6 dmr-ipv6-prefix. A variable-length field specifying the IPv6
prefix for the BR. This field is right-padded with zeros to prefix for the BR. This field is right-padded with zeros to
the nearest octet boundary when dmr-prefix6-len is not the nearest octet boundary when dmr-prefix6-len is not
divisible by 8. Prefixes with from 0 to 96 are allowed. divisible by 8. Prefixes with from 0 to 96 are allowed.
3.1.3.4. Softwire46-V4V6Bind Attribute 3.1.3.4. Softwire46-V4V6Bind Attribute
The Softwire46-V4V6Bind may only be encapsulated in the Softwire46- Softwire46-V4V6Bind may only be encapsulated in Softwire46-
Lightweight-4over6 (Section 3.1.1.3). There MUST be exactly one Lightweight-4over6 (Section 3.1.1.3). There MUST be exactly one
Softwire46-V4V6Bind included in each Softwire46-Lightweight-4over6. Softwire46-V4V6Bind included in each Softwire46-Lightweight-4over6.
The structure of Softwire46-V4V6Bind is shown below: The structure of Softwire46-V4V6Bind is shown below:
TLV-Type TLV-Type
8 8
TLV-Length TLV-Length
Indicates the length of this attribute, including Indicates the length of this attribute, including
skipping to change at page 15, line 31 skipping to change at page 14, line 39
the full or shared IPv4 address of the CE. Refer to the full or shared IPv4 address of the CE. Refer to
Section 3.1.5.1. Section 3.1.5.1.
Bind-IPv6-Prefix Bind-IPv6-Prefix
This attribute contains an IPv6 prefix used to indicate which This attribute contains an IPv6 prefix used to indicate which
configured prefix the Softwire46 CE should use for constructing configured prefix the Softwire46 CE should use for constructing
the softwire. Refer to Section 3.1.5.2. the softwire. Refer to Section 3.1.5.2.
3.1.3.5. Softwire46-PORTPARAMS Attribute 3.1.3.5. Softwire46-PORTPARAMS Attribute
The Softwire46-PORTPARAMS is optional. It is used to specify port Softwire46-PORTPARAMS is optional. It is used to specify port set
set information for IPv4 address sharing between clients. The information for IPv4 address sharing between clients.
Softwire46-PORTPARAMS MAY be included in any of the Softwire46 Softwire46-PORTPARAMS MAY be included in any of the Softwire46
attributes. attributes.
The structure of Softwire46-PORTPARAMS is shown below: The structure of Softwire46-PORTPARAMS is shown below:
TLV-Type TLV-Type
9 9
TLV-Length TLV-Length
Indicates the length of this attribute, including Indicates the length of this attribute, including
skipping to change at page 16, line 35 skipping to change at page 15, line 35
This attribute specifies the number of significant bits in the This attribute specifies the number of significant bits in the
PSID field (also known as 'k'). Refer to Section 3.1.6.2. PSID field (also known as 'k'). Refer to Section 3.1.6.2.
PSID PSID
This attribute specifies PSID value. Refer to Section 3.1.6.3. This attribute specifies PSID value. Refer to Section 3.1.6.3.
3.1.4. Sub-Attributes for Sofwtire46-Rule 3.1.4. Sub-Attributes for Sofwtire46-Rule
There are two types of Softwire46-Rule: the Basic Mapping Rule and There are two types of Softwire46-Rule: the Basic Mapping Rule and
the Forwarding Mapping Rule, indicated by the value in the TLV-Type the Forwarding Mapping Rule, indicated by the value in the TLV-Type
field of the Softwire46-Rule (see Section 3.1.3.1). field of Softwire46-Rule (see Section 3.1.3.1).
Each type of Softwire46-Rule also contains a number of Sub-attributes Each type of Softwire46-Rule also contains a number of Sub-attributes
as detailed in the following sub-sections. as detailed in the following sub-sections.
3.1.4.1. Rule-IPv6-Prefix Attribute 3.1.4.1. Rule-IPv6-Prefix Attribute
The Rule-IPv6-Prefix is REQUIRED for every Softwire46-Rule. There Rule-IPv6-Prefix is REQUIRED for every Softwire46-Rule. There MUST
MUST be exactly one Rule-IPv6-Prefix encapsulated in each type of be exactly one Rule-IPv6-Prefix encapsulated in each type of
Softwire46-Rule. Softwire46-Rule.
The Rule-IPv6-Prefix follows the framed IPv6 prefix designed in Rule-IPv6-Prefix follows the framed IPv6 prefix designed in [RFC3162]
[RFC3162] and [RFC8044]. and [RFC8044].
The structure of Rule-IPv6-Prefix is shown below: The structure of Rule-IPv6-Prefix is shown below:
TLV-Type TLV-Type
10 10
TLV-Length TLV-Length
20 octets 20 octets
Data Type Data Type
skipping to change at page 18, line 39 skipping to change at page 17, line 39
13 13
TLV-Length TLV-Length
6 octets 6 octets
Data Type Data Type
The attribute IPv4-address is of type ipv4addr (Section 3.8 The attribute IPv4-address is of type ipv4addr (Section 3.8
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
32-bits long. Specifies the IPv4 address to appear in the 32-bits long. Specifies the IPv4 address to appear in
Softwire46-V4V6Bind (Section 3.1.3.4). Softwire46-V4V6Bind (Section 3.1.3.4).
3.1.5.2. Bind-IPv6-Prefix Attribute 3.1.5.2. Bind-IPv6-Prefix Attribute
The Bind-IPv6-Prefix is used by the CE to identify the correct IPv6 The Bind-IPv6-Prefix is used by the CE to identify the correct IPv6
prefix to be used as the tunnel source. prefix to be used as the tunnel source.
The structure of Bind-IPv6-Prefix is shown below: The structure of Bind-IPv6-Prefix is shown below:
TLV-Type TLV-Type
skipping to change at page 23, line 22 skipping to change at page 22, line 22
The Softwire46-Multicast Attribute MAY appear in a CoA-Request The Softwire46-Multicast Attribute MAY appear in a CoA-Request
packet. packet.
The Softwire46-Multicast Attribute MAY appear in an Accounting- The Softwire46-Multicast Attribute MAY appear in an Accounting-
Request packet. Request packet.
The Softwire46-Multicast Attribute MUST NOT appear in any other The Softwire46-Multicast Attribute MUST NOT appear in any other
RADIUS packet. RADIUS packet.
The Softwire46-Multicast Attribute MAY contain the ASM-Prefix64 The Softwire46-Multicast Attribute MAY contain ASM-Prefix64 (see
(see Section 3.3.1). Section 3.3.1).
The Softwire46-Multicast Attribute MAY contain the SSM-Prefix64 The Softwire46-Multicast Attribute MAY contain SSM-Prefix64 (see
(see Section 3.3.2). Section 3.3.2).
The Softwire46-Multicast Attribute MAY contain the U-Prefix64 (see The Softwire46-Multicast Attribute MAY contain U-Prefix64 (see
Section 3.3.3). Section 3.3.3).
The Softwire46-Multicast Attribute MUST include the ASM-Prefix64 The Softwire46-Multicast Attribute MUST include ASM-Prefix64 or
or the SSM-Prefix64, and it MAY include both. SSM-Prefix64, and it MAY include both.
The U-Prefix64 MUST be present when the SSM-Prefix64 is present. The U-Prefix64 MUST be present when SSM-Prefix64 is present.
The U-Prefix64 MAY be present when the ASM-Prefix64 is present. U-Prefix64 MAY be present when ASM-Prefix64 is present.
The Softwire46-Multicast Attribute is structured as follows: The Softwire46-Multicast Attribute is structured as follows:
Type Type
241 (To be confirmed by IANA) 241 (To be confirmed by IANA)
Length Length
This field indicates the total length in bytes of all fields of This field indicates the total length in bytes of all fields of
this attribute, including the Type, Length, Extended-Type, and the this attribute, including the Type, Length, Extended-Type, and the
entire length of the embedded attributes. entire length of the embedded attributes.
skipping to change at page 25, line 27 skipping to change at page 24, line 27
[RFC8044]). [RFC8044]).
TLV-Type TLV-Type
This field specifies the IPv6 multicast prefix (ssm-prefix64) This field specifies the IPv6 multicast prefix (ssm-prefix64)
to be used to synthesize the IPv4-embedded IPv6 addresses of the to be used to synthesize the IPv4-embedded IPv6 addresses of the
multicast groups in the SSM mode. The conveyed multicast IPv6 multicast groups in the SSM mode. The conveyed multicast IPv6
prefix MUST belong to the SSM range. prefix MUST belong to the SSM range.
3.3.3. U-Prefix64 Attribute 3.3.3. U-Prefix64 Attribute
The structure of the U-Prefix64 attribute is shown below: The structure of U-Prefix64 is shown below:
TLV-Type TLV-Type
20 20
TLV-Length TLV-Length
4 + length of unicast-prefix. As specified in [RFC6052], 4 + length of unicast-prefix. As specified in [RFC6052],
the unicast-prefix prefix-length MUST be set to 32, 40, 48, the unicast-prefix prefix-length MUST be set to 32, 40, 48,
56, 64, or 96. 56, 64, or 96.
Data Type Data Type
skipping to change at page 27, line 9 skipping to change at page 26, line 9
User-Password Attribute (2) (with a pre-configured shared User-Password Attribute (2) (with a pre-configured shared
password as defined in [RFC2865]. The Softwire46-Configuration password as defined in [RFC2865]. The Softwire46-Configuration
Attribute and/or Softwire46-Multicast Attribute are also included Attribute and/or Softwire46-Multicast Attribute are also included
(as requested by the client). The resulting message is sent to (as requested by the client). The resulting message is sent to
the AAA server. the AAA server.
3. The AAA server authenticates the request. If this is successful, 3. The AAA server authenticates the request. If this is successful,
and suitable configuration is available, an Access-Accept message and suitable configuration is available, an Access-Accept message
is sent to the BNG containing the requested is sent to the BNG containing the requested
Softwire46-Configuration Attribute or Softwire46-Multicast Softwire46-Configuration Attribute or Softwire46-Multicast
Attribute. Attribute. It is the responsibility of the AAA server to ensure
the consistency of the provided configuration.
4. The BNG maps the received softwire configuration into the 4. The BNG maps the received softwire configuration into the
corresponding fields in the DHCPv6 softwire configuration corresponding fields in the DHCPv6 softwire configuration
option(s). Theses are included in the DHCPv6 Advertise message option(s). Theses are included in the DHCPv6 Advertise message
which is sent to the CE. which is sent to the CE.
5. The CE send a DHCPv6 Request message. In the ORO, the option 5. The CE send a DHCPv6 Request message. In the ORO, the option
code(s) of any of the required softwire options that were code(s) of any of the required softwire options that were
received in the Advertise message are included. received in the Advertise message are included.
skipping to change at page 28, line 8 skipping to change at page 27, line 8
protect both Access-Request and Access-Accept messages. protect both Access-Request and Access-Accept messages.
o If the BNG does not receive the corresponding o If the BNG does not receive the corresponding
Softwire46-Configuration Attribute in the Access-Accept message it Softwire46-Configuration Attribute in the Access-Accept message it
MAY fallback to creating the DHCPv6 softwire configuration options MAY fallback to creating the DHCPv6 softwire configuration options
using pre-configured Softwire46 configuration, if this is present. using pre-configured Softwire46 configuration, if this is present.
o If the BNG receives an Access-Reject from the AAA server, then o If the BNG receives an Access-Reject from the AAA server, then
Softwire46 configuration MUST NOT be supplied to the client. Softwire46 configuration MUST NOT be supplied to the client.
o As specified in [RFC3315], Section 18.1.4, "Creation and o As specified in [RFC8415], Section 18.2.5, "Creation and
Transmission of Rebind Messages", if the DHCPv6 server to which Transmission of Rebind Messages", if the DHCPv6 server to which
the DHCPv6 Renew message was sent at time T1 has not responded by the DHCPv6 Renew message was sent at time T1 has not responded by
time T2, the CE (DHCPv6 client) SHOULD enter the Rebind state and time T2, the CE (DHCPv6 client) SHOULD enter the Rebind state and
attempt to contact any available server. In this situation, a attempt to contact any available server. In this situation, a
secondary BNG receiving the DHCPv6 message MUST initiate a new secondary BNG receiving the DHCPv6 message MUST initiate a new
Access-Request message towards the AAA server. The secondary BNG Access-Request message towards the AAA server. The secondary BNG
includes the Softwire46-Configuration Attribute in this Access- includes the Softwire46-Configuration Attribute in this Access-
Request message. Request message.
o For Lightweight 4over6, the subscriber's binding state needs to be o For Lightweight 4over6, the subscriber's binding state needs to be
skipping to change at page 29, line 40 skipping to change at page 28, line 40
7. IANA Considerations 7. IANA Considerations
IANA is requested to make new code point assignments for RADIUS IANA is requested to make new code point assignments for RADIUS
attributes as described in the following subsections. attributes as described in the following subsections.
7.1. New RADIUS Attributes 7.1. New RADIUS Attributes
This document requests IANA to assign the Attribute Types defined in This document requests IANA to assign the Attribute Types defined in
this document from the RADIUS namespace as described in the "IANA this document from the RADIUS namespace as described in the "IANA
Considerations" section of [RFC3575], in accordance with BCP 26 Considerations" section of [RFC3575], in accordance with BCP 26
[RFC5226]. [RFC8126].
This document requests that IANA register three new RADIUS This document requests that IANA register three new RADIUS
attributes, from the "Short Extended Space" of [RFC6929]. The attributes, from the "Short Extended Space" of [RFC6929]. The
attributes are: Softwire46-Configuration Attribute, attributes are: Softwire46-Configuration Attribute,
Softwire46-Priority Attribute, and Softwire46-Multicast Attribute: Softwire46-Priority Attribute, and Softwire46-Multicast Attribute:
Type Description Data Type Reference Type Description Data Type Reference
---- ----------- --------- --------- ---- ----------- --------- ---------
241.TBD1 Softwire46-Configuration tlv Section 4.1 241.TBD1 Softwire46-Configuration tlv Section 3.1
241.TBD5 Softwire46-Priority integer Section 4.2 241.TBD5 Softwire46-Priority integer Section 3.2
241.TBD6 Softwire46-Multicast tlv Section 4.3 241.TBD6 Softwire46-Multicast tlv Section 3.3
7.2. RADIUS Softwire46 Configuration and Multicast Attributes 7.2. RADIUS Softwire46 Configuration and Multicast Attributes
IANA is requested to create a new registry called "RADIUS Softwire46 IANA is requested to create a new registry called "RADIUS Softwire46
Configuration and Multicast Attributes". Configuration and Multicast Attributes".
All attributes in this registry have one or more parent RADIUS All attributes in this registry have one or more parent RADIUS
attributes in nesting (refer to [RFC6929]). attributes in nesting (refer to [RFC6929]).
This registry must be initially populated with the following values: This registry must be initially populated with the following values:
skipping to change at page 30, line 41 skipping to change at page 29, line 41
14 Bind-IPv6-Prefix ipv6prefix Section 3.1.5.2 14 Bind-IPv6-Prefix ipv6prefix Section 3.1.5.2
15 PSID-offset integer Section 3.1.6.1 15 PSID-offset integer Section 3.1.6.1
16 PSID-len integer Section 3.1.6.2 16 PSID-len integer Section 3.1.6.2
17 PSID integer Section 3.1.6.3 17 PSID integer Section 3.1.6.3
18 ASM-Prefix64 ipv6prefix Section 3.3.1 18 ASM-Prefix64 ipv6prefix Section 3.3.1
19 SSM-Prefix64 ipv6prefix Section 3.3.2 19 SSM-Prefix64 ipv6prefix Section 3.3.2
20 U-Prefix64 ipv6prefix Section 3.3.3 20 U-Prefix64 ipv6prefix Section 3.3.3
21-255 Unassigned 21-255 Unassigned
The registration procedure for this registry is Standards Action as The registration procedure for this registry is Standards Action as
defined in [RFC5226]. The registry may be added to using the IETF defined in [RFC8126].
Review process described in Section 4.1 of [RFC5226].
7.3. Softwire46 Mechanisms and Their Identifying Option Codes 7.3. Softwire46 Mechanisms and Their Identifying Option Codes
The Softwire46-Priority Attribute defines a 16-bit Softwire46-option- The Softwire46-Priority Attribute defines a 16-bit Softwire46-option-
code field, for which IANA is requested to create and maintain a new code field, for which IANA is requested to create and maintain a new
registry entitled "Option Codes Permitted in the Softwire46-Priority registry entitled "Option Codes Permitted in the Softwire46-Priority
Attribute". The registration procedure for this registry is Attribute". The registration procedure for this registry is
Standards Action as defined in [RFC5226]. Standards Action as defined in [RFC8126].
This document requests IANA to register the three option codes of the This document requests IANA to register the three option codes of the
Softwire46 mechanisms permitted to be included in the Softwire46 mechanisms permitted to be included in the
Softwire46-Priority Attribute. The value of option code corresponds Softwire46-Priority Attribute. The value of option code corresponds
to the TLV-Type defined in the Section 3.1.1. Additional options may to the TLV-Type defined in Section 3.1.1. Additional options may be
be added to this list in the future using the IETF Review process added to this list in the future using the IETF Review process
described in Section 4.1 of [RFC5226]. described in Section 4.8 of [RFC8126].
Table 3 shows the option codes required, and the Softwire46 Table 3 shows the option codes required, and the Softwire46
mechanisms that they represent. The option code for DS-Lite is mechanisms that they represent. The option code for DS-Lite is
derived from the IANA allocated RADIUS Attribute Type value for DS- derived from the IANA allocated RADIUS Attribute Type value for DS-
Lite [RFC6519]. The option codes for MAP-E, MAP-T, and Lightweight Lite [RFC6519]. The option codes for MAP-E, MAP-T, and Lightweight
4over6 need to be assigned. The option codes for MAP-E, MAP-T, and 4over6 need to be assigned. The option codes for MAP-E, MAP-T, and
Lightweight 4over6 should also be used as the TLV-Type values for the Lightweight 4over6 should also be used as the TLV-Type values for the
MAP-E, MAP-T, and Lightweight 4over6 TLV defined in Section 3.1.1. MAP-E, MAP-T, and Lightweight 4over6 attributes defined in
Section 3.1.1.
+-----------+--------------------+-----------+ +-----------+--------------------+-----------+
|Option Code|Softwire46 Mechanism| Reference | |Option Code|Softwire46 Mechanism| Reference |
+-----------+--------------------+-----------+ +-----------+--------------------+-----------+
| TBD2 | MAP-E | RFC7597 | | TBD2 | MAP-E | RFC7597 |
| TBD3 | MAP-T | RFC7599 | | TBD3 | MAP-T | RFC7599 |
| TBD4 | Lightweight 4over6 | RFC7596 | | TBD4 | Lightweight 4over6 | RFC7596 |
| 144 | DS-Lite | RFC6519 | | 144 | DS-Lite | RFC6519 |
+--------------------------------+-----------+ +--------------------------------+-----------+
skipping to change at page 32, line 48 skipping to change at page 31, line 48
Tsinghua University Tsinghua University
Beijing 100084 Beijing 100084
P.R.China P.R.China
Phone: +86-10-62603059 Phone: +86-10-62603059
Email: yong@csnet1.cs.tsinghua.edu.cn Email: yong@csnet1.cs.tsinghua.edu.cn
9. Acknowledgements 9. Acknowledgements
The authors would like to thank the valuable comments made by Peter The authors would like to thank the valuable comments made by Peter
Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan, Qian Wang, Wei Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan, Qian Wang, Wei
Meng, Cui Wang, Alan Dekok, and Stefan Winter to this document. Meng, Cui Wang, Alan Dekok, Stefan Winter, and Yu Tianpeng to this
document.
This document was merged with draft-sun-softwire-lw4over6-radext-01 This document was merged with draft-sun-softwire-lw4over6-radext-01
and draft-wang-radext-multicast-radius-ext-00, thanks to everyone who and draft-wang-radext-multicast-radius-ext-00, thanks to everyone who
contributed to this document. contributed to this document.
This document was produced using the xml2rfc tool [RFC7991]. This document was produced using the xml2rfc tool [RFC7991].
10. References 10. References
10.1. Normative References 10.1. Normative References
skipping to change at page 33, line 29 skipping to change at page 32, line 29
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, DOI 10.17487/RFC2865, June 2000, RFC 2865, DOI 10.17487/RFC2865, June 2000,
<https://www.rfc-editor.org/info/rfc2865>. <https://www.rfc-editor.org/info/rfc2865>.
[RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",
RFC 3162, DOI 10.17487/RFC3162, August 2001, RFC 3162, DOI 10.17487/RFC3162, August 2001,
<https://www.rfc-editor.org/info/rfc3162>. <https://www.rfc-editor.org/info/rfc3162>.
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <https://www.rfc-editor.org/info/rfc3315>.
[RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote
Authentication Dial In User Service)", RFC 3575, Authentication Dial In User Service)", RFC 3575,
DOI 10.17487/RFC3575, July 2003, DOI 10.17487/RFC3575, July 2003,
<https://www.rfc-editor.org/info/rfc3575>. <https://www.rfc-editor.org/info/rfc3575>.
[RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication [RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication
Dial In User Service (RADIUS) Implementation Issues and Dial In User Service (RADIUS) Implementation Issues and
Suggested Fixes", RFC 5080, DOI 10.17487/RFC5080, December Suggested Fixes", RFC 5080, DOI 10.17487/RFC5080, December
2007, <https://www.rfc-editor.org/info/rfc5080>. 2007, <https://www.rfc-editor.org/info/rfc5080>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<https://www.rfc-editor.org/info/rfc5226>.
[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,
DOI 10.17487/RFC6052, October 2010, DOI 10.17487/RFC6052, October 2010,
<https://www.rfc-editor.org/info/rfc6052>. <https://www.rfc-editor.org/info/rfc6052>.
[RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines", [RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines",
BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011, BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011,
<https://www.rfc-editor.org/info/rfc6158>. <https://www.rfc-editor.org/info/rfc6158>.
[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User
skipping to change at page 34, line 34 skipping to change at page 33, line 25
Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients
over an IPv6 Multicast Network", RFC 8114, over an IPv6 Multicast Network", RFC 8114,
DOI 10.17487/RFC8114, March 2017, DOI 10.17487/RFC8114, March 2017,
<https://www.rfc-editor.org/info/rfc8114>. <https://www.rfc-editor.org/info/rfc8114>.
[RFC8115] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6 [RFC8115] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6
Option for IPv4-Embedded Multicast and Unicast IPv6 Option for IPv4-Embedded Multicast and Unicast IPv6
Prefixes", RFC 8115, DOI 10.17487/RFC8115, March 2017, Prefixes", RFC 8115, DOI 10.17487/RFC8115, March 2017,
<https://www.rfc-editor.org/info/rfc8115>. <https://www.rfc-editor.org/info/rfc8115>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,
Richardson, M., Jiang, S., Lemon, T., and T. Winters,
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 8415, DOI 10.17487/RFC8415, November 2018,
<https://www.rfc-editor.org/info/rfc8415>.
10.2. Informative References 10.2. Informative References
[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
Implementation in Roaming", RFC 2607, Implementation in Roaming", RFC 2607,
DOI 10.17487/RFC2607, June 1999, DOI 10.17487/RFC2607, June 1999,
<https://www.rfc-editor.org/info/rfc2607>. <https://www.rfc-editor.org/info/rfc2607>.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000, Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,
<https://www.rfc-editor.org/info/rfc2869>. <https://www.rfc-editor.org/info/rfc2869>.
 End of changes. 53 change blocks. 
121 lines changed or deleted 117 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/