draft-ietf-softwire-map-radius-11.txt   draft-ietf-softwire-map-radius-12.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: October 2, 2017 CNNIC Expires: November 3, 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
March 31, 2017 May 2, 2017
RADIUS Attribute for Softwire Address plus Port based Mechanisms RADIUS Attribute for Softwire Address plus Port based Mechanisms
draft-ietf-softwire-map-radius-11 draft-ietf-softwire-map-radius-12
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 an Authentication configuration information may be stored in an Authentication
Authorization and Accounting (AAA) server, while user configuration Authorization and Accounting (AAA) server, 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 October 2, 2017. This Internet-Draft will expire on November 3, 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 2, line 46 skipping to change at page 2, line 46
4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 13 4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 13
4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 14 4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 14
4.5. Softwire46 Sub Options Encapsulation . . . . . . . . . . 14 4.5. Softwire46 Sub Options Encapsulation . . . . . . . . . . 14
4.6. Softwire46-Priority Attribute . . . . . . . . . . . . . . 14 4.6. Softwire46-Priority Attribute . . . . . . . . . . . . . . 14
4.7. Table of attributes . . . . . . . . . . . . . . . . . . . 15 4.7. Table of attributes . . . . . . . . . . . . . . . . . . . 15
5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 16 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6.1. S46 Mechanisms and Their Identifying Option Codes . . . . 16 6.1. S46 Mechanisms and Their Identifying Option Codes . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
9.1. Normative References . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . 18
9.2. Informative References . . . . . . . . . . . . . . . . . 18 9.2. Informative References . . . . . . . . . . . . . . . . . 18
Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 20 Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
Recently providers have started to deploy IPv6 and consider how to Recently providers have started to deploy IPv6 and consider how to
transit to IPv6. Many transition mechanisms based on the Address transit to IPv6. Many transition mechanisms based on the Address
plus Port (A+P) [RFC6346] have been proposed for running IPv4 over plus Port (A+P) [RFC6346] have been proposed for running IPv4 over
IPv6-only infrastructure, including MAP-E, MAP-T, and Lightweight IPv6-only infrastructure, including MAP-E, MAP-T, and Lightweight
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 Figure 1 below illustrates how the RADIUS protocol and DHCPv6 co- The Figure 1 below 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 DHCPv6 server. acts as a RADIUS client and DHCPv6 server.
CE BNG AAA Server CE BNG AAA Server
| | | | | |
|-------1.DHCPv6 Solicit------->| | |-------1.DHCPv6 Solicit------->| |
| (ORO w/container option code) | | | (ORO w/container option code) | |
| |-------2.Access-Request------->| | |-------2.Access-Request------->|
| | (S46-Configuration attribute) | | | (S46-Configuration attribute) |
| | | | | |
| |<------3.Access-Accept---------| | |<------3.Access-Accept---------|
|<---4.DHCPv6 Advertisement-----| (S46-Configuration attribute) | |<---4.DHCPv6 Advertisement-----| (S46-Configuration attribute) |
| (container option) | | | (container option) | |
|-------5.DHCPv6 Request------>| | |-------5.DHCPv6 Request------>| |
| (container Option) | | | (container Option) | |
|<------6.DHCPv6 Reply----------| | |<------6.DHCPv6 Reply----------| |
| (container 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 option an Option Request option(6) [RFC3315] with the S46 Container option
codes as defined in[RFC7598]. As described in [RFC7598], codes as defined in[RFC7598]. As described in [RFC7598],
OPTION_S46_CONT_MAPE should be included for MAP-E[RFC7597], OPTION_S46_CONT_MAPE should be included for MAP-E[RFC7597],
OPTION_S46_CONT_MAPT for MAP-T [RFC7599], and OPTION_S46_CONT_LW for OPTION_S46_CONT_MAPT for MAP-T [RFC7599], and OPTION_S46_CONT_LW for
Lightweight 4over6 [RFC7596]. Note however, that the ORO (Option Lightweight 4over6 [RFC7596]. Note however, that the ORO (Option
skipping to change at page 6, line 38 skipping to change at page 7, line 4
request for more than one S46 mechanism at a time. The request for more than one S46 mechanism at a time. The
Softwire46-Priority Attribute contains information allowing the Softwire46-Priority Attribute contains information allowing the
client to prioritize which mechanism to use, corresponding to client to prioritize which mechanism to use, corresponding to
OPTION_S46_PRIORITY defined in [RFC8026]. OPTION_S46_PRIORITY defined in [RFC8026].
4.1. Softwire46-Configuration Attribute 4.1. Softwire46-Configuration Attribute
The Softwire46-Configuration Attribute can only encapsulate S46 The Softwire46-Configuration Attribute can only encapsulate S46
Container Option(s). The Softwire46-Configuration Attribute is Container Option(s). The Softwire46-Configuration Attribute is
structured as follows: 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) specified in octets
S46 Container Option (s) 0 1 2 3
A variable field that may contains one or more S46 Container 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
option(s), defined in Section 4.2. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
+ S46 Container Option(s) +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBD
Length
2 + the length of the S46 Container option(s) specified in octets
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 4.2. S46 Container Options
The S46 Container Option can only be encapsulated in the The S46 Container Option can only be encapsulated in the
Softwire46-Configuration Attribute. Depending on the deployment Softwire46-Configuration Attribute. Depending on the deployment
scenario, a client might request for more than one transition scenario, a client might request for more than one transition
mechanism at a time, there MUST be at least one S46 Container option mechanism at a time, there MUST be at least one S46 Container option
encapsulated in one Softwire46-Configuration Attribute. There MUST encapsulated in one Softwire46-Configuration Attribute. There MUST
be at most one instance of each type of S46 Container Option be at most one instance of each type of S46 Container Option
encapsulated in one Softwire46-Configuration Attribute. encapsulated in one Softwire46-Configuration Attribute.
/ /
/ | 1.Rule-IPv6-Prefix Sub / | 1.Rule-IPv6-Prefix Sub
| | Option | | Option
| 1.S46-Rule Sub Option--+ 2.Rule-IPv4-Prefix Sub | 1.S46-Rule Sub Option--+ 2.Rule-IPv4-Prefix Sub
| | Option | | Option
| 2.S46-BR Sub Option | 3.EA Length Sub Option | 2.S46-BR Sub Option | 3.EA Length Sub Option
S46 Container Option--+ 3.S46-DMR Sub Option \ S46 Container Option--+ 3.S46-DMR Sub Option \
| 4.S46-v4v6Bind Sub Option | 4.S46-v4v6Bind Sub Option
| 5.S46-PORTPARAMS Sub Option | 5.S46-PORTPARAMS Sub Option
\ \
Figure 2: S46 Container Option Hierarchy Figure 2: S46 Container Option Hierarchy
There are three types of S46 Container Options, namely MAP-E There are three types of S46 Container Options, namely MAP-E
Container Option, MAP-T Container Option, Lightweight 4over6 Container Container Option, MAP-T Container Option, Lightweight 4over6
Option. Each type of S46 Container Option contains a number of sub Container Option. Each type of S46 Container Option contains a
options, defined in Section 4.3. The hierarchy of the S46 Container number of sub options, defined in Section 4.3. The hierarchy of the
Option is shown in Figure 2. Section 4.5 describes which Sub Options S46 Container Option is shown in Figure 2. Section 4.5 describes
are mandatory, optional, or not permitted for each defined S46 which Sub Options are mandatory, optional, or not permitted for each
Container Option. defined S46 Container Option.
There are three types of S46-Rule Sub Options, namely Basic Mapping There are three types of S46-Rule Sub Options, namely Basic Mapping
Rule, Forwarding Mapping Rule, Basic and Forwarding Mapping Rule. Rule, Forwarding Mapping Rule, Basic and Forwarding Mapping Rule.
Each type of S46-Rule Sub Option also contains a number of Sub Each type of S46-Rule Sub Option also contains a number of Sub
Options. The Rule-IPv6-Prefix Sub Option is necessary for every type Options. The Rule-IPv6-Prefix Sub Option is necessary for every type
of S46-Rule Sub Option. It should appear for once and only once. of S46-Rule Sub Option. It should appear for once and only once.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | | Type | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
1 MAP-E Container Option TBD1 MAP-E Container Option
2 MAP-T Container Option TBD2 MAP-T Container Option
3 Lightweight 4over6 Container Option TBD3 Lightweight 4over6 Container Option
Length Length
2 + the length of the Sub Options specified in octets 2 + the length of the Sub Options specified in octets
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.
NOTE: The Type values for each S46 Container Option are the same
as the S46-option-code values of the corresponding S46 Mechanisms
specified in Section 6.1.
4.3. Sub Options for S46 Container Option 4.3. Sub Options for S46 Container Option
4.3.1. S46-Rule Sub Option 4.3.1. S46-Rule Sub Option
The S46-Rule Sub Option can only be encapsulated in the MAP-E The S46-Rule Sub Option can only be encapsulated in the MAP-E
Container Option or the MAP-T Container Option. Depending on Container Option or the MAP-T Container Option. Depending on
deployment scenario, one Basic Mapping Rule and zero or more deployment scenario, one Basic Mapping Rule and zero or more
Forwarding Mapping Rules MUST be included in one MAP-E Container Forwarding Mapping Rules MUST be included in one MAP-E Container
Option or MAP-T Container Option. Option or MAP-T Container Option.
skipping to change at page 8, line 45 skipping to change at page 9, line 4
The S46-Rule Sub Option can only be encapsulated in the MAP-E The S46-Rule Sub Option can only be encapsulated in the MAP-E
Container Option or the MAP-T Container Option. Depending on Container Option or the MAP-T Container Option. Depending on
deployment scenario, one Basic Mapping Rule and zero or more deployment scenario, one Basic Mapping Rule and zero or more
Forwarding Mapping Rules MUST be included in one MAP-E Container Forwarding Mapping Rules MUST be included in one MAP-E Container
Option or MAP-T Container Option. Option or MAP-T Container Option.
Each type of S46-Rule Sub Option also contains a number of sub Each type of S46-Rule Sub Option also contains a number of sub
options, including Rule-IPv6-Prefix Sub Option, Rule-IPv4-Prefix Sub options, including Rule-IPv6-Prefix Sub Option, Rule-IPv4-Prefix Sub
Option, and EA Length Sub Option. The structure of the sub options Option, and EA Length Sub Option. The structure of the sub options
for S46-Rule Sub Option is defined in section 4.4. for S46-Rule Sub Option is defined in section 4.4.
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 | | | SubType | SubLen | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
1 Basic Mapping Rule (Not Forwarding Mapping Rule) 1 Basic Mapping Rule (Not Forwarding Mapping Rule)
2 Forwarding Mapping Rule (Not Basic Mapping Rule) 2 Forwarding Mapping Rule (Not Basic Mapping Rule)
3 Basic & Forwarding Mapping Rule 3 Basic & Forwarding Mapping Rule
SubLen SubLen
2 + the length of the Sub Options specified in octets 2 + the length of the Sub Options specified in octets
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
The S46-BR Sub Option an only be encapsulated in the MAP-E Container The S46-BR Sub Option an only be encapsulated in the MAP-E Container
Option or the Lightweight 4over6 Container Option. There MUST be at Option or the Lightweight 4over6 Container Option. There MUST be at
least one S46-BR Sub Option included in each MAP-E Container Option least one S46-BR Sub Option included in each MAP-E Container Option
or Lightweight 4over6 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 | | | SubType | SubLen | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
| BR-ipv6-address | | BR-ipv6-address |
| | | |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
4 (SubType number, for the S46-BR sub option) 4 (SubType number, for the S46-BR sub option)
SubLen SubLen
18 (the length of the S46-BR sub option) 18 (the length of the S46-BR sub option)
BR-ipv6-address BR-ipv6-address
a fixed-length field of 16 octets that specifies the IPv6 address a fixed-length field of 16 octets that specifies the IPv6 address
for the S46 BR. for the S46 BR.
4.3.3. S46-DMR Sub Option 4.3.3. S46-DMR Sub Option
The S46-DMR Sub Option can only appear in the MAP-T Container Option. The S46-DMR Sub Option can only appear in the MAP-T Container Option.
There MUST be exactly one S46-DMR Sub Option included in one MAP-T There MUST be exactly one S46-DMR Sub Option included in one MAP-T
Container Option. Container Option.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen |dmr-prefix6-len| | | SubType | SubLen |dmr-prefix6-len| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| 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 octets 3 + length of dmr-ipv6-prefix specified in octets
dmr-prefix6-len dmr-prefix6-len
8 bits long; 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 prefix specified in the dmr-ipv6-prefix field. Allowed values
range from 0 to 96. range 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
octet boundary when dmr-prefix6-len is not divisible by 8. octet boundary when dmr-prefix6-len is not divisible by 8.
4.3.4. S46-V4V6Bind Sub Option 4.3.4. S46-V4V6Bind Sub Option
The S46-V4V6Bind Sub Option can only be encapsulated in the The S46-V4V6Bind Sub Option can only be encapsulated in the
Lightweight 4over6 Container Option. There MUST be at most one Lightweight 4over6 Container Option. There MUST be at most one
S46-V4V6Bind Sub Option included in each Lightweight 4over6 Container S46-V4V6Bind Sub Option included in each Lightweight 4over6 Container
Option. 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SubType | SubLen | ipv4-address |
| (Continued) |bindprefix6-len| | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | (Continued) |bindprefix6-len| |
| bind-ipv6-prefix | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| (variable length) | | bind-ipv6-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
6 (SubType number, for the S46-V4V6Bind sub option) 6 (SubType number, for the S46-V4V6Bind sub option)
SubLen SubLen
the length of the S46-V4V6Bind sub option expressed in octets the length of the S46-V4V6Bind sub option expressed in octets
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
8 bits long; expresses the bitmask length of the IPv6 prefix 8 bits long; expresses the bitmask length of the IPv6 prefix
specified in the bind-ipv6-prefix field. Allowed values range from specified in the bind-ipv6-prefix field. Allowed values range from
skipping to change at page 11, line 25 skipping to change at page 12, line 4
bind-ipv6-prefix bind-ipv6-prefix
a variable-length field specifying the IPv6 prefix or address for a variable-length field specifying the IPv6 prefix or address for
the S46 CE. This field is right-padded with zeros to the nearest the S46 CE. This field is right-padded with zeros to the nearest
octet boundary when bindprefix6-len is not divisible by 8. octet boundary when bindprefix6-len is not divisible by 8.
4.3.5. S46-PORTPARAMS Sub Option 4.3.5. S46-PORTPARAMS Sub Option
The S46-PORTPARAMS Sub Option specifies optional port set information The S46-PORTPARAMS Sub Option specifies optional port set information
that MAY be provided to CEs. The S46-PORTPARAMS sub option can be that MAY be provided to CEs. The S46-PORTPARAMS sub option can be
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SubType | SubLen | PSID-Offset | PSID-len |
| PSID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
7 (SubType number, for the S46-PORTPARAMS Sub Option sub option) 7 (SubType number, for the S46-PORTPARAMS Sub Option sub option)
SubLen SubLen
6 (the length of the S46-PORTPARAMS Sub Option sub option) 6 (the length of the S46-PORTPARAMS Sub Option sub option)
PSID Offset PSID Offset
8 bits long field that specifies the numeric value for the S46 8 bits long field that specifies the numeric value for the S46
algorithm's excluded port range/ offset bits (a bits), as per algorithm's excluded port range/ offset bits (a bits), as per
Section 5.1 of RFC7597. Allowed values are between 0 and 15. Section 5.1 of RFC7597. Allowed values are between 0 and 15.
Default values for this field are specific to the Softwire Default values for this field are specific to the Softwire
mechanism being implemented and are defined in the relevant mechanism being implemented and are defined in the relevant
specification document. specification document.
PSID-len PSID-len
8 bits long; specifies the number of significant bits in the PSID 8 bits long; specifies the number of significant bits in the PSID
field. (also known as 'k'). When set to 0, the PSID field is to field. (also known as 'k'). When set to 0, the PSID field is to
be ignored. After the first 'a' bits, there are k bits in the be ignored. After the first 'a' bits, there are k bits in the
port number representing valid of PSID. Subsequently, the port number representing valid of PSID. Subsequently, the
address sharing ratio would be 2 ^k. address sharing ratio would be 2 ^k.
PSID (Port-set ID) PSID (Port-set ID)
Explicit 16-bit (unsigned word) PSID value. The PSID value Explicit 16-bit (unsigned word) PSID value. The PSID value
algorithmically identifies a set of ports assigned to a CE. The algorithmically identifies a set of ports assigned to a CE. The
first k-bits on the left of this 2-octets field is the PSID first k-bits on the left of this 2-octets field is the PSID
skipping to change at page 16, line 25 skipping to change at page 16, line 25
o Softwire46-Configuration Attribute TBD1 o Softwire46-Configuration Attribute TBD1
o Softwire46-Priority Attribute TBD2 o Softwire46-Priority Attribute TBD2
IANA should allocate the numbers from the standard RADIUS Attributes IANA should allocate the numbers from the standard RADIUS Attributes
space using the "IETF Review" policy [RFC5226]. space using the "IETF Review" policy [RFC5226].
6.1. S46 Mechanisms and Their Identifying Option Codes 6.1. S46 Mechanisms and Their Identifying Option Codes
This document requires IANA to register five option codes of the The Softwire46-Priority Attribute defines a 16-bit S46-option-code
Softwire46 mechanisms permitted to be included in the field, for which IANA is to create and maintain a new registry
Softwire46-Priority Attribute. As this work had be done in the entitled "Option Codes Permitted in the Softwire46-Priority
section 4.1 of [RFC8026], the five option codes could be consistent Attribute". This document requires IANA to register four option
with those defined in section 4.1 of [RFC8026]. Additional options codes of the Softwire46 mechanisms permitted to be included in the
may be added to this list in the future using the IETF Review process Softwire46-Priority Attribute. Additional options may be added to
described in Section 4.1 of [RFC5226]. this list in the future using the IETF Review process described in
Section 4.1 of [RFC5226].
The following table shows the option codes that are currently The following table shows the option codes that are required and the
defined and the S46 mechanisms that they represent. S46 mechanisms that they represent. The option code for DS-Lite is
derived from the IANA allocated RADIUS Attribute Type value for DS-
Lite [RFC6519]. The option codes for MAP-E, MAP-T and Lightweight
4over6 need to be determined. The option codes for MAP-E, MAP-T, and
Lightweight 4over6 should also be used as the option Type values for
the MAP-E, MAP-T, and Lightweight 4over6 Container Options defined in
Section 4.2.
+-------------+------------------+-----------+ +-------------+------------------+-----------+
| Option Code | S46 Mechanism | Reference | | Option Code | S46 Mechanism | Reference |
+-------------+------------------+-----------+ +-------------+------------------+-----------+
| 94 | MAP-E | RFC7598 | | TBD1 | MAP-E | RFC7597 |
+-------------+------------------+-----------+ +-------------+------------------+-----------+
| 95 | MAP-T | RFC7598 | | TBD2 | MAP-T | RFC7599 |
+-------------+------------------+-----------+ +-------------+------------------+-----------+
| 96 |Lightweight 4over6| RFC7598 | | TBD3 |Lightweight 4over6| RFC7596 |
+-------------+------------------+-----------+ +-------------+------------------+-----------+
| 64 | DS-Lite | RFC6334 | | 144 | DS-Lite | RFC6519 |
+--------------------------------+-----------+ +--------------------------------+-----------+
| 88 |DHCPv4 over DHCPv6| RFC7341 |
+-------------+------------------+-----------+
Table 1: Option Codes to S46 Mechanisms Table 1: Option Codes to S46 Mechanisms
7. Security Considerations 7. Security Considerations
Known security vulnerabilities of the RADIUS protocol are discussed Known security vulnerabilities of the RADIUS protocol are discussed
in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for
providing security when RADIUS is carried in IPv6 is discussed in providing security when RADIUS is carried in IPv6 is discussed in
[RFC3162]. [RFC3162].
 End of changes. 28 change blocks. 
122 lines changed or deleted 134 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/