draft-ietf-softwire-map-radius-14.txt   draft-ietf-softwire-map-radius-15.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: August 4, 2018 CNNIC Expires: September 22, 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
M. Boucadair M. Boucadair
Orange Orange
January 31, 2018 March 21, 2018
RADIUS Attribute for Softwire Address plus Port based Mechanisms RADIUS Attribute for Softwire Address plus Port based Mechanisms
draft-ietf-softwire-map-radius-14 draft-ietf-softwire-map-radius-15
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, Lightweight 4over6 and PREFIX64 option for Multicast Basic MAP-T, Lightweight 4over6 and PREFIX64 option for Multicast Basic
Bridging BroadBand (mB4) in multicast scenarios. However, in many Bridging BroadBand (mB4) in multicast scenarios. However, in many
networks, the configuration information may be stored in an networks, the configuration information may be stored in an
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 August 4, 2018. This Internet-Draft will expire on September 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 3, line 26 skipping to change at page 3, line 26
Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 29 Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
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 IPv4 service continuity mechanisms based on transit to IPv6. Many IPv4 service continuity mechanisms based on
the Address plus Port (A+P) [RFC6346] have been proposed for running the Address plus Port (A+P) [RFC6346] have been proposed for running
IPv4 over IPv6-only infrastructure. Mapping of Address and Port with IPv4 over IPv6-only infrastructure. Mapping of Address and Port with
Encapsulation (MAP-E)[RFC7597] and Mapping of Address and Port using Encapsulation (MAP-E)[RFC7597] and Mapping of Address and Port using
Translation (MAP-T)[RFC7599] are stateless mechanisms for running Translation (MAP-T) [RFC7599] are stateless mechanisms for running
IPv4 over IPv6-only infrastructure. Lightweight 4over6 [RFC7596] is IPv4 over IPv6-only infrastructure. Lightweight 4over6 [RFC7596] is
a hub-and-spoke IPv4-over-IPv6 tunneling mechanism, with complete a hub-and-spoke IPv4-over-IPv6 tunneling mechanism, with complete
independence of IPv4 and IPv6 addressing. MAP-E, MAP-T, and independence of IPv4 and IPv6 addressing. MAP-E, MAP-T, and
Lightweight 4over6 Customer Edge (CE) devices may be provisionned by Lightweight 4over6 Customer Edge (CE) devices may be provisioned by
mans of Dynamic Host Configuration Protocol for IPv6 (DHCPv6) means of Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
[RFC3315]. In particualr, the CE uses DHCPv6 options to discover the [RFC3315]. In particualr, the CE uses DHCPv6 options to discover the
Border Relay (BR) and retrieve Softwire46 (S46) configurations. Border Relay (BR) and retrieve Softwire46 (S46) configurations.
[RFC8114] specifies a generic solution for delivery of IPv4 multicast [RFC8114] specifies a generic solution for delivery of IPv4 multicast
services to IPv4 clients over an IPv6 multicast network. The services to IPv4 clients over an IPv6 multicast network. The
solution applies also for lw4o6 and MAP-E. [RFC8115] defines a solution applies also to lw4o6 and MAP-E. [RFC8115] defines a DHCPv6
DHCPv6 PREFIX64 option to convey the IPv6 prefixes to be used for PREFIX64 option to convey the IPv6 prefixes to be used for
constructing IPv4-embedded IPv6 addresses to inform the mB4 element constructing IPv4-embedded IPv6 addresses to inform the mB4 element
of the PREFIX64. The following lists the multicast-related of the PREFIX64. The following lists the multicast-related
information that needs to be provisioned: information that needs to be provisioned:
o ASM Multicast Prefix64: the IPv6 multicast prefix to be used to o ASM Multicast Prefix64: the IPv6 multicast prefix to be used to
synthesize the IPv4-embedded IPv6 addresses of the multicast synthesize the IPv4-embedded IPv6 addresses of the multicast
groups in the Any-Source Multicast (ASM) mode. groups in the Any-Source Multicast (ASM) mode.
o SSM Multicast Prefix64: the IPv6 multicast prefix to be used to o SSM Multicast Prefix64: the IPv6 multicast prefix to be used to
synthesize the IPv4-embedded IPv6 addresses of the multicast synthesize the IPv4-embedded IPv6 addresses of the multicast
skipping to change at page 4, line 17 skipping to change at page 4, line 17
IPv4 multicast sources in the IPv6 domain. Unicast Prefix64 may IPv4 multicast sources in the IPv6 domain. Unicast Prefix64 may
also be used to extract the IPv4 address from the received also be used to extract the IPv4 address from the received
multicast data flows. The address mapping follows the guidelines multicast data flows. The address mapping follows the guidelines
documented in [RFC6052]. documented in [RFC6052].
In many networks, user configuration information may be stored in an In many networks, user configuration information may be stored in an
Authentication, Authorization, and Accounting (AAA) server. Authentication, Authorization, and Accounting (AAA) server.
Currently, the AAA servers communicate using the Remote Currently, the AAA servers communicate using the Remote
Authentication Dial In User Service (RADIUS) [RFC2865] protocol. In Authentication Dial In User Service (RADIUS) [RFC2865] protocol. In
a fixed line broadband network, a Broadband Network Gateway (BNG) a fixed line broadband network, a Broadband Network Gateway (BNG)
acts as the access gateway of users. The BNG is assumed to embed a acts as the access gateway of users. A DHCPv6 server function is
DHCPv6 server function that allows it to locally handle any DHCPv6 assumed to be embedded in the BNG that allows it to locally handle
requests initiated by hosts. any DHCPv6 requests initiated by hosts.
Since the S46 configuration information is stored in an AAA servers Since the S46 configuration information is stored in an AAA servers
and user configuration information is mainly transmitted through and user configuration information is mainly transmitted through
DHCPv6 protocol between the BNGs and hosts/CEs, new RADIUS attributes DHCPv6 protocol between the BNGs and hosts/CEs, new RADIUS attributes
are needed to propagate the information from the AAA servers to BNGs. are needed to propagate the information from the AAA servers to BNGs.
The RADIUS attributes designed in this document are especially for The RADIUS attributes designed in this document are especially for
the MAP-E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], the MAP-E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596],
providing enough information to form the correspondent DHCPv6 providing enough information to form the corresponding DHCPv6
configuration options[RFC7598]. At the Section 4.9, a new RADIUS configuration options[RFC7598]. At the Section 4.9, a new RADIUS
attribute is defined to be used for carrying the Multicast-Prefixes- attribute is defined to be used for carrying the Multicast-Prefixes-
64, based on the equivalent DHCPv6 option already specified in 64, based on the equivalent DHCPv6 option already specified in
[RFC8115]. [RFC8115].
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 DS-Lite multicast Basic Bridging BroadBand element (mB4) The terms DS-Lite multicast Basic Bridging BroadBand element (mB4)
and the DS-Lite multicast Address Family Transition Router element and the DS-Lite multicast Address Family Transition Router element
(mAFTR) are defined in [RFC8114] . (mAFTR) are defined in [RFC8114] .
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 a 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 |
| |and/or S46-Multicast attribute)| | |and/or S46-Multicast attribute)|
| |<------3.Access-Accept---------| | |<------3.Access-Accept---------|
|<---4.DHCPv6 Advertisement----- | (S46-Configuration attribute | |<---4.DHCPv6 Advertisement----- | (S46-Configuration attribute |
| (container option) |and/or S46-Multicast attribute)| | (container option) |and/or S46-Multicast attribute)|
|-------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 combined 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]. For the multicast case, Lightweight 4over6 [RFC7596]. For the multicast case,
OPTION_V6_PREFIX64 should be included for the delivery of multicast OPTION_V6_PREFIX64 should be included for the delivery of multicast
services in the context of transition to IPv6. Note however, that services in the context of transition to IPv6. Note however, that
the ORO (Option Request option) with the S46 Container option code the ORO (Option Request option) with the S46 Container option code
could be optional if the network was planned as being S46-enabled as could be optional if the network was planned to be S46-enabled by
default. default.
2. When the BNG receives the Solicit message, it should initiate a 2. When the BNG receives the Solicit message, it should initiate a
radius Access-Request message, in which an User-Name attribute (1) radius Access-Request message. In this message, a User-Name
should be filled by a CE MAC address or interface-id or both, to the attribute (1) should be filled by a CE MAC address or interface-id or
RADIUS server and a User-password attribute (2) should be filled by both. This message will be sent to the RADIUS server. In this
the shared password that has been preconfigured on the DHCPv6 server, message, a User-password attribute (2) should be filled by the shared
requesting authentication as defined in [RFC2865] with the password that has been preconfigured on the DHCPv6 server, requesting
corresponding Softwire46-Configuration Attribute or authentication as defined in [RFC2865] with the corresponding
Softwire46-Multicast Attribute , which will be defined in the next Softwire46-Configuration Attribute or Softwire46-Multicast Attribute.
Section. The Softwire46-Configuration Attribute and Softwire46-Multicast
Attribute will be 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 or Softwire46-Multicast Attribute. Softwire46-Configuration Attribute or Softwire46-Multicast 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 DHCPv6 Client (CE) with an Attribute, the BNG SHOULD respond to the DHCPv6 Client (CE) with an
Advertisement 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 message, containing the 6. After receiving the client's Request message, 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
Identifier) portion. Identifier) portion.
For Lightweight 4over6 [RFC7596], the subscriber's binding state For Lightweight 4over6 [RFC7596], the subscriber's binding state
should be synchronized between the AAA server and lwAFTR. If the should be synchronized between the AAA server and lwAFTR. If the
bindings are pre-configured statically, in both the AAA server and bindings are pre-configured statically in both the AAA server and
lwAFTR, an AAA server does not need to configure the lwAFTR anymore. lwAFTR, an AAA server does not need to configure the lwAFTR anymore.
Otherwise, if the bindings are locally created on-demand in an AAA Otherwise, if the bindings are locally created on-demand in an AAA
server, it should inform the lwAFTR with the subscriber's binding server, it should inform the lwAFTR with the subscriber's binding
state, in order to synchronize the binding information of the lwB4 state, in order to synchronize the binding information of the lwB4
with the lwAFTR. 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.
skipping to change at page 9, line 35 skipping to change at page 9, line 35
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
TBD1 MAP-E Container Option TBD1 MAP-E Container Option
TBD2 MAP-T Container Option TBD2 MAP-T Container Option
TBD3 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 A variable-length field that contains necessary sub options
in Section 4.3 and zero or several optional sub options, defined in Section 4.3 and zero or several optional sub
defined in Section 4.4. options, defined in Section 4.4.
NOTE: The Type values for each S46 Container Option are the same NOTE: The Type values for each S46 Container Option are the same
as the S46-option-code values of the corresponding S46 Mechanisms as the S46-option-code values of the corresponding S46 Mechanisms
specified in Section 6.1. 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
skipping to change at page 10, line 26 skipping to change at page 10, line 26
+ 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-length 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 can 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 | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
skipping to change at page 11, line 22 skipping to change at page 11, line 22
| | | |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 A fixed-length field of 16 octets that specifies the IPv6
address for the S46 BR. address 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
skipping to change at page 12, line 21 skipping to change at page 12, line 21
| (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
4 + length of dmr-ipv6-prefix specified in octets 4 + length of dmr-ipv6-prefix specified in octets
Reserved Reserved
This field is reserved. It should be set to all zero. This field is reserved. It should be set to all zero.
dmr-prefix6-len dmr-prefix6-len
8 bits long; expresses the bitmask length of the IPv6 An 8 bits long field that expresses the bitmask length of
prefix specified in the dmr-ipv6-prefix field. Allowed the IPv6 prefix specified in the dmr-ipv6-prefix field.
values range from 0 to 96. Allowed values 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
for the BR. This field is right-padded with zeros to the address for the BR. This field is right-padded with zeros
nearest octet boundary when dmr-prefix6-len is not divisible to the nearest octet boundary when dmr-prefix6-len is not
by 8. 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
skipping to change at page 12, line 51 skipping to change at page 12, line 51
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
6 (SubType number, for the S46-V4V6Bind sub option) 6 (SubType number, for the S46-V4V6Bind sub option)
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-length field that contains sub options defined
Section 4.5. in Section 4.5.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 13, line 25 skipping to change at page 13, line 25
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
+ Sub Options + + Sub Options +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
7 (SubType number, for the S46-PORTPARAMS Sub Option) 7 (SubType number, for the S46-PORTPARAMS Sub Option)
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-length field that contains sub options defined
Section 4.6. in Section 4.6.
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 follows the framed IPv6 prefix designed in
designed in [RFC3162]. [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 |ruleprefix6-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
This field is reserved. It always set to zero. This field This field is reserved. It is always set to zero. This field
is one octet in length. is one octet in length.
ruleprefix6-len 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 A 128 bits long field that specifies an IPv6 prefix that
in a MAP rule. appears in 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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
This field is reserved. It always set to zero. This field This field is reserved. It is always set to zero. This field
is one octet in length. 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 A 32 bits long field that specifies an IPv4 prefix that
in a MAP rule. appears in 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) A 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. Sub Options for S46-v4v6Bind Sub Option 4.5. Sub Options for S46-v4v6Bind Sub Option
4.5.1. The IPv4-address Sub Option 4.5.1. The IPv4-address Sub Option
The IPv4-address Sub Option MAY be used to specify the full or shared The IPv4-address Sub Option MAY be used to specify the full or shared
IPv4 address of the CE. IPv4 address of the CE.
0 1 2 3 0 1 2 3
skipping to change at page 15, line 39 skipping to change at page 15, line 39
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubType | SubLen | ipv4-address | | SubType | SubLen | ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipv4-address | | ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
11 (SubType number, for the IPv4-address Sub Option) 11 (SubType number, for the IPv4-address Sub Option)
SubLen SubLen
6 (the length of the Rule-IPv4-Prefix Sub Option) 6 (the length of the Rule-IPv4-Prefix Sub Option)
ipv4-address ipv4-address
a 32-bits field that specifies an IPv4 address that appears A 32 bits long field that specifies an IPv4 address that
in the V4V6Bind Option appears in the V4V6Bind Option.
4.5.2. The Bind-IPv6-Prefix Sub Option 4.5.2. The Bind-IPv6-Prefix Sub Option
The IPv6 prefix field specified in this field is used by the CE to The IPv6 prefix field specified in this field is used by the CE to
identify the correct prefix to use for the tunnel source. identify the correct prefix to be used for the tunnel source.
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 |bindprefix6-len| | SubType | SubLen | Reserved |bindprefix6-len|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| bind-ipv6-prefix | | bind-ipv6-prefix |
| (variable length) | | (variable length) |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
12 (SubType number, for the Bind-IPv6-Prefix Sub Option) 12 (SubType number, for the Bind-IPv6-Prefix Sub Option)
SubLen SubLen
20 (the length of the Bind-IPv6-Prefix Sub Option) 20 (the length of the Bind-IPv6-Prefix Sub Option)
Reserved Reserved
This field is reserved. It always set to zero. This field This field is reserved. It is always set to zero. This field
is one octet in length. is one octet in length.
bindprefix6-len bindprefix6-len
8 bits long; expresses the bitmask length of the IPv6 prefix An 8 bits long field that expresses the bitmask length of
specified in the bind-ipv6-prefix field. Allowed values range the IPv6 prefix specified in the bind-ipv6-prefix field.
from 0 to 96. Allowed values range from 0 to 96.
bind-ipv6-prefix bind-ipv6-prefix
a variable-length field specifying the IPv6 prefix or address A variable-length field specifying the IPv6 prefix or
for the S46 CE. This field is right-padded with zeros to the address for the S46 CE. This field is right-padded with
nearest octet boundary when bindprefix6-len is not divisible zeros to the nearest octet boundary when bindprefix6-len
by 8. is not divisible by 8.
4.6. Sub Options for S46-PORTPARAMS Sub Option 4.6. Sub Options for S46-PORTPARAMS Sub Option
4.6.1. The PSID-offset Sub Option 4.6.1. The PSID-offset Sub Option
0 1 2 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 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 | SubLen | PSID-Offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
13 (SubType number, for the PSID-offset Sub Option) 13 (SubType number, for the PSID-offset Sub Option)
SubLen SubLen
3 (the length of the PSID-offset Sub Option) 3 (the length of the PSID-offset Sub Option)
PSID Offset PSID-Offset
8 bits long field that specifies the numeric value for the An 8 bits long field that specifies the numeric value
S46 algorithm's excluded port range/ offset bits (a bits), for the S46 algorithm's excluded port range/offset
as per Section 5.1 of RFC7597. Allowed values are between bits (a bits), as per Section 5.1 of RFC7597. Allowed
0 and 15. Default values for this field are specific to the values are between 0 and 15. Default values for this
Softwire mechanism being implemented and are defined in the field are specific to the Softwire mechanism being
relevant specification document. implemented and are defined in the relevant
specification document.
4.6.2. The PSID-len Sub Option 4.6.2. The PSID-len Sub Option
0 1 2 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 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 | SubLen | PSID-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
14 (SubType number, for the PSID-len Sub Option) 14 (SubType number, for the PSID-len Sub Option)
SubLen SubLen
3 (the length of the PSID-len Sub Option) 3 (the length of the PSID-len Sub Option)
PSID-len PSID-len
8 bits long; specifies the number of significant bits in An 8 bits long field that specifies the number of
the PSID field. (also known as 'k'). When set to 0, the significant bits in the PSID field (also known
PSID field is to be ignored. After the first 'a' bits, as 'k'). When set to 0, the PSID field is to be
there are k bits in the port number representing valid ignored. After the first 'a' bits, there are k bits
of PSID. Subsequently, the address sharing ratio would in the port number representing the value of the PSID.
be 2 ^k. Subsequently, the address sharing ratio would be 2 ^k.
4.6.3. The PSID Sub Option 4.6.3. The PSID 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 | PSID | | SubType | SubLen | PSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SubType SubType
15 (SubType number, for the PSID Sub Option) 15 (SubType number, for the PSID Sub Option)
SubLen SubLen
4 (the length of the PSID Sub Option) 4 (the length of the PSID Sub Option)
PSID (Port-set ID) PSID (Port-set ID)
Explicit 16-bit (unsigned word) PSID value. The PSID value An explicit 16-bit (unsigned word) PSID value. The PSID
algorithmically identifies a set of ports assigned to a CE. value algorithmically identifies a set of ports assigned
The first k-bits on the left of this 2-octets field is the to a CE. The first k bits on the left of this 2-octet field
PSID value. The remaining (16-k) bits on the right are is the PSID value. The remaining (16-k) bits on the right
padding zeros. are padding zeros.
4.7. Softwire46 Sub Options Encapsulation 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 |
skipping to change at page 18, line 38 skipping to change at page 18, line 38
| Type | Length | S46-option-code | | Type | Length | S46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | S46-option-code | | ... | S46-option-code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
TBD TBD
Length Length
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 A 16-bit IANA-registered option code of the DHCPv6 option
is used to identify the softwire mechanisms. S46 mechanisms that is used to identify the softwire mechanisms. S46
are prioritized in the appearance order of the mechanisms are prioritized in the appearance order of the
S46-option-code(s) in the Softwire46-Priority Attribute. S46-option-code(s) in the Softwire46-Priority Attribute.
A Softwire46-Priority Attribute MUST contain at least one A Softwire46-Priority Attribute MUST contain at least one
S46-option-code. The option codes of the corresponding S46 S46-option-code. The option codes of the corresponding S46
mechanisms are listed in Section 6.1. mechanisms are listed in Section 6.1.
4.9. Softwire46-Multicast Attribute 4.9. Softwire46-Multicast Attribute
The Softwire46-Multicast attribute conveys the IPv6 prefixes to be The Softwire46-Multicast attribute conveys the IPv6 prefixes to be
used in [RFC8114] to synthesize IPv4-embedded IPv6 addresses. The used in [RFC8114] to synthesize IPv4-embedded IPv6 addresses. The
BNG SHALL use the IPv6 prefixes returned in the RADIUS BNG SHALL use the IPv6 prefixes returned in the RADIUS
Softwire46-Multicast attribute to populate the DHCPv6 PREFIX64 Option Softwire46-Multicast attribute to populate the DHCPv6 PREFIX64 Option
[RFC8115]. [RFC8115].
This attribute MAY be used in Access-Request packets as a hint to the This attribute MAY be used in Access-Request packets as a hint to the
RADIUS server, for example, if the BNG is pre-configured with RADIUS server. For example, if the BNG is pre-configured with
Softwire46-Multicast, these prefixes MAY be inserted in the Softwire46-Multicast, these prefixes MAY be inserted in the
attribute. The RADIUS server MAY ignore the hint sent by the BNG, attribute. The RADIUS server MAY ignore the hint sent by the BNG,
and it MAY assign a different Softwire46-Multicast attribute. and it MAY assign a different Softwire46-Multicast attribute.
The Softwire46-Multicast Attribute MAY appear in an Access-Accept The Softwire46-Multicast Attribute MAY appear in an Access-Accept
packet. It MAY also appear in an Access-Request packet. packet. It MAY also appear in an Access-Request packet.
The Softwire46-Multicast Attribute MAY appear in a CoA-Request The Softwire46-Multicast Attribute MAY appear in a CoA-Request
packet. packet.
skipping to change at page 21, line 25 skipping to change at page 21, line 25
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 Figure 4
TLV-Type TLV-Type
1 1
Reserved Reserved
This field is reserved. It always set to zero. This field is one This field is reserved. It is always set to zero. This field is
octet in length. one octet in length.
Length Length
The length of the prefix, in bits. The length of the prefix, in bits.
ASM Prefix64 ASM Prefix64
IPv6 prefix. This field specifies the IPv6 multicast prefix to be IPv6 prefix. This field specifies the IPv6 multicast prefix to be
used to synthesize the IPv4-embedded IPv6 addresses of the used to synthesize the IPv4-embedded IPv6 addresses of the
multicast groups in the ASM mode. The conveyed multicast IPv6 multicast groups in the ASM mode. The conveyed multicast IPv6
skipping to change at page 22, line 25 skipping to change at page 22, line 25
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5 Figure 5
TLV-Type TLV-Type
2 2
Reserved Reserved
This fiel is reserved. It always set to zero. This field is one This fiel is reserved. It is always set to zero. This field is
octet in length. one octet in length.
Length Length
The length of the prefix, in bits. The length of the prefix, in bits.
SSM Prefix64 SSM Prefix64
IPv6 prefix. This field specifies the IPv6 multicast prefix to be IPv6 prefix. This field specifies the IPv6 multicast prefix to be
used to synthesize the IPv4-embedded IPv6 addresses of the used to synthesize the IPv4-embedded IPv6 addresses of the
multicast groups in the SSM mode. The conveyed multicast IPv6 multicast groups in the SSM mode. The conveyed multicast IPv6
skipping to change at page 23, line 25 skipping to change at page 23, line 25
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6 Figure 6
TLV-Type TLV-Type
3 3
Reserved Reserved
This fiel is reserved. It always set to zero. This field is one This fiel is reserved. It is always set to zero. This field is
octet in length. one octet in length.
Length Length
The length of the prefix, in bits. The length of the prefix, in bits.
Unicast Prefix64 Unicast Prefix64
IPv6 prefix. This field identifies the IPv6 unicast prefix to be IPv6 prefix. This field identifies the IPv6 unicast prefix to be
used in SSM mode for constructing the IPv4-embedded IPv6 addresses used in SSM mode for constructing the IPv4-embedded IPv6 addresses
representing the IPv4 multicast sources in the IPv6 domain. It representing the IPv4 multicast sources in the IPv6 domain. It
may also be used to extract the IPv4 address from the received may also be used to extract the IPv4 address from the received
multicast data flows. multicast data flows.
4.10. Table of attributes 4.10. Table of attributes
The following table provides a guide to which attributes may be found The following table describes which attributes may be found, in which
in which kinds of packets, and in what quantity. 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
0-1 0-1 0 0 0-1 TBD3 Softwire46- 0-1 0-1 0 0 0-1 TBD3 Softwire46-
Multicast Multicast
0-1 0-1 0 0 0-1 1 User-Name 0-1 0-1 0 0 0-1 1 User-Name
skipping to change at page 25, line 50 skipping to change at page 25, line 50
Known security vulnerabilities of the RADIUS protocol are discussed Known security vulnerabilities of the RADIUS protocol are discussed
in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for
providing security when RADIUS is carried in IPv6 is discussed in providing security when RADIUS is carried in IPv6 is discussed in
[RFC3162]. [RFC3162].
A malicious user may use MAC address spoofing on the shared password A malicious user may use MAC address spoofing on the shared password
that has been preconfigured on the DHCPv6 server to get unauthorized that has been preconfigured on the DHCPv6 server to get unauthorized
configuration information. configuration information.
Security considerations for MAP specific between the MAP CE and the Specific security considerations for interactions between the MAP CE
BNG are discussed in [RFC7597]. Security considerations for and the BNG are discussed in [RFC7597]. Security considerations for
Lightweight 4over6 are discussed in [RFC7596]. Security Lightweight 4over6 are discussed in [RFC7596]. Security
considerations for DHCPv6-Based S46 Prioritization Mechanism are considerations for DHCPv6-Based S46 Prioritization Mechanism are
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 to 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, Suresh Krishnan, Qian Wang, Wei Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan, Qian Wang, Wei
Meng and Cui Wang for this document. This document was merged with Meng and Cui Wang for this document. This document was merged with
 End of changes. 47 change blocks. 
99 lines changed or deleted 100 lines changed or added

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