draft-ietf-softwire-map-radius-06.txt   draft-ietf-softwire-map-radius-07.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: December 19, 2016 CNNIC Expires: January 8, 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
June 17, 2016 July 7, 2016
RADIUS Attribute for MAP RADIUS Attribute for Softwire
draft-ietf-softwire-map-radius-06 draft-ietf-softwire-map-radius-07
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 Authentication
Authorization and Accounting (AAA) servers while user configuration Authorization and Accounting (AAA) servers while user configuration
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 December 19, 2016. This Internet-Draft will expire on January 8, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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. MAP-Configuration Attribute . . . . . . . . . . . . . . . 6 4.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6
4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 7 4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . 8 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 . . . . . . . . . . . . . . . . . 9 4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 8
4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 10 4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 9
4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 10 4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 9
4.4. Sub Options for S46-RULE Sub Option . . . . . . . . . . . 11 4.4. Sub Options for S46-RULE Sub Option . . . . . . . . . . . 10
4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 11 4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 10
4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 12 4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 11
4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 13 4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 12
4.5. Table of attributes . . . . . . . . . . . . . . . . . . . 13 4.5. Softwire46 Sub Options Encapsulation . . . . . . . . . . 12
4.6. Table of attributes . . . . . . . . . . . . . . . . . . . 12
5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 13 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . 15
Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 17 Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
Recently providers start to deploy IPv6 and consider how to transit Recently providers start to deploy IPv6 and consider how to transit
to IPv6. Many transition mechanisms have been proposed for running to IPv6. Many transition mechanisms have been proposed for running
IPv4 over IPv6-only infrastructure, including MAP-E, MAP-T, and IPv4 over IPv6-only infrastructure, including MAP-E, MAP-T, and
Lightweight 4over6. Mapping of Address and Port with Lightweight 4over6. Mapping of Address and Port with
Encapsulation(MAP-E)[RFC7597], Mapping of Address and Port with using Encapsulation(MAP-E)[RFC7597], Mapping of Address and Port with using
Translation(MAP-T)[RFC7599] are stateless mechanisms for running IPv4 Translation(MAP-T)[RFC7599] are stateless mechanisms for running IPv4
over IPv6-only infrastructure. Lightweight 4over6[RFC7596] is a hub- over IPv6-only infrastructure. Lightweight 4over6[RFC7596] is a hub-
and-spoke IPv4-over-IPv6 tunneling mechanism, with complete and-spoke IPv4-over-IPv6 tunneling mechanism, with complete
independence of IPv4 and IPv6 addressing. They provide both IPv4 and independence of IPv4 and IPv6 addressing. They provide both IPv4 and
IPv6 connectivity services simultaneously during the IPv4/IPv6 co- IPv6 connectivity services simultaneously during the IPv4/IPv6 co-
existing period. MAP-E, MAP-T and Lightweight 4over6 have adopted existing period. MAP-E, MAP-T and Lightweight 4over6 have adopted
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as
auto-configuring protocol. The Customer Edge (CE) uses DHCPv6 auto-configuring protocol. The Customer Edge (CE) uses DHCPv6
options to discover the Border Relay (BR) and get MAP configurations. options to discover the Border Relay (BR) and get S46 configurations.
In many networks, user configuration information may be stored by AAA In many networks, user configuration information may be stored in AAA
(Authentication, Authorization, and Accounting) servers. Current AAA (Authentication, Authorization, and Accounting) servers. Current AAA
servers communicate using the Remote Authentication Dial In User servers communicate using the Remote Authentication Dial In User
Service (RADIUS) [RFC2865] protocol. In a fixed line broadband 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 MAP configuration information is stored in AAA servers and Since the S46 configuration information is stored in AAA servers and
user configuration is mainly transmitted through DHCPv6 protocol user configuration is mainly transmitted through DHCPv6 protocol
between BNGs and hosts/CEs, new RADIUS attributes are needed to between BNGs and hosts/CEs, new RADIUS attributes are needed to
propagate the information from AAA servers to BNGs. The RADIUS propagate the information from AAA servers to BNGs. The RADIUS
attributes designed in this document are especially for the MAP- attributes designed in this document are especially for the MAP-
E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], providing E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], providing
enough information to form the correspondent DHCPv6 configuration enough information to form the correspondent DHCPv6 configuration
options[RFC7598]. 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
cooperate to provide CE with MAP configuration information. cooperate to provide CE with MAP configuration information. The BNG
acts as a RADIUS client and as a DHCPv6 server.
CE BNG AAA Server CE BNG AAA Server
| | | | | |
|------DHCPv6 Solicit----->| | |-----1.DHCPv6 Solicit----->| |
| (Option Request w/container option) | | (ORO w/container option) | |
| |-------Access-Request------->| | |-------2.Access-Request------->|
| | (Map attriubte) | | | (S46-Configuration attriubte) |
| | | | | |
| |<-------Access-Accept--------| | |<------3.Access-Accept---------|
|<---DHCPv6 Advertisement--| (MAP attriubte) | |<--4.DHCPv6 Advertisement--| (S46-Configuration attriubte) |
| | | | | |
|------DHCPv6 Request---->| | |-----5.DHCPv6 Request---->| |
| (container Option) | | | (container Option) | |
|<---- -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
The BNG acts as a RADIUS client and as a DHCPv6 server. First, CE 1. First, CE MAY initiate a DHCPv6 Solicit message that includes an
MAY initiate a DHCPv6 Solicit message that includes an Option Request Option Request option(6) [RFC3315] with the S46 Container options as
option (6) [RFC3315] with the Container options as defined defined in[RFC7598]. OPTION_S46_CONT_MAPE should be included for
in[RFC7598]. OPTION_S46_CONT_MAPE should be included for MAP- MAP-E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599], and
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]. But note that
the ORO (Option Request option) with the MAP option could be optional the ORO (Option Request option) with the S46 Container options could
if the network was planned as MAP-enabled as default. When BNG be optional if the network was planned as S46-enabled as default.
receives the SOLICIT, it SHOULD initiates radius 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 RADIUS server and the
User-password attribute (2) SHOULD be filled by the shared password
that has been preconfigured on the DHCPv6 server, requesting
authentication as defined in [RFC2865] with the corresponding MAP-
Configuration Attribute, which will be defined in the next Section.
If the authentication request is approved by the AAA server, an 2. When BNG receives the SOLICIT, it SHOULD initiate the radius
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
RADIUS server and the User-password attribute (2) SHOULD be filled by
the shared password that has been preconfigured on the DHCPv6 server,
requesting authentication as defined in [RFC2865] with the
corresponding Softwire46-Configuration Attribute, which will be
defined in the next Section.
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
MAP-Configuration Attribute. After receiving the Access-Accept Softwire46-Configuration Attribute.
message with the corresponding Attribute, the BNG SHOULD respond the
user an Advertisement message. Then the user can requests for the 4. After receiving the Access-Accept message with the corresponding
corresponding Container option, and the BNG SHOULD reply the user Attribute, the BNG SHOULD respond the user an Advertisement message.
with the message containing the Container option. The recommended
5. After receiving the Advertise message, the user can request for
the corresponding S46 Container option, by including the S46
Container option in the Request Message.
6. After receiving the client's Request messsage, containing the
corresponding S46 Container option the BNG SHOULD reply the user with
the message containing the S46 Container option. The recommended
format of the MAC address is defined as Calling-Station-Id format of the MAC address is defined as Calling-Station-Id
(Section 3.20 in [RFC3580] without the SSID (Service Set Identifier) (Section 3.20 in [RFC3580] without the SSID (Service Set Identifier)
portion. 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 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 AAA server and lwAFTR,
the AAA server does not need to configure lwAFTR anymore. Otherwise, the AAA server does not need to configure lwAFTR anymore. Otherwise,
if the bindings are locally creately in AAA server on-demand, it if the bindings are locally creately in AAA server on-demand, it
should inform the lwAFTR with the subscriber's binding state, to should inform the lwAFTR with the subscriber's binding state, to
synchronise the binding information of the lwB4 with the lwAFTR. In synchronise the binding information of the lwB4 with the lwAFTR. In
the Lightweight 4over6 scenario, the lwB4 could also be configured the Lightweight 4over6 scenario, the lwB4 could also be configured
through DHCPv4-over-DHCPv6 [RFC7341] as well as PCP [RFC6887], in 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 which the lwB4 act a PCP client and the BNG act as both a Radius
client and a PCP server. client and a PCP server.
Figure 2 describes another scenario, in which the authorization The authorization operation could also be done independently after
operation is not coupled with authentication. Authorization is done the authentication process. In such scenario, after the
independently after the authentication process. As similar to above authentication operation, the client MAY initiate a DHCPv6 Request
scenario, the ORO with the corresponding MAP option in the initial message that includes the corresponding S46 Container options. As
DHCPv6 request could be optional if the network was planned as MAP- similar to above scenario, the ORO with the corresponding S46
enabled as default. Container option in the initial DHCPv6 request could be optional if
the network was planned as S46-enabled as default. When BNG receives
CE BNG AAA Server the DHCPv6 Request, it SHOULD initiate the radius Access-Request
| | | message, which MUST contain a Service-Type attribute (6) with the
|------DHCPv6 Request---->| | value Authorize Only (17), the corresponding Softwire46-Configuration
|(Option Request w/container option) | Attribute, and a State attribute obtained from the previous
| |-------Access-Request------->| authentication process according to [RFC5080]. If the authorization
| | (MAP attribute) | request is approved by the AAA server, an Access-Accept message MUST
| | | be acknowledged with the corresponding Softwire46-Configuration
| |<-------Access-Accept--------| Attribute. The BNG SHOULD then send the DHCPv6 Reply message
| | (MAP attribute) | containing the S46 Container option.
|<-----DHCPv6 Reply--------| |
| (container option) | |
| | |
DHCPv6 RADIUS
Figure 2: the cooperation between DHCPv6 and RADIUS decoupled with
RADIUS authentication
In the above mentioned scenario, the Access-Request packet SHOULD
contain a Service-Type attribute (6) with the value Authorize Only
(17); thus, according to [RFC5080], the Access-Request packet MUST
contain a State attribute that obtained from the previous
authentication process.
In both above-mentioned scenarios, Message-authenticator (type 80) In both above-mentioned scenarios, Message-authenticator (type 80)
[RFC2869] SHOULD be used to protect both Access-Request and Access- [RFC2869] SHOULD be used to protect both Access-Request and Access-
Accept messages. Accept messages.
After receiving the corresponding MAP-Configuration Attribute in the
initial Access-Accept, the BNG SHOULD store the received MAP
configuration parameters locally. When the CE sends a DHCPv6 Request
message to request an extension of the lifetimes for the assigned
address, the BNG does not have to initiate a new Access-Request
towards the AAA server to request the MAP configuration parameters.
The BNG could retrieve the previously stored MAP configuration
parameters and use them in its reply.
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 MAP 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 MAP configuration or if the BNG receives an configured default S46 configuration or if the BNG receives an
Access-Reject, the MAP 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 S46 Attributes which are used in the MAP
scenario. The attribute design follows [RFC6158] and refers scenario. The attribute design follows [RFC6158] and refers
to[RFC6929]. to[RFC6929].
The S46 attributes are designed following the simplify principle. The S46 attributes are designed following the simplify principle.
Different sub options are required for each type of S46 Container Different sub options are required for each type of S46 Container
option. option.
4.1. MAP-Configuration Attribute 4.1. Softwire46-Configuration Attribute
The MAP-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) +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 31 skipping to change at page 8, line 7
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
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 one S46 There MUST be atleast one S46-BR Sub Option included in each MAP-E
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 |
+ + + +
skipping to change at page 10, line 30 skipping to change at page 9, line 30
+ + + +
| bind-ipv6-prefix | | 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) 23 (the length of the S46-V4V6Bind sub option)
Prefix4-len
length of the IPv4 prefix, specified in the rule-ipv4-prefix
field, expressed in bits
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 length of the IPv6 prefix, specified in the bind-ipv6-prefix
field, expressed in bits field, expressed in bits
rule-ipv6-prefix bind-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
the V4V6Bind Option the V4V6Bind Option
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
skipping to change at page 13, line 21 skipping to change at page 12, line 21
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
10 (SubType number, for the EA Length sub option) 10 (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. Table of attributes 4.5. Softwire46 Sub Options Encapsulation
The table below shows which encapsulated Sub Options are mandatory,
optional, or not permitted for each defined S46 Container Option.
+----------------+-------+-------+--------------------+
| Sub Option | MAP-E | MAP-T | Lightweight 4over6 |
+----------------+-------+-------+--------------------+
| S46-Rule | M | M | N/P |
+----------------+-------+-------+--------------------+
| S46-BR | M | N/P | M |
+----------------+-------+-------+--------------------+
| S46-DMR | N/P | M | N/P |
+----------------+-------+-------+--------------------+
| S46-V4V6Bind | N/P | N/P | O |
+----------------+-------+-------+--------------------+
| S46-PORTPARAMS | O | O | O |
+----------------+-------+-------+--------------------+
M - Maandabdatory, O - Optional, N/P - Not Permitted
4.6. 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 MAP- 0-1 0-1 0 0 0-1 TBD1 Softwire46-
Configuration Configuration
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.
0-1 Zero or one instance of this attribute MAY be present in 0-1 Zero or one instance of this attribute MAY be present in
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
This attribute is usable within either RADIUS or Diameter [RFC6733]. S46 Configuration using Diameter [RFC6733] is specified in [RFC7678].
Since the Attributes defined in this document will be allocated from
the standard RADIUS type space, no special handling is required by
Diameter entities.
6. IANA Considerations 6. IANA Considerations
This document requires the assignment of two new RADIUS Attributes This document requires the assignment of one new RADIUS Attributes
Types 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 MAP-Configuration TBD1 o Softwire46-Configuration Attribute TBD1
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
In softwire scenarios, both CE and BNG are within a provider network,
which can be considered as a closed network and a lower security
threat environment. A similar consideration can be applied to the
RADIUS message exchange between BNG and the AAA server.
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 proofing and/or dictionary
attack on the shared password that has been preconfigured on the attack on the shared password that has been preconfigured on the
DHCPv6 server to get unauthorized configuration information. DHCPv6 server to get unauthorized configuration information.
Security considerations for MAP specific between MAP CE and BNG are Security considerations for MAP specific between MAP CE and BNG are
skipping to change at page 15, line 19 skipping to change at page 14, line 34
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, DOI 10.17487/RFC2865, June 2000, RFC 2865, DOI 10.17487/RFC2865, June 2000,
<http://www.rfc-editor.org/info/rfc2865>. <http://www.rfc-editor.org/info/rfc2865>.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,
<http://www.rfc-editor.org/info/rfc2869>.
[RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",
RFC 3162, DOI 10.17487/RFC3162, August 2001, RFC 3162, DOI 10.17487/RFC3162, August 2001,
<http://www.rfc-editor.org/info/rfc3162>. <http://www.rfc-editor.org/info/rfc3162>.
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <http://www.rfc-editor.org/info/rfc3315>. 2003, <http://www.rfc-editor.org/info/rfc3315>.
[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese,
skipping to change at page 16, line 10 skipping to change at page 15, line 26
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>.
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>.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,
<http://www.rfc-editor.org/info/rfc2869>.
[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>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
skipping to change at page 17, line 16 skipping to change at page 16, line 27
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,
<http://www.rfc-editor.org/info/rfc7598>. <http://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, <http://www.rfc-editor.org/info/rfc7599>. 2015, <http://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,
<http://www.rfc-editor.org/info/rfc7678>.
[RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary", [RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary",
RFC 7749, DOI 10.17487/RFC7749, February 2016, RFC 7749, DOI 10.17487/RFC7749, February 2016,
<http://www.rfc-editor.org/info/rfc7749>. <http://www.rfc-editor.org/info/rfc7749>.
Additional Authors Additional Authors
Qiong Sun Qiong Sun
China Telecom China Telecom
Beijing China Beijing China
Email: sunqiong@ctbri.com.cn Email: sunqiong@ctbri.com.cn
 End of changes. 36 change blocks. 
129 lines changed or deleted 133 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/