draft-ietf-softwire-map-radius-17.txt   draft-ietf-softwire-map-radius-18.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: May 11, 2019 CNNIC Expires: July 25, 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
November 7, 2018 January 21, 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-17 draft-ietf-softwire-map-radius-18
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,
Authorization, and Accounting server which utilizes the RADIUS Authorization, and Accounting server which utilizes the RADIUS
protocol to provide centralized management for users. When a new protocol to provide centralized management for users. When a new
transition mechanism is developed, new RADIUS attributes need to be transition mechanism is developed, new RADIUS attributes need to be
defined correspondingly. defined correspondingly.
This document defines three new RADIUS attributes to carry Address This document defines new RADIUS attributes to carry Address plus
plus Port based softwire configuration parameters from an Port based softwire configuration parameters from an Authentication,
Authentication, Authorization, and Accounting server to a Broadband Authorization, and Accounting server to a Broadband Network Gateway.
Network Gateway. Both unicast and multicast attributes are covered. Both unicast and multicast attributes are covered.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 May 11, 2019. This Internet-Draft will expire on July 25, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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. Extensions of RADIUS Attributes and TLVs . . . . . . . . . . 6 3. New RADIUS Attributes . . . . . . . . . . . . . . . . . . . . 6
3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6 3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 7
3.1.1. Softwire46 TLVs . . . . . . . . . . . . . . . . . . . 8 3.1.1. Softwire46 Attributes . . . . . . . . . . . . . . . . 8
3.1.1.1. S46-MAP-E TLV Format . . . . . . . . . . . . . . 10 3.1.1.1. Softwire46-MAP-E Attribute . . . . . . . . . . . 10
3.1.1.2. S46-MAP-T TLV Format . . . . . . . . . . . . . . 11 3.1.1.2. Softwire46-MAP-T Attribute . . . . . . . . . . . 10
3.1.1.3. S46-Lightweight-4over6 TLV Format . . . . . . . . 12 3.1.1.3. Softwire46-Lightweight-4over6 Attribute . . . . . 11
3.1.2. Softwire46 Sub-TLVs . . . . . . . . . . . . . . . . . 13 3.1.2. Softwire46 Sub-Attributes . . . . . . . . . . . . . . 11
3.1.3. Format of the Softwire46 Sub-TLVs . . . . . . . . . . 14 3.1.3. Specification of the Softwire46 Sub-Attributes . . . 12
3.1.3.1. S46-Rule Sub-TLV . . . . . . . . . . . . . . . . 14 3.1.3.1. Softwire46-Rule Attribute . . . . . . . . . . . . 12
3.1.3.2. S46-BR Sub-TLV . . . . . . . . . . . . . . . . . 15 3.1.3.2. Softwire46-BR Attribute . . . . . . . . . . . . . 13
3.1.3.3. S46-DMR Sub-TLV . . . . . . . . . . . . . . . . . 16 3.1.3.3. Softwire46-DMR Attribute . . . . . . . . . . . . 14
3.1.3.4. S46-V4V6Bind Sub-TLV . . . . . . . . . . . . . . 17 3.1.3.4. Softwire46-V4V6Bind Attribute . . . . . . . . . . 14
3.1.3.5. S46-PORTPARAMS Sub-TLV . . . . . . . . . . . . . 18 3.1.3.5. Softwire46-PORTPARAMS Attribute . . . . . . . . . 15
3.1.4. Sub-TLVs for S46-Rule Sub-TLV . . . . . . . . . . . . 19 3.1.4. Sub-Attributes for Sofwtire46-Rule . . . . . . . . . 16
3.1.4.1. Rule-IPv6-Prefix Sub-TLV . . . . . . . . . . . . 19 3.1.4.1. Rule-IPv6-Prefix Attribute . . . . . . . . . . . 16
3.1.4.2. Rule-IPv4-Prefix Sub-TLV . . . . . . . . . . . . 20 3.1.4.2. Rule-IPv4-Prefix Attribute . . . . . . . . . . . 17
3.1.4.3. EA-Length Sub-TLV . . . . . . . . . . . . . . . . 21 3.1.4.3. EA-Length Attribute . . . . . . . . . . . . . . . 17
3.1.5. Sub-TLVs for S46-v4v6Bind Sub-TLV . . . . . . . . . . 22 3.1.5. Attributes for Softwire46-v4v6Bind . . . . . . . . . 18
3.1.5.1. The IPv4-address Sub-TLV . . . . . . . . . . . . 22 3.1.5.1. IPv4-address Attribute . . . . . . . . . . . . . 18
3.1.5.2. The Bind-IPv6-Prefix Sub-TLV . . . . . . . . . . 22 3.1.5.2. Bind-IPv6-Prefix Attribute . . . . . . . . . . . 18
3.1.6. Sub-TLVs for S46-PORTPARAMS Sub-TLV . . . . . . . . . 23 3.1.6. Attributes for S46-PORTPARAMS . . . . . . . . . . . . 19
3.1.6.1. The PSID-offset Sub-TLV . . . . . . . . . . . . . 23 3.1.6.1. PSID-offset Attribute . . . . . . . . . . . . . . 19
3.1.6.2. The PSID-len Sub-TLV . . . . . . . . . . . . . . 24 3.1.6.2. PSID-len Attribute . . . . . . . . . . . . . . . 20
3.1.6.3. The PSID Sub-TLV . . . . . . . . . . . . . . . . 25 3.1.6.3. PSID Attribute . . . . . . . . . . . . . . . . . 20
3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 25 3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 21
3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 26 3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22
3.3.1. ASM-Prefix64 TLV . . . . . . . . . . . . . . . . . . 28 3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 24
3.3.2. SSM-Prefix64 TLV . . . . . . . . . . . . . . . . . . 29 3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 25
3.3.3. U-Prefix64 TLV . . . . . . . . . . . . . . . . . . . 30 3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 25
4. A Sample Configuration Process with RADIUS . . . . . . . . . 31 4. A Sample Configuration Process with RADIUS . . . . . . . . . 25
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 34 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 28
6. Security Considerations . . . . . . . . . . . . . . . . . . . 35 6. Security Considerations . . . . . . . . . . . . . . . . . . . 29
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 35 7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 29
7.2. New RADIUS TLVs . . . . . . . . . . . . . . . . . . . . . 36 7.2. RADIUS Softwire46 Configuration and Multicast Attributes 30
7.3. S46 Mechanisms and Their Identifying Option Codes . . . . 36 7.3. Softwire46 Mechanisms and Their Identifying Option Codes 30
8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 37 8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 31
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.1. Normative References . . . . . . . . . . . . . . . . . . 39 10.1. Normative References . . . . . . . . . . . . . . . . . . 33
10.2. Informative References . . . . . . . . . . . . . . . . . 40 10.2. Informative References . . . . . . . . . . . . . . . . . 34
Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 42 Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 35
A.1. OPTION_S46_RULE (89) to S46-Rule Sub-TLV Field Mappings . 42 A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field
A.2. OPTION_S46_BR (90) to S46-BR Sub-TLV Sub-TLV Field Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 42 A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings . . . 36
A.3. OPTION_S46_DMR (91) to S46-DMR Sub-TLV . . . . . . . . . 42 A.3. OPTION_S46_DMR (91) to Softwire46-DMR . . . . . . . . . . 36
A.4. OPTION_S46_V4V6BIND (92) to S46-V4V6Bind Sub-TLV . . . . 42 A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind . . . . . 36
A.5. OPTION_S46_PORTPARAMS (93) to S46-PORTPARAMS Sub-TLV A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field
Field Mappings . . . . . . . . . . . . . . . . . . . . . 43 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36
A.6. OPTION_S46_PRIORITY (111) to S46-PORTPARAMS Sub-TLV Field A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 43 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 37
A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast
Attribute TLV Field Mappings . . . . . . . . . . . . . . 43 Attribute Field Mappings . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 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 37 skipping to change at page 4, line 37
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/sub-TLVs defined in this document have The contents of the attributes defined in this document have a 1:1
a 1:1 mapping into the fields of the various DHCPv6 options in mapping into the fields of the various DHCPv6 options in [RFC7598],
[RFC7598], [RFC8026], and [RFC8115]. Table 1 shows how the DHCPv6 [RFC8026], and [RFC8115]. Table 1 shows how the DHCPv6 options map
options map to the corresponding RADIUS attribute, or Sub-TLV. For to the corresponding RADIUS attribute. For detailed mappings between
detailed mappings between each DHCPv6 option field and the each DHCPv6 option field and the corresponding RADIUS Attribute or
corresponding RAIDUS Attribute, TLV, or Sub-TLV field, see field, see Appendix A.
Appendix A.
+----------------------------+--------------------------------+ +----------------------------+--------------------------------+
| DHCPv6 Option | RADIUS Attribute/Sub-TLV | | DHCPv6 Option | RADIUS Attribute |
+----------------------------+--------------------------------+ +----------------------------+--------------------------------+
| OPTION_S46_RULE (89) | S46-Rule Sub-TLV | | OPTION_S46_RULE (89) | Softwire46-Rule |
| OPTION_S46_BR (90) | S46-BR Sub-TLV | | OPTION_S46_BR (90) | Softwire46-BR |
| OPTION_S46_DMR (91) | S46-DMR Sub-TLV | | OPTION_S46_DMR (91) | Softwire46-DMR |
| OPTION_S46_V4V6BIND (92) | S46-v4v6Bind Sub-TLV | | OPTION_S46_V4V6BIND (92) | Softwire46-v4v6Bind |
| OPTION_S46_PORTPARAMS (93) | S46-PORTPARAMS Sub-TLV | | OPTION_S46_PORTPARAMS (93) | Softwire46-PORTPARAMS |
| OPTION_S46_PRIORITY (111) | Softwire46-Priority Attribute | | OPTION_S46_PRIORITY (111) | Softwire46-Priority Attribute |
| OPTION_V6_PREFIX64 (113) | Softwire46-Multicast Attribute | | OPTION_V6_PREFIX64 (113) | Softwire46-Multicast Attribute |
+----------------------------+--------------------------------+ +----------------------------+--------------------------------+
Table 1: Mapping between DHCPv6 Options and RADIUS Attributes/TLVs 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",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119] [RFC8174] when, and only when, they appear in all capitals, [RFC2119] [RFC8174] when, and only when, they appear in all capitals,
as shown here. as shown here.
The reader should be familiar with the concepts and terms defined in The reader should be familiar with the concepts and terms defined in
[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].
S46 is used throughout to denote any of the IPv4-in-IPv6 softwire Softwire46 (S46) is used throughout to denote any of the IPv4-in-IPv6
mechanisms listed above. Additionally, the following abbrevitiaons softwire mechanisms listed above. Additionally, the following
are used within the document: abbreviations are used within the document:
o BMR: Basic Mapping Rule 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
skipping to change at page 6, line 14 skipping to change at page 6, line 14
o FMR: Forwarding Mapping Rule 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. Extensions of RADIUS Attributes and TLVs 3. New RADIUS Attributes
This section defines the following attributes: This section defines the following attributes:
1. Softwire46-Configuration Attribute (Section 3.1): 1. Softwire46-Configuration Attribute (Section 3.1):
This attribute carries the configuration information for MAP-E, This attribute carries the configuration information for MAP-E,
MAP-T, and Lightweight 4over6. The configuration information for MAP-T, and Lightweight 4over6. The configuration information for
each S46 mechanism is carried in the corresponding Softwire46 each Softwire46 mechanism is carried in the corresponding
TLVs. Different Sub-TLVs are required for each type of Softwire46 attributes. Different attributes are required for
Softwire46 TLVs. each Softwire46 mechanism.
2. Softwire46-Priority Attribute (Section 3.2): 2. Softwire46-Priority Attribute (Section 3.2):
Depending on the deployment scenario, a client may support Depending on the deployment scenario, a client may support
several different S46 mechanisms and so request configuration for several different Softwire46 mechanisms and so request
more than one S46 mechanism at a time. The Softwire46-Priority configuration for more than one Softwire46 mechanism at a time.
Attribute contains information allowing the client to prioritize The Softwire46-Priority Attribute contains information allowing
which mechanism to use, corresponding to OPTION_S46_PRIORITY the client to prioritize which mechanism to use, corresponding to
defined in [RFC8026]. OPTION_S46_PRIORITY defined in [RFC8026].
3. Softwire46-Multicast Attribute (Section 3.3): 3. Softwire46-Multicast Attribute (Section 3.3):
This attribute conveys the IPv6 prefixes to be used in [RFC8114] This attribute conveys the IPv6 prefixes to be used in [RFC8114]
to synthesize IPv4-embedded IPv6 addresses. The BNG uses the to synthesize IPv4-embedded IPv6 addresses. The BNG uses the
IPv6 prefixes returned in the RADIUS Softwire46-Multicast IPv6 prefixes returned in the RADIUS Softwire46-Multicast
Attribute to populate the DHCPv6 PREFIX64 Option [RFC8115]. Attribute to populate the DHCPv6 PREFIX64 Option [RFC8115].
All of these attributes are allocated from the RADIUS "Extended Type" All of these attributes are allocated from the RADIUS "Extended Type"
code space per [RFC6929]. code space per [RFC6929].
All of these attribute designs follow [RFC6158] and [RFC6929]. All of these attribute designs follow [RFC6158] and [RFC6929].
This document adheres to [RFC8044] for defining the new attributes.
3.1. Softwire46-Configuration Attribute 3.1. Softwire46-Configuration Attribute
This attribute is of type "TLV", as defined in the RADIUS Protocol This attribute is of type "tlv", as defined in the RADIUS Protocol
Extensions [RFC6929]. It contains some sub-attributes, with the Extensions [RFC6929]. It contains some sub-attributes, with the
following requirements: following requirements:
The Softwire46-Configuration Attribute MUST contain one or more of The Softwire46-Configuration Attribute MUST contain one or more of
the following: S46-MAP-E TLV, S46-MAP-T TLV, and/or S46- the following attributes: Softwire46-MAP-E, Softwire46-MAP-T, and/
Lightweight-4over6 TLV. 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.
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.
The Softwire46-Configuration Attribute MUST only encapsulate one The Softwire46-Configuration Attribute MUST only encapsulate one
or more of the Softwire46 TLVs defined in this document. or more of the Softwire46 attributes defined in this document.
The Softwire46-Configuration Attribute is structured as follows: The Softwire46-Configuration Attribute is structured as follows:
0 1 2 3 Type
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 241 (To be confirmed by IANA).
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Extended-Type | Value ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
241 (To be confirmed by IANA).
Length Length
Indicates the total length, in bytes, of all fields of Indicates the total length, in bytes, of all fields of
this attribute, including the Type, Length, Extended-Type, this attribute, including the Type, Length, Extended-Type,
and the entire length of the embedded TLVs. and the entire length of the embedded attributes.
Extended-Type Extended-Type
TBD1 TBD1
Value Value
Contains one or more of the following TLVs. Each TLV type Contains one or more of the following attributes. Each attribute
may appear at most once: type may appear at most once:
S46-MAP-E TLV Softwire46-MAP-E
For configuring MAP-E clients. For the construction of For configuring MAP-E clients. For the construction of
this TLV, Refer to Section 3.1.1.1. this attribute, Refer to Section 3.1.1.1.
S46-MAP-T TLV Softwire46-MAP-T
For configuring MAP-T clients. For the construction of For configuring MAP-T clients. For the construction of
this TLV, Refer to Section 3.1.1.2. this attribute, Refer to Section 3.1.1.2.
S46-Lightweight-4over6 TLV Softwire46-Lightweight-4over6
For configuring Lightweight 4over6 clients. For the For configuring Lightweight 4over6 clients. For the
construction of this TLV, 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 TLVs 3.1.1. Softwire46 Attributes
The Softwire46 TLVs 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 TLV mechanism at a time. There MUST be at least one Softwire46 attribute
encapsulated in one Softwire46-Configuration Attribute. There MUST encapsulated in one Softwire46-Configuration Attribute. There MUST
be at most one instance of each type of Softwire46 TLV encapsulated be at most one instance of each type of Softwire46 attribute
in one Softwire46-Configuration Attribute. encapsulated in one Softwire46-Configuration Attribute.
There are three types of Softwire46 TLV, namely:
1. S46-MAP-E TLV (Section 3.1.1.1) There are three types of Softwire46 attributes, namely:
2. S46-MAP-T TLV (Section 3.1.1.2) 1. Softwire46-MAP-E (Section 3.1.1.1)
3. S46-Lightweight 4over6 TLV (Section 3.1.1.3) 2. Softwire46-MAP-T (Section 3.1.1.2)
Each type of Softwire46 TLV contains a number of sub-TLVs, defined in 3. Softwire46-Lightweight 4over6 (Section 3.1.1.3)
Section 3.1.3. The hierarchy of the Softwire46 TLVs is shown in Each type of Softwire46 attribute contains a number of sub-
Figure 1. Section 3.1.2 describes which Sub-TLVs are mandatory, attributes, defined in Section 3.1.3. The hierarchy of the
optional, or not permitted for each defined Softwire46 TLV. Softwire46 attributes is shown in Figure 1. Section 3.1.2 describes
which sub-attributes are mandatory, optional, or not permitted for
each defined Softwire46 attribute.
/1.Rule-IPv6-Prefix /1.Rule-IPv6-Prefix
S / | Sub-TLV S / |
o / | 1.S46-Rule Sub-TLV ----+ 2.Rule-IPv4-Prefix o / | 1.Softwire46-Rule -----+ 2.Rule-IPv4-Prefix
f | S46-MAP-E TLV-----+ | Sub-TLV f | Softwire46-MAP-E--+ |
t | | 2.S46-BR Sub-TLV | 3.EA Length Sub- t | | 2.Softwire46-BR | 3.EA Length
w | | \ TLV w | | \
i | | /1.PSID-offset i | | /1.PSID-offset
r | | | Sub-TLV r | | |
e | | 5.S46-PORTPARAMS Sub-TLV ----+ 2.PSID-len e | | 5.Softwire46-PORTPARAMS -----+ 2.PSID-len
- | \ | Sub-TLV - | \ |
C | | 3.PSID Sub- C | | 3.PSID
o | \ TLV o | \
n | n |
f | /1.Rule-IPv6-Prefix f | /1.Rule-IPv6-Prefix
i | / | Sub-TLV i | / |
g | | 1.S46-Rule Sub-TLV ----+ 2.Rule-IPv4-Prefix g | | 1.Softwire46-Rule------+ 2.Rule-IPv4-Prefix
u | S46-MAP-T TLV ----+ | Sub-TLV u | Softwire46-MAP-T--+ |
r | | 3.S46-DMR Sub-TLV | 3.EA Length Sub- r | | 3.Softwire46-DMR | 3.EA Length
a | | \ TLV a | | \
t | | /1.PSID-offset t | | /1.PSID-offset
i | | | Sub-TLV i | | |
o | | 5.S46-PORTPARAMS Sub-TLV ----+ 2.PSID-len o | | 5.Softwire46-PORTPARAMS------+ 2.PSID-len
n | \ | Sub-TLV n | \ |
| | 3.PSID Sub- | | 3.PSID
A | \ TLV A | \
t | t |
t | /1.IPv4-address t | /1.IPv4-address
r | / | Sub-TLV r | / |
i | | 4.S46-v4v6Bind Sub-TLV ----+ 2.Bind-IPv6-Prefix i | | 4.Softwire46-v4v6Bind -----+ 2.Bind-IPv6-Prefix
b | S46-Lightweight | \ Sub-TLV b | Softwire46- | \
u | -4over6 TLV ------+ /1.PSID-offset u | Lightweight-4over6+ /1.PSID-offset
t \ | | Sub-TLV t \ | |
e | 5.S46-PORTPARAMS Sub-TLV ----+ 2.PSID-len e | 5.Softwire46-PORTPARAMS ----+ 2.PSID-len
\ | Sub-TLV \ |
| 3.PSID Sub- | 3.PSID
\ TLV \
Figure 1: Softwire46 TLV Hierarchy
3.1.1.1. S46-MAP-E TLV Format
The format of the S46-MAP-E TLV is shown below:
0 1 2 3 Figure 1: Softwire46 Attributes Hierarchy
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | TLV-Value ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type 3.1.1.1. Softwire46-MAP-E Attribute
TBD2
TLV-Length Softwire46-MAP-E attribute is designed for carrying the configuration
One octet long. Indicates the length of this TLV, including information for MAP-E. The structure of the Softwire46-MAP-E is
the TLV-Type, TLV-Length, and TLV-Value fields. shown below:
TLV-Value TLV-Type
Contains a set of Sub-TLVs, with the following requirements: 1
It MUST contain the S46-Rule Sub-TLV, defined in Section 3.1.3.1. TLV-Length
Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields.
It MUST contain the S46-BR Sub-TLV, defined in Section 3.1.3.2. TLV-Value
Contains a set of sub-attributes, with the following requirements:
It MAY contain the S46-PORTPARAMS Sub-TLV, defined in It MUST contain the Softwire46-Rule, defined in Section 3.1.3.1.
Section 3.1.3.5.
3.1.1.2. S46-MAP-T TLV Format It MUST contain the Softwire46-BR, defined in Section 3.1.3.2.
The format of the S46-MAP-T TLV is shown below: It MAY contain the Softwire46-PORTPARAMS, defined in
Section 3.1.3.5.
0 1 2 3 3.1.1.2. Softwire46-MAP-T Attribute
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | TLV-Value ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type Softwire46-MAP-T attribute is designed for carrying the configuration
TBD3 information for MAP-T. The structure of the Softwire46-MAP-T is
shown below:
TLV-Length TLV-Type
One octet long. Indicates the length of this TLV, including 2
the TLV-Type, TLV-Length, and TLV-Value fields.
TLV-Value TLV-Length
Contains a set of Sub-TLVs, with the following requirements: Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields.
It MUST contain the S46-Rule Sub-TLV, defined in TLV-Value
Section 3.1.3.1. Contains a set of sub-attributes, with the following requirements:
It MUST contain the S46-DMR Sub-TLV, defined in It MUST contain the Softwire46-Rule, defined in
Section 3.1.3.3. Section 3.1.3.1.
It MAY contain the S46-PORTPARAMS Sub-TLV, defined in It MUST contain the Softwire46-DMR, defined in
Section 3.1.3.5. Section 3.1.3.3.
3.1.1.3. S46-Lightweight-4over6 TLV Format It MAY contain the Softwire46-PORTPARAMS, defined in
Section 3.1.3.5.
The format of the S46-Lightweight-4over6 TLV is shown below: 3.1.1.3. Softwire46-Lightweight-4over6 Attribute
0 1 2 3 Softwire46-Lightweight-4over6 attribute is designed for carrying the
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 configuration information for Lightweight 4over6. The structure of
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ the Softwire46-Lightweight-4over6 is shown below:
| TLV-Type | TLV-Length | TLV-Value ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Type
TBD4 3
TLV-Length TLV-Length
One octet long. Indicates the length of this TLV, 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-TLVs as follows: Contains a set of sub-attributes as follows:
It MUST contain the S46-BR Sub-TLV, defined in It MUST contain the Softwire46-BR, defined in
Section 3.1.3.2. Section 3.1.3.2.
It MUST contain the S46-V4V6Bind Sub-TLV, defined in It MUST contain the Softwire46-V4V6Bind, defined in
Section 3.1.3.4. Section 3.1.3.4.
It MAY contain the S46-PORTPARAMS Sub-TLV, defined in It MAY contain the Softwire46-PORTPARAMS, defined in
Section 3.1.3.5. Section 3.1.3.5.
3.1.2. Softwire46 Sub-TLVs 3.1.2. Softwire46 Sub-Attributes
Table 2 shows which encapsulated Sub-TLVs are mandatory, optional, or
not permitted for each defined Softwire46 TLV.
+----------------+-------+-------+--------------------+ Table 2 shows which encapsulated sub-attributes are mandatory,
| Sub-TLV | MAP-E | MAP-T | Lightweight 4over6 | optional, or not permitted for each defined Softwire46 attribute.
+----------------+-------+-------+--------------------+
| S46-BR | M | N/P | M |
| S46-Rule | M | M | N/P |
| S46-DMR | N/P | M | N/P |
| S46-V4V6Bind | N/P | N/P | M |
| S46-PORTPARAMS | O | O | O |
+----------------+-------+-------+--------------------+
M - Mandatory, O - Optional, N/P - Not Permitted +-----------------------+-------+-------+--------------------+
| Sub-Attributes | MAP-E | MAP-T | Lightweight 4over6 |
+-----------------------+-------+-------+--------------------+
| Softwire46-BR | 1 | 0 | 1 |
| Softwire46-Rule | 1 | 1 | 0 |
| Softwire46-DMR | 0 | 1 | 0 |
| Softwire46-V4V6Bind | 0 | 0 | 1 |
| Softwire46-PORTPARAMS | 0-1 | 0-1 | 0-1 |
+-----------------------+-------+-------+--------------------+
Table 2: Softwire46 Sub-TLVs Table 2: Softwire46 Sub-Attributes
3.1.3. Format of the Softwire46 Sub-TLVs The following table defines the meaning of the above table entries.
3.1.3.1. S46-Rule Sub-TLV 0 Not Permitted
0+ Optional, zero or more instances of the attribute
may be present.
0-1 Optional, zero or one instance of the attribute
may be present.
1 Mandatory
The S46-Rule Sub-TLV can only be encapsulated in the S46-MAP-E TLV 3.1.3. Specification of the Softwire46 Sub-Attributes
(Section 3.1.1.1) or the S46-MAP-T TLV (Section 3.1.1.2). Depending
on the deployment scenario, one Basic Mapping Rule (BMR) and zero or
more Forwarding Mapping Rules (RMRs) MUST be included in one
S46-MAP-E TLV or S46-MAP-T TLV.
Each type of S46-Rule Sub-TLV also contains a number of Sub-TLVs, 3.1.3.1. Softwire46-Rule Attribute
including Rule-IPv6-Prefix Sub-TLV, Rule-IPv4-Prefix Sub-TLV, and EA-
Length Sub-TLV. The structure of the Sub-TLVs for the S46-Rule Sub-
TLV is defined in Section 3.1.4.
Defining multiple TLV-types achieves the same design goals as the The Softwire46-Rule can only be encapsulated in the Softwire46-MAP-E
"S46 Rule Flags" defined in Section 4.1 of [RFC7598]. Using TLV-type (Section 3.1.1.1) or the Softwire46-MAP-T (Section 3.1.1.2).
set to 2 is equivalent to setting the F-flag in the OPTION_S46_RULE Depending on the deployment scenario, one Basic Mapping Rule (BMR)
S46 Rule Flags field. and zero or more Forwarding Mapping Rules (FMRs) MUST be included in
one Softwire46-MAP-E or Softwire46-MAP-T.
0 1 2 3 Each type of Softwire46-Rule also contains a number of sub-
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 attributes, including Rule-IPv6-Prefix, Rule-IPv4-Prefix, and EA-
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Length. The structure of the sub-attributes for the Softwire46-Rule
| TLV-Type | TLV-Length | TLV-Value ... . is defined in Section 3.1.4.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type Defining multiple TLV-types achieves the same design goals as the
TBD7 Basic Mapping Rule only (not to be used for forwarding) "Softwire46 Rule Flags" defined in Section 4.1 of [RFC7598]. Using
TBD8 Forwarding Premitted Mapping Rule (may be used for TLV-type set to 4 is equivalent to setting the F-flag in the
forwarding. Can also be a Basic Mapping Rule) OPTION_S46_RULE S46 Rule Flags field.
TLV-Length TLV-Type
One octet long. Indicates the length of this TLV, including 4 Basic Mapping Rule only (not to be used for forwarding)
the TLV-Type, TLV-Length, and TLV-Value fields. 5 Forwarding Permitted Mapping Rule (may be used for
forwarding. Can also be a Basic Mapping Rule)
TLV-Value TLV-Length
This field contains a set of TLVs as follows: Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields.
Rule-IPv6-Prefix Sub-TLV Data Type
This TLV contains the IPv6 prefix for use in the MAP rule. The attribute Softwire46-Rule is of type tlv (Section 3.13 of
Refer to Section 3.1.4.1. [RFC8044]).
Rule-IPv4-Prefix Sub-TLV TLV-Value
This TLV contains the IPv4 prefix for use in the MAP rule. This field contains a set of attributes as follows:
Refer to Section 3.1.4.2.
EA-Length Sub-TLV Rule-IPv6-Prefix
This TLV contains the Embedded-Address (EA) bit length. 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.
3.1.3.2. S46-BR Sub-TLV Rule-IPv4-Prefix
This attribute contains the IPv4 prefix for use in the MAP rule.
Refer to Section 3.1.4.2.
The S46-BR Sub-TLV can only be encapsulated in the S46-MAP-E TLV EA-Length
(Section 3.1.1.1) or S46-Lightweight-4over6 TLV (Section 3.1.1.3). This attribute contains the Embedded-Address (EA) bit length.
Refer to Section 3.1.4.1.
There MUST be at least one S46-BR Sub-TLV included in each S46-MAP-E 3.1.3.2. Softwire46-BR Attribute
TLV or S46-Lightweight-4over6 TLV.
The format of the S46-BR Sub-TLV is shown below: The Softwire46-BR can only be encapsulated in the Softwire46-MAP-E
(Section 3.1.1.1) or Softwire46-Lightweight-4over6 (Section 3.1.1.3).
0 1 2 3 There MUST be at least one Softwire46-BR included in each
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 Softwire46-MAP-E or Softwire46-Lightweight-4over6.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| br-ipv6-address |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type The structure of the Softwire46-BR is shown below:
TBD9
TLV-Length TLV-Type
18 octets 6
br-ipv6-address TLV-Length
IPv6 address. A fixed-length field of 16 octets that 18 octets
specifies the IPv6 address for the S46 Border Relay (BR).
3.1.3.3. S46-DMR Sub-TLV Data Type
The attribute Softwire46-BR is of type ip6addr (Section 3.9 of
[RFC8044]).
The S46-DMR Sub-TLV may only appear in the S46-MAP-T TLV TLV-Value
(Section 3.1.1.2). There MUST be exactly one S46-DMR Sub-TLV br-ipv6-address. A fixed-length field of 16 octets that
included in one S46-MAP-T TLV. specifies the IPv6 address for the Softwire46 Border Relay (BR).
The format of the S46-DMR Sub-TLV is shown below: 3.1.3.3. Softwire46-DMR Attribute
0 1 2 3 The Softwire46-DMR may only appear in the Softwire46-MAP-T
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 (Section 3.1.1.2). There MUST be exactly one Softwire46-DMR included
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ in one Softwire46-MAP-T.
| TLV-Type | TLV-Length | Reserved |dmr-prefix6-len|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dmr-ipv6-prefix |
. (variable length) .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type The structure of the Softwire46-DMR is shown below:
TBD10
TLV-Length TLV-Type
4 + length of dmr-ipv6-prefix specified in octets 7
Reserved TLV-Length
This field is reserved. It should be set to all zeros. 4 + length of dmr-ipv6-prefix specified in octets.
dmr-prefix6-len Data Type
8-bits long. Expresses the bitmask length of the IPv6 prefix The attribute Softwire46-DMR is of type ip6pref (Section 3.10 of
specified in the dmr-ipv6-prefix field. Allowed values range [RFC8044]).
from 0 to 96.
dmr-ipv6-prefix TLV-Value
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. divisible by 8. Prefixes with from 0 to 96 are allowed.
3.1.3.4. S46-V4V6Bind Sub-TLV 3.1.3.4. Softwire46-V4V6Bind Attribute
The S46-V4V6Bind Sub-TLV may only be encapsulated in the S46- The Softwire46-V4V6Bind may only be encapsulated in the Softwire46-
Lightweight-4over6 TLV (Section 3.1.1.3). There MUST be exactly one Lightweight-4over6 (Section 3.1.1.3). There MUST be exactly one
S46-V4V6Bind Sub-TLV included in each S46-Lightweight-4over6 TLV. Softwire46-V4V6Bind included in each Softwire46-Lightweight-4over6.
The format of the S46-V4V6Bind Sub-TLV is shown below: The structure of the Softwire46-V4V6Bind is shown below:
0 1 2 3 TLV-Type
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | TLV-Value ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Length
TBD11 Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields.
TLV-Length Data Type
8-bits long. Indicates the length of this TLV, including The attribute Softwire46-V4V6Bind is of type tlv (Section 3.13 of
the TLV-Type, TLV-Length, and TLV-Value fields. [RFC8044]).
TLV-Value TLV-Value
This field contains a set of Sub-TLVs as follows: This field contains a set of attributes as follows:
IPv4-address Sub-TLV IPv4-address
This TLV contains an IPv4 address, used to specify the full This attribute contains an IPv4 address, used to specify
or shared IPv4 address of the CE. Refer to Section 3.1.5.1. the full or shared IPv4 address of the CE. Refer to
Section 3.1.5.1.
Bind-IPv6-Prefix Sub-TLV Bind-IPv6-Prefix
This TLV contains an IPv6 prefix used to indicate which This attribute contains an IPv6 prefix used to indicate which
configured prefix the S46 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. S46-PORTPARAMS Sub-TLV 3.1.3.5. Softwire46-PORTPARAMS Attribute
The S46-PORTPARAMS Sub-TLV is optional. It is used to specify port The Softwire46-PORTPARAMS is optional. It is used to specify port
set information for IPv4 address sharing between clients. The set information for IPv4 address sharing between clients. The
S46-PORTPARAMS Sub-TLV MAY be included in any of the Softwire46 TLVs. Softwire46-PORTPARAMS MAY be included in any of the Softwire46
attributes.
The format of the S46-PORTPARAMS Sub-TLV is shown below:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | TLV-Value ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type
TBD12
TLV-Length
8-bits long. Indicates the length of this TLV, including
the TLV-Type, TLV-Length, and TLV-Value fields.
TLV-Value
This field contains a set of TLVs as follows:
PSID-offset Sub-TLV The structure of the Softwire46-PORTPARAMS is shown below:
This TLV specifies the numeric value for the S46 algorithm's
excluded port range/offset bits (a bits). Refer to
Section 3.1.6.1.
PSID-len Sub-TLV TLV-Type
This TLV specifies the number of significant bits in the 9
PSID field (also known as 'k'). Refer to Section 3.1.6.2.
PSID Sub-TLV TLV-Length
This TLV specifies PSID value. Refer to Section 3.1.6.3. Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields.
3.1.4. Sub-TLVs for S46-Rule Sub-TLV Data Type
The attribute Softwire46-PORTPARAMS is of type tlv (Section 3.13
of [RFC8044]).
There are two types of S46-Rule: the Basic Mapping Rule and the TLV-Value
Forwarding Mapping Rule, indicated by the value in the TLV-Type field This field contains a set of attributes as follows:
of the S46-Rule Sub-TLV (see Section 3.1.3.1).
Each type of S46-Rule Sub-TLV also contains a number of Sub-TLVs as PSID-offset
detailed in the following sub-sections. This attribute specifies the numeric value for the Softwire46
algorithm's excluded port range/offset bits (a bits). Refer to
Section 3.1.6.1.
3.1.4.1. Rule-IPv6-Prefix Sub-TLV PSID-len
This attribute specifies the number of significant bits in the
PSID field (also known as 'k'). Refer to Section 3.1.6.2.
The Rule-IPv6-Prefix Sub-TLV is REQUIRED for every S46-Rule Sub-TLV. PSID
There MUST be exactly one Rule-IPv6-Prefix Sub-TLV encapsulated in This attribute specifies PSID value. Refer to Section 3.1.6.3.
each type of S46-Rule Sub-TLV.
The Rule-IPv6-Prefix Sub-TLV follows the framed IPv6 prefix designed 3.1.4. Sub-Attributes for Sofwtire46-Rule
in [RFC3162] and [RFC8044].
The format of the Rule-IPv6-Prefix Sub-TLV is shown below: There are two types of Softwire46-Rule: the Basic Mapping Rule and
the Forwarding Mapping Rule, indicated by the value in the TLV-Type
field of the Softwire46-Rule (see Section 3.1.3.1).
0 1 2 3 Each type of Softwire46-Rule also contains a number of Sub-attributes
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 as detailed in the following sub-sections.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | Reserved |ruleprefix6-len|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| rule-ipv6-prefix |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type 3.1.4.1. Rule-IPv6-Prefix Attribute
TBD13
TLV-Length The Rule-IPv6-Prefix is REQUIRED for every Softwire46-Rule. There
20 MUST be exactly one Rule-IPv6-Prefix encapsulated in each type of
Softwire46-Rule.
Reserved The Rule-IPv6-Prefix follows the framed IPv6 prefix designed in
This field is reserved. It is always set to zero. This field [RFC3162] and [RFC8044].
is one octet in length.
Ruleprefix6-len The structure of the Rule-IPv6-Prefix is shown below:
The length of IPv6 prefix, specified in the rule-ipv6-prefix
field, expressed in bits.
rule-ipv6-prefix TLV-Type
IPv6 Prefix. 128-bits long field that specifying an IPv6 10
prefix appearing in the MAP rule.
3.1.4.2. Rule-IPv4-Prefix Sub-TLV TLV-Length
20 octets
This Sub-TLV is used to convey the MAP Rule IPv4 prefix. The format Data Type
of the Rule-IPv4-Prefix Sub-TLV is shown below: The attribute Rule-IPv6-Prefix is of type ipv6pref (Section 3.10
of [RFC8044]).
0 1 2 3 TLV-Value
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 rule-ipv6-prefix. 128-bits long field that specifies an IPv6
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ prefix appearing in the MAP rule.
| TLV-Type | TLV-Length | Reserved |ruleprefix4-len|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| rule-ipv4-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type 3.1.4.2. Rule-IPv4-Prefix Attribute
TBD14
TLV-Length This attribute is used to convey the MAP Rule IPv4 prefix. The
8 structure of the Rule-IPv4-Prefix is shown below:
Reserved TLV-Type
8-bits long. This field is reserved and is always set to 11
zero.
ruleprefix4-len TLV-Length
8-bits long. The length of IPv4 prefix specified in the 8 octets
rule-ipv4-prefix field, expressed in bits.
rule-ipv4-prefix Data Type
32-bits long. Specifies the IPv4 prefix appearing in the MAP The attribute Rule-IPv4-Prefix is of type ipv4pref (Section 3.11
rule. of [RFC8044]).
3.1.4.3. EA-Length Sub-TLV TLV-Value
rule-ipv4-prefix. 32-bits long. Specifies the IPv4 prefix
appearing in the MAP rule.
This Sub-TLV is used to convey the Embedded-Address(EA) bit length. 3.1.4.3. EA-Length Attribute
The format of the EA-Length Sub-TLV is shown below:
0 1 2 3 This attribute is used to convey the Embedded-Address(EA) bit length.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 The structure of the EA-Length is shown below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | EA-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Type
TBD15 12
TLV-Length TLV-Length
4 6 octets
EA-len Data Type
16-bits long. Specifies the Embedded-Address(EA) bit length. The attribute EA-Length is of type integer (Section 3.1 of
Allowed values range from 0 to 48. [RFC8044]).
3.1.5. Sub-TLVs for S46-v4v6Bind Sub-TLV TLV-Value
EA-len; 32-bits long. Specifies the Embedded-Address(EA) bit
length. Allowed values range from 0 to 48.
3.1.5.1. The IPv4-address Sub-TLV 3.1.5. Attributes for Softwire46-v4v6Bind
The IPv4-address Sub-TLV MAY be used to specify the full or shared 3.1.5.1. IPv4-address Attribute
IPv4 address of the CE.
The format of the IPv4-address Sub-TLV is shown below: The IPv4-address MAY be used to specify the full or shared IPv4
address of the CE.
0 1 2 3 The structure of the IPv4-address is shown below:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | ipv4-address .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Type
TBD16 13
TLV-Length TLV-Length
6 6 octets
ipv4-address
32-bits long. Specifies the IPv4 address to appear in the
S46-V4V6Bind Sub-TLV (Section 3.1.3.4).
3.1.5.2. The Bind-IPv6-Prefix Sub-TLV
The Bind-IPv6-Prefix Sub-TLV is used by the CE to identify the Data Type
correct IPv6 prefix to be used as the tunnel source. The attribute IPv4-address is of type ipv4addr (Section 3.8
of [RFC8044]).
The format of the Bind-IPv6-Prefix Sub-TLV is shown below: TLV-Value
32-bits long. Specifies the IPv4 address to appear in the
Softwire46-V4V6Bind (Section 3.1.3.4).
0 1 2 3 3.1.5.2. Bind-IPv6-Prefix Attribute
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | Reserved |bindprefix6-len|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| bind-ipv6-prefix |
| (variable length) |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type The Bind-IPv6-Prefix is used by the CE to identify the correct IPv6
TBD17 prefix to be used as the tunnel source.
TLV-Length The structure of the Bind-IPv6-Prefix is shown below:
4 + length of bind-ipv6-prefix specified in octets
Reserved TLV-Type
8-bits long. This field is reserved and is always set 14
to zero.
bindprefix6-len TLV-Length
8-bits long. Expresses the bitmask length of the IPv6 4 + length of bind-ipv6-prefix specified in octets.
prefix specified in the bind-ipv6-prefix field. Allowed
values range from 0 to 128.
bind-ipv6-prefix Data Type
IPv6 prefix. A variable-length field specifying the IPv6 The attribute Bind-IPv6-Prefix is of type ipv6pref (Section 3.10
prefix or address for the S46 CE. This field is of [RFC8044]).
right-padded with zeros to the nearest octet boundary
when bindprefix6-len is not divisible by 8.
3.1.6. Sub-TLVs for S46-PORTPARAMS Sub-TLV TLV-Value
bind-ipv6-prefix. A variable-length field specifying the IPv6
prefix or address for the Softwire46 CE. This field is
right-padded with zeros to the nearest octet boundary
when bindprefix6-len is not divisible by 8.
3.1.6.1. The PSID-offset Sub-TLV 3.1.6. Attributes for S46-PORTPARAMS
This Sub-TLV is used to convey the Port Set Identifier offset as 3.1.6.1. PSID-offset Attribute
defined in [RFC7597].
The format of the PSID-offset Sub-TLV is shown below: This attribute is used to convey the Port Set Identifier offset as
defined in [RFC7597]. This attribute is encoded 32 bits as per the
recommendation in Appendix A.2.1 of [RFC6158].
0 1 2 The structure of the PSID-offset is shown below:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | PSID-Offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Type
TBD18 15
TLV-Length TLV-Length
3 6 octets
PSID-Offset Data Type
Integer. An 8-bits long field that specifies the The attribute PSID-offset is of type integer (Section 3.1
numeric value for the S46 algorithm's excluded of [RFC8044]).
TLV-Value
Contains the PSID-Offset (8-bits) right
justified, and the unused bits in this field MUST
be set to zero. This field that specifies the
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. The PSID-len Sub-TLV 3.1.6.2. PSID-len Attribute
This Sub-TLV is used to convey the PSID length as defined in
[RFC7597].
The format of the PSID-len Sub-TLV is shown below: This attribute is used to convey the PSID length as defined in
[RFC7597]. This attribute is encoded 32 bits as per the
recommendation in Appendix A.2.1 of [RFC6158].
0 1 2 The structure of the PSID-len is shown below:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | PSID-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Type
TBD19 16
TLV-Length TLV-Length
3 6 octets
PSID-len Data Type
8-bits long field specifying the number of The attribute PSID-len is of type integer (Section 3.1
of [RFC8044]).
TLV-Value
Contains the PSID-len (8-bits) right
justified, and the unused bits in this field MUST
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. The PSID Sub-TLV 3.1.6.3. PSID Attribute
This Sub-TLV 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
Appendix A.2.1 of [RFC6158].
The format of the PSID Sub-TLV is shown below: The structure of the PSID is shown below:
0 1 2 3 TLV-Type
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 17
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | TLV-Length | PSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Length
TBD20 6 octets
TLV-Length Data Type
4 The attribute Bind-IPv6-Prefix is of type integer (Section 3.1
of [RFC8044]).
PSID (Port-set ID) TLV-Value
Integer. An explicit 16-bit (unsigned word) PSID value. Contains the PSID (16-bits) right justified, and the unused bits
The PSID value algorithmically identifies a set of ports in this field MUST be set to zero.
assigned to a CE. The first k bits on the left of this The PSID value algorithmically identifies a set of ports
2-octet field is the PSID value. The remaining (16-k) bits assigned to a CE. The first k bits on the left of this
on the right are padding zeros. 2-octet field is the PSID value. The remaining (16-k) bits
on the right are padding zeros.
3.2. Softwire46-Priority Attribute 3.2. Softwire46-Priority Attribute
The Softwire46-Priority Attribute defines a 16-bit S46-option-code The Softwire46-Priority Attribute defines a 32-bit Softwire46-option-
field to contain the information allowing the client to prioritize code field to contain the information allowing the client to
which mechanism to use, corresponding to OPTION_S46_PRIORITY defined prioritize which mechanism to use, corresponding to
in [RFC8026]. The following requirements apply: OPTION_S46_PRIORITY defined in [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-
Request packet. Request packet.
The Softwire46-Priority Attribute MUST NOT appear in any other The Softwire46-Priority Attribute MUST NOT appear in any other
RADIUS packet. RADIUS packet.
The S46-Priority Attribute is structured as follows: The Softwrie46-Priority Attribute is structured as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Extended-Type | ... . | Type | Length | Extended-Type | ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. S46-option-code | S46-option-code | . Softwire46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Softwire46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
241 (To be confirmed by IANA) 241 (To be confirmed by IANA)
Length Length
One octet long. Indicates the length of this TLV, including Indicates the length of this attribute,
the TLV-Type, TLV-Length, and TLV-Value fields. including the Type, Length, Extended-Type and Value fields.
Extended-Type Extended-Type
TBD5 TBD5
S46-option-code Softwire46-option-code
Integer. A 16-bit IANA-registered option code representing Integer. A 32-bit IANA-registered option code representing
an S46 mechanism. The option codes and their corresponding an Softwire46 mechanism. The option codes and their
S46 mechanisms are listed in Section 7.3. corresponding Softwire46 mechanisms are listed in Section 7.3.
S46 mechanisms are prioritized in the appearance order of the Softwire46 mechanisms are prioritized in the appearance order
S46-option-code(s) in the Softwire46-Priority Attribute. of the Softwire46-option-code(s) in the Softwire46-Priority
Attribute.
A Softwire46-Priority Attribute MUST contain at least one A Softwire46-Priority Attribute MUST contain at least one
S46-option-code. Softwire46-option-code.
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.3. Softwire46-Multicast Attribute 3.3. Softwire46-Multicast Attribute
The Softwire46-Multicast Attribute conveys the IPv6 prefixes to be The Softwire46-Multicast Attribute conveys the IPv6 prefixes to be
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,
skipping to change at page 27, line 21 skipping to change at page 23, line 23
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 the ASM-Prefix64
TLV (see Section 3.3.1). (see Section 3.3.1).
The Softwire46-Multicast Attribute MAY contain the SSM-Prefix64 The Softwire46-Multicast Attribute MAY contain the SSM-Prefix64
TLV (see Section 3.3.2). (see Section 3.3.2).
The Softwire46-Multicast Attribute MAY contain the U-Prefix64 TLV The Softwire46-Multicast Attribute MAY contain the U-Prefix64 (see
(see Section 3.3.3). Section 3.3.3).
The Softwire46-Multicast Attribute MUST include the ASM-Prefix64 The Softwire46-Multicast Attribute MUST include the ASM-Prefix64
TLV or the SSM-Prefix64 TLV, and it MAY include both. or the SSM-Prefix64, and it MAY include both.
The U-Prefix64 TLV MUST be present when the SSM-Prefix64 TLV is The U-Prefix64 MUST be present when the SSM-Prefix64 is present.
present. The U-Prefix64 TLV MAY be present when the ASM-Prefix64 The U-Prefix64 MAY be present when the ASM-Prefix64 is present.
TLV is present.
The the Softwire46-Multicast Attribute is structured as follows: The the Softwire46-Multicast Attribute is structured as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Extended-Type | Value ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 TLVs. entire length of the embedded attributes.
Extended-Type Extended-Type
TBD6 TBD6
Value Value
This field contains a set of TLVs as follows: This field contains a set of attributes as follows:
ASM-Prefix64 TLV ASM-Prefix64
This TLV contains the ASM IPv6 prefix. Refer to Section 3.3.1. This attribute contains the ASM IPv6 prefix. Refer to
Section 3.3.1.
SSM-Prefix64 TLV SSM-Prefix64
This TLV contains the SSM IPv6 prefix. Refer to Section 3.3.2. This attribute contains the SSM IPv6 prefix. Refer to
Section 3.3.2.
U-Prefix64 TLV U-Prefix64
This TLV contains the IPv4 prefix used for address This attribute contains the IPv4 prefix used for address
translation. Refer to Section 3.3.3. translation. Refer to Section 3.3.3.
The Softwire46-Multicast Attribute is associated with the following The Softwire46-Multicast Attribute is associated with the following
identifier: 241.Extended-Type(TBD6). identifier: 241.Extended-Type(TBD6).
3.3.1. ASM-Prefix64 TLV 3.3.1. ASM-Prefix64 Attribute
The ASM-Prefix64 TLV is structured as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Reserved | Prefix-Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| |
| ASM Prefix64 |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type
TBD21
Reserved The ASM-Prefix64 is structured as follows:
This field is reserved. It is always set to zero. This field
is one octet in length.
Prefix-Length TLV-Type
The length of the prefix, in bits. It MUST be set to 96 [RFC8115]. 18
ASM Prefix64 TLV-Length
IPv6 prefix. This field specifies the IPv6 multicast prefix 16 octets. The length of ssm-prefix64 must be to 96 [RFC8115].
to be used to synthesize the IPv4-embedded IPv6 addresses of the
multicast groups in the ASM mode. The conveyed multicast IPv6
prefix MUST belong to the ASM range.
3.3.2. SSM-Prefix64 TLV Data Type
The attribute ASM-Prefix64 is of type ipv6prefix (Section 3.10 of
[RFC8044]).
The format of SSM-Prefix64 TLV is shown below: TLV-Value
This field specifies the IPv6 multicast prefix (asm-prefix64)
to be used to synthesize the IPv4-embedded IPv6 addresses of the
multicast groups in the ASM mode. The conveyed multicast IPv6
prefix MUST belong to the ASM range.
0 1 2 3 3.3.2. SSM-Prefix64 Attribute
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Reserved |Prefix-Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| |
| SSM Prefix64 |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type The SSM-Prefix64 attribute is structured as follows:
TBD22
Reserved Type
This field is reserved. It is always set to zero. This field 19
is one octet in length.
Prefix-Length TLV-Length
The length of the prefix, in bits. It MUST be set to 96 [RFC8115]. 16 octets. The length of ssm-prefix64 must be to 96 [RFC8115].
SSM Prefix64 Data Type
IPv6 prefix. This field specifies the IPv6 multicast prefix The attribute SSM-Prefix64 is of type ipv6prefix (Section 3.10 of
to be used to synthesize the IPv4-embedded IPv6 addresses of the [RFC8044]).
multicast groups in the SSM mode. The conveyed multicast IPv6
prefix MUST belong to the SSM range.
3.3.3. U-Prefix64 TLV TLV-Type
This field specifies the IPv6 multicast prefix (ssm-prefix64)
to be used to synthesize the IPv4-embedded IPv6 addresses of the
multicast groups in the SSM mode. The conveyed multicast IPv6
prefix MUST belong to the SSM range.
The format of the U-Prefix64 TLV is shown below: 3.3.3. U-Prefix64 Attribute
0 1 2 3 The structure of the U-Prefix64 attribute is shown below:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Reserved | Prefix-Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| |
| Unicast Prefix64 |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV-Type TLV-Type
TBD23 20
Reserved
This field is reserved. It is always set to zero. This field
is one octet in length.
Prefix-Length TLV-Length
The length of the prefix, in bits. 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.
Unicast Prefix64 Data Type
IPv6 prefix. This field identifies the IPv6 unicast prefix to The attribute U-Prefix64 is of type ipv6prefix (Section 3.10 of
[RFC8044]).
TLV-Value
This field identifies the IPv6 unicast prefix to
be used in SSM mode for constructing the IPv4-embedded IPv6 be used in SSM mode for constructing the IPv4-embedded IPv6
addresses representing the IPv4 multicast sources in the IPv6 addresses representing the IPv4 multicast sources in the IPv6
domain. It may also be used to extract the IPv4 address from the domain. It may also be used to extract the IPv4 address from the
received multicast data flows. received multicast data flows.
4. A Sample Configuration Process with RADIUS 4. A Sample Configuration Process with RADIUS
Figure 2 illustrates how the RADIUS and DHCPv6 protocols interwork to Figure 2 illustrates how the RADIUS and DHCPv6 protocols interwork to
provide CE with softwire configuration information. provide CE with softwire configuration information.
skipping to change at page 32, line 37 skipping to change at page 26, line 37
|<--------6.DHCPv6 Reply--------| | |<--------6.DHCPv6 Reply--------| |
| (container option(s)) | | | (container option(s)) | |
| | | | | |
DHCPv6 RADIUS DHCPv6 RADIUS
Figure 2: Interaction between DHCPv6 and AAA Server with RADIUS Figure 2: Interaction between DHCPv6 and AAA Server with RADIUS
authentication authentication
1. The CE creates a DHCPv6 Solicit message. For unicast softwire 1. The CE creates a DHCPv6 Solicit message. For unicast softwire
configuration, the message includes an OPTION_REQUEST_OPTION (6) configuration, the message includes an OPTION_REQUEST_OPTION (6)
with the S46 Container option codes as defined in [RFC7598]. with the Softwire46 Container option codes as defined in
OPTION_S46_CONT_MAPE (94) should be included for MAP-E, [RFC7598]. OPTION_S46_CONT_MAPE (94) should be included for MAP-
OPTION_S46_CONT_MAPT (95) for MAP-T, and OPTION_S46_CONT_LW (96) E, OPTION_S46_CONT_MAPT (95) for MAP-T, and OPTION_S46_CONT_LW
for Lightweight 4over6. For multicast configuration, the option (96) for Lightweight 4over6. For multicast configuration, the
number for OPTION_V6_PREFIX64 (113) is included in the client's option number for OPTION_V6_PREFIX64 (113) is included in the
ORO. The message is sent to the BNG. client's ORO. The message is sent to the BNG.
2. On receipt of the Solicit message, the BNG constructs a RADIUS 2. On receipt of the Solicit message, the BNG constructs a RADIUS
Access-Request message containing a User-Name Attribute (1) Access-Request message containing a User-Name Attribute (1)
(containing either a CE MAC address, interface-id or both), a (containing either a CE MAC address, interface-id or both), a
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.
skipping to change at page 33, line 50 skipping to change at page 27, line 50
In addition to the above, the following points need to be considered: In addition to the above, the following points need to be considered:
o In both the configuration message flows described above the o In both the configuration message flows described above the
Message-authenticator (type 80) [RFC2869] SHOULD be used to Message-authenticator (type 80) [RFC2869] SHOULD be used to
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 S46 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 S46 o If the BNG receives an Access-Reject from the AAA server, then
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 [RFC3315], Section 18.1.4, "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
synchronized between the clients and the lwAFTR/BR. This can be synchronized between the clients and the lwAFTR/BR. This can be
achieved in two ways: static pre-configuring of the bindings on achieved in two ways: static pre-configuring of the bindings on
both the AAA server and lwAFTR, or on-demand whereby the AAA both the AAA server and lwAFTR, or on-demand whereby the AAA
server updates the lwAFTR with the subscriber's binding state as server updates the lwAFTR with the subscriber's binding state as
it is created or deleted. it is created or deleted.
In some deployments, the DHCP server may use the Accounting-Request
to report to a AAA server the softwire configuration returned to a
requesting host. It is the responsibility of the DHCP server to
ensure the consistency of the configuration provided to requesting
hosts. Reported data to a AAA server may be required for various
operational purposes (e.g., regulatory).
5. Table of Attributes 5. Table of Attributes
This document specifies three new RADIUS attributes, and their This document specifies three new RADIUS attributes, and their
formats are as follows: formats are as follows:
o Softwire46-Configuration Attribute: 241.TBD1 o Softwire46-Configuration Attribute: 241.TBD1
o Softwire46-Priority Attribute: 241.TBD5 o Softwire46-Priority Attribute: 241.TBD5
o Softwire46-Multicast Attribute: 241.TBD6 o Softwire46-Multicast Attribute: 241.TBD6
skipping to change at page 34, line 48 skipping to change at page 29, line 14
Request Accept Reject Challenge Accounting # Attribute Request Accept Reject Challenge Accounting # Attribute
Request Request
0-1 0-1 0 0 0-1 241.TBD1 Softwire46- 0-1 0-1 0 0 0-1 241.TBD1 Softwire46-
Configuration Configuration
0-1 0-1 0 0 0-1 241.TBD5 Softwire46- 0-1 0-1 0 0 0-1 241.TBD5 Softwire46-
Priority Priority
0-1 0-1 0 0 0-1 241.TBD6 Softwire46- 0-1 0-1 0 0 0-1 241.TBD6 Softwire46-
Multicast Multicast
The following table defines the meaning of the above table entries.
0 This attribute MUST NOT be present in packet.
0+ Zero or more instances of this attribute MAY be present in
packet.
0-1 Zero or one instance of this attribute MAY be present in
packet.
1 Exactly one instance of this attribute MUST be present in
packet.
6. Security Considerations 6. Security Considerations
Known security vulnerabilities of the RADIUS protocol are discussed Known security vulnerabilities of the RADIUS protocol are discussed
in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for
providing security when RADIUS is carried in IPv6 is discussed in providing security when RADIUS is carried in IPv6 is discussed in
[RFC3162]. [RFC3162].
Specific security considerations for interactions between the MAP CE Specific security considerations for interactions between the MAP CE
and the BNG are discussed in [RFC7597] and [RFC7599]. Security and the BNG are discussed in [RFC7597] and [RFC7599]. Security
considerations for Lightweight 4over6 are discussed in [RFC7596]. considerations for Lightweight 4over6 are discussed in [RFC7596].
Security considerations for DHCPv6-Based S46 Prioritization Mechanism Security considerations for DHCPv6-Based Softwire46 Prioritization
are discussed in [RFC8026]. Security considerations for multicast Mechanism are discussed in [RFC8026]. Security considerations for
scenarios are discussed in [RFC 8114]. Furthermore, generic DHCPv6 multicast scenarios are discussed in [RFC8114]. Furthermore, generic
security mechanisms can be applied to DHCPv6 intercommunication DHCPv6 security mechanisms can be applied to DHCPv6
between the CE and the BNG. intercommunication between the CE and the BNG.
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]. [RFC5226].
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 4.1
241.TBD5 Softwire46-Priority integer Section 4.2 241.TBD5 Softwire46-Priority integer Section 4.2
241.TBD6 Softwire46-Multicast TLV Section 4.3 241.TBD6 Softwire46-Multicast tlv Section 4.3
7.2. New RADIUS TLVs 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 TLVs". Configuration and Multicast Attributes".
All TLVs in this registry have one or more parent RADIUS attributes All attributes in this registry have one or more parent RADIUS
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
TBD2 S46-MAP-E TLV Section 3.1.1.1 1 Softwire46-MAP-E tlv Section 3.1.1.1
TBD3 S46-MAP-T TLV Section 3.1.1.2 2 Softwire46-MAP-T tlv Section 3.1.1.2
TBD4 S46-Lightweight-4over6 TLV Section 3.1.1.3 3 Softwire46-Lightweight-4over6 tlv Section 3.1.1.3
TBD7 S46-Rule TLV Section 3.1.3.1 4 Softwire46-Rule tlv Section 3.1.3.1
TBD8 S46-Rule TLV Section 3.1.3.1 5 Softwire46-Rule tlv Section 3.1.3.1
TBD9 S46-BR ipv6addr Section 3.1.3.2 6 Softwire46-BR ipv6addr Section 3.1.3.2
TBD10 S46-DMR ipv6prefix Section 3.1.3.3 7 Softwire46-DMR ipv6prefix Section 3.1.3.3
TBD11 S46-V4V6Bind TLV Section 3.1.3.4 8 Softwire46-V4V6Bind tlv Section 3.1.3.4
TBD12 S46-PORTPARAMS TLV Section 3.1.3.5 9 Softwire46-PORTPARAMS tlv Section 3.1.3.5
TBD13 Rule-IPv6-Prefix ipv6prefix Section 3.1.4.1 10 Rule-IPv6-Prefix ipv6prefix Section 3.1.4.1
TBD14 Rule-IPv4-Prefix ipv4prefix Section 3.1.4.2 11 Rule-IPv4-Prefix ipv4prefix Section 3.1.4.2
TBD15 EA-Length integer Section 3.1.4.3 12 EA-Length integer Section 3.1.4.3
TBD16 IPv4-address ipv4addr Section 3.1.5.1 13 IPv4-address ipv4addr Section 3.1.5.1
TBD17 Bind-IPv6-Prefix ipv6prefix Section 3.1.5.2 14 Bind-IPv6-Prefix ipv6prefix Section 3.1.5.2
TBD18 PSID-offset integer Section 3.1.6.1 15 PSID-offset integer Section 3.1.6.1
TBD19 PSID-len integer Section 3.1.6.2 16 PSID-len integer Section 3.1.6.2
TBD20 PSID integer Section 3.1.6.3 17 PSID integer Section 3.1.6.3
TBD21 ASM-Prefix64 ipv6prefix Section 3.3.1 18 ASM-Prefix64 ipv6prefix Section 3.3.1
TBD22 SSM-Prefix64 ipv6prefix Section 3.3.2 19 SSM-Prefix64 ipv6prefix Section 3.3.2
TBD23 U-Prefix64 ipv6prefix Section 3.3.3 20 U-Prefix64 ipv6prefix Section 3.3.3
21-255 Unassigned, TBD2,TBD3,TBD4 will be assigned by IANA 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 [RFC5226]. The registry may be added to using the IETF
Review process described in Section 4.1 of [RFC5226]. Review process described in Section 4.1 of [RFC5226].
7.3. S46 Mechanisms and Their Identifying Option Codes 7.3. Softwire46 Mechanisms and Their Identifying Option Codes
The Softwire46-Priority Attribute defines a 16-bit S46-option-code The Softwire46-Priority Attribute defines a 16-bit Softwire46-option-
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 [RFC5226].
This document requires 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 the Section 3.1.1. Additional options may
be added to this list in the future using the IETF Review process be added to this list in the future using the IETF Review process
described in Section 4.1 of [RFC5226]. described in Section 4.1 of [RFC5226].
Table 3. shows the option codes required, and the S46 mechanisms that Table 3 shows the option codes required, and the Softwire46
they represent. The option code for DS-Lite is derived from the IANA mechanisms that they represent. The option code for DS-Lite is
allocated RADIUS Attribute Type value for DS-Lite [RFC6519]. The derived from the IANA allocated RADIUS Attribute Type value for DS-
option codes for MAP-E, MAP-T, and Lightweight 4over6 need to be Lite [RFC6519]. The option codes for MAP-E, MAP-T, and Lightweight
assigned. The option codes for MAP-E, MAP-T, and Lightweight 4over6 4over6 need to be assigned. The option codes for MAP-E, MAP-T, and
should also be used as 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 TLV defined in Section 3.1.1. MAP-E, MAP-T, and Lightweight 4over6 TLV defined in Section 3.1.1.
+-------------+------------------+-----------+ +-----------+--------------------+-----------+
| Option Code | S46 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 |
+--------------------------------+-----------+ +--------------------------------+-----------+
Table 3: Option Codes to S46 Mechanisms Table 3: Option Codes to S46 Mechanisms
8. Contributing Authors 8. Contributing Authors
Qiong Sun Qiong Sun
China Telecom China Telecom
Beijing China Beijing China
Email: sunqiong@ctbri.com.cn Email: sunqiong@ctbri.com.cn
skipping to change at page 38, line 48 skipping to change at page 32, 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 and Cui Wang for this document. This document was merged with Meng, Cui Wang, Alan Dekok, and Stefan Winter to this document.
draft-sun-softwire-lw4over6-radext-01 and draft-wang-radext-
multicast-radius-ext-00, thanks to everyone who contributed to this This document was merged with draft-sun-softwire-lw4over6-radext-01
document. and draft-wang-radext-multicast-radius-ext-00, thanks to everyone who
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
[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,
skipping to change at page 41, line 41 skipping to change at page 35, line 41
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for
Configuration of Softwire Address and Port-Mapped Configuration of Softwire Address and Port-Mapped
Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015, Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015,
<https://www.rfc-editor.org/info/rfc7598>. <https://www.rfc-editor.org/info/rfc7598>.
[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>.
[RFC7678] Zhou, C., Taylor, T., Sun, Q., and M. Boucadair,
"Attribute-Value Pairs for Provisioning Customer Equipment
Supporting IPv4-Over-IPv6 Transitional Solutions",
RFC 7678, DOI 10.17487/RFC7678, October 2015,
<https://www.rfc-editor.org/info/rfc7678>.
[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>.
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, TLVs and DHCPv6 option fields and the relevant RADIUS attributes as defined in
Sub-TLVs as defined in this document. this document.
A.1. OPTION_S46_RULE (89) to S46-Rule Sub-TLV Field Mappings A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field Mappings
+---------------------+----------------------+----------------------+ +---------------------+----------------------+----------------------+
| OPTION_S46_RULE | S46-Rule Sub-TLV | TLV Field | | OPTION_S46_RULE | Softwire46-Rule Name | TLV Field |
| Field | Name | | | Field | | |
+---------------------+----------------------+----------------------+ +---------------------+----------------------+----------------------+
| flags | N/A | TLV-type (TBD7, | | flags | N/A | TLV-type (TBD7, |
| | | TBD8) | | | | TBD8) |
| ea-len | EA-Length | EA-len | | ea-len | EA-Length | EA-len |
| prefix4-len | Rule-IPv4-Prefix | ruleprefix4-len | | prefix4-len | Rule-IPv4-Prefix | ruleprefix4-len |
| ipv4-prefix | Rule-IPv4-Prefix | rule-ipv4-prefix | | ipv4-prefix | Rule-IPv4-Prefix | rule-ipv4-prefix |
| prefix6-len | Rule-IPv6-Prefix | ruleprefix6-len | | prefix6-len | Rule-IPv6-Prefix | ruleprefix6-len |
| ipv6-prefix | Rule-IPv6-Prefix | rule-ipv6-prefix | | ipv6-prefix | Rule-IPv6-Prefix | rule-ipv6-prefix |
+---------------------+----------------------+----------------------+ +---------------------+----------------------+----------------------+
A.2. OPTION_S46_BR (90) to S46-BR Sub-TLV Sub-TLV Field Mappings A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings
+---------------------+---------------------+
| OPTION_S46_BR Field | Softwire46-BR Field |
+---------------------+---------------------+
| br-ipv6-address | br-ipv6-address |
+---------------------+---------------------+
A.3. OPTION_S46_DMR (91) to Softwire46-DMR
+---------------------+----------------------+ +---------------------+----------------------+
| OPTION_S46_BR Field | S46-BR Sub-TLV Field | | OPTION_S46_BR Field | Softwire46-DMR Field |
+---------------------+----------------------+ +---------------------+----------------------+
| br-ipv6-address | br-ipv6-address | | dmr-prefix6-len | dmr-prefix6-len |
| dmr-ipv6-prefix | dmr-ipv6-prefix |
+---------------------+----------------------+ +---------------------+----------------------+
A.3. OPTION_S46_DMR (91) to S46-DMR Sub-TLV A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind
+---------------------+-----------------------+
| OPTION_S46_BR Field | S46-DMR Sub-TLV Field |
+---------------------+-----------------------+
| dmr-prefix6-len | dmr-prefix6-len |
| dmr-ipv6-prefix | dmr-ipv6-prefix |
+---------------------+-----------------------+
A.4. OPTION_S46_V4V6BIND (92) to S46-V4V6Bind Sub-TLV
+------------------------+-----------------------+------------------+
| OPTION_S46_V4V6BIND | S46-V4V6Bind Sub-TLV | TLV Field |
| Field | Name | |
+------------------------+-----------------------+------------------+
| ipv4-address | IPv4-address | ipv4-address |
| bindprefix6-len | Bind-IPv6-Prefix | bind6prefix-len |
| bind-ipv6-prefix | Bind-IPv6-Prefix | bind-ipv6-prefix |
+------------------------+-----------------------+------------------+
A.5. OPTION_S46_PORTPARAMS (93) to S46-PORTPARAMS Sub-TLV Field +-----------------------+------------------------+------------------+
Mappings | OPTION_S46_V4V6BIND | Softwire46-V4V6Bind | TLV Field |
| Field | Name | |
+-----------------------+------------------------+------------------+
| ipv4-address | IPv4-address | ipv4-address |
| bindprefix6-len | Bind-IPv6-Prefix | bind6prefix-len |
| bind-ipv6-prefix | Bind-IPv6-Prefix | bind-ipv6-prefix |
+-----------------------+------------------------+------------------+
+---------------------------+-------------------------+-------------+ A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field Mappings
| OPTION_S46_PORTPARAMS | S46-PORTPARAMS Sub-TLV | TLV Field | +--------------------------+--------------------------+-------------+
| Field | Name | | | OPTION_S46_PORTPARAMS | Softwire46-PORTPARAMS | TLV Field |
+---------------------------+-------------------------+-------------+ | Field | Name | |
| offset | PSID-offset | PSID-Offset | +--------------------------+--------------------------+-------------+
| PSID-len | PSID-len | PSID-len | | offset | PSID-offset | PSID-Offset |
| PSID | PSID | PSID | | PSID-len | PSID-len | PSID-len |
+---------------------------+-------------------------+-------------+ | PSID | PSID | PSID |
+--------------------------+--------------------------+-------------+
A.6. OPTION_S46_PRIORITY (111) to S46-PORTPARAMS Sub-TLV Field Mappings A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field Mappings
+---------------------------+-------------------------------------+ +---------------------------+-------------------------------------+
| OPTION_S46_PRIORITY Field | Softwire46-Priority Attribute Field | | OPTION_S46_PRIORITY Field | Softwire46-Priority Attribute Field |
+---------------------------+-------------------------------------+ +---------------------------+-------------------------------------+
| s46-option-code | S46-option-code | | s46-option-code | Softwire46-option-code |
+---------------------------+-------------------------------------+ +---------------------------+-------------------------------------+
A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast Attribute TLV A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast Attribute Field
Field Mappings Mappings
+--------------------+------------------------------+---------------+ +--------------------+------------------------------+---------------+
| OPTION_V6_PREFIX64 | Softwire46-Multicast | TLV Field | | OPTION_V6_PREFIX64 | Softwire46-Multicast | TLV Field |
| Field | Attribute TLV Name | | | Field | Attribute TLV Name | |
+--------------------+------------------------------+---------------+ +--------------------+------------------------------+---------------+
| asm-length | ASM-Prefix64 | Prefix-Length | | asm-length | ASM-Prefix64 | Prefix-Length |
| ASM_mPrefix64 | ASM-Prefix64 | ASM Prefix64 | | ASM_mPrefix64 | ASM-Prefix64 | ASM Prefix64 |
| ssm-length | SSM-Prefix64 | Prefix-Length | | ssm-length | SSM-Prefix64 | Prefix-Length |
| SSM_mPrefix64 | SSM-Prefix64 | SSM Prefix64 | | SSM_mPrefix64 | SSM-Prefix64 | SSM Prefix64 |
| unicast-length | U-Prefix64 | Prefix-Length | | unicast-length | U-Prefix64 | Prefix-Length |
skipping to change at page 44, line 30 skipping to change at page 38, line 30
Peter Deacon Peter Deacon
IEA Software, Inc. IEA Software, Inc.
P.O. Box 1170 P.O. Box 1170
Veradale, WA 99037 Veradale, WA 99037
USA USA
Email: peterd@iea-software.com Email: peterd@iea-software.com
Chongfeng Xie Chongfeng Xie
China Telecom China Telecom
China Telecom Beijing Information Sci.&Tech. Park, Beijing
Beiqijia Town, Changping District, Beijing 102209
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
P.R.China P.R.China
Email: peter416733@gmail.com Email: peter416733@gmail.com
 End of changes. 245 change blocks. 
785 lines changed or deleted 655 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/