draft-ietf-softwire-map-radius-23.txt   draft-ietf-softwire-map-radius-24.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: November 15, 2019 CNNIC Expires: December 2, 2019 CNNIC
B. Liu
Huawei Technologies Co., Ltd
P. Deacon
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
May 14, 2019 May 31, 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-23 draft-ietf-softwire-map-radius-24
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 7
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 November 15, 2019. This Internet-Draft will expire on December 2, 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 32 skipping to change at page 2, line 29
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. New RADIUS Attributes . . . . . . . . . . . . . . . . . . . . 6 3. New RADIUS Attributes . . . . . . . . . . . . . . . . . . . . 6
3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 7 3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6
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 . . . . . . . . . . . . 13 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 . . . . . . . . . 14 3.1.3.5. Softwire46-PORTPARAMS Attribute . . . . . . . . . 14
3.1.4. Sub-Attributes for Sofwtire46-Rule . . . . . . . . . 15 3.1.4. Sub-Attributes for Sofwtire46-Rule . . . . . . . . . 15
3.1.4.1. Rule-IPv6-Prefix Attribute . . . . . . . . . . . 15 3.1.4.1. Rule-IPv6-Prefix Attribute . . . . . . . . . . . 15
3.1.4.2. Rule-IPv4-Prefix Attribute . . . . . . . . . . . 16 3.1.4.2. Rule-IPv4-Prefix Attribute . . . . . . . . . . . 16
3.1.4.3. EA-Length Attribute . . . . . . . . . . . . . . . 16 3.1.4.3. EA-Length Attribute . . . . . . . . . . . . . . . 16
3.1.5. Attributes for Softwire46-v4v6Bind . . . . . . . . . 17 3.1.5. Attributes for Softwire46-v4v6Bind . . . . . . . . . 17
3.1.5.1. IPv4-address Attribute . . . . . . . . . . . . . 17 3.1.5.1. IPv4-Address Attribute . . . . . . . . . . . . . 17
3.1.5.2. Bind-IPv6-Prefix Attribute . . . . . . . . . . . 17 3.1.5.2. Bind-IPv6-Prefix Attribute . . . . . . . . . . . 17
3.1.6. Attributes for S46-PORTPARAMS . . . . . . . . . . . . 18 3.1.6. Attributes for Softwire46-PORTPARAMS . . . . . . . . 18
3.1.6.1. PSID-offset Attribute . . . . . . . . . . . . . . 18 3.1.6.1. PSID-Offset Attribute . . . . . . . . . . . . . . 18
3.1.6.2. PSID-len Attribute . . . . . . . . . . . . . . . 19 3.1.6.2. PSID-Len Attribute . . . . . . . . . . . . . . . 19
3.1.6.3. PSID Attribute . . . . . . . . . . . . . . . . . 19 3.1.6.3. PSID Attribute . . . . . . . . . . . . . . . . . 19
3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 20 3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 20
3.2.1. Softwire46-Option-Code . . . . . . . . . . . . . . . 21 3.2.1. Softwire46-Option-Code . . . . . . . . . . . . . . . 21
3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22 3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22
3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 23 3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 23
3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 24 3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 24
3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 24 3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 24
4. A Sample Configuration Process with RADIUS . . . . . . . . . 24 4. A Sample Configuration Process with RADIUS . . . . . . . . . 24
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 27 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 27
6. Security Considerations . . . . . . . . . . . . . . . . . . . 28 6. Security Considerations . . . . . . . . . . . . . . . . . . . 28
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
skipping to change at page 3, line 16 skipping to change at page 3, line 15
3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 20 3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 20
3.2.1. Softwire46-Option-Code . . . . . . . . . . . . . . . 21 3.2.1. Softwire46-Option-Code . . . . . . . . . . . . . . . 21
3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22 3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22
3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 23 3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 23
3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 24 3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 24
3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 24 3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 24
4. A Sample Configuration Process with RADIUS . . . . . . . . . 24 4. A Sample Configuration Process with RADIUS . . . . . . . . . 24
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 27 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 27
6. Security Considerations . . . . . . . . . . . . . . . . . . . 28 6. Security Considerations . . . . . . . . . . . . . . . . . . . 28
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 28 7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 29
7.2. RADIUS Softwire46 Configuration and Multicast Attributes 29 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 30
8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 30 8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 31
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.1. Normative References . . . . . . . . . . . . . . . . . . 32 10.1. Normative References . . . . . . . . . . . . . . . . . . 33
10.2. Informative References . . . . . . . . . . . . . . . . . 33 10.2. Informative References . . . . . . . . . . . . . . . . . 34
Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 35 Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 36
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 . . . . . . . . . . . . . . . . . . . . . . . . 35
A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings . . . 35
A.3. OPTION_S46_DMR (91) to Softwire46-DMR . . . . . . . . . . 35
A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind . . . . . 35
A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36
A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings . . . 36
A.3. OPTION_S46_DMR (91) to Softwire46-DMR . . . . . . . . . . 36
A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind . . . . . 36
A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 37
A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 37
A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast
Attribute Field Mappings . . . . . . . . . . . . . . . . 36 Attribute Field Mappings . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37
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 4, line 17 skipping to change at page 4, line 13
servers generally communicate using the Remote Authentication Dial In servers generally communicate using the Remote Authentication Dial In
User Service (RADIUS) [RFC2865] protocol. In a fixed broadband User Service (RADIUS) [RFC2865] protocol. In a fixed broadband
network, a Broadband Network Gateway (BNG) acts as the access gateway network, a Broadband Network Gateway (BNG) acts as the access gateway
for users. That is, the BNG acts as both an AAA client to the AAA for users. That is, the BNG acts as both an AAA client to the AAA
server, and a DHCPv6 server for DHCPv6 messages sent by clients. server, and a DHCPv6 server for DHCPv6 messages sent by clients.
Throughout this document, the term BNG describes a device Throughout this document, the term BNG describes a device
implementing both the AAA client and DHCPv6 server functions. implementing both the AAA client and DHCPv6 server functions.
Since IPv4-in-IPv6 softwire configuration information is stored in an Since IPv4-in-IPv6 softwire configuration information is stored in an
AAA server, and user configuration information is mainly transmitted AAA server, and user configuration information is mainly transmitted
through DHCPv6 protocol between the BNGs and Customer Premises through DHCPv6 between the BNGs and Customer Premises Equipment (CEs,
Equipment (CEs, a.k.a., CPE), new RADIUS attributes are needed to a.k.a., CPE), new RADIUS attributes are needed to propagate the
propagate the information from the AAA servers to BNGs. information from the AAA servers to BNGs.
The RADIUS attributes defined in this document provide configuration The RADIUS attributes defined in this document provide configuration
to populate the corresponding DHCPv6 options for unicast and to populate the corresponding DHCPv6 options for unicast and
multicast softwire configuration, specifically: multicast softwire configuration, specifically:
o "Mapping of Address and Port with Encapsulation (MAP-E)" [RFC7597] o "Mapping of Address and Port with Encapsulation (MAP-E)" [RFC7597]
(DHCPv6 options defined in [RFC7598]. (DHCPv6 options defined in [RFC7598]).
o "Mapping of Address and Port using Translation (MAP-T)" [RFC7599] o "Mapping of Address and Port using Translation (MAP-T)" [RFC7599]
(DHCPv6 options defined in [RFC7598]. (DHCPv6 options defined in [RFC7598]).
o "Lightweight 4over6: An Extension to the Dual-Stack Lite o "Lightweight 4over6: An Extension to the Dual-Stack Lite
Architecture" [RFC7596] (DHCPv6 options defined in [RFC7598]. Architecture" [RFC7596] (DHCPv6 options defined in [RFC7598]).
o "Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): o "Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE):
A DHCPv6-Based Prioritization Mechanism" [RFC8026]. A DHCPv6-Based Prioritization Mechanism" [RFC8026].
o "Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 o "Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6
Multicast Network" [RFC8114] (DHCPv6 options defined in [RFC8115]. Multicast Network" [RFC8114] (DHCPv6 options defined in
[RFC8115]).
The contents of the attributes defined in this document have a 1:1 The contents of the attributes defined in this document have a 1:1
mapping into the fields of the various DHCPv6 options in [RFC7598], mapping into the fields of the various DHCPv6 options in [RFC7598],
[RFC8026], and [RFC8115]. Table 1 shows how the DHCPv6 options map [RFC8026], and [RFC8115]. Table 1 shows how the DHCPv6 options map
to the corresponding RADIUS attribute. For detailed mappings between to the corresponding RADIUS attribute. For detailed mappings between
each DHCPv6 option field and the corresponding RADIUS Attribute or each DHCPv6 option field and the corresponding RADIUS Attribute or
field, see Appendix A. field, see Appendix A.
+----------------------------+--------------------------------+ +----------------------------+--------------------------------+
| DHCPv6 Option | RADIUS Attribute | | DHCPv6 Option | RADIUS Attribute |
+----------------------------+--------------------------------+ +----------------------------+--------------------------------+
| OPTION_S46_RULE (89) | Softwire46-Rule | | OPTION_S46_RULE (89) | Softwire46-Rule |
| OPTION_S46_BR (90) | Softwire46-BR | | OPTION_S46_BR (90) | Softwire46-BR |
| OPTION_S46_DMR (91) | Softwire46-DMR | | OPTION_S46_DMR (91) | Softwire46-DMR |
| OPTION_S46_V4V6BIND (92) | Softwire46-v4v6Bind | | OPTION_S46_V4V6BIND (92) | Softwire46-V4V6Bind |
| OPTION_S46_PORTPARAMS (93) | Softwire46-PORTPARAMS | | OPTION_S46_PORTPARAMS (93) | Softwire46-PORTPARAMS |
| OPTION_S46_PRIORITY (111) | Softwire46-Priority Attribute | | OPTION_S46_PRIORITY (111) | Softwire46-Priority |
| OPTION_V6_PREFIX64 (113) | Softwire46-Multicast Attribute | | OPTION_V6_PREFIX64 (113) | Softwire46-Multicast |
+----------------------------+--------------------------------+ +----------------------------+--------------------------------+
Table 1: Mapping between DHCPv6 Options and RADIUS Attributes Table 1: Mapping between DHCPv6 Options and RADIUS Attributes
A RADIUS attribute for Dual-Stack Lite [RFC6333] is defined in A RADIUS attribute for Dual-Stack Lite [RFC6333] is defined in
[RFC6519]. [RFC6519].
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 5, line 41 skipping to change at page 5, line 41
[RFC7596], [RFC7597], [RFC7599], and [RFC8026]. [RFC7596], [RFC7597], [RFC7599], and [RFC8026].
The terms "multicast Basic Bridging BroadBand" element (mB4) and The terms "multicast Basic Bridging BroadBand" element (mB4) and
"multicast Address Family Transition Router" element (mAFTR) are "multicast Address Family Transition Router" element (mAFTR) are
defined in [RFC8114]. defined in [RFC8114].
Softwire46 (S46) is used throughout to denote any of the IPv4-in-IPv6 Softwire46 (S46) is used throughout to denote any of the IPv4-in-IPv6
softwire mechanisms listed above. Additionally, the following softwire mechanisms listed above. Additionally, the following
abbreviations are used within the document: abbreviations are used within the document:
o BMR: Basic Mapping Rule
o BNG: Broadband Network Gateway o BNG: Broadband Network Gateway
o BR: Border Relay o BR: Border Relay
o CE: Customer Edge o CE: Customer Edge
o DMR: Default Mapping Rule o DMR: Default Mapping Rule
o EA: Embedded Address o lwAFTR: Lightweight AFTR
o FMR: Forwarding Mapping Rule
o PSID: Port Set Identifier o PSID: Port Set Identifier
o TLV: Type, Length, Value o TLV: Type, Length, Value
o MAP-E: Mapping of Address and Port with Encapsulation o MAP-E: Mapping of Address and Port with Encapsulation
o MAP-T: Mapping of Address and Port using Translation o MAP-T: Mapping of Address and Port using Translation
3. New RADIUS Attributes 3. New RADIUS Attributes
This section defines the following attributes: This section defines the following attributes:
skipping to change at page 7, line 22 skipping to change at page 7, line 16
the following attributes: Softwire46-MAP-E, Softwire46-MAP-T, and/ the following attributes: Softwire46-MAP-E, Softwire46-MAP-T, and/
or Softwire46-Lightweight-4over6. or Softwire46-Lightweight-4over6.
The Softwire46-Configuration Attribute conveys the configuration The Softwire46-Configuration Attribute conveys the configuration
information for MAP-E, MAP-T, or Lightweight 4over6. The BNG information for MAP-E, MAP-T, or Lightweight 4over6. The BNG
SHALL use the configuration information returned in the RADIUS SHALL use the configuration information returned in the RADIUS
attribute to populate the DHCPv6 Softwire46 Container Option attribute to populate the DHCPv6 Softwire46 Container Option
defined in Section 5 of [RFC7598]. defined in Section 5 of [RFC7598].
The Softwire46-Configuration Attribute MAY appear in an Access- The Softwire46-Configuration Attribute MAY appear in an Access-
Accept packet. It MAY also appear in an Access-Request packet. Accept packet. It MAY also appear in an Access-Request packet to
indicate a preferred Softwire46 configuration. However, the
server is not required to honor such a preference.
The Softwire46-Configuration Attribute MAY appear in a CoA-Request The Softwire46-Configuration Attribute MAY appear in a CoA-Request
packet. packet.
The Softwire46-Configuration Attribute MAY appear in an The Softwire46-Configuration Attribute MAY appear in an
Accounting-Request packet. Accounting-Request packet.
The Softwire46-Configuration Attribute MUST NOT appear in any The Softwire46-Configuration Attribute MUST NOT appear in any
other RADIUS packet. other RADIUS packet.
skipping to change at page 9, line 16 skipping to change at page 9, line 16
Softwire46 attributes is shown in Figure 1. Section 3.1.2 describes Softwire46 attributes is shown in Figure 1. Section 3.1.2 describes
which sub-attributes are mandatory, optional, or not permitted for which sub-attributes are mandatory, optional, or not permitted for
each defined Softwire46 attribute. each defined Softwire46 attribute.
/1.Rule-IPv6-Prefix /1.Rule-IPv6-Prefix
S / | S / |
o / | 1.Softwire46-Rule -----+ 2.Rule-IPv4-Prefix o / | 1.Softwire46-Rule -----+ 2.Rule-IPv4-Prefix
f | Softwire46-MAP-E--+ | f | Softwire46-MAP-E--+ |
t | | 2.Softwire46-BR | 3.EA Length t | | 2.Softwire46-BR | 3.EA Length
w | | \ w | | \
i | | /1.PSID-offset i | | /1.PSID-Offset
r | | | r | | |
e | | 5.Softwire46-PORTPARAMS -----+ 2.PSID-len e | | 3.Softwire46-PORTPARAMS -----+ 2.PSID-Len
- | \ | - | \ |
C | | 3.PSID C | | 3.PSID
o | \ o | \
n | n |
f | /1.Rule-IPv6-Prefix f | /1.Rule-IPv6-Prefix
i | / | i | / |
g | | 1.Softwire46-Rule------+ 2.Rule-IPv4-Prefix g | | 1.Softwire46-Rule------+ 2.Rule-IPv4-Prefix
u | Softwire46-MAP-T--+ | u | Softwire46-MAP-T--+ |
r | | 3.Softwire46-DMR | 3.EA Length r | | 2.Softwire46-DMR | 3.EA Length
a | | \ a | | \
t | | /1.PSID-offset t | | /1.PSID-Offset
i | | | i | | |
o | | 5.Softwire46-PORTPARAMS------+ 2.PSID-len o | | 3.Softwire46-PORTPARAMS------+ 2.PSID-Len
n | \ | n | \ |
| | 3.PSID | | 3.PSID
A | \ A | \
t | t |
t | /1.IPv4-address t | /1.IPv4-Address
r | / | r | / |
i | | 4.Softwire46-v4v6Bind -----+ 2.Bind-IPv6-Prefix i | | 1.Softwire46-V4V6Bind -----+ 2.Bind-IPv6-Prefix
b | Softwire46- | \ b | Softwire46- | \
u | Lightweight-4over6+ /1.PSID-offset u | Lightweight-4over6+ 2.Softwire46-BR /1.PSID-Offset
t \ | | t \ | |
e | 5.Softwire46-PORTPARAMS ----+ 2.PSID-len e | 3.Softwire46-PORTPARAMS ----+ 2.PSID-Len
\ | \ |
| 3.PSID | 3.PSID
\ \
Figure 1: Softwire46 Attributes Hierarchy Figure 1: Softwire46 Attributes Hierarchy
3.1.1.1. Softwire46-MAP-E Attribute 3.1.1.1. Softwire46-MAP-E Attribute
Softwire46-MAP-E attribute is designed for carrying the configuration Softwire46-MAP-E attribute is designed for carrying the configuration
information for MAP-E. The structure of Softwire46-MAP-E is shown information for MAP-E. The structure of Softwire46-MAP-E is shown
skipping to change at page 11, line 49 skipping to change at page 11, line 49
| Softwire46-PORTPARAMS | 0-1 | 0-1 | 0-1 | | Softwire46-PORTPARAMS | 0-1 | 0-1 | 0-1 |
+-----------------------+-------+-------+--------------------+ +-----------------------+-------+-------+--------------------+
Table 2: Softwire46 Sub-Attributes Table 2: Softwire46 Sub-Attributes
The following table defines the meaning of Table 2 entries. The following table defines the meaning of Table 2 entries.
0 Not Permitted 0 Not Permitted
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, only one instance of the attribute
must be present.
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
Softwire46-Rule can only be encapsulated in Softwire46-MAP-E Softwire46-Rule can only be encapsulated in Softwire46-MAP-E
(Section 3.1.1.1) or Softwire46-MAP-T (Section 3.1.1.2). Depending (Section 3.1.1.1) or Softwire46-MAP-T (Section 3.1.1.2). Depending
on the deployment scenario, one Basic Mapping Rule (BMR) and zero or on the deployment scenario, one Basic Mapping Rule (BMR) and zero or
more Forwarding Mapping Rules (FMRs) MUST be included in one more Forwarding Mapping Rules (FMRs) MUST be included in one
Softwire46-MAP-E or Softwire46-MAP-T. Softwire46-MAP-E or Softwire46-MAP-T.
skipping to change at page 12, line 50 skipping to change at page 12, line 50
Rule-IPv6-Prefix Rule-IPv6-Prefix
This attribute contains the IPv6 prefix for use in the MAP rule. This attribute contains the IPv6 prefix for use in the MAP rule.
Refer to Section 3.1.4.1. Refer to Section 3.1.4.1.
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.3.
3.1.3.2. Softwire46-BR Attribute 3.1.3.2. Softwire46-BR Attribute
Softwire46-BR can only be encapsulated in 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:
skipping to change at page 13, line 37 skipping to change at page 13, line 37
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
Softwire46-DMR may only appear in Softwire46-MAP-T (Section 3.1.1.2). Softwire46-DMR may only appear in Softwire46-MAP-T (Section 3.1.1.2).
There MUST be exactly one Softwire46-DMR included in one Softwire46- There MUST be exactly one Softwire46-DMR included 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
The attribute Softwire46-DMR is of type ip6pref (Section 3.10 of The attribute Softwire46-DMR is of type ip6pref (Section 3.10 of
[RFC8044]). [RFC8044]).
TLV-Value TLV-Value
dmr-ipv6-prefix. A variable-length (dmr-prefix6-len) field dmr-ipv6-prefix. A variable-length (dmr-prefix6-len) field
specifying the IPv6 prefix for the BR. This field is right-padded specifying the IPv6 prefix for the BR. This field is right-padded
with zeros to the nearest octet boundary when dmr-prefix6-len with zeros to the nearest octet boundary when dmr-prefix6-len
is not divisible by 8. Prefixes with from 0 to 96 are allowed. is not divisible by 8. Prefixes with length from 0 to 96 are allowed.
3.1.3.4. Softwire46-V4V6Bind Attribute 3.1.3.4. Softwire46-V4V6Bind Attribute
Softwire46-V4V6Bind may only be encapsulated in 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
skipping to change at page 14, line 27 skipping to change at page 14, line 27
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.
Data Type Data Type
The attribute Softwire46-V4V6Bind is of type tlv (Section 3.13 of The attribute Softwire46-V4V6Bind is of type tlv (Section 3.13 of
[RFC8044]). [RFC8044]).
TLV-Value TLV-Value
This field contains a set of attributes as follows: This field contains a set of attributes as follows:
IPv4-address IPv4-Address
This attribute contains an IPv4 address, used to specify This attribute contains an IPv4 address, used to specify
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
skipping to change at page 15, line 19 skipping to change at page 15, line 19
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.
Data Type Data Type
The attribute Softwire46-PORTPARAMS is of type tlv (Section 3.13 The attribute Softwire46-PORTPARAMS is of type tlv (Section 3.13
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
This field contains a set of attributes as follows: This field contains a set of attributes as follows:
PSID-offset PSID-Offset
This attribute specifies the numeric value for the Softwire46 This attribute specifies the numeric value for the Softwire46
algorithm's excluded port range/offset bits (a bits). Refer to algorithm's excluded port range/offset bits (a bits). Refer to
Section 3.1.6.1. Section 3.1.6.1.
PSID-len PSID-Len
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
skipping to change at page 16, line 9 skipping to change at page 16, line 9
Rule-IPv6-Prefix follows the framed IPv6 prefix designed in [RFC3162] Rule-IPv6-Prefix follows the framed IPv6 prefix designed in [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 4 + length of rule-ipv6-prefix specified in octets.
Data Type Data Type
The attribute Rule-IPv6-Prefix is of type ipv6pref (Section 3.10 The attribute Rule-IPv6-Prefix is of type ipv6pref (Section 3.10
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
rule-ipv6-prefix. 128-bits long field that specifies an IPv6 rule-ipv6-prefix. A variable-length field that specifies an IPv6
prefix appearing in the MAP rule. prefix appearing in the MAP rule.
3.1.4.2. Rule-IPv4-Prefix Attribute 3.1.4.2. Rule-IPv4-Prefix Attribute
This attribute is used to convey the MAP Rule IPv4 prefix. The This attribute is used to convey the MAP Rule IPv4 prefix. The
structure of Rule-IPv4-Prefix is shown below: structure of Rule-IPv4-Prefix is shown below:
TLV-Type TLV-Type
11 11
TLV-Length TLV-Length
8 octets 4 + length of rule-ipv4-prefix specified in octets.
Data Type Data Type
The attribute Rule-IPv4-Prefix is of type ipv4pref (Section 3.11 The attribute Rule-IPv4-Prefix is of type ipv4pref (Section 3.11
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
rule-ipv4-prefix. 32-bits long. Specifies the IPv4 prefix rule-ipv4-prefix. A variable-length field that pecifies
appearing in the MAP rule. an IPv4 prefix appearing in the MAP rule.
3.1.4.3. EA-Length Attribute 3.1.4.3. EA-Length Attribute
This attribute is used to convey the Embedded-Address(EA) bit length. This attribute is used to convey the Embedded-Address (EA) bit
The structure of EA-Length is shown below: length. The structure of EA-Length is shown below:
TLV-Type TLV-Type
12 12
TLV-Length TLV-Length
6 octets 6 octets
Data Type Data Type
The attribute EA-Length is of type integer (Section 3.1 of The attribute EA-Length is of type integer (Section 3.1 of
[RFC8044]). [RFC8044]).
TLV-Value TLV-Value
EA-len; 32-bits long. Specifies the Embedded-Address(EA) bit EA-len; 32-bits long. Specifies the Embedded-Address (EA) bit
length. Allowed values range from 0 to 48. length. Allowed values range from 0 to 48.
3.1.5. Attributes for Softwire46-v4v6Bind 3.1.5. Attributes for Softwire46-v4v6Bind
3.1.5.1. IPv4-address Attribute 3.1.5.1. IPv4-Address Attribute
The IPv4-address MAY be used to specify the full or shared IPv4 The IPv4-Address MAY be used to specify the full or shared IPv4
address of the CE. address of the CE.
The structure of IPv4-address is shown below: The structure of IPv4-Address is shown below:
TLV-Type TLV-Type
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 (ipv4-address) to 32-bits long. Specifies the IPv4 address (ipv4-address) to
appear in Softwire46-V4V6Bind (Section 3.1.3.4). appear in 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.
skipping to change at page 18, line 19 skipping to change at page 18, line 19
4 + length of bind-ipv6-prefix specified in octets. 4 + length of bind-ipv6-prefix specified in octets.
Data Type Data Type
The attribute Bind-IPv6-Prefix is of type ipv6pref (Section 3.10 The attribute Bind-IPv6-Prefix is of type ipv6pref (Section 3.10
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
bind-ipv6-prefix. A variable-length field specifying the IPv6 bind-ipv6-prefix. A variable-length field specifying the IPv6
prefix or address for the Softwire46 CE. This field is prefix or address for the Softwire46 CE. This field is
right-padded with zeros to the nearest octet boundary right-padded with zeros to the nearest octet boundary
when bindprefix6-len is not divisible by 8. when the prefix length is not divisible by 8.
3.1.6. Attributes for S46-PORTPARAMS 3.1.6. Attributes for Softwire46-PORTPARAMS
3.1.6.1. PSID-offset Attribute 3.1.6.1. PSID-Offset Attribute
This attribute is used to convey the Port Set Identifier offset as This attribute is used to convey the Port Set Identifier offset as
defined in [RFC7597]. This attribute is encoded 32 bits as per the defined in [RFC7597]. This attribute is encoded in 32 bits as per
recommendation in Appendix A.2.1 of [RFC6158]. the recommendation in Appendix A.2.1 of [RFC6158].
The structure of PSID-offset is shown below: The structure of PSID-Offset is shown below:
TLV-Type TLV-Type
15 15
TLV-Length TLV-Length
6 octets 6 octets
Data Type Data Type
The attribute PSID-offset is of type integer (Section 3.1 The attribute PSID-Offset is of type integer (Section 3.1
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
Contains the PSID-Offset (8-bits) right Contains the PSID-Offset (8-bits) right
justified, and the unused bits in this field MUST justified, and the unused bits in this field MUST
be set to zero. This field that specifies the be set to zero. This field that specifies the
numeric value for the Softwire46 algorithm's excluded numeric value for the Softwire46 algorithm's excluded
port range/offset bits (a bits), as per Section 5.1 port range/offset bits (a bits), as per Section 5.1
of RFC7597. Allowed values are between 0 and 15. of [RFC7597]. Allowed values are between 0 and 15.
Default values for this field are specific to the Default values for this field are specific to the
Softwire mechanism being implemented and are defined Softwire mechanism being implemented and are defined
in the relevant specification document. in the relevant specification document.
3.1.6.2. PSID-len Attribute 3.1.6.2. PSID-Len Attribute
This attribute is used to convey the PSID length as defined in This attribute is used to convey the PSID length as defined in
[RFC7597]. This attribute is encoded 32 bits as per the [RFC7597]. This attribute is encoded in 32 bits as per the
recommendation in Appendix A.2.1 of [RFC6158]. recommendation in Appendix A.2.1 of [RFC6158].
The structure of PSID-len is shown below: The structure of PSID-Len is shown below:
TLV-Type TLV-Type
16 16
TLV-Length TLV-Length
6 octets 6 octets
Data Type Data Type
The attribute PSID-len is of type integer (Section 3.1 The attribute PSID-Len is of type integer (Section 3.1
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
Contains the PSID-len (8-bits) right Contains the PSID-len (8-bits) right
justified, and the unused bits in this field MUST justified, and the unused bits in this field MUST
be set to zero. This field specifies the number of be set to zero. This field specifies the number of
significant bits in the PSID field (also known as significant bits in the PSID field (also known as
'k'). When set to 0, the PSID field is to be ignored. 'k'). When set to 0, the PSID field is to be ignored.
After the first 'a' bits, there are k bits in the After the first 'a' bits, there are k bits in the
port number representing the value of the PSID. port number representing the value of the PSID.
Subsequently, the address sharing ratio would be Subsequently, the address sharing ratio would be
2^k. 2^k.
3.1.6.3. PSID Attribute 3.1.6.3. PSID Attribute
This attribute is used to convey the PSID as defined in [RFC7597]. This attribute is used to convey the PSID as defined in [RFC7597].
This attribute is encoded 32 bits as per the recommendation in This attribute is encoded in 32 bits as per the recommendation in
Appendix A.2.1 of [RFC6158]. Appendix A.2.1 of [RFC6158].
The structure of PSID is shown below: The structure of PSID is shown below:
TLV-Type TLV-Type
17 17
TLV-Length TLV-Length
6 octets 6 octets
Data Type Data Type
The attribute Bind-IPv6-Prefix is of type integer (Section 3.1 The attribute PSID is of type integer (Section 3.1
of [RFC8044]). of [RFC8044]).
TLV-Value TLV-Value
Contains the PSID (16-bits) right justified, and the unused bits Contains the PSID (16-bits) right justified, and the unused bits
in this field MUST be set to zero. in this field MUST be set to zero.
The PSID value algorithmically identifies a set of ports The PSID value algorithmically identifies a set of ports
assigned to a CE. The first k bits on the left of this assigned to a CE. The first k bits on the left of this
2-octet field is the PSID value. The remaining (16-k) bits 2-octet field is the PSID value. The remaining (16-k) bits
on the right are padding zeros. on the right are padding zeros.
3.2. Softwire46-Priority Attribute 3.2. Softwire46-Priority Attribute
The Softwire46-Priority Attribute includes an ordered list of The Softwire46-Priority Attribute includes an ordered list of
Softwire64 mechanisms allowing the client to prioritize which Softwire46 mechanisms allowing the client to prioritize which
mechanism to use, corresponding to OPTION_S46_PRIORITY defined in mechanism to use, corresponding to OPTION_S46_PRIORITY defined in
[RFC8026]. The following requirements apply: [RFC8026]. The following requirements apply:
The Softwire46-Priority Attribute MAY appear in an Access-Accept The Softwire46-Priority Attribute MAY appear in an Access-Accept
packet. It MAY also appear in an Access-Request packet. packet. It MAY also appear in an Access-Request packet.
The Softwire46-Priority Attribute MAY appear in a CoA-Request The Softwire46-Priority Attribute MAY appear in a CoA-Request
packet. packet.
The Softwire46-Priority Attribute MAY appear in an Accounting- The Softwire46-Priority Attribute MAY appear in an Accounting-
skipping to change at page 21, line 29 skipping to change at page 21, line 29
Softwire46 mechanisms are prioritized in the appearance order Softwire46 mechanisms are prioritized in the appearance order
of the in the Softwire46-Priority Attribute. of the in the Softwire46-Priority Attribute.
The Softwire46-Priority Attribute is associated with the following The Softwire46-Priority Attribute is associated with the following
identifier: 241.Extended-Type (TBD5). identifier: 241.Extended-Type (TBD5).
3.2.1. Softwire46-Option-Code 3.2.1. Softwire46-Option-Code
This attribute is used to convey an option code assigned to a This attribute is used to convey an option code assigned to a
Softwire64 mechanism [RFC8026]. This attribute is encoded 32 bits as Softwire46 mechanism [RFC8026]. This attribute is encoded in 32 bits
per the recommendation in Appendix A.2.1 of [RFC6158]. as per the recommendation in Appendix A.2.1 of [RFC6158].
The structure of Softwire46-Option-Code is shown below: The structure of Softwire46-Option-Code is shown below:
TLV-Type TLV-Type
18 18
TLV-Length TLV-Length
6 octets 6 octets
Data Type Data Type
skipping to change at page 22, line 18 skipping to change at page 22, line 18
used to synthesize multicast and unicast IPv4-embedded IPv6 addresses used to synthesize multicast and unicast IPv4-embedded IPv6 addresses
as per [RFC8114]. This attribute is of type "tlv" and contains as per [RFC8114]. This attribute is of type "tlv" and contains
additional TLVs. The following requirements apply: additional TLVs. The following requirements apply:
The BNG SHALL use the IPv6 prefixes returned in the RADIUS The BNG SHALL use the IPv6 prefixes returned in the RADIUS
Softwire46-Multicast Attribute to populate the DHCPv6 PREFIX64 Softwire46-Multicast Attribute to populate the DHCPv6 PREFIX64
Option [RFC8115]. Option [RFC8115].
This attribute MAY be used in Access-Request packets as a hint to This attribute MAY be used in Access-Request packets as a hint to
the RADIUS server. For example, if the BNG is pre-configured for the RADIUS server. For example, if the BNG is pre-configured for
Softwire46-Multicast, these prefixes MAY be inserted in the Softwire46-Multicast, these prefixes may be inserted in the
attribute. The RADIUS server MAY ignore the hint sent by the BNG, attribute. The RADIUS server MAY ignore the hint sent by the BNG,
and it MAY assign a different Softwire46-Multicast Attribute. and it MAY assign a different Softwire46-Multicast Attribute.
The Softwire46-Multicast Attribute MAY appear in an Access- The Softwire46-Multicast Attribute MAY appear in an Access-
Request, Access-Accept, CoA-Request, and Accounting-Request Request, Access-Accept, CoA-Request, and Accounting-Request
packet. 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.
skipping to change at page 23, line 42 skipping to change at page 23, line 42
identifier: 241.Extended-Type(TBD6). identifier: 241.Extended-Type(TBD6).
3.3.1. ASM-Prefix64 Attribute 3.3.1. ASM-Prefix64 Attribute
The ASM-Prefix64 attribute is structured as follows: The ASM-Prefix64 attribute is structured as follows:
TLV-Type TLV-Type
19 19
TLV-Length TLV-Length
16 octets. The length of ssm-prefix64 must be to 96 [RFC8115]. 16 octets. The length of asm-prefix64 must be to 96 [RFC8115].
Data Type Data Type
The attribute ASM-Prefix64 is of type ipv6prefix (Section 3.10 of The attribute ASM-Prefix64 is of type ipv6prefix (Section 3.10 of
[RFC8044]). [RFC8044]).
TLV-Value TLV-Value
This field specifies the IPv6 multicast prefix (asm-prefix64) This field specifies the IPv6 multicast prefix (asm-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 ASM mode. The conveyed multicast IPv6 multicast groups in the ASM mode. The conveyed multicast IPv6
prefix MUST belong to the ASM range. prefix MUST belong to the ASM range.
skipping to change at page 27, line 19 skipping to change at page 27, line 19
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
synchronized between the clients and the lwAFTR/BR. This can be synchronized between the clients and the Lightweight AFTR
achieved in two ways: static pre-configuration of the bindings on (lwAFTR)/BR. This can be achieved in two ways: static pre-
both the AAA server and lwAFTR, or on-demand whereby the AAA configuration of the bindings on both the AAA server and lwAFTR,
server updates the lwAFTR with the subscriber's binding state as or on-demand whereby the AAA server updates the lwAFTR with the
it is created or deleted. subscriber's binding state as it is created or deleted.
In some deployments, the DHCP server may use the Accounting-Request In some deployments, the DHCP server may use the Accounting-Request
to report to a AAA server the softwire configuration returned to a to report to a AAA server the softwire configuration returned to a
requesting host. It is the responsibility of the DHCP server to requesting host. It is the responsibility of the DHCP server to
ensure the consistency of the configuration provided to requesting ensure the consistency of the configuration provided to requesting
hosts. Reported data to a AAA server may be required for various hosts. Reported data to a AAA server may be required for various
operational purposes (e.g., regulatory). operational purposes (e.g., regulatory).
5. Table of Attributes 5. Table of Attributes
skipping to change at page 28, line 18 skipping to change at page 28, line 18
Configuration Configuration
0-1 0-1 0 0 0-1 0-1 241.TBD5 Softwire46- 0-1 0-1 0 0 0-1 0-1 241.TBD5 Softwire46-
Priority Priority
0-1 0-1 0 0 0-1 0-1 241.TBD6 Softwire46- 0-1 0-1 0 0 0-1 0-1 241.TBD6 Softwire46-
Multicast Multicast
Table 3: Table of Attributes Table 3: Table of Attributes
6. Security Considerations 6. Security Considerations
Known security vulnerabilities of the RADIUS protocol are discussed Section 9 of [RFC7596] discusses security issues related to
in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for Lightweight 4over6, Section 10 of [RFC7597] discusses security issues
providing security when RADIUS is carried in IPv6 is discussed in related to MAP-E, Section 13 of [RFC7599] discusses security issues
[RFC3162]. related to MAP-T, and Section 9 of [RFC8114] discusses security
issues related to the delivery of IPv4 multicast services to IPv4
clients over an IPv6 multicast network.
Specific security considerations for interactions between the MAP CE This document does not introduce any security issue other than the
and the BNG are discussed in [RFC7597] and [RFC7599]. Security ones already identified in RADIUS documents [RFC2865] and [RFC5176]
considerations for Lightweight 4over6 are discussed in [RFC7596]. for CoA messages. Known security vulnerabilities of the RADIUS
Security considerations for DHCPv6-Based Softwire46 Prioritization protocol discussed in [RFC2607], [RFC2865], and [RFC2869] apply to
Mechanism are discussed in [RFC8026]. Security considerations for this specification.
multicast scenarios are discussed in [RFC8114]. Furthermore, generic
DHCPv6 security mechanisms can be applied to DHCPv6 This document targets deployments where a trusted relationship is in
intercommunication between the CE and the BNG. place between the RADIUS client and server with communication
optionally secured by IPsec or Transport Layer Security (TLS)
[RFC6614]. The use of IPsec [RFC4301] for providing security when
RADIUS is carried in IPv6 is discussed in [RFC3162].
Security considerations for interactions between a Softwire46 CE and
the BNG are discussed in Section 9 of [RFC7598] (DHCPv6 options for
configuration of softwire46 address and port-mapped clients),
Section 3 of [RFC8026] (DHCPv6-based Softwire46 prioritization
mechanism), and Section 5 of [RFC8115] (DHCPv6 options for
configuration of IPv4-embedded IPv6 prefixes).
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. The
assignments should use the RADIUS registry available at
https://www.iana.org/assignments/radius-types/.
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
[RFC8126]. [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
skipping to change at page 29, line 27 skipping to change at page 30, line 11
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:
Value Description Data Type Reference Value Description Data Type Reference
----- ----------- --------- --------- ----- ----------- --------- ---------
0 Reserved 0 Reserved
1 Softwire46-MAP-E tlv Section 3.1.1.1 1 Softwire46-MAP-E tlv Section 3.1.1.1
2 Softwire46-MAP-T tlv Section 3.1.1.2 2 Softwire46-MAP-T tlv Section 3.1.1.2
3 Softwire46-Lightweight-4over6 tlv Section 3.1.1.3 3 Softwire46-Lightweight-4over6 tlv Section 3.1.1.3
4 Softwire46-Rule tlv Section 3.1.3.1 4 Softwire46-Rule (BMR) tlv Section 3.1.3.1
5 Softwire46-Rule tlv Section 3.1.3.1 5 Softwire46-Rule (FMR) tlv Section 3.1.3.1
6 Softwire46-BR ipv6addr Section 3.1.3.2 6 Softwire46-BR ipv6addr Section 3.1.3.2
7 Softwire46-DMR ipv6prefix Section 3.1.3.3 7 Softwire46-DMR ipv6prefix Section 3.1.3.3
8 Softwire46-V4V6Bind tlv Section 3.1.3.4 8 Softwire46-V4V6Bind tlv Section 3.1.3.4
9 Softwire46-PORTPARAMS tlv Section 3.1.3.5 9 Softwire46-PORTPARAMS tlv Section 3.1.3.5
10 Rule-IPv6-Prefix ipv6prefix Section 3.1.4.1 10 Rule-IPv6-Prefix ipv6prefix Section 3.1.4.1
11 Rule-IPv4-Prefix ipv4prefix Section 3.1.4.2 11 Rule-IPv4-Prefix ipv4prefix Section 3.1.4.2
12 EA-Length integer Section 3.1.4.3 12 EA-Length integer Section 3.1.4.3
13 IPv4-address ipv4addr Section 3.1.5.1 13 IPv4-Address ipv4addr Section 3.1.5.1
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 Softwire64-Option-Code integer Section 3.2.1 18 Softwire46-Option-Code integer Section 3.2.1
19 ASM-Prefix64 ipv6prefix Section 3.3.1 19 ASM-Prefix64 ipv6prefix Section 3.3.1
20 SSM-Prefix64 ipv6prefix Section 3.3.2 20 SSM-Prefix64 ipv6prefix Section 3.3.2
21 U-Prefix64 ipv6prefix Section 3.3.3 21 U-Prefix64 ipv6prefix Section 3.3.3
22-255 Unassigned 22-255 Unassigned
The registration procedure for this registry is Standards Action as The registration procedure for this registry is Standards Action as
defined in [RFC8126]. defined in [RFC8126].
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 conveys an ordered list of option
code field, for which IANA is requested to create and maintain a new codes assigned to Softwire46 mechanisms, for which IANA is requested
registry entitled "Option Codes Permitted in the Softwire46-Priority to create and maintain a new registry entitled "Option Codes
Attribute". The registration procedure for this registry is Permitted in the Softwire46-Priority Attribute".
Standards Action as defined in [RFC8126].
This document requests IANA to register the three option codes of the
Softwire46 mechanisms permitted to be included in the
Softwire46-Priority Attribute. The value of option code corresponds
to the TLV-Type defined in Section 3.1.1. Additional options may be
added to this list in the future using the IETF Review process
described in Section 4.8 of [RFC8126].
Table 4 shows the option codes required, and the Softwire46 Table 4 shows the initial version of allowed option codes, and the
mechanisms that they represent. The option code for DS-Lite is Softwire46 mechanisms that they represent. The option code for DS-
derived from the IANA allocated RADIUS Attribute Type value for DS- Lite is derived from the IANA allocated RADIUS Attribute Type value
Lite [RFC6519]. The option codes for MAP-E, MAP-T, and Lightweight for DS-Lite [RFC6519]. 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 are the TLV-Type values for the MAP-E, MAP-T, and
Lightweight 4over6 should also be used as the TLV-Type values for the Lightweight 4over6 attributes 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 | | 1 | MAP-E | RFC7597 |
| TBD3 | MAP-T | RFC7599 | | 2 | MAP-T | RFC7599 |
| TBD4 | Lightweight 4over6 | RFC7596 | | 3 | Lightweight 4over6 | RFC7596 |
| 144 | DS-Lite | RFC6519 | | 144 | DS-Lite | RFC6519 |
+--------------------------------+-----------+ +-----------+--------------------+-----------+
Table 4: Option Codes to S46 Mechanisms Table 4: Option Codes to S46 Mechanisms
Additional option codes may be added to this list in the future using
the IETF Review process described in Section 4.8 of [RFC8126].
8. Contributing Authors 8. Contributing Authors
Bing Liu
Huawei Technologies Co., Ltd
Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095
P.R. China
Email: leo.liubing@huawei.com
Peter Deacon
IEA Software, Inc.
P.O. Box 1170
Veradale, WA 99037
USA
Email: peterd@iea-software.com
Qiong Sun Qiong Sun
China Telecom China Telecom
Beijing China Beijing China
Email: sunqiong@ctbri.com.cn Email: sunqiong@ctbri.com.cn
Qi Sun Qi Sun
Tsinghua University Tsinghua University
Department of Computer Science, Tsinghua University Department of Computer Science, Tsinghua University
Beijing 100084 Beijing 100084
P.R.China P.R.China
Phone: +86-10-6278-5822 Phone: +86-10-6278-5822
Email: sunqibupt@gmail.com Email: sunqibupt@gmail.com
Cathy Zhou Cathy Zhou
Huawei Technologies Huawei Technologies
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 Shenzhen 518129
Email: cathy.zhou@huawei.com Email: cathy.zhou@huawei.com
Tina Tsou Tina Tsou
Huawei Technologies(USA) Huawei Technologies(USA)
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA USA
Email: Tina.Tsou.Zouting@huawei.com Email: Tina.Tsou.Zouting@huawei.com
ZiLong Liu ZiLong Liu
Tsinghua University Tsinghua University
Beijing 100084 Beijing 100084
P.R.China P.R.China
Phone: +86-10-6278-5822 Phone: +86-10-6278-5822
Email: liuzilong8266@126.com Email: liuzilong8266@126.com
Yong Cui Yong Cui
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, Stefan Winter, and Yu Tianpeng to this Meng, Cui Wang, Alan Dekok, Stefan Winter, and Yu Tianpeng to this
document. document.
This document was merged with draft-sun-softwire-lw4over6-radext-01 This document was merged with draft-sun-softwire-lw4over6-radext-01
skipping to change at page 32, line 11 skipping to change at page 32, line 47
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, Stefan Winter, and Yu Tianpeng to this Meng, Cui Wang, Alan Dekok, Stefan Winter, and Yu Tianpeng to this
document. 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].
Many thanks to Al Morton and Bernie Volz for the review. Many thanks to Al Morton, Bernie Volz, Joel Halpern, and Donald
Eastlake for the review.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 32, line 41 skipping to change at page 33, line 33
[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>.
[RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
Aboba, "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", RFC 5176,
DOI 10.17487/RFC5176, January 2008,
<https://www.rfc-editor.org/info/rfc5176>.
[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 33, line 19 skipping to change at page 34, line 14
[RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6 [RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6
Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Softwire Customer Premises Equipment (CPE): A DHCPv6-Based
Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026, Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026,
November 2016, <https://www.rfc-editor.org/info/rfc8026>. November 2016, <https://www.rfc-editor.org/info/rfc8026>.
[RFC8044] DeKok, A., "Data Types in RADIUS", RFC 8044, [RFC8044] DeKok, A., "Data Types in RADIUS", RFC 8044,
DOI 10.17487/RFC8044, January 2017, DOI 10.17487/RFC8044, January 2017,
<https://www.rfc-editor.org/info/rfc8044>. <https://www.rfc-editor.org/info/rfc8044>.
[RFC8114] Boucadair, M., Qin, C., Jacquenet, C., Lee, Y., and Q.
Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients
over an IPv6 Multicast Network", RFC 8114,
DOI 10.17487/RFC8114, March 2017,
<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 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
skipping to change at page 34, line 27 skipping to change at page 35, line 14
[RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to [RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to
the IPv4 Address Shortage", RFC 6346, the IPv4 Address Shortage", RFC 6346,
DOI 10.17487/RFC6346, August 2011, DOI 10.17487/RFC6346, August 2011,
<https://www.rfc-editor.org/info/rfc6346>. <https://www.rfc-editor.org/info/rfc6346>.
[RFC6519] Maglione, R. and A. Durand, "RADIUS Extensions for Dual- [RFC6519] Maglione, R. and A. Durand, "RADIUS Extensions for Dual-
Stack Lite", RFC 6519, DOI 10.17487/RFC6519, February Stack Lite", RFC 6519, DOI 10.17487/RFC6519, February
2012, <https://www.rfc-editor.org/info/rfc6519>. 2012, <https://www.rfc-editor.org/info/rfc6519>.
[RFC6614] Winter, S., McCauley, M., Venaas, S., and K. Wierenga,
"Transport Layer Security (TLS) Encryption for RADIUS",
RFC 6614, DOI 10.17487/RFC6614, May 2012,
<https://www.rfc-editor.org/info/rfc6614>.
[RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. [RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I.
Farrer, "Lightweight 4over6: An Extension to the Dual- Farrer, "Lightweight 4over6: An Extension to the Dual-
Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596, Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596,
July 2015, <https://www.rfc-editor.org/info/rfc7596>. July 2015, <https://www.rfc-editor.org/info/rfc7596>.
[RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., [RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, Ed., "Mapping of Address and Murakami, T., and T. Taylor, Ed., "Mapping of Address and
Port with Encapsulation (MAP-E)", RFC 7597, Port with Encapsulation (MAP-E)", RFC 7597,
DOI 10.17487/RFC7597, July 2015, DOI 10.17487/RFC7597, July 2015,
<https://www.rfc-editor.org/info/rfc7597>. <https://www.rfc-editor.org/info/rfc7597>.
skipping to change at page 35, line 5 skipping to change at page 35, line 45
[RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S., [RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S.,
and T. Murakami, "Mapping of Address and Port using and T. Murakami, "Mapping of Address and Port using
Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July
2015, <https://www.rfc-editor.org/info/rfc7599>. 2015, <https://www.rfc-editor.org/info/rfc7599>.
[RFC7991] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", [RFC7991] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary",
RFC 7991, DOI 10.17487/RFC7991, December 2016, RFC 7991, DOI 10.17487/RFC7991, December 2016,
<https://www.rfc-editor.org/info/rfc7991>. <https://www.rfc-editor.org/info/rfc7991>.
[RFC8114] Boucadair, M., Qin, C., Jacquenet, C., Lee, Y., and Q.
Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients
over an IPv6 Multicast Network", RFC 8114,
DOI 10.17487/RFC8114, March 2017,
<https://www.rfc-editor.org/info/rfc8114>.
Appendix A. DHCPv6 to RADIUS Field Mappings Appendix A. DHCPv6 to RADIUS Field Mappings
The following sections detail the mappings between the softwire The following sections detail the mappings between the softwire
DHCPv6 option fields and the relevant RADIUS attributes as defined in DHCPv6 option fields and the relevant RADIUS attributes as defined in
this document. this document.
A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field Mappings A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field Mappings
+---------------------+----------------------+----------------------+ +---------------------+----------------------+----------------------+
| OPTION_S46_RULE | Softwire46-Rule Name | TLV Subfield | | OPTION_S46_RULE | Softwire46-Rule Name | TLV Subfield |
skipping to change at page 35, line 49 skipping to change at page 36, line 49
| dmr-prefix6-len | dmr-prefix6-len | | dmr-prefix6-len | dmr-prefix6-len |
| dmr-ipv6-prefix | dmr-ipv6-prefix | | dmr-ipv6-prefix | dmr-ipv6-prefix |
+---------------------+-------------------------+ +---------------------+-------------------------+
A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind
+-----------------------+------------------------+------------------+ +-----------------------+------------------------+------------------+
| OPTION_S46_V4V6BIND | Softwire46-V4V6Bind | TLV Subfield | | OPTION_S46_V4V6BIND | Softwire46-V4V6Bind | TLV Subfield |
| Field | Name | | | Field | Name | |
+-----------------------+------------------------+------------------+ +-----------------------+------------------------+------------------+
| ipv4-address | IPv4-address | ipv4-address | | ipv4-address | IPv4-Address | ipv4-address |
| bindprefix6-len | Bind-IPv6-Prefix | Prefix-Length | | bindprefix6-len | Bind-IPv6-Prefix | Prefix-Length |
| bind-ipv6-prefix | Bind-IPv6-Prefix | bind-ipv6-prefix | | bind-ipv6-prefix | Bind-IPv6-Prefix | bind-ipv6-prefix |
+-----------------------+------------------------+------------------+ +-----------------------+------------------------+------------------+
A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field Mappings A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field Mappings
+--------------------------+--------------------------+-------------+ +--------------------------+--------------------------+-------------+
| OPTION_S46_PORTPARAMS | Softwire46-PORTPARAMS | TLV | | OPTION_S46_PORTPARAMS | Softwire46-PORTPARAMS | TLV |
| Field | Name | Subfield | | Field | Name | Subfield |
+--------------------------+--------------------------+-------------+ +--------------------------+--------------------------+-------------+
| offset | PSID-offset | PSID-Offset | | offset | PSID-Offset | PSID-Offset |
| PSID-len | PSID-len | PSID-len | | PSID-len | PSID-Len | PSID-len |
| PSID | PSID | PSID | | PSID | PSID | PSID |
+--------------------------+--------------------------+-------------+ +--------------------------+--------------------------+-------------+
A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field Mappings A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field Mappings
+---------------------------+---------------------------------------+ +---------------------------+---------------------------------------+
| OPTION_S46_PRIORITY Field | Softwire46-Priority Attribute | | OPTION_S46_PRIORITY Field | Softwire46-Priority Attribute |
| | Subfield | | | Subfield |
+---------------------------+---------------------------------------+ +---------------------------+---------------------------------------+
| s46-option-code | Softwire46-option-code | | s46-option-code | Softwire46-option-code |
skipping to change at page 37, line 12 skipping to change at page 38, line 12
Email: jiangsheng@huawei.com Email: jiangsheng@huawei.com
Yu Fu Yu Fu
CNNIC CNNIC
No.4 South 4th Street, Zhongguancun No.4 South 4th Street, Zhongguancun
Hai-Dian District, Beijing, 100190 Hai-Dian District, Beijing, 100190
P.R. China P.R. China
Email: eleven711711@foxmail.com Email: eleven711711@foxmail.com
Bing Liu
Huawei Technologies Co., Ltd
Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095
P.R. China
Email: leo.liubing@huawei.com
Peter Deacon
IEA Software, Inc.
P.O. Box 1170
Veradale, WA 99037
USA
Email: peterd@iea-software.com
Chongfeng Xie Chongfeng Xie
China Telecom China Telecom
Beijing Beijing
P.R. China P.R. China
Email: xiechf.bri@chinatelecom.cn Email: xiechf.bri@chinatelecom.cn
Tianxiang Li Tianxiang Li
Tsinghua University Tsinghua University
Beijing 100084 Beijing 100084
 End of changes. 98 change blocks. 
175 lines changed or deleted 198 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/