draft-ietf-softwire-map-radius-05.txt   draft-ietf-softwire-map-radius-06.txt 
Softwire S. Jiang Softwire S. Jiang, Ed.
Internet-Draft Huawei Technologies Co., Ltd Internet-Draft Huawei Technologies Co., Ltd
Intended status: Standards Track Y. Fu Intended status: Standards Track Y. Fu, Ed.
Expires: June 25, 2016 CNNIC Expires: December 19, 2016 CNNIC
B. Liu B. Liu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
P. Deacon P. Deacon
IEA Software, Inc. IEA Software, Inc.
December 23, 2015 C. Xie
China Telecom
T. Li
Tsinghua University
June 17, 2016
RADIUS Attribute for MAP RADIUS Attribute for MAP
draft-ietf-softwire-map-radius-05 draft-ietf-softwire-map-radius-06
Abstract Abstract
Mapping of Address and Port (MAP) is a stateless mechanism for IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6
running IPv4 over IPv6-only infrastructure. It provides both IPv4 connectivity services simultaneously during the IPv4/IPv6 co-existing
and IPv6 connectivity services simultaneously during the IPv4/IPv6 period. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
co-existing period. The Dynamic Host Configuration Protocol for IPv6 options have been defined to configure Customer Edge (CE) in MAP-E,
(DHCPv6) MAP options has been defined to configure MAP Customer Edge MAP-T, and Lightweight 4over6. However, in many networks, the
(CE). However, in many networks, the configuration information may configuration information may be stored in Authentication
be stored in Authentication Authorization and Accounting (AAA) Authorization and Accounting (AAA) servers while user configuration
servers while user configuration is mainly from Broadband Network is mainly from Broadband Network Gateway (BNG) through DHCPv6
Gateway (BNG) through DHCPv6 protocol. This document defines a protocol. This document defines a Remote Authentication Dial In User
Remote Authentication Dial In User Service (RADIUS) attribute that Service (RADIUS) attribute that carries CE configuration information
carries MAP configuration information from AAA server to BNG. The from AAA server to BNG.
MAP RADIUS attribute are designed following the simplify principle.
It provides just enough information to form the correspondent DHCPv6
MAP option.
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 June 25, 2016. This Internet-Draft will expire on December 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. MAP 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. MAP-Configuration Attribute . . . . . . . . . . . . . . . 6
4.2. MAP Rule Options . . . . . . . . . . . . . . . . . . . . 6 4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 7
4.3. Sub Options for MAP Rule Option . . . . . . . . . . . . . 7 4.3. Sub Options for S46 Container Option . . . . . . . . . . 7
4.3.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 7 4.3.1. S46-Rule Sub Option . . . . . . . . . . . . . . . . . 8
4.3.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 8 4.3.2. S46-BR Sub Option . . . . . . . . . . . . . . . . . . 8
4.3.3. EA Length Sub Option . . . . . . . . . . . . . . . . 9 4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 9
4.3.4. BR-IPv6-Address Sub Option . . . . . . . . . . . . . 9 4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 10
4.3.5. PSID Sub Option . . . . . . . . . . . . . . . . . . . 9 4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 10
4.3.6. PSID Length Sub Option . . . . . . . . . . . . . . . 10 4.4. Sub Options for S46-RULE Sub Option . . . . . . . . . . . 11
4.3.7. PSID Offset Sub Option . . . . . . . . . . . . . . . 10 4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 11
4.4. Table of attributes . . . . . . . . . . . . . . . . . . . 11 4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 12
5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 11 4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 4.5. Table of attributes . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 15
Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
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. Mapping of Address and Port (MAP)[I-D.ietf-softwire-map] is to IPv6. Many transition mechanisms have been proposed for running
a stateless mechanism for running IPv4 over IPv6-only infrastructure. IPv4 over IPv6-only infrastructure, including MAP-E, MAP-T, and
It provides both IPv4 and IPv6 connectivity services simultaneously Lightweight 4over6. Mapping of Address and Port with
during the IPv4/IPv6 co-existing period. MAP has adopted Dynamic Encapsulation(MAP-E)[RFC7597], Mapping of Address and Port with using
Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as auto- Translation(MAP-T)[RFC7599] are stateless mechanisms for running IPv4
configuring protocol. The MAP Customer Edge (CE) uses the DHCPv6 over IPv6-only infrastructure. Lightweight 4over6[RFC7596] is a hub-
extension options [I-D.ietf-softwire-map-dhcp] to discover MAP Border and-spoke IPv4-over-IPv6 tunneling mechanism, with complete
Relay (in tunnel model only) and to configure relevant MAP rules. independence of IPv4 and IPv6 addressing. They provide both IPv4 and
IPv6 connectivity services simultaneously during the IPv4/IPv6 co-
existing period. MAP-E, MAP-T and Lightweight 4over6 have adopted
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as
auto-configuring protocol. The Customer Edge (CE) uses DHCPv6
options to discover the Border Relay (BR) and get MAP configurations.
In many networks, user configuration information may be stored by AAA In many networks, user configuration information may be stored by 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 MAP 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 MAP 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-
encapsulation mode, while providing enough information to form the E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], providing
correspondent DHCPv6 MAP option [I-D.ietf-softwire-map-dhcp]. enough information to form the correspondent DHCPv6 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].
The terms MAP CE and MAP Border Relay are defined in 3. Configuration process with RADIUS
[I-D.ietf-softwire-map].
3. MAP 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 MAP CE with MAP configuration information. cooperate to provide CE with MAP configuration information.
MAP CE BNG AAA Server CE BNG AAA Server
| | | | | |
|------DHCPv6 Solicit----->| | |------DHCPv6 Solicit----->| |
|(Option Request w/ MAP option) | | (Option Request w/container option) |
| |--Access-Request(MAP Attr)-->| | |-------Access-Request------->|
| | (Map attriubte) |
| | | | | |
| |<--Access-Accept(MAP Attr)---| | |<-------Access-Accept--------|
|<---DHCPv6 Advertisement--| | |<---DHCPv6 Advertisement--| (MAP attriubte) |
| | | | | |
|------DHCPv6 Request---->| | |------DHCPv6 Request---->| |
| (MAP Option) | | | (container Option) | |
|<---- -DHCPv6 Reply-------| | |<---- -DHCPv6 Reply-------| |
| (MAP 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, the The BNG acts as a RADIUS client and as a DHCPv6 server. First, CE
MAP CE MAY initiate a DHCPv6 Solicit message that includes an Option MAY initiate a DHCPv6 Solicit message that includes an Option Request
Request option (6) [RFC3315] with the MAP option option (6) [RFC3315] with the Container options as defined
[I-D.ietf-softwire-map-dhcp] from the MAP CE. But note that the ORO in[RFC7598]. OPTION_S46_CONT_MAPE should be included for MAP-
(Option Request option) with the MAP option could be optional if the E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599], and
network was planned as MAP-enabled as default. When BNG receives the OPTION_S46_CONT_LW for Lightweight 4over6[RFC7596]. But note that
SOLICIT, it SHOULD initiates radius Access-Request message, in which the ORO (Option Request option) with the MAP option could be optional
the User-Name attribute (1) SHOULD be filled by the MAP CE MAC if the network was planned as MAP-enabled as default. When BNG
address or interface-id or both, to the RADIUS server and the User- receives the SOLICIT, it SHOULD initiates radius Access-Request
password attribute (2) SHOULD be filled by the shared MAP password 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 that has been preconfigured on the DHCPv6 server, requesting
authentication as defined in [RFC2865] with MAP-Configuration authentication as defined in [RFC2865] with the corresponding MAP-
attribute, which will be defined in the next Section. If the Configuration Attribute, which will be defined in the next Section.
authentication request is approved by the AAA server, an Access-
Accept message MUST be acknowledged with the IPv6-MAP-Configuration If the authentication request is approved by the AAA server, an
Attribute. After receiving the Access-Accept message with MAP- Access-Accept message MUST be acknowledged with the corresponding
Configuration Attribute, the BNG SHOULD respond the user an MAP-Configuration Attribute. After receiving the Access-Accept
Advertisement message. Then the user can requests for a MAP Option, message with the corresponding Attribute, the BNG SHOULD respond the
and the BNG SHOULD reply the user with the message containing the MAP user an Advertisement message. Then the user can requests for the
option. The recommended format of the MAC address is defined as corresponding Container option, and the BNG SHOULD reply the user
Calling-Station-Id (Section 3.20 in [RFC3580] without the SSID with the message containing the Container option. The recommended
(Service Set Identifier) portion. format of the MAC address is defined as Calling-Station-Id
(Section 3.20 in [RFC3580] without the SSID (Service Set Identifier)
portion.
For Lightweight 4over6 [RFC7596], the subscriber's binding state
should be synchronized between AAA server and the lwAFTR. If the
bindings are pre-configured statically in both AAA server and lwAFTR,
the AAA server does not need to configure lwAFTR anymore. Otherwise,
if the bindings are locally creately in AAA server on-demand, it
should inform the lwAFTR with the subscriber's binding state, to
synchronise the binding information of the lwB4 with the lwAFTR. In
the Lightweight 4over6 scenario, the lwB4 could also be configured
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.
Figure 2 describes another scenario, in which the authorization Figure 2 describes another scenario, in which the authorization
operation is not coupled with authentication. Authorization relevant operation is not coupled with authentication. Authorization is done
to MAP is done independently after the authentication process. As independently after the authentication process. As similar to above
similar to above scenario, the ORO with the MAP option in the initial scenario, the ORO with the corresponding MAP option in the initial
DHCPv6 request could be optional if the network was planned as MAP- DHCPv6 request could be optional if the network was planned as MAP-
enabled as default. enabled as default.
MAP CE BNG AAA Server CE BNG AAA Server
| | | | | |
|------DHCPv6 Request---->| | |------DHCPv6 Request---->| |
|(Option Request w/ MAP option) | |(Option Request w/container option) |
| |--Access-Request(MAP Attr)-->| | |-------Access-Request------->|
| | | | | (MAP attribute) |
| |<--Access-Accept(MAP Attr)---|
| | | | | |
| |<-------Access-Accept--------|
| | (MAP attribute) |
|<-----DHCPv6 Reply--------| | |<-----DHCPv6 Reply--------| |
| (MAP option) | | | (container option) | |
| | | | | |
DHCPv6 RADIUS DHCPv6 RADIUS
Figure 2: the cooperation between DHCPv6 and RADIUS decoupled with Figure 2: the cooperation between DHCPv6 and RADIUS decoupled with
RADIUS authentication RADIUS authentication
In the above mentioned scenario, the Access-Request packet SHOULD In the above mentioned scenario, the Access-Request packet SHOULD
contain a Service-Type attribute (6) with the value Authorize Only contain a Service-Type attribute (6) with the value Authorize Only
(17); thus, according to [RFC5080], the Access-Request packet MUST (17); thus, according to [RFC5080], the Access-Request packet MUST
contain a State attribute that obtained from the previous contain a State attribute that obtained from the previous
authentication process. 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 MAP-Configuration Attribute in the initial After receiving the corresponding MAP-Configuration Attribute in the
Access-Accept, the BNG SHOULD store the received MAP configuration initial Access-Accept, the BNG SHOULD store the received MAP
parameters locally. When the MAP CE sends a DHCPv6 Request message configuration parameters locally. When the CE sends a DHCPv6 Request
to request an extension of the lifetimes for the assigned address, message to request an extension of the lifetimes for the assigned
the BNG does not have to initiate a new Access-Request towards the address, the BNG does not have to initiate a new Access-Request
AAA server to request the MAP configuration parameters. The BNG towards the AAA server to request the MAP configuration parameters.
could retrieve the previously stored MAP configuration parameters and The BNG could retrieve the previously stored MAP configuration
use them in its reply. parameters and use them in its reply.
If the BNG does not receive the MAP-Configuration Attribute in the If the BNG does not receive the corresponding MAP-Configuration
Access-Accept it MAY fallback to a pre-configured default MAP Attribute in the Access-Accept it MAY fallback to a pre-configured
configuration, if any. If the BNG does not have any pre-configured default MAP configuration, if any. If the BNG does not have any pre-
default MAP configuration or if the BNG receives an Access-Reject, configured default MAP configuration or if the BNG receives an
the tunnel cannot be established. Access-Reject, the MAP 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 MAP CE message was sent at time T1 has not responded by time T2, the CE
(DHCPv6 client) SHOULD enters 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 MAP-Rule Attribute which is 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 MAP RADIUS attribute are designed following the simplify The S46 attributes are designed following the simplify principle.
principle. The sub options are organized into two categories: the Different sub options are required for each type of S46 Container
necessary and the optional. option.
4.1. MAP-Configuration Attribute 4.1. MAP-Configuration Attribute
The MAP-Configuration Attribute is structured as follows: The MAP-Configuration 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 Container Option(s) +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBD
Length
2 + the length of the S46 Container option(s)
S46 Container Option (s)
A variable field that may contains one or more S46 Container option(s),
defined in Section 4.2
4.2. S46 Container Options
Depending on the deployment scenario, a client might request for more
than one transition mechanism at a time, at least one S46 Container
option MUST be included in one MAP-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 | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ MAP Rule Option(s) + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
TBD 1 MAP-E Container Option
Length 2 MAP-T Container Option
2 + the length of the Rule option(s) 3 Lightweight 4over6 Container Option
MAP Rule Option (s) Length
A variable field that may contains one or more Rule option(s), 2 + the length of the sub options
defined in Section 4.2 Sub Option
A variable field that contains necessary sub options defined in
Section 4.3 and zero or several optional sub options, defined
in Section 4.4
4.2. MAP Rule Options 4.3. Sub Options for S46 Container 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- more Forwarding Mapping Rules MUST be included in one MAP-E or MAP-T
Configuration Attribute. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | | SubType | SubLen | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 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
Length SubLen
2 + the length of the sub options 2 + the length of the sub options
Sub Option Sub Option
A variable field that contains necessary sub options defined in A variable field that contains sub options defined in
Section 4.3 and zero or several optional sub options, defined Section 4.4
in Section 4.4
4.3. Sub Options for MAP Rule Option 4.3.2. S46-BR Sub Option
4.3.1. Rule-IPv6-Prefix Sub Option There MUST be atleast one S46-BR Sub Option included in one S46
Container Option.
The Rule-IPv6-Prefix Sub Option is necessary for every MAP Rule 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| BR-ipv6-address |
+ +
| BR-ipv6-address |
+ +
| BR-ipv6-address |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
4 (SubType number, for the S46-BR sub option)
SubLen
18 (the length of the S46-BR sub option)
BR-ipv6-address
a 128-bits field that specifies the IPv6 address for the BR.
4.3.3. S46-DMR Sub Option
There MUST be exactly one S46-DMR Sub Option included in one MAP-T
Container Option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen |dmr-prefix6-len|dmr-ipv6-prefix|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| dmr-ipv6-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
5 (SubType number, for the S46-DMR sub option)
SubLen
8 (the length of the Rule-IPv4-Prefix6 sub option)
dmr-prefix6-len
length of the IPv6 prefix, specified in the dmr-ipv6-prefix
field, expressed in bits
dmr-ipv6-prefix
a 32-bits field that specifies an IPv6 prefix that appears in
the Default Mapping Rule
4.3.4. S46-V4V6Bind Sub Option
There MUST be atmost one S46-RULE Sub Option included in each
Lightweight 4over6 Container Option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued) |bindprefix6-len| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| bind-ipv6-prefix |
+ +
| bind-ipv6-prefix |
+ +
| bind-ipv6-prefix |
+ +-+-+-+-+-+-+-+-+
| bind-ipv6-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
6 (SubType number, for the S46-V4V6Bind sub option)
SubLen
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
a 32-bits field that specifies an IPv4 address that appears in
the V4V6Bind Option
bindprefix6-len
length of the IPv6 prefix, specified in the bind-ipv6-prefix
field, expressed in bits
rule-ipv6-prefix
a 128-bits field that specifies an IPv6 prefix that appears in
the V4V6Bind Option
4.3.5. S46-PORTPARAMS Sub Option
The S46-PORTPARAMS sub option specifies optional port set information
that MAY be provided to CEs. The S46-PORTPARAMS sub option canbe
included optionally by each type of S46 Container Option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | PSID-Offset | PSID-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
7 (SubType number, for the S46-PORTPARAMS Sub Option sub option)
SubLen
6 (the length of the S46-PORTPARAMS Sub Option sub option)
PSID Offset
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.
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.
PSID-len
Bit length value of the number of significant bits in the PSID
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
port number representing valid of PSID. Subsequently, the
address sharing ratio would be 2 ^k.
PSID (Port-set ID)
Explicit 16-bit (unsigned word) PSID value. The PSID value
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
value. The remaining (16-k) bits on the right are padding zeros.
4.4. Sub Options for S46-RULE Sub Option
4.4.1. Rule-IPv6-Prefix Sub Option
The Rule-IPv6-Prefix Sub Option is necessary for every S46-RULE sub
option. It should appear for once and only once. option. It should appear for once and only once.
The IPv6 Prefix sub option is followed the framed IPv6 prefix The IPv6 Prefix sub option is followed the framed IPv6 prefix
designed in [RFC3162]. designed in [RFC3162].
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 | prefix6-len | | SubType | SubLen | Reserved | prefix6-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| rule-ipv6-prefix | | rule-ipv6-prefix |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
1 (SubType number, for the Rule-IPv6-Prefix6 sub option) 8 (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
4.3.2. Rule-IPv4-Prefix Sub Option 4.4.2. Rule-IPv4-Prefix 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 | Reserved | prefix4-len | | SubType | SubLen | Reserved | prefix4-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| rule-ipv4-prefix | | rule-ipv4-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
2 (SubType number, for the Rule-IPv4-Prefix6 sub option) 9 (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.3.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
3 (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.3.4. BR-IPv6-Address Sub Option 4.5. Table of attributes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| BR-ipv6-address |
+ +
| BR-ipv6-address |
+ +
| BR-ipv6-address |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
4 (SubType number, for the BR-ipv6-address sub option)
SubLen
20 (the length of the BR-ipv6-address sub option)
BR-ipv6-address
a 128-bits field that specifies the IPv6 address for the BR.
4.3.5. PSID Sub Option
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | PSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
5 (SubType number, for the PSID Sub Option sub option)
SubLen
4 (the length of the PSID Sub Option sub option)
PSID (Port-set ID)
Explicit 16-bit (unsigned word) PSID value. The PSID value
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
value. The remaining (16-k) bits on the right are padding zeros.
4.3.6. PSID Length Sub Option
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | PSID-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
6 (SubType number, for the PSID Length sub option)
SubLen
4 (the length of the PSID Length sub option)
PSID-len
Bit length value of the number of significant bits in the PSID
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
port number representing valid of PSID. Subsequently, the
address sharing ratio would be 2 ^k.
4.3.7. PSID Offset Sub Option
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | PSID Offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
7 (SubType number, for the PSID Offset sub option)
SubLen
4 (the length of the PSID Offset sub option)
PSID Offset
4 bits long field that specifies the numeric value for the MAP
algorithm's excluded port range/offset bits (A-bits), as per
section 5.1.1 in [I-D.ietf-softwire-map]. Default must be set
to 4.
4.4. 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 MAP-
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
skipping to change at page 12, line 19 skipping to change at page 14, line 19
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 MAP-Configuration 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 MAP scenarios, both CE and BNG are within a provider network, In softwire scenarios, both CE and BNG are within a provider network,
which can be considered as a closed network and a lower security which can be considered as a closed network and a lower security
threat environment. A similar consideration can be applied to the threat environment. A similar consideration can be applied to the
RADIUS message exchange between BNG and the AAA server. 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 MAP password that has been preconfigured on the attack on the shared password that has been preconfigured on the
DHCPv6 server to get unauthorized MAP 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
discussed in [I-D.ietf-softwire-map]. Furthermore, generic DHCPv6 discussed in [RFC7597]. Security considerations for Lightweight
4over6 are discussed in [RFC7596]. Furthermore, generic DHCPv6
security mechanisms can be applied DHCPv6 intercommunication between security mechanisms can be applied DHCPv6 intercommunication between
MAP CE and BNG. CE and 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, Suresh Krishnan and Ross Chandler for this Lothberg, Wojciech Dec, and Suresh Krishnan for this document. This
document. document was merged with draft-sun-softwire-lw4over6-radext-01,
thanks to everyone who contributed to this draft.
This document was produced using the xml2rfc tool [RFC2629]. This document was produced using the xml2rfc tool [RFC7749].
9. References 9. References
9.1. Normative References 9.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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 14, line 5 skipping to change at page 16, line 5
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>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-softwire-map]
Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, "Mapping of Address and Port
with Encapsulation (MAP)", draft-ietf-softwire-map-13
(work in progress), March 2015.
[I-D.ietf-softwire-map-dhcp]
Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec,
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for
configuration of Softwire Address and Port Mapped
Clients", draft-ietf-softwire-map-dhcp-12 (work in
progress), March 2015.
[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>.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
DOI 10.17487/RFC2629, June 1999,
<http://www.rfc-editor.org/info/rfc2629>.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000, Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,
<http://www.rfc-editor.org/info/rfc2869>. <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,
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.
Farrer, "Lightweight 4over6: An Extension to the Dual-
Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596,
July 2015, <http://www.rfc-editor.org/info/rfc7596>.
[RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, Ed., "Mapping of Address and
Port with Encapsulation (MAP-E)", RFC 7597,
DOI 10.17487/RFC7597, July 2015,
<http://www.rfc-editor.org/info/rfc7597>.
[RFC7598] Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec,
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for
Configuration of Softwire Address and Port-Mapped
Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015,
<http://www.rfc-editor.org/info/rfc7598>.
[RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S.,
and T. Murakami, "Mapping of Address and Port using
Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July
2015, <http://www.rfc-editor.org/info/rfc7599>.
[RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary",
RFC 7749, DOI 10.17487/RFC7749, February 2016,
<http://www.rfc-editor.org/info/rfc7749>.
Additional Authors
Qiong Sun
China Telecom
Beijing China
Email: sunqiong@ctbri.com.cn
Qi Sun
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-6278-5822
Email: sunqibupt@gmail.com
Cathy Zhou
Huawei Technologies
Bantian, Longgang District
Shenzhen 518129
Email: cathy.zhou@huawei.com
Tina Tsou
Huawei Technologies(USA)
2330 Central Expressway
Santa Clara, CA 95050
USA
Email: Tina.Tsou.Zouting@huawei.com
ZiLong Liu
Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-6278-5822
Email: liuzilong8266@126.com
Yong Cui
Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-62603059
Email: yong@csnet1.cs.tsinghua.edu.cn
Authors' Addresses Authors' Addresses
Sheng Jiang Sheng Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Q14, Huawei Campus, No.156 Beiqing Road Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095 Hai-Dian District, Beijing, 100095
P.R. China P.R. China
Email: jiangsheng@huawei.com Email: jiangsheng@huawei.com
Yu Fu Yu Fu
skipping to change at line 640 skipping to change at page 19, line 35
Email: leo.liubing@huawei.com Email: leo.liubing@huawei.com
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
China Telecom
Beijing
P.R. China
Email: xiechf@ctbri.com.cn
Tianxiang Li
Tsinghua University
Beijing 100084
P.R.China
Email: peter416733@gmail.com
 End of changes. 59 change blocks. 
251 lines changed or deleted 399 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/