draft-ietf-softwire-map-radius-12.txt   draft-ietf-softwire-map-radius-13.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: November 3, 2017 CNNIC Expires: February 8, 2018 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
May 2, 2017 August 7, 2017
RADIUS Attribute for Softwire Address plus Port based Mechanisms RADIUS Attribute for Softwire Address plus Port based Mechanisms
draft-ietf-softwire-map-radius-12 draft-ietf-softwire-map-radius-13
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 November 3, 2017. This Internet-Draft will expire on February 8, 2018.
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
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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Configuration process with RADIUS . . . . . . . . . . . . . . 3 3. Configuration process with RADIUS . . . . . . . . . . . . . . 4
4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6 4.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6
4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 7 4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 7
4.3. Sub Options for S46 Container Option . . . . . . . . . . 8 4.3. Sub Options for S46 Container Option . . . . . . . . . . 8
4.3.1. S46-Rule Sub Option . . . . . . . . . . . . . . . . . 8 4.3.1. S46-Rule Sub Option . . . . . . . . . . . . . . . . . 8
4.3.2. S46-BR Sub Option . . . . . . . . . . . . . . . . . . 9 4.3.2. S46-BR Sub Option . . . . . . . . . . . . . . . . . . 9
4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 10 4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 10
4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 10 4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 11
4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 11 4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 12
4.4. Sub Options for S46-Rule Sub Option . . . . . . . . . . . 12 4.4. Sub Options for S46-Rule Sub Option . . . . . . . . . . . 12
4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 12 4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 12
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. Sub Options for S46-v4v6Bind Sub Option . . . . . . . . . 14
4.6. Softwire46-Priority Attribute . . . . . . . . . . . . . . 14 4.5.1. The IPv4-address Sub Option . . . . . . . . . . . . . 14
4.7. Table of attributes . . . . . . . . . . . . . . . . . . . 15 4.5.2. The Bind-IPv6-Prefix Sub Option . . . . . . . . . . . 14
5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 16 4.6. Sub Options for S46-PORTPARAMS Sub Option . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 4.6.1. The PSID-offset Sub Option . . . . . . . . . . . . . 15
6.1. S46 Mechanisms and Their Identifying Option Codes . . . . 16 4.6.2. The PSID-len Sub Option . . . . . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 4.6.3. The PSID Sub Option . . . . . . . . . . . . . . . . . 16
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 4.7. Softwire46 Sub Options Encapsulation . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.8. Softwire46-Priority Attribute . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . 18 4.9. Table of attributes . . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . 18 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 18
Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 20 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 6.1. S46 Mechanisms and Their Identifying Option Codes . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1. Normative References . . . . . . . . . . . . . . . . . . 20
9.2. Informative References . . . . . . . . . . . . . . . . . 21
Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
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
4over6. Mapping of Address and Port with Encapsulation(MAP- 4over6. Mapping of Address and Port with Encapsulation(MAP-
E)[RFC7597], Mapping of Address and Port using Translation(MAP- E)[RFC7597], Mapping of Address and Port using Translation(MAP-
T)[RFC7599] are stateless mechanisms for running IPv4 over IPv6-only T)[RFC7599] are stateless mechanisms for running IPv4 over IPv6-only
skipping to change at page 7, line 32 skipping to change at page 7, line 32
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 | /1.IPv4-address
| 5.S46-PORTPARAMS Sub Option | | Sub Option
\ | 4.S46-v4v6Bind Sub Option---| 2.Bind-IPv6-Prefix
| \ Sub Option
| /1.PSID-offset
| | Sub Option
| 5.S46-PORTPARAMS Sub Option--| 2.PSID-len
| | Sub Option
\ \3.PSID 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 Option, MAP-T Container Option, Lightweight 4over6
Container Option. Each type of S46 Container Option contains a Container Option. Each type of S46 Container Option contains a
number of sub options, defined in Section 4.3. The hierarchy of the number of sub options, defined in Section 4.3. The hierarchy of the
S46 Container Option is shown in Figure 2. Section 4.5 describes S46 Container Option is shown in Figure 2. Section 4.5 describes
which Sub Options are mandatory, optional, or not permitted for each which Sub Options are mandatory, optional, or not permitted for each
defined S46 Container Option. defined S46 Container Option.
skipping to change at page 10, line 14 skipping to change at page 11, line 8
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 | Reserved |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 4 + length of dmr-ipv6-prefix specified in octets
Reserved
Reserved for future usage. It should be set to all zero.
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
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 | ipv4-address | | SubType | SubLen | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| (Continued) |bindprefix6-len| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + + Sub Options +
| bind-ipv6-prefix | | |
| (variable length) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ SubType
6 (SubType number, for the S46-V4V6Bind sub option)
SubType SubLen
6 (SubType number, for the S46-V4V6Bind sub option) 2 + the length of the Sub Options specified in octets
SubLen Sub Option
the length of the S46-V4V6Bind sub option expressed in octets A variable field that contains sub options defined in
ipv4-address Section 4.5.
a 32-bits field that specifies an IPv4 address that appears in
the V4V6Bind Option
bindprefix6-len
8 bits long; expresses the bitmask length of the IPv6 prefix
specified in the bind-ipv6-prefix field. Allowed values range from
0 to 96.
bind-ipv6-prefix
a variable-length field specifying the IPv6 prefix or address for
the S46 CE. This field is right-padded with zeros to the nearest
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
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 | PSID-Offset | PSID-len | | SubType | SubLen | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| PSID | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + Sub Options +
| |
SubType +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
7 (SubType number, for the S46-PORTPARAMS Sub Option sub option) SubType
SubLen 7 (SubType number, for the S46-PORTPARAMS Sub Option)
6 (the length of the S46-PORTPARAMS Sub Option sub option) SubLen
PSID Offset 2 + the length of the Sub Options specified in octets
8 bits long field that specifies the numeric value for the S46 Sub Option
algorithm's excluded port range/ offset bits (a bits), as per A variable field that contains sub options defined in
Section 5.1 of RFC7597. Allowed values are between 0 and 15. Section 4.6.
Default values for this field are specific to the Softwire
mechanism being implemented and are defined in the relevant
specification document.
PSID-len
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
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. Sub Options for S46-Rule Sub Option
4.4.1. Rule-IPv6-Prefix Sub Option 4.4.1. Rule-IPv6-Prefix Sub Option
The Rule-IPv6-Prefix Sub Option is necessary for every S46-RULE sub The Rule-IPv6-Prefix Sub Option is necessary for every S46-RULE sub
option. There MUST be exactly one S46-IPv6-Prefix Sub Option option. There MUST be exactly one S46-IPv6-Prefix Sub Option
encapsulated in each type of S46-Rule Sub Option. encapsulated in each type of S46-Rule Sub Option.
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 |ruleprefix6-len|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| rule-ipv6-prefix | | rule-ipv6-prefix |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
8 (SubType number, for the Rule-IPv6-Prefix Sub Option) 8 (SubType number, for the Rule-IPv6-Prefix Sub Option)
SubLen SubLen
20 (the length of the Rule-IPv6-Prefix Sub Option) 20 (the length of the Rule-IPv6-Prefix Sub Option)
Reserved Reserved
Reserved for future usage. It should be set to all zero. Reserved for future usage. It always set to zero. This field is
prefix6-len one octet in length.
ruleprefix6-len
the length of IPv6 prefix, specified in the rule-ipv6-prefix the length of 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.4.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
skipping to change at page 13, line 37 skipping to change at page 13, line 38
4.4.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
9 (SubType number, for the Rule-IPv4-Prefix sub option) 9 (SubType number, for the Rule-IPv4-Prefix Sub Option)
SubLen SubLen
8 (the length of the Rule-IPv4-Prefix sub option) 8 (the length of the Rule-IPv4-Prefix Sub Option)
Reserved Reserved
Reserved for future usage. It should be set to all zero Reserved for future usage. It always set to zero. This field is
one octet in length.
Prefix4-len Prefix4-len
the length of IPv4 prefix, specified in the rule-ipv4-prefix the length of IPv4 prefix, specified in the rule-ipv4-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
skipping to change at page 14, line 12 skipping to change at page 14, line 12
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
10 (SubType number, for the EA Length Sub Option) 10 (SubType number, for the EA Length Sub Option)
SubLen SubLen
4 (the length of the EA Length Sub Option) 4 (the length of the EA Length Sub Option)
EA-len EA-len
16 bits long field that specifies the Embedded-Address (EA) 16 bits long field that specifies the Embedded-Address (EA)
bit length. Allowed values range from 0 to 48. bit length. Allowed values range from 0 to 48.
4.5. Softwire46 Sub Options Encapsulation 4.5. Sub Options for S46-v4v6Bind Sub Option
4.5.1. The IPv4-address Sub Option
The IPv4-address Sub Option MAY be used to specify the full or shared
IPv4 address of the CE.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
11 (SubType number, for the IPv4-address Sub Option)
SubLen
6 (the length of the Rule-IPv4-Prefix Sub Option)
ipv4-address
a 32-bits field that specifies an IPv4 address that appears in
the V4V6Bind Option
4.5.2. The Bind-IPv6-Prefix Sub Option
The IPv6 prefix field specified in this field is used by the CE to
identify the correct prefix to use for the tunnel source.
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 | Reserved |bindprefix6-len|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| bind-ipv6-prefix |
| (variable length) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
12 (SubType number, for the Bind-IPv6-Prefix Sub Option)
SubLen
20 (the length of the Bind-IPv6-Prefix Sub Option)
Reserved
Reserved for future usage. It always set to zero. This field is
one octet in length.
bindprefix6-len
8 bits long; expresses the bitmask length of the IPv6 prefix
specified in the bind-ipv6-prefix field. Allowed values range from
0 to 96.
bind-ipv6-prefix
a variable-length field specifying the IPv6 prefix or address for
the S46 CE. This field is right-padded with zeros to the nearest
octet boundary when bindprefix6-len is not divisible by 8.
4.6. Sub Options for S46-PORTPARAMS Sub Option
4.6.1. The PSID-offset Sub Option
0 1 2
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | PSID-Offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
13 (SubType number, for the PSID-offset Sub Option)
SubLen
3 (the length of the PSID-offset 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 RFC7597. 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.
4.6.2. The PSID-len Sub Option
0 1 2
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | PSID-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType
14 (SubType number, for the PSID-len Sub Option)
SubLen
3 (the length of the PSID-len Sub Option)
PSID-len
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
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.6.3. The 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
15 (SubType number, for the PSID Sub Option)
SubLen
4 (the length of the PSID 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.7. 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.
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| Sub Option | MAP-E | MAP-T | Lightweight 4over6 | | Sub Option | MAP-E | MAP-T | Lightweight 4over6 |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-BR | M | N/P | M | | S46-BR | M | N/P | M |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-Rule | M | M | N/P | | S46-Rule | M | M | N/P |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-DMR | N/P | M | N/P | | S46-DMR | N/P | M | N/P |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-V4V6Bind | N/P | N/P | O | | S46-V4V6Bind | N/P | N/P | O |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
| S46-PORTPARAMS | O | O | O | | S46-PORTPARAMS | O | O | O |
+----------------+-------+-------+--------------------+ +----------------+-------+-------+--------------------+
M - Mandatory, O - Optional, N/P - Not Permitted M - Mandatory, O - Optional, N/P - Not Permitted
4.6. Softwire46-Priority Attribute 4.8. Softwire46-Priority Attribute
The S46-Priority Attribute is structured as follows: The S46-Priority Attribute is structured as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | S46-option-code | | Type | Length | S46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | S46-option-code | | ... | S46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 26 skipping to change at page 17, line 46
2 + the length of the S46-option-code(s) specified in octets 2 + the length of the S46-option-code(s) specified in octets
S46-option-code S46-option-code
16-bit IANA-registered option code of the DHCPv6 option that 16-bit IANA-registered option code of the DHCPv6 option that
is used to identify the softwire mechanisms. S46 mechanisms is used to identify the softwire mechanisms. S46 mechanisms
are prioritized in the appearance order of the S46-option-code(s) are prioritized in the appearance order of the S46-option-code(s)
in the Softwire46-Priority Attribute. A Softwire46-Priority in the Softwire46-Priority Attribute. A Softwire46-Priority
Attribute MUST contain at least one S46-option-code. The option Attribute MUST contain at least one S46-option-code. The option
codes of the corresponding S46 mechanisms are listed in codes of the corresponding S46 mechanisms are listed in
Section 6.1. Section 6.1.
4.7. Table of attributes 4.9. 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 Softwire46- 0-1 0-1 0 0 0-1 TBD1 Softwire46-
Configuration Configuration
0-1 0-1 0 0 0-1 TBD2 Softwire46- 0-1 0-1 0 0 0-1 TBD2 Softwire46-
Priority Priority
skipping to change at page 17, line 44 skipping to change at page 20, line 8
discussed in [RFC8026]. Furthermore, generic DHCPv6 security discussed in [RFC8026]. Furthermore, generic DHCPv6 security
mechanisms can be applied DHCPv6 intercommunication between the CE mechanisms can be applied DHCPv6 intercommunication between the CE
and the BNG. and the 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, Ian Farrer and Suresh Krishnan for this Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan and Mohamed
document. This document was merged with draft-sun-softwire-lw4over6- Boucadair for this document. This document was merged with draft-
radext-01, thanks to everyone who contributed to this draft. sun-softwire-lw4over6-radext-01, thanks to everyone who contributed
to this draft.
This document was produced using the xml2rfc tool [RFC7991]. This document was produced using the xml2rfc tool [RFC7991].
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,
skipping to change at page 19, line 20 skipping to change at page 21, line 32
"IEEE 802.1X Remote Authentication Dial In User Service "IEEE 802.1X Remote Authentication Dial In User Service
(RADIUS) Usage Guidelines", RFC 3580, (RADIUS) Usage Guidelines", RFC 3580,
DOI 10.17487/RFC3580, September 2003, DOI 10.17487/RFC3580, September 2003,
<http://www.rfc-editor.org/info/rfc3580>. <http://www.rfc-editor.org/info/rfc3580>.
[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", 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>.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011,
<http://www.rfc-editor.org/info/rfc6333>. <http://www.rfc-editor.org/info/rfc6333>.
[RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to [RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to
the IPv4 Address Shortage", RFC 6346, the IPv4 Address Shortage", RFC 6346,
 End of changes. 24 change blocks. 
104 lines changed or deleted 205 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/