draft-ietf-softwire-map-radius-03.txt   draft-ietf-softwire-map-radius-04.txt 
Softwire S. Jiang Softwire S. Jiang
Internet-Draft Y. Fu Internet-Draft Huawei Technologies Co., Ltd
Intended status: Standards Track B. Liu Intended status: Standards Track Y. Fu
Expires: June 22, 2015 Huawei Technologies Co., Ltd Expires: December 24, 2015 CNNIC
B. Liu
Huawei Technologies Co., Ltd
P. Deacon P. Deacon
IEA Software, Inc. IEA Software, Inc.
December 19, 2014 June 22, 2015
RADIUS Attribute for MAP RADIUS Attribute for MAP
draft-ietf-softwire-map-radius-03 draft-ietf-softwire-map-radius-04
Abstract Abstract
Mapping of Address and Port (MAP) is a stateless mechanism for Mapping of Address and Port (MAP) is a stateless mechanism for
running IPv4 over IPv6-only infrastructure. It provides both IPv4 running IPv4 over IPv6-only infrastructure. It provides both IPv4
and IPv6 connectivity services simultaneously during the IPv4/IPv6 and IPv6 connectivity services simultaneously during the IPv4/IPv6
co-existing period. The Dynamic Host Configuration Protocol for IPv6 co-existing period. The Dynamic Host Configuration Protocol for IPv6
(DHCPv6) MAP options has been defined to configure MAP Customer Edge (DHCPv6) MAP options has been defined to configure MAP Customer Edge
(CE). However, in many networks, the configuration information may (CE). However, in many networks, the configuration information may
be stored in Authentication Authorization and Accounting (AAA) be stored in Authentication Authorization and Accounting (AAA)
skipping to change at page 1, line 46 skipping to change at page 1, line 48
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 22, 2015. This Internet-Draft will expire on December 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 3, line 21 skipping to change at page 3, line 21
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. Mapping of Address and Port (MAP)[I-D.ietf-softwire-map] is
a stateless mechanism for running IPv4 over IPv6-only infrastructure. a stateless mechanism for running IPv4 over IPv6-only infrastructure.
It provides both IPv4 and IPv6 connectivity services simultaneously It provides both IPv4 and IPv6 connectivity services simultaneously
during the IPv4/IPv6 co-existing period. MAP has adopted Dynamic during the IPv4/IPv6 co-existing period. MAP has adopted Dynamic
Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as auto- Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as auto-
configuring protocol. The MAP Customer Edge (CE) uses the DHCPv6 configuring protocol. The MAP Customer Edge (CE) uses the DHCPv6
extension options [I-D.ietf-softwire-map-dhcp] to discover MAP Border extension options [I-D.ietf-softwire-map-dhcp] to discover MAP Border
Relay (in tunnel model only) and to configure relevant MAP rules. Relay (in tunnel model only) and to configure relevant MAP rules.
In many networks, user configuration information may be managed by In many networks, user configuration information may be stored by AAA
AAA (Authentication, Authorization, and Accounting) servers. Current (Authentication, Authorization, and Accounting) servers. Current AAA
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 through DHCPv6 protocol between BNGs and user configuration is mainly transmitted through DHCPv6 protocol
hosts/CEs, new RADIUS attributes are needed to propagate the between BNGs and hosts/CEs, new RADIUS attributes are needed to
information from AAA servers to BNGs. The MAP RADIUS attributes propagate the information from AAA servers to BNGs. The MAP RADIUS
designed in this document are especially for the MAP encapsulation attributes designed in this document are especially for the MAP
mode, while providing enough information to form the correspondent encapsulation mode, while providing enough information to form the
DHCPv6 MAP option [I-D.ietf-softwire-map-dhcp]. correspondent DHCPv6 MAP option [I-D.ietf-softwire-map-dhcp].
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 The terms MAP CE and MAP Border Relay are defined in
[I-D.ietf-softwire-map]. [I-D.ietf-softwire-map].
skipping to change at page 4, line 24 skipping to change at page 4, line 24
|------DHCPv6 Request---->| | |------DHCPv6 Request---->| |
| (MAP Option) | | | (MAP Option) | |
|<---- -DHCPv6 Reply-------| | |<---- -DHCPv6 Reply-------| |
| (MAP option) | | | (MAP 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
BNGs act as a RADIUS client and as a DHCPv6 server. First, the MAP The BNG acts as a RADIUS client and as a DHCPv6 server. First, the
CE MAY initiate a DHCPv6 Solicit message that includes an Option MAP CE MAY initiate a DHCPv6 Solicit message that includes an Option
Request option (6) [RFC3315] with the MAP option Request option (6) [RFC3315] with the MAP option
[I-D.ietf-softwire-map-dhcp] from the MAP CE. But note that the ORO [I-D.ietf-softwire-map-dhcp] from the MAP CE. But note that the ORO
(Option Request option) with the MAP option could be optional if the (Option Request option) with the MAP option could be optional if the
network was planned as MAP-enabled as default. When BNG receives the network was planned as MAP-enabled as default. When BNG receives the
SOLICIT, it SHOULD initiates radius Access-Request message, in which SOLICIT, it SHOULD initiates radius Access-Request message, in which
the User-Name attribute (1) SHOULD be filled by the MAP CE MAC the User-Name attribute (1) SHOULD be filled by the MAP CE MAC
address, to the RADIUS server and the User-password attribute (2) address or interface-id or both, to the RADIUS server and the User-
SHOULD be filled by the shared MAP password that has been password attribute (2) SHOULD be filled by the shared MAP password
preconfigured on the DHCPv6 server, requesting authentication as that has been preconfigured on the DHCPv6 server, requesting
defined in [RFC2865] with MAP-Configuration attribute, defined in the authentication as defined in [RFC2865] with MAP-Configuration
next Section. If the authentication request is approved by the AAA attribute, which will be defined in the next Section. If the
server, an Access-Accept message MUST be acknowledged with the IPv6- authentication request is approved by the AAA server, an Access-
MAP-Configuration Attribute. After receiving the Access-Accept Accept message MUST be acknowledged with the IPv6-MAP-Configuration
message with MAP-Configuration Attribute, the BNG SHOULD respond the Attribute. After receiving the Access-Accept message with MAP-
user an Advertisement message. Then the user can requests for a MAP Configuration Attribute, the BNG SHOULD respond the user an
Option, the BNG SHOULD reply the user with the message containing the Advertisement message. Then the user can requests for a MAP Option,
MAP option. The recommended format of the MAC address is as defined and the BNG SHOULD reply the user with the message containing the MAP
in Calling-Station-Id (Section 3.20 in [RFC3580] without the SSID option. The recommended format of the MAC address is defined as
Calling-Station-Id (Section 3.20 in [RFC3580] without the SSID
(Service Set Identifier) portion. (Service Set Identifier) portion.
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 relevant
to MAP is done independently after the authentication process. As to MAP is done independently after the authentication process. As
similar to above scenario, the ORO with the MAP option in the initial similar to above scenario, the ORO with the 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 MAP CE BNG AAA Server
skipping to change at page 5, line 21 skipping to change at page 5, line 21
| |<--Access-Accept(MAP Attr)---| | |<--Access-Accept(MAP Attr)---|
| | | | | |
|<-----DHCPv6 Reply--------| | |<-----DHCPv6 Reply--------| |
| (MAP option) | | | (MAP 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 abovementioned 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 MAP-Configuration Attribute in the initial
skipping to change at page 6, line 10 skipping to change at page 6, line 10
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 MAP CE
(DHCPv6 client) SHOULD enters the Rebind state and attempt to contact (DHCPv6 client) SHOULD enters 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 MAP-Rule Attribute which is used in the MAP
scenario. The attribute design follows [RFC6158] and referring scenario. The attribute design follows [RFC6158] and refers
to[RFC6929]. to[RFC6929].
The MAP RADIUS attribute are designed following the simplify The MAP RADIUS attribute are designed following the simplify
principle. The sub options are organized into two categories: the principle. The sub options are organized into two categories: the
necessary and the optional. necessary and the optional.
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:
skipping to change at page 6, line 36 skipping to change at page 6, line 36
| | | |
+ MAP Rule Option(s) + + MAP Rule Option(s) +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
TBD TBD
Length Length
2 + the length of the Rule option(s) 2 + the length of the Rule option(s)
MAP Rule Option (s) MAP Rule Option (s)
A variable field that may contains one or more Rule option(s), A variable field that may contains one or more Rule option(s),
defined in Section 4.2. defined in Section 4.2
4.2. MAP Rule Options 4.2. MAP Rule Options
Depending on deployment scenario, one Default Mapping rule and zero Depending on deployment scenario, one Basic Mapping Rule and zero or
or more other type Mapping Rules MUST be included in one MAP- more Forwarding Mapping Rules MUST be included in one MAP-
Configuration Attribute. 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 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 Default Mapping Rule 3 Basic & Forwarding Mapping Rule
4 Basic & Forwarding Mapping Rule
Length Length
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 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 MAP Rule Option 4.3. Sub Options for MAP Rule Option
4.3.1. Rule-IPv6-Prefix Sub Option 4.3.1. Rule-IPv6-Prefix Sub Option
The Rule-IPv6-Prefix Sub Option is necessary for every MAP Rule The Rule-IPv6-Prefix Sub Option is necessary for every MAP Rule
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].
skipping to change at page 8, line 20 skipping to change at page 8, line 20
| | | |
| rule-ipv6-prefix | | rule-ipv6-prefix |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
1 (SubType number, for the Rule-IPv6-Prefix6 sub option) 1 (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.3.2. Rule-IPv4-Prefix Sub Option
0 1 2 3 0 1 2 3
skipping to change at page 8, line 43 skipping to change at page 8, line 43
| 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) 2 (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.3.3. EA Length Sub Option
0 1 2 3 0 1 2 3
skipping to change at page 9, line 19 skipping to change at page 9, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | EA-len | | SubType | SubLen | EA-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
3 (SubType number, for the EA Length sub option) 3 (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.3.4. BR-IPv6-Address 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 | BR-ipv6-address | SubType | SubLen | BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
BR-ipv6-address | BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +
BR-ipv6-address | BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +
BR-ipv6-address | BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
BR-ipv6-address | | BR-ipv6-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
4 (SubType number, for the BR-ipv6-address sub option) 4 (SubType number, for the BR-ipv6-address sub option)
SubLen SubLen
20 (the length of the BR-ipv6-address sub option) 20 (the length of the BR-ipv6-address sub option)
BR-ipv6-address BR-ipv6-address
a 128-bits field that specifies the IPv6 address for the BR. a 128-bits field that specifies the IPv6 address for the BR.
4.3.5. PSID Sub Option 4.3.5. PSID Sub Option
0 1 2 3 0 1 2 3
skipping to change at page 13, line 40 skipping to change at page 13, line 40
[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, April Service (RADIUS) Protocol Extensions", RFC 6929, April
2013. 2013.
9.2. Informative References 9.2. Informative References
[I-D.ietf-softwire-map] [I-D.ietf-softwire-map]
Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S., Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, "Mapping of Address and Port Murakami, T., and T. Taylor, "Mapping of Address and Port
with Encapsulation (MAP)", draft-ietf-softwire-map-12 with Encapsulation (MAP)", draft-ietf-softwire-map-13
(work in progress), November 2014. (work in progress), March 2015.
[I-D.ietf-softwire-map-dhcp] [I-D.ietf-softwire-map-dhcp]
Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec, Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec,
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", draft-ietf-softwire-map-dhcp-11 (work in Clients", draft-ietf-softwire-map-dhcp-12 (work in
progress), November 2014. 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, June 1999. Implementation in Roaming", RFC 2607, June 1999.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999. June 1999.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, June 2000. Extensions", RFC 2869, June 2000.
skipping to change at page 14, line 32 skipping to change at page 14, line 32
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
Huawei Technologies Co., Ltd CNNIC
Q14, Huawei Campus, No.156 Beiqing Road No.4 South 4th Street, Zhongguancun
Hai-Dian District, Beijing, 100095 Hai-Dian District, Beijing, 100190
P.R. China P.R. China
Email: eleven.fuyu@huawei.com Email: fuyu@cnnic.cn
Bing Liu Bing Liu
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: leo.liubing@huawei.com Email: leo.liubing@huawei.com
Peter Deacon Peter Deacon
IEA Software, Inc. IEA Software, Inc.
 End of changes. 23 change blocks. 
58 lines changed or deleted 60 lines changed or added

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