draft-ietf-softwire-map-radius-08.txt   draft-ietf-softwire-map-radius-09.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: April 30, 2017 CNNIC Expires: July 7, 2017 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
October 27, 2016 January 3, 2017
RADIUS Attribute for Softwire Address plus Port based Mechanisms RADIUS Attribute for Softwire Address plus Port based Mechanisms
draft-ietf-softwire-map-radius-08 draft-ietf-softwire-map-radius-09
Abstract Abstract
IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6 IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6
connectivity services simultaneously during the IPv4/IPv6 co-existing connectivity services simultaneously during the IPv4/IPv6 co-existing
period. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) period. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
options have been defined to configure Customer Edge (CE) in MAP-E, options have been defined to configure Customer Edge (CE) in MAP-E,
MAP-T, and Lightweight 4over6. However, in many networks, the MAP-T, and Lightweight 4over6. However, in many networks, the
configuration information may be stored in Authentication configuration information may be stored in the Authentication
Authorization and Accounting (AAA) servers while user configuration Authorization and Accounting (AAA) servers, while user configuration
is mainly from Broadband Network Gateway (BNG) through DHCPv6 is mainly provided by the Broadband Network Gateway (BNG) through the
protocol. This document defines a Remote Authentication Dial In User DHCPv6 protocol. This document defines a Remote Authentication Dial
Service (RADIUS) attribute that carries CE configuration information In User Service (RADIUS) attribute that carries CE configuration
from AAA server to BNG. information from the AAA server to the BNG.
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 April 30, 2017. This Internet-Draft will expire on July 7, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Configuration process with RADIUS . . . . . . . . . . . . . . 3 3. Configuration process with RADIUS . . . . . . . . . . . . . . 3
4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6 4.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6
4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 6 4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 7
4.3. Sub Options for S46 Container Option . . . . . . . . . . 7 4.3. Sub Options for S46 Container Option . . . . . . . . . . 7
4.3.1. S46-Rule Sub Option . . . . . . . . . . . . . . . . . 7 4.3.1. S46-Rule Sub Option . . . . . . . . . . . . . . . . . 7
4.3.2. S46-BR Sub Option . . . . . . . . . . . . . . . . . . 8 4.3.2. S46-BR Sub Option . . . . . . . . . . . . . . . . . . 8
4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 8 4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 9
4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 9 4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 9
4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 9 4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 10
4.4. Sub Options for S46-RULE Sub Option . . . . . . . . . . . 10 4.4. Sub Options for S46-RULE Sub Option . . . . . . . . . . . 11
4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 10 4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 11
4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 11 4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 12
4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 12 4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 13
4.5. Softwire46 Sub Options Encapsulation . . . . . . . . . . 12 4.5. Softwire46 Sub Options Encapsulation . . . . . . . . . . 13
4.6. Table of attributes . . . . . . . . . . . . . . . . . . . 12 4.6. Softwire46-Priority Attribute . . . . . . . . . . . . . . 13
5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 13 4.7. Table of attributes . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.2. Informative References . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . 16
Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 16 9.2. Informative References . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
Recently providers start to deploy IPv6 and consider how to transit Recently providers have started to deploy IPv6 and consider how to
to IPv6. Many transition mechanisms based on the Address plus Port transit to IPv6. Many transition mechanisms based on the Address
(A+P) [RFC6346] have been proposed for running IPv4 over IPv6-only plus Port (A+P) [RFC6346] have been proposed for running IPv4 over
infrastructure, including MAP-E, MAP-T, and Lightweight 4over6. IPv6-only infrastructure, including MAP-E, MAP-T, and Lightweight
Mapping of Address and Port with Encapsulation(MAP-E)[RFC7597], 4over6. Mapping of Address and Port with Encapsulation(MAP-
Mapping of Address and Port with using Translation(MAP-T)[RFC7599] E)[RFC7597], Mapping of Address and Port with using Translation(MAP-
are stateless mechanisms for running IPv4 over IPv6-only T)[RFC7599] are stateless mechanisms for running IPv4 over IPv6-only
infrastructure. Lightweight 4over6[RFC7596] is a hub-and-spoke IPv4- infrastructure. Lightweight 4over6[RFC7596] is a hub-and-spoke IPv4-
over-IPv6 tunneling mechanism, with complete independence of IPv4 and over-IPv6 tunneling mechanism, with complete independence of IPv4 and
IPv6 addressing. They provide both IPv4 and IPv6 connectivity IPv6 addressing. They provide both IPv4 and IPv6 connectivity
services simultaneously during the IPv4/IPv6 co-existing period. services simultaneously during the IPv4/IPv6 co-existing period.
MAP-E, MAP-T and Lightweight 4over6 have adopted Dynamic Host MAP-E, MAP-T and Lightweight 4over6 have adopted Dynamic Host
Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as auto- Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as auto-
configuring protocol. The Customer Edge (CE) uses DHCPv6 options to configuring protocol. The Customer Edge (CE) uses DHCPv6 options to
discover the Border Relay (BR) and get S46 configurations. discover the Border Relay (BR) and get Softwire46 (S46)
configurations.
In many networks, user configuration information may be stored in AAA In many networks, user configuration information may be stored in the
(Authentication, Authorization, and Accounting) servers. Current AAA Authentication, Authorization, and Accounting (AAA) servers. Current
servers communicate using the Remote Authentication Dial In User the AAA servers communicate using the Remote Authentication Dial In
Service (RADIUS) [RFC2865] protocol. In a fixed line broadband User Service (RADIUS) [RFC2865] protocol. In a fixed line broadband
network, the Broadband Network Gateways (BNGs) act as the access network, the Broadband Network Gateways (BNGs) act as the access
gateway of users. The BNGs are assumed to embed a DHCPv6 server gateway of users. The BNGs are assumed to embed a DHCPv6 server
function that allows them to locally handle any DHCPv6 requests function that allows them to locally handle any DHCPv6 requests
initiated by hosts. initiated by hosts.
Since the S46 configuration information is stored in AAA servers and Since the S46 configuration information is stored in the AAA servers
user configuration is mainly transmitted through DHCPv6 protocol and user configuration is mainly transmitted through DHCPv6 protocol
between BNGs and hosts/CEs, new RADIUS attributes are needed to between the BNGs and hosts/CEs, new RADIUS attributes are needed to
propagate the information from AAA servers to BNGs. The RADIUS propagate the information from the AAA servers to the BNGs. The
attributes designed in this document are especially for the MAP- RADIUS attributes designed in this document are especially for the
E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], providing MAP-E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596],
enough information to form the correspondent DHCPv6 configuration providing enough information to form the correspondent DHCPv6
options[RFC7598]. configuration options[RFC7598].
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", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Configuration process with RADIUS 3. Configuration process with RADIUS
The below Figure 1 illustrates how the RADIUS protocol and DHCPv6 The below Figure 1 illustrates how the RADIUS protocol and DHCPv6 co-
cooperate to provide CE with MAP configuration information. The BNG operate to provide CE with MAP configuration information. The BNG
acts as a RADIUS client and as a DHCPv6 server. acts as a RADIUS client and as a DHCPv6 server.
CE BNG AAA Server CE BNG AAA Server
| | | | | |
|-----1.DHCPv6 Solicit----->| | |-----1.DHCPv6 Solicit----->| |
| (ORO w/container option) | | | (ORO w/container option) | |
| |-------2.Access-Request------->| | |-------2.Access-Request------->|
| | (S46-Configuration attriubte) | | | (S46-Configuration attriubte) |
| | | | | |
| |<------3.Access-Accept---------| | |<------3.Access-Accept---------|
skipping to change at page 4, line 25 skipping to change at page 4, line 25
|-----5.DHCPv6 Request---->| | |-----5.DHCPv6 Request---->| |
| (container Option) | | | (container Option) | |
|<----6.DHCPv6 Reply--------| | |<----6.DHCPv6 Reply--------| |
| (cointainer option) | | | (cointainer option) | |
| | | | | |
DHCPv6 RADIUS DHCPv6 RADIUS
Figure 1: the cooperation between DHCPv6 and RADIUS combining with Figure 1: the cooperation between DHCPv6 and RADIUS combining with
RADIUS authentication RADIUS authentication
1. First, CE MAY initiate a DHCPv6 Solicit message that includes an 1. First, the CE MAY initiate a DHCPv6 Solicit message that includes
Option Request option(6) [RFC3315] with the S46 Container options as an Option Request option(6) [RFC3315] with the S46 Container options
defined in[RFC7598]. OPTION_S46_CONT_MAPE should be included for as defined in[RFC7598]. OPTION_S46_CONT_MAPE should be included for
MAP-E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599], and MAP-E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599], and
OPTION_S46_CONT_LW for Lightweight 4over6[RFC7596]. But note that OPTION_S46_CONT_LW for Lightweight 4over6[RFC7596]. Note however,
the ORO (Option Request option) with the S46 Container options could that the ORO (Option Request option) with the S46 Container option
be optional if the network was planned as S46-enabled as default. code could be optional if the network was planned as S46-enabled as
default.
2. When BNG receives the SOLICIT, it SHOULD initiate the radius 2. When the BNG receives the SOLICIT, it should initiate the radius
Access-Request message, in which the User-Name attribute (1) SHOULD Access-Request message, in which the User-Name attribute (1) should
be filled by the CE MAC address or interface-id or both, to the be filled by the CE MAC address or interface-id or both, to the
RADIUS server and the User-password attribute (2) SHOULD be filled by RADIUS server and the User-password attribute (2) should be filled by
the shared password that has been preconfigured on the DHCPv6 server, the shared password that has been preconfigured on the DHCPv6 server,
requesting authentication as defined in [RFC2865] with the requesting authentication as defined in [RFC2865] with the
corresponding Softwire46-Configuration Attribute, which will be corresponding Softwire46-Configuration Attribute, which will be
defined in the next Section. defined in the next Section.
3. If the authentication request is approved by the AAA server, an 3. If the authentication request is approved by the AAA server, an
Access-Accept message MUST be acknowledged with the corresponding Access-Accept message MUST be acknowledged with the corresponding
Softwire46-Configuration Attribute. Softwire46-Configuration Attribute.
4. After receiving the Access-Accept message with the corresponding 4. After receiving the Access-Accept message with the corresponding
Attribute, the BNG SHOULD respond the user an Advertisement message. Attribute, the BNG SHOULD respond to the CE with an Advertisement
message.
5. After receiving the Advertise message, the user can request for 5. After receiving the Advertise message, the CE MAY request for the
the corresponding S46 Container option, by including the S46 corresponding S46 Container option, by including the S46 Container
Container option in the Request Message. option in the Request Message.
6. After receiving the client's Request messsage, containing the 6. After receiving the client's Request messsage, containing the
corresponding S46 Container option the BNG SHOULD reply the user with corresponding S46 Container option the BNG SHOULD reply to the CE
the message containing the S46 Container option. The recommended with the message containing the S46 Container option. The
format of the MAC address is defined as Calling-Station-Id recommended format of the MAC address is defined as Calling-Station-
(Section 3.20 in [RFC3580] without the SSID (Service Set Identifier) Id (Section 3.20 in [RFC3580] without the SSID (Service Set
portion. Identifier) portion.
For Lightweight 4over6 [RFC7596], the subscriber's binding state For Lightweight 4over6 [RFC7596], the subscriber's binding state
should be synchronized between AAA server and the lwAFTR. If the should be synchronized between the AAA server and the lwAFTR. If the
bindings are pre-configured statically in both AAA server and lwAFTR, bindings are pre-configured statically, in both the AAA server and
the AAA server does not need to configure lwAFTR anymore. Otherwise, the lwAFTR, the AAA server does not need to configure the lwAFTR
if the bindings are locally creately in AAA server on-demand, it anymore. Otherwise, if the bindings are locally created on-demand in
should inform the lwAFTR with the subscriber's binding state, to the AAA server, it should inform the lwAFTR with the subscriber's
synchronise the binding information of the lwB4 with the lwAFTR. In binding state, in order to synchronise the binding information of the
the Lightweight 4over6 scenario, the lwB4 could also be configured lwB4 with the lwAFTR.
through DHCPv4-over-DHCPv6 [RFC7341] as well as PCP [RFC6887], in
which the lwB4 act a PCP client and the BNG act as both a Radius
client and a PCP server.
The authorization operation could also be done independently after The authorization operation could also be done independently after
the authentication process. In such scenario, after the the authentication process. In such a scenario, after the
authentication operation, the client MAY initiate a DHCPv6 Request authentication operation, the client MAY initiate a DHCPv6 Request
message that includes the corresponding S46 Container options. As message that includes the corresponding S46 Container options.
similar to above scenario, the ORO with the corresponding S46 Similar to the above scenario, the ORO with the corresponding S46
Container option in the initial DHCPv6 request could be optional if Container option code in the initial DHCPv6 request could be optional
the network was planned as S46-enabled as default. When BNG receives if the network was planned as being S46-enabled vy default. When the
the DHCPv6 Request, it SHOULD initiate the radius Access-Request BNG receives the DHCPv6 Request, it SHOULD initiate the radius
message, which MUST contain a Service-Type attribute (6) with the Access-Request message, which MUST contain a Service-Type attribute
value Authorize Only (17), the corresponding Softwire46-Configuration (6) with the value Authorize Only (17), the corresponding
Attribute, and a State attribute obtained from the previous Softwire46-Configuration Attribute, and a State attribute obtained
authentication process according to [RFC5080]. If the authorization from the previous authentication process according to [RFC5080]. If
request is approved by the AAA server, an Access-Accept message MUST the authorization request is approved by the AAA server, an Access-
be acknowledged with the corresponding Softwire46-Configuration Accept message MUST be acknowledged with the corresponding
Attribute. The BNG SHOULD then send the DHCPv6 Reply message Softwire46-Configuration Attribute. The BNG SHOULD then send the
containing the S46 Container option. DHCPv6 Reply message containing the S46 Container option.
In both above-mentioned scenarios, Message-authenticator (type 80) In both the above-mentioned scenarios, Message-authenticator (type
[RFC2869] SHOULD be used to protect both Access-Request and Access- 80) [RFC2869] SHOULD be used to protect both Access-Request and
Accept messages. Access-Accept messages.
If the BNG does not receive the corresponding MAP-Configuration If the BNG does not receive the corresponding MAP-Configuration
Attribute in the Access-Accept it MAY fallback to a pre-configured Attribute in the Access-Accept it MAY fallback to a pre-configured
default S46 configuration, if any. If the BNG does not have any pre- default S46 configuration, if any. If the BNG does not have any pre-
configured default S46 configuration or if the BNG receives an configured default S46 configuration, or if the BNG receives an
Access-Reject, then S46 cannot be established. Access-Reject, then S46 cannot be established.
As specified in [RFC3315], section 18.1.4, "Creation and Transmission As specified in [RFC3315], section 18.1.4, "Creation and Transmission
of Rebind Messages ", if the DHCPv6 server to which the DHCPv6 Renew of Rebind Messages ", if the DHCPv6 server to which the DHCPv6 Renew
message was sent at time T1 has not responded by time T2, the CE message was sent at time T1 has not responded by time T2, the CE
(DHCPv6 client) SHOULD enter the Rebind state and attempt to contact (DHCPv6 client) SHOULD enter the Rebind state and attempt to contact
any available server. In this situation, the secondary BNG receiving any available server. In this situation, the secondary BNG receiving
the DHCPv6 message MUST initiate a new Access-Request towards the AAA the DHCPv6 message MUST initiate a new Access-Request towards the AAA
server. The secondary BNG MAY include the MAP-Configuration server. The secondary BNG MAY include the MAP-Configuration
Attribute in its Access-Request. Attribute in its Access-Request.
4. Attributes 4. Attributes
This section defines S46 Attributes which are used in the MAP This section defines the Softwire46-Configuration Attribute and the
scenario. The attribute design follows [RFC6158] and refers Softwire46-Priority Attribute. The attribute design follows
to[RFC6929]. [RFC6158] and refers to [RFC6929]. The Softwire46-Configuration
Attribute carries the configuration information for MAP-E, MAP-T, and
The S46 attributes are designed following the simplify principle. Lightweight 4over6. The configuration information for each S46
mechanism is carried in the corresponding S46 Container option.
Different sub options are required for each type of S46 Container Different sub options are required for each type of S46 Container
option. option. The RADIUS attribute for Dual-Stack Lite [RFC6333] is
defined in [RFC6519].
A client may be capable of supporting several different S46
mechanisms. Depending on the deployment scenario, a client might
request for more than one S46 mechanism at a time. The
Softwire46-Priority Attribute contains information allowing the
client to prioritize which mechanism to use, corresponding to
OPTION_S46_PRIORITY defined in [RFC8026].
4.1. Softwire46-Configuration Attribute 4.1. Softwire46-Configuration Attribute
The Softwire46-Configuration Attribute is structured as follows: The Softwire46-Configuration 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 | | | Type | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ S46 Container Option(s) + + S46 Container Option(s) +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
TBD TBD
Length Length
2 + the length of the S46 Container option(s) 2 + the length of the S46 Container option(s) specified in octects
S46 Container Option (s) S46 Container Option (s)
A variable field that may contains one or more S46 Container option(s), A variable field that may contains one or more S46 Container option(s),
defined in Section 4.2 defined in Section 4.2
4.2. S46 Container Options 4.2. S46 Container Options
Depending on the deployment scenario, a client might request for more Depending on the deployment scenario, a client might request for more
than one transition mechanism at a time, at least one S46 Container than one transition mechanism at a time, at least one S46 Container
option MUST be included in one MAP-Configuration Attribute. option MUST be included in one Softwire46-Configuration Attribute.
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 | | | Type | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
1 MAP-E Container Option 1 MAP-E Container Option
2 MAP-T Container Option 2 MAP-T Container Option
3 Lightweight 4over6 Container Option 3 Lightweight 4over6 Container Option
Length Length
2 + the length of the sub options 2 + the length of the sub options specified in octects
Sub Option Sub Option
A variable field that contains necessary sub options defined in A variable field that contains necessary sub options defined in
Section 4.3 and zero or several optional sub options, defined Section 4.3 and zero or several optional sub options, defined
in Section 4.4 in Section 4.4.
4.3. Sub Options for S46 Container Option 4.3. Sub Options for S46 Container Option
4.3.1. S46-Rule Sub Option 4.3.1. S46-Rule Sub Option
Depending on deployment scenario, one Basic Mapping Rule and zero or Depending on deployment scenario, one Basic Mapping Rule and zero or
more Forwarding Mapping Rules MUST be included in one MAP-E or MAP-T more Forwarding Mapping Rules MUST be included in one MAP-E or MAP-T
Container Option. Container Option.
0 1 2 3 0 1 2 3
skipping to change at page 7, line 47 skipping to change at page 8, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
1 Basic Mapping Rule (Not Forwarding Mapping Rule) 1 Basic Mapping Rule (Not Forwarding Mapping Rule)
2 Forwarding Mapping Rule (Not Basic Mapping Rule) 2 Forwarding Mapping Rule (Not Basic Mapping Rule)
3 Basic & Forwarding Mapping Rule 3 Basic & Forwarding Mapping Rule
SubLen SubLen
2 + the length of the sub options 2 + the length of the sub options specified in octects
Sub Option Sub Option
A variable field that contains sub options defined in A variable field that contains sub options defined in
Section 4.4 Section 4.4
4.3.2. S46-BR Sub Option 4.3.2. S46-BR Sub Option
There MUST be atleast one S46-BR Sub Option included in each MAP-E There MUST be atleast one S46-BR Sub Option included in each MAP-E
Container Option or Lightweight 4over6 Container Option. Container Option or Lightweight 4over6 Container Option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | BR-ipv6-address | | SubType | SubLen | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| BR-ipv6-address | | |
+ + | BR-ipv6-address |
| BR-ipv6-address | | |
+ + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BR-ipv6-address | | |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ SubType
SubType 4 (SubType number, for the S46-BR sub option)
4 (SubType number, for the S46-BR sub option) SubLen
SubLen 18 (the length of the S46-BR sub option)
18 (the length of the S46-BR sub option) BR-ipv6-address
BR-ipv6-address a fixed-length field of 16 octects that specifies the IPv6 address
a 128-bits field that specifies the IPv6 address for the BR. for the S46 BR.
4.3.3. S46-DMR Sub Option 4.3.3. S46-DMR Sub Option
There MUST be exactly one S46-DMR Sub Option included in one MAP-T There MUST be exactly one S46-DMR Sub Option included in one MAP-T
Container Option. Container Option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen |dmr-prefix6-len|dmr-ipv6-prefix| | SubType | SubLen |dmr-prefix6-len| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| dmr-ipv6-prefix | | dmr-ipv6-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5 (SubType number, for the S46-DMR sub option) SubType
SubLen 5 (SubType number, for the S46-DMR sub option)
8 (the length of the Rule-IPv4-Prefix6 sub option) SubLen
dmr-prefix6-len 3 + length of dmr-ipv6-prefix specified in octects
length of the IPv6 prefix, specified in the dmr-ipv6-prefix dmr-prefix6-len
field, expressed in bits 8 bits longs; expresses the bitmask length of the IPv6
dmr-ipv6-prefix prefix specified in the dmr-ipv6-prefix field. Allowed values range
a 32-bits field that specifies an IPv6 prefix that appears in from 0-96.
the Default Mapping Rule dmr-ipv6-prefix
a variable-length field specifying the IPv6 prefix or address
for the BR. This field is right-padded with zeros to the nearest
octect boundary when dmr-prefix6-len is not divisible by 8.
4.3.4. S46-V4V6Bind Sub Option 4.3.4. S46-V4V6Bind Sub Option
There MUST be atmost one S46-RULE Sub Option included in each There MUST be atmost one S46-V4V6Bind Sub Option included in each
Lightweight 4over6 Container Option. Lightweight 4over6 Container Option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | ipv4-address | | SubType | SubLen | ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued) |bindprefix6-len| | | (Continued) |bindprefix6-len| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| bind-ipv6-prefix | | bind-ipv6-prefix |
+ + | (variable length) |
| bind-ipv6-prefix | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ +
| bind-ipv6-prefix |
+ +-+-+-+-+-+-+-+-+
| bind-ipv6-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
6 (SubType number, for the S46-V4V6Bind sub option) 6 (SubType number, for the S46-V4V6Bind sub option)
SubLen SubLen
23 (the length of the S46-V4V6Bind sub option) the length of the S46-V4V6Bind sub option expressed in octects
ipv4-address ipv4-address
a 32-bits field that specifies an IPv4 address that appears in a 32-bits field that specifies an IPv4 address that appears in
the V4V6Bind Option the V4V6Bind Option
bindprefix6-len bindprefix6-len
length of the IPv6 prefix, specified in the bind-ipv6-prefix 8 bits long; expresses the bitmask length of the IPv6 prefix
field, expressed in bits specified in the bind-ipv6-prefix field. Allowed values range from
bind-ipv6-prefix 0 to 96.
a 128-bits field that specifies an IPv6 prefix that appears in bind-ipv6-prefix
the V4V6Bind Option a variable-length field specifying the IPv6 prefix or address for
the S46 CE. This field is right-padded with zeros to the nearest octect
boundary when bindprefix6-len is not divisible by 8.
4.3.5. S46-PORTPARAMS Sub Option 4.3.5. S46-PORTPARAMS Sub Option
The S46-PORTPARAMS sub option specifies optional port set information The S46-PORTPARAMS sub option specifies optional port set information
that MAY be provided to CEs. The S46-PORTPARAMS sub option canbe that MAY be provided to CEs. The S46-PORTPARAMS sub option canbe
included optionally by each type of S46 Container Option. included optionally by each type of S46 Container Option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 23 skipping to change at page 11, line 23
SubType SubType
7 (SubType number, for the S46-PORTPARAMS Sub Option sub option) 7 (SubType number, for the S46-PORTPARAMS Sub Option sub option)
SubLen SubLen
6 (the length of the S46-PORTPARAMS Sub Option sub option) 6 (the length of the S46-PORTPARAMS Sub Option sub option)
PSID Offset PSID Offset
8 bits long field that specifies the numeric value for the S46 algorithm's excluded 8 bits long field that specifies the numeric value for the S46 algorithm's excluded
port range/ offset bits (a bits), as per Section 5.1 of RFC 7597. port range/ offset bits (a bits), as per Section 5.1 of RFC 7597.
Allowed values are between 0 and 15. Default values for this field are specific to the Allowed values are between 0 and 15. Default values for this field are specific to the
Softwire mechanism being implemented and are defined in the relevant specification document. Softwire mechanism being implemented and are defined in the relevant specification document.
PSID-len PSID-len
Bit length value of the number of significant bits in the PSID 8 bits long; specifies the number of significant bits in the PSID
field. (also known as 'k'). When set to 0, the PSID field is to field. (also known as 'k'). When set to 0, the PSID field is to
be ignored. After the first 'a' bits, there are k bits in the be ignored. After the first 'a' bits, there are k bits in the
port number representing valid of PSID. Subsequently, the port number representing valid of PSID. Subsequently, the
address sharing ratio would be 2 ^k. address sharing ratio would be 2 ^k.
PSID (Port-set ID) PSID (Port-set ID)
Explicit 16-bit (unsigned word) PSID value. The PSID value Explicit 16-bit (unsigned word) PSID value. The PSID value
algorithmically identifies a set of ports assigned to a CE. The algorithmically identifies a set of ports assigned to a CE. The
first k-bits on the left of this 2-octets field is the PSID first k-bits on the left of this 2-octets field is the PSID
value. The remaining (16-k) bits on the right are padding zeros. value. The remaining (16-k) bits on the right are padding zeros.
skipping to change at page 11, line 16 skipping to change at page 12, line 16
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | Reserved | prefix6-len | | SubType | SubLen | Reserved | prefix6-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| rule-ipv6-prefix | | rule-ipv6-prefix |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
8 (SubType number, for the Rule-IPv6-Prefix6 sub option) 9 (SubType number, for the Rule-IPv6-Prefix6 sub option)
SubLen SubLen
20 (the length of the Rule-IPv6-Prefix6 sub option) 20 (the length of the Rule-IPv6-Prefix6 sub option)
Reserved Reserved
Reserved for future usage. It should be set to all zero Reserved for future usage. It should be set to all zero
prefix6-len prefix6-len
length of the IPv6 prefix, specified in the rule-ipv6-prefix length of the IPv6 prefix, specified in the rule-ipv6-prefix
field, expressed in bits field, expressed in bits
rule-ipv6-prefix rule-ipv6-prefix
a 128-bits field that specifies an IPv6 prefix that appears in a 128-bits field that specifies an IPv6 prefix that appears in
a MAP rule a MAP rule
skipping to change at page 11, line 39 skipping to change at page 12, line 39
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | Reserved | prefix4-len | | SubType | SubLen | Reserved | prefix4-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| rule-ipv4-prefix | | rule-ipv4-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
9 (SubType number, for the Rule-IPv4-Prefix6 sub option) 10 (SubType number, for the Rule-IPv4-Prefix6 sub option)
SubLen SubLen
8 (the length of the Rule-IPv4-Prefix6 sub option) 8 (the length of the Rule-IPv4-Prefix6 sub option)
Reserved Reserved
Reserved for future usage. It should be set to all zero Reserved for future usage. It should be set to all zero
Prefix4-len Prefix4-len
length of the IPv6 prefix, specified in the rule-ipv6-prefix length of the IPv6 prefix, specified in the rule-ipv6-prefix
field, expressed in bits field, expressed in bits
rule-ipv4-prefix rule-ipv4-prefix
a 32-bits field that specifies an IPv4 prefix that appears in a 32-bits field that specifies an IPv4 prefix that appears in
a MAP rule a MAP rule
4.4.3. EA Length Sub Option 4.4.3. EA Length Sub Option
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | EA-len | | SubType | SubLen | EA-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
10 (SubType number, for the EA Length sub option) 11 (SubType number, for the EA Length sub option)
SubLen SubLen
4 (the length of the EA Length sub option) 4 (the length of the EA Length sub option)
EA-len EA-len
16 bits long field that specifies the Embedded-Address (EA) 16 bits long field that specifies the Embedded-Address (EA)
bit length. Allowed values range from 0 to 48 bit length. Allowed values range from 0 to 48
4.5. Softwire46 Sub Options Encapsulation 4.5. Softwire46 Sub Options Encapsulation
The table below shows which encapsulated Sub Options are mandatory, The table below shows which encapsulated Sub Options are mandatory,
optional, or not permitted for each defined S46 Container Option. optional, or not permitted for each defined S46 Container Option.
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| Sub Option | MAP-E | MAP-T | Lightweight 4over6 | | Sub Option | MAP-E | MAP-T | Lightweight 4over6 |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-Rule | M | M | N/P |
+----------------+-------+-------+--------------------+
| S46-BR | M | N/P | M | | S46-BR | M | N/P | M |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-Rule | M | M | N/P |
+----------------+-------+-------+--------------------+
| S46-DMR | N/P | M | N/P | | S46-DMR | N/P | M | N/P |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-V4V6Bind | N/P | N/P | O | | S46-V4V6Bind | N/P | N/P | O |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-PORTPARAMS | O | O | O | | S46-PORTPARAMS | O | O | O |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-Option-Code| N/P | N/P | N/P |
+----------------+-------+-------+--------------------+
M - Maandabdatory, O - Optional, N/P - Not Permitted M - Maandabdatory, O - Optional, N/P - Not Permitted
4.6. Table of attributes 4.6. Softwire46-Priority Attribute
The S46-Priority 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 | S46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | S46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBD
Length
2 + the length of the S46-option-code(s) specified in octects
S46-option-code
16-bit IANA-registered option code of the DHCPv6 option that is used to identify the
softwire mechanisms. S46 mechanisms are prioritized in the appearance order of the
S46-option-code(s) in the Softwire46-Priority Attribute. A Softwire46-Priority Attribute
MUST contain at least one S46-option-code.
4.7. Table of attributes
The following table provides a guide to which attributes may be found The following table provides a guide to which attributes may be found
in which kinds of packets, and in what quantity. in which kinds of packets, and in what quantity.
Request Accept Reject Challenge Accounting # Attribute Request Accept Reject Challenge Accounting # Attribute
Request Request
0-1 0-1 0 0 0-1 TBD1 Softwire46- 0-1 0-1 0 0 0-1 TBD1 Softwire46-
Configuration Configuration
0-1 0-1 0 0 0-1 TBD2 Softwire46-
Priority
0-1 0-1 0 0 0-1 1 User-Name 0-1 0-1 0 0 0-1 1 User-Name
0-1 0 0 0 0 2 User-Password 0-1 0 0 0 0 2 User-Password
0-1 0-1 0 0 0-1 6 Service-Type 0-1 0-1 0 0 0-1 6 Service-Type
0-1 0-1 0-1 0-1 0-1 80 Message-Authenticator 0-1 0-1 0-1 0-1 0-1 80 Message-Authenticator
The following table defines the meaning of the above table entries. The following table defines the meaning of the above table entries.
0 This attribute MUST NOT be present in packet. 0 This attribute MUST NOT be present in packet.
0+ Zero or more instances of this attribute MAY be present in 0+ Zero or more instances of this attribute MAY be present in
packet. packet.
skipping to change at page 13, line 30 skipping to change at page 15, line 11
packet. packet.
1 Exactly one instance of this attribute MUST be present in 1 Exactly one instance of this attribute MUST be present in
packet. packet.
5. Diameter Considerations 5. Diameter Considerations
S46 Configuration using Diameter [RFC6733] is specified in [RFC7678]. S46 Configuration using Diameter [RFC6733] is specified in [RFC7678].
6. IANA Considerations 6. IANA Considerations
This document requires the assignment of one new RADIUS Attributes This document requires the assignment of two new RADIUS Attributes
Type in the "Radius Types" registry (currently located at Type in the "Radius Types" registry (currently located at
http://www.iana.org/assignments/radius-types for the following http://www.iana.org/assignments/radius-types for the following
attributes: attributes:
o Softwire46-Configuration Attribute TBD1 o Softwire46-Configuration Attribute TBD1
o Softwire46-Priority Attribute TBD2
IANA should allocate the numbers from the standard RADIUS Attributes IANA should allocate the numbers from the standard RADIUS Attributes
space using the "IETF Review" policy [RFC5226]. space using the "IETF Review" policy [RFC5226].
7. Security Considerations 7. 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].
A malicious user may use MAC address proofing and/or dictionary A malicious user may use MAC address spoofing on the shared password
attack on the shared password that has been preconfigured on the that has been preconfigured on the DHCPv6 server to get unauthorized
DHCPv6 server to get unauthorized configuration information. configuration information.
Security considerations for MAP specific between MAP CE and BNG are Security considerations for MAP specific between the MAP CE and the
discussed in [RFC7597]. Security considerations for Lightweight BNG are discussed in [RFC7597]. Security considerations for
4over6 are discussed in [RFC7596]. Furthermore, generic DHCPv6 Lightweight 4over6 are discussed in [RFC7596]. Security
security mechanisms can be applied DHCPv6 intercommunication between considerations for DHCPv6-Based S46 Prioritization Mechanism are
CE and BNG. discussed in [RFC8026]. Furthermore, generic DHCPv6 security
mechanisms can be applied DHCPv6 intercommunication between the CE
and the BNG.
Security considerations for the Diameter protocol are discussed in Security considerations for the Diameter protocol are discussed in
[RFC6733]. [RFC6733].
8. Acknowledgements 8. 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, and Suresh Krishnan for this document. This Lothberg, Wojciech Dec, and Suresh Krishnan for this document. This
document was merged with draft-sun-softwire-lw4over6-radext-01, document was merged with draft-sun-softwire-lw4over6-radext-01,
thanks to everyone who contributed to this draft. thanks to everyone who contributed to this draft.
skipping to change at page 15, line 19 skipping to change at page 17, line 5
[RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines", [RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines",
BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011, BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011,
<http://www.rfc-editor.org/info/rfc6158>. <http://www.rfc-editor.org/info/rfc6158>.
[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User
Service (RADIUS) Protocol Extensions", RFC 6929, Service (RADIUS) Protocol Extensions", RFC 6929,
DOI 10.17487/RFC6929, April 2013, DOI 10.17487/RFC6929, April 2013,
<http://www.rfc-editor.org/info/rfc6929>. <http://www.rfc-editor.org/info/rfc6929>.
[RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6
Softwire Customer Premises Equipment (CPE): A DHCPv6-Based
Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026,
November 2016, <http://www.rfc-editor.org/info/rfc8026>.
9.2. Informative References 9.2. Informative References
[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
Implementation in Roaming", RFC 2607, Implementation in Roaming", RFC 2607,
DOI 10.17487/RFC2607, June 1999, DOI 10.17487/RFC2607, June 1999,
<http://www.rfc-editor.org/info/rfc2607>. <http://www.rfc-editor.org/info/rfc2607>.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the [RFC4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, Internet Protocol", RFC 4301, DOI 10.17487/RFC4301,
December 2005, <http://www.rfc-editor.org/info/rfc4301>. December 2005, <http://www.rfc-editor.org/info/rfc4301>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011,
<http://www.rfc-editor.org/info/rfc6333>.
[RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to [RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to
the IPv4 Address Shortage", RFC 6346, the IPv4 Address Shortage", RFC 6346,
DOI 10.17487/RFC6346, August 2011, DOI 10.17487/RFC6346, August 2011,
<http://www.rfc-editor.org/info/rfc6346>. <http://www.rfc-editor.org/info/rfc6346>.
[RFC6519] Maglione, R. and A. Durand, "RADIUS Extensions for Dual-
Stack Lite", RFC 6519, DOI 10.17487/RFC6519, February
2012, <http://www.rfc-editor.org/info/rfc6519>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", RFC 6733, Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012, DOI 10.17487/RFC6733, October 2012,
<http://www.rfc-editor.org/info/rfc6733>. <http://www.rfc-editor.org/info/rfc6733>.
[RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and
P. Selkirk, "Port Control Protocol (PCP)", RFC 6887,
DOI 10.17487/RFC6887, April 2013,
<http://www.rfc-editor.org/info/rfc6887>.
[RFC7341] Sun, Q., Cui, Y., Siodelski, M., Krishnan, S., and I.
Farrer, "DHCPv4-over-DHCPv6 (DHCP 4o6) Transport",
RFC 7341, DOI 10.17487/RFC7341, August 2014,
<http://www.rfc-editor.org/info/rfc7341>.
[RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. [RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I.
Farrer, "Lightweight 4over6: An Extension to the Dual- Farrer, "Lightweight 4over6: An Extension to the Dual-
Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596, Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596,
July 2015, <http://www.rfc-editor.org/info/rfc7596>. July 2015, <http://www.rfc-editor.org/info/rfc7596>.
[RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., [RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, Ed., "Mapping of Address and Murakami, T., and T. Taylor, Ed., "Mapping of Address and
Port with Encapsulation (MAP-E)", RFC 7597, Port with Encapsulation (MAP-E)", RFC 7597,
DOI 10.17487/RFC7597, July 2015, DOI 10.17487/RFC7597, July 2015,
<http://www.rfc-editor.org/info/rfc7597>. <http://www.rfc-editor.org/info/rfc7597>.
 End of changes. 57 change blocks. 
200 lines changed or deleted 245 lines changed or added

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