draft-ietf-softwire-map-radius-09.txt   draft-ietf-softwire-map-radius-10.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: July 7, 2017 CNNIC Expires: September 9, 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
January 3, 2017 March 8, 2017
RADIUS Attribute for Softwire Address plus Port based Mechanisms RADIUS Attribute for Softwire Address plus Port based Mechanisms
draft-ietf-softwire-map-radius-09 draft-ietf-softwire-map-radius-10
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 the Authentication configuration information may be stored in the Authentication
Authorization and Accounting (AAA) servers, while user configuration Authorization and Accounting (AAA) servers, while user configuration
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 July 7, 2017. This Internet-Draft will expire on September 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 5 skipping to change at page 4, line 5
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 co- The below Figure 1 illustrates how the RADIUS protocol and DHCPv6 co-
operate to provide CE with MAP configuration information. The BNG operate to provide CE with MAP configuration information. The BNG
acts as a RADIUS client and as a DHCPv6 server. acts as a RADIUS client and as a DHCPv6 server.
CE BNG AAA Server CE BNG AAA Server
| | | | | |
|-----1.DHCPv6 Solicit----->| | |-------1.DHCPv6 Solicit------->| |
| (ORO w/container option) | | | (ORO w/container option code) | |
| |-------2.Access-Request------->| | |-------2.Access-Request------->|
| | (S46-Configuration attriubte) | | | (S46-Configuration attriubte) |
| | | | | |
| |<------3.Access-Accept---------| | |<------3.Access-Accept---------|
|<--4.DHCPv6 Advertisement--| (S46-Configuration attriubte) | |<---4.DHCPv6 Advertisement-----| (S46-Configuration attriubte) |
| | | | (container option) | |
|-----5.DHCPv6 Request---->| | |-------5.DHCPv6 Request------>| |
| (container Option) | | | (container Option) | |
|<----6.DHCPv6 Reply--------| | |<------6.DHCPv6 Reply----------| |
| (cointainer option) | | | (container option) | |
| | | | | |
DHCPv6 RADIUS DHCPv6 RADIUS
Figure 1: the cooperation between DHCPv6 and RADIUS combining with Figure 1: the cooperation between DHCPv6 and RADIUS combining with
RADIUS authentication RADIUS authentication
1. First, the CE MAY initiate a DHCPv6 Solicit message that includes 1. First, the CE MAY initiate a DHCPv6 Solicit message that includes
an Option Request option(6) [RFC3315] with the S46 Container options an Option Request option(6) [RFC3315] with the S46 Container option
as defined in[RFC7598]. OPTION_S46_CONT_MAPE should be included for codes as defined in[RFC7598]. OPTION_S46_CONT_MAPE should be
MAP-E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599], and included for MAP-E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599],
OPTION_S46_CONT_LW for Lightweight 4over6[RFC7596]. Note however, and OPTION_S46_CONT_LW for Lightweight 4over6[RFC7596]. Note
that the ORO (Option Request option) with the S46 Container option however, that the ORO (Option Request option) with the S46 Container
code could be optional if the network was planned as S46-enabled as option code could be optional if the network was planned as
default. S46-enabled as default.
2. When the BNG receives the SOLICIT, it should initiate the radius 2. When the BNG receives the SOLICIT, it should initiate the radius
Access-Request message, in which the User-Name attribute (1) should Access-Request message, in which the User-Name attribute (1) should
be filled by the CE MAC address or interface-id or both, to the be filled by the CE MAC address or interface-id or both, to the
RADIUS server and the User-password attribute (2) should be filled by RADIUS server and the User-password attribute (2) should be filled by
the shared password that has been preconfigured on the DHCPv6 server, the shared password that has been preconfigured on the DHCPv6 server,
requesting authentication as defined in [RFC2865] with the requesting authentication as defined in [RFC2865] with the
corresponding Softwire46-Configuration Attribute, which will be corresponding Softwire46-Configuration Attribute, which will be
defined in the next Section. defined in the next Section.
3. If the authentication request is approved by the AAA server, an 3. If the authentication request is approved by the AAA server, an
Access-Accept message MUST be acknowledged with the corresponding Access-Accept message MUST be acknowledged with the corresponding
Softwire46-Configuration Attribute. Softwire46-Configuration Attribute.
4. After receiving the Access-Accept message with the corresponding 4. After receiving the Access-Accept message with the corresponding
Attribute, the BNG SHOULD respond to the CE with an Advertisement Attribute, the BNG SHOULD respond to the DHCPv6 Client (CE) with an
message. Advertisement message.
5. After receiving the Advertise message, the CE MAY request for the 5. After receiving the Advertise message, the CE MAY request for the
corresponding S46 Container option, by including the S46 Container corresponding S46 Container option, by including the S46 Container
option in the Request Message. option in the Request Message.
6. After receiving the client's Request messsage, containing the 6. After receiving the client's Request messsage, containing the
corresponding S46 Container option the BNG SHOULD reply to the CE corresponding S46 Container option the BNG SHOULD reply to the CE
with the message containing the S46 Container option. The with the message containing the S46 Container option. The
recommended format of the MAC address is defined as Calling-Station- recommended format of the MAC address is defined as Calling-Station-
Id (Section 3.20 in [RFC3580] without the SSID (Service Set Id (Section 3.20 in [RFC3580] without the SSID (Service Set
skipping to change at page 5, line 31 skipping to change at page 5, line 31
the AAA server, it should inform the lwAFTR with the subscriber's the AAA server, it should inform the lwAFTR with the subscriber's
binding state, in order to synchronise the binding information of the binding state, in order to synchronise the binding information of the
lwB4 with the lwAFTR. lwB4 with the lwAFTR.
The authorization operation could also be done independently after The authorization operation could also be done independently after
the authentication process. In such a scenario, after the the authentication process. In such a scenario, after the
authentication operation, the client MAY initiate a DHCPv6 Request authentication operation, the client MAY initiate a DHCPv6 Request
message that includes the corresponding S46 Container options. message that includes the corresponding S46 Container options.
Similar to the above scenario, the ORO with the corresponding S46 Similar to the above scenario, the ORO with the corresponding S46
Container option code in the initial DHCPv6 request could be optional Container option code in the initial DHCPv6 request could be optional
if the network was planned as being S46-enabled vy default. When the if the network was planned as being S46-enabled by default. When the
BNG receives the DHCPv6 Request, it SHOULD initiate the radius BNG receives the DHCPv6 Request, it SHOULD initiate the radius
Access-Request message, which MUST contain a Service-Type attribute Access-Request message, which MUST contain a Service-Type attribute
(6) with the value Authorize Only (17), the corresponding (6) with the value Authorize Only (17), the corresponding
Softwire46-Configuration Attribute, and a State attribute obtained Softwire46-Configuration Attribute, and a State attribute obtained
from the previous authentication process according to [RFC5080]. If from the previous authentication process according to [RFC5080]. If
the authorization request is approved by the AAA server, an Access- the authorization request is approved by the AAA server, an Access-
Accept message MUST be acknowledged with the corresponding Accept message MUST be acknowledged with the corresponding
Softwire46-Configuration Attribute. The BNG SHOULD then send the Softwire46-Configuration Attribute. The BNG SHOULD then send the
DHCPv6 Reply message containing the S46 Container option. DHCPv6 Reply message containing the S46 Container option.
skipping to change at page 9, line 24 skipping to change at page 9, line 24
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| dmr-ipv6-prefix | | dmr-ipv6-prefix |
| (variable length) | | (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
5 (SubType number, for the S46-DMR sub option) 5 (SubType number, for the S46-DMR sub option)
SubLen SubLen
3 + length of dmr-ipv6-prefix specified in octects 3 + length of dmr-ipv6-prefix specified in octects
dmr-prefix6-len dmr-prefix6-len
8 bits longs; expresses the bitmask length of the IPv6 8 bits long; expresses the bitmask length of the IPv6
prefix specified in the dmr-ipv6-prefix field. Allowed values range prefix specified in the dmr-ipv6-prefix field. Allowed values range
from 0-96. from 0 to 96.
dmr-ipv6-prefix dmr-ipv6-prefix
a variable-length field specifying the IPv6 prefix or address a variable-length field specifying the IPv6 prefix or address
for the BR. This field is right-padded with zeros to the nearest for the BR. This field is right-padded with zeros to the nearest
octect boundary when dmr-prefix6-len is not divisible by 8. octect boundary when dmr-prefix6-len is not divisible by 8.
4.3.4. S46-V4V6Bind Sub Option 4.3.4. S46-V4V6Bind Sub Option
There MUST be atmost one S46-V4V6Bind Sub Option included in each There MUST be atmost one S46-V4V6Bind Sub Option included in each
Lightweight 4over6 Container Option. Lightweight 4over6 Container Option.
skipping to change at page 12, line 16 skipping to change at page 12, line 16
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | Reserved | prefix6-len | | SubType | SubLen | Reserved | prefix6-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| rule-ipv6-prefix | | rule-ipv6-prefix |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
9 (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
skipping to change at page 12, line 39 skipping to change at page 12, line 39
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | Reserved | prefix4-len | | SubType | SubLen | Reserved | prefix4-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| rule-ipv4-prefix | | rule-ipv4-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
10 (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.4.3. EA Length Sub Option 4.4.3. EA Length Sub Option
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | EA-len | | SubType | SubLen | EA-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
11 (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. Softwire46 Sub Options Encapsulation 4.5. Softwire46 Sub Options Encapsulation
The table below shows which encapsulated Sub Options are mandatory, The table below shows which encapsulated Sub Options are mandatory,
optional, or not permitted for each defined S46 Container Option. optional, or not permitted for each defined S46 Container Option.
 End of changes. 13 change blocks. 
35 lines changed or deleted 35 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/