rfc8658xml2.original.xml   rfc8658.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!-- This template is for creating an Internet Draft using xml2rfc, <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
which is available here: http://xml.resource.org. -->
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-ietf-softwire-map-radius-26"
ipr="trust200902">
<front>
<title abbrev="A+P RADIUS Attributes">RADIUS Attributes for Address plus
Port (A+P) based Softwire Mechanisms</title>
<author fullname="Sheng Jiang" initials="S." surname="Jiang, Ed.">
<organization>Huawei Technologies Co., Ltd</organization>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="
std" consensus="true" number="8658" ipr="trust200902" obsoletes="" updates="" xm
l:lang="en" version="3" sortRefs="true" symRefs="true" tocInclude="true" tocDept
h="4" docName="draft-ietf-softwire-map-radius-26">
<!-- xml2rfc v2v3 conversion 2.28.0 -->
<front>
<title abbrev="A+P RADIUS Attributes">RADIUS Attributes for Softwire
Mechanisms Based on Address&nbsp;plus&nbsp;Port&nbsp;(A&wj;+P)</title>
<seriesInfo name="RFC" value="8658"/>
<author fullname="Sheng Jiang" initials="S." surname="Jiang" role="editor">
<organization abbrev="Huawei">Huawei Technologies Co., Ltd.</organization>
<address> <address>
<postal> <postal>
<street>Q14, Huawei Campus, No.156 Beiqing Road</street> <street>Q14, Huawei Campus, No.156 Beiqing Road</street>
<city>Hai-Dian District, Beijing, 100095</city> <city>Hai-Dian District, Beijing, 100095</city>
<country>China</country>
<country>P.R. China</country>
</postal> </postal>
<email>jiangsheng@huawei.com</email> <email>jiangsheng@huawei.com</email>
</address> </address>
</author> </author>
<author fullname="Yu Fu" initials="Y." surname="Fu" role="editor">
<author fullname="Yu Fu" initials="Y." surname="Fu, Ed.">
<organization>CNNIC</organization> <organization>CNNIC</organization>
<address> <address>
<postal> <postal>
<street>No.4 South 4th Street, Zhongguancun</street> <street>No.4 South 4th Street, Zhongguancun</street>
<city>Hai-Dian District, Beijing, 100190</city> <city>Hai-Dian District, Beijing, 100190</city>
<country>China</country>
<country>P.R. China</country>
</postal> </postal>
<email>eleven711711@foxmail.com</email> <email>eleven711711@foxmail.com</email>
</address> </address>
</author> </author>
<author fullname="Chongfeng Xie" initials="C." surname="Xie"> <author fullname="Chongfeng Xie" initials="C." surname="Xie">
<organization>China Telecom</organization> <organization>China Telecom</organization>
<address> <address>
<postal> <postal>
<street></street> <street/>
<city>Beijing</city> <city>Beijing</city>
<code/>
<code></code> <country>China</country>
<country>P.R. China</country>
</postal> </postal>
<email>xiechf.bri@chinatelecom.cn</email> <email>xiechf.bri@chinatelecom.cn</email>
</address> </address>
</author> </author>
<author fullname="Tianxiang Li" initials="T" surname="Li"> <author fullname="Tianxiang Li" initials="T" surname="Li">
<organization>Tsinghua University</organization> <organization>Tsinghua University</organization>
<address> <address>
<postal> <postal>
<street></street> <street/>
<city>Beijing</city> <city>Beijing</city>
<code>100084</code> <code>100084</code>
<country>China</country>
<country>P.R.China</country>
</postal> </postal>
<email>peter416733@gmail.com</email> <email>peter416733@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Mohamed Boucadair" initials="M. " role="editor" surname="B
<author fullname="Mohamed Boucadair" initials="M. " role="editor" oucadair">
surname="Boucadair">
<organization>Orange</organization> <organization>Orange</organization>
<address> <address>
<postal> <postal>
<street>Rennes, 35000</street> <street/>
<city>Rennes</city>
<city>France</city> <region/>
<code>35000</code>
<region></region> <country>France</country>
<code></code>
<country></country>
</postal> </postal>
<phone/>
<phone></phone>
<facsimile></facsimile>
<email>mohamed.boucadair@orange.com</email> <email>mohamed.boucadair@orange.com</email>
<uri/>
<uri></uri>
</address> </address>
</author> </author>
<date month="October" year="2019"/>
<date day="14" month="June" year="2019" /> <area>Internet</area>
<area>Internet Area</area>
<workgroup>Softwire</workgroup> <workgroup>Softwire</workgroup>
<keyword>IPv6 Transition, MAP-E, MAP-T, Lightweight 4over6, RADIUS, <keyword>IPv6 Transition, MAP-E, MAP-T, Lightweight 4over6, RADIUS,
address sharing, authorization, AAA, provisioning</keyword> address sharing, authorization, AAA, provisioning</keyword>
<abstract> <abstract>
<t>IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity <t>IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity
services over IPv6 native networks during the IPv4/IPv6 co-existence services over IPv6 native networks during the IPv4/IPv6 coexistence
period. DHCPv6 options have been defined for configuring clients for period. DHCPv6 options have been defined to configure clients for
Lightweight 4over6, Mapping of Address and Port with Encapsulation, and Lightweight 4over6, Mapping of Address and Port with Encapsulation (MAP-E)
Mapping of Address and Port using Translation unicast softwire ,
mechanisms, and also multicast softwires. However, in many networks, Mapping of Address and Port using Translation (MAP-T) unicast softwire
mechanisms, and multicast softwires. However, in many networks,
configuration information is stored in an Authentication, Authorization, configuration information is stored in an Authentication, Authorization,
and Accounting server which utilizes the RADIUS protocol to provide and Accounting (AAA) server, which utilizes the Remote Authentication Dial
centralized management for users. When a new transition mechanism is In
developed, new RADIUS attributes need to be defined correspondingly.</t> User Service (RADIUS) protocol to provide centralized management for
users. When a new transition mechanism is developed, new RADIUS
<t>This document defines new RADIUS attributes to carry Address plus attributes need to be defined correspondingly.</t>
Port based softwire configuration parameters from an Authentication, <t>This document defines new RADIUS attributes to carry softwire
Authorization, and Accounting server to a Broadband Network Gateway. configuration parameters based on Address plus Port from a
Both unicast and multicast attributes are covered.</t> AAA server to a Broadband
Network Gateway. Both unicast and multicast attributes are covered.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section title="Introduction"> <section numbered="true" toc="default">
<name>Introduction</name>
<t>Providers have started deploying and transitioning to IPv6. Several <t>Providers have started deploying and transitioning to IPv6. Several
IPv4 service continuity mechanisms based on the Address plus Port (A+P) IPv4 service continuity mechanisms based on Address plus Port (A+P)
<xref target="RFC6346"></xref> have been proposed for providing unicast <xref target="RFC6346" format="default"/> have been proposed for providing
IPv4 over IPv6-only infrastructure, such as Mapping of Address and Port unicast
with Encapsulation (MAP-E) <xref target="RFC7597"></xref>, Mapping of IPv4-over-IPv6-only infrastructure, such as Mapping of Address and Port
Address and Port using Translation (MAP-T) <xref with Encapsulation (MAP-E) <xref target="RFC7597" format="default"/>, Mapp
target="RFC7599"></xref>, and Lightweight 4over6 <xref ing of
target="RFC7596"></xref>. Also, <xref target="RFC8114"></xref> specifies Address and Port using Translation (MAP-T) <xref target="RFC7599" format="
default"/>, and Lightweight 4over6 <xref target="RFC7596" format="default"/>. Al
so, <xref target="RFC8114" format="default"/> specifies
a generic solution for the delivery of IPv4 multicast services to IPv4 a generic solution for the delivery of IPv4 multicast services to IPv4
clients over an IPv6 multicast network. For each of these mechanisms, clients over an IPv6 multicast network. For each of these mechanisms,
DHCPv6 options have been specified for client configuration.</t> DHCPv6 options have been specified for client configuration.</t>
<!-- -->
<t>In many networks, user configuration information is stored in an <t>In many networks, user configuration information is stored in an
Authentication, Authorization, and Accounting (AAA) server. AAA servers Authentication, Authorization, and Accounting (AAA) server. AAA servers
generally communicate using the Remote Authentication Dial In User generally communicate using the Remote Authentication Dial In User
Service (RADIUS) <xref target="RFC2865"></xref> protocol. In a fixed Service (RADIUS) <xref target="RFC2865" format="default"/> protocol. In a fixed
broadband network, a Broadband Network Gateway (BNG) acts as the access broadband network, a Broadband Network Gateway (BNG) acts as the access
gateway for users. That is, the BNG acts as both an AAA client to the gateway for users. That is, the BNG acts as both a AAA client to the
AAA server, and a DHCPv6 server for DHCPv6 messages sent by clients. AAA server and a DHCPv6 server for DHCPv6 messages sent by clients.
Throughout this document, the term BNG describes a device implementing
both the AAA client and DHCPv6 server functions.</t>
<t>Since IPv4-in-IPv6 softwire configuration information is stored in an Throughout this document, the term "BNG" describes a device implementing
AAA server, and user configuration information is mainly transmitted both the AAA client and DHCPv6 server functions.</t>
<t>Since IPv4-in-IPv6 softwire configuration information is stored in a
AAA server and user configuration information is mainly transmitted
through DHCPv6 between the BNGs and Customer Premises Equipment (CEs, through DHCPv6 between the BNGs and Customer Premises Equipment (CEs,
a.k.a., CPE), new RADIUS attributes are needed to propagate the a.k.a., CPE), new RADIUS attributes are needed to propagate the
information from the AAA servers to BNGs so that they can be provided to information from the AAA servers to BNGs so that they can be provided to
CEs using the existing DHCPv6 options. </t> CEs using the existing DHCPv6 options. </t>
<t>The RADIUS attributes defined in this document provide the configuratio
<t>The RADIUS attributes defined in this document provide configuration n
to populate the corresponding DHCPv6 options for unicast and multicast to populate the corresponding DHCPv6 options for unicast and multicast
softwire configuration, specifically:</t> softwire configurations, specifically:</t>
<ul spacing="normal">
<t><list style="symbols"> <li>"Mapping of Address and Port with Encapsulation (MAP-E)" <xref targe
<t>"Mapping of Address and Port with Encapsulation (MAP-E)" <xref t="RFC7597" format="default"/> (DHCPv6 options defined in <xref target="RFC7598"
target="RFC7597"></xref> (DHCPv6 options defined in <xref format="default"/>).</li>
target="RFC7598"></xref>).</t> <li>"Mapping of Address and Port using Translation (MAP-T)" <xref target
="RFC7599" format="default"/> (DHCPv6 options defined in <xref target="RFC7598"
<t>"Mapping of Address and Port using Translation (MAP-T)" <xref format="default"/>).</li>
target="RFC7599"></xref> (DHCPv6 options defined in <xref <li>"Lightweight 4over6: An Extension to the Dual-Stack Lite
target="RFC7598"></xref>).</t> Architecture" <xref target="RFC7596" format="default"/> (DHCPv6 option
s defined
<t>"Lightweight 4over6: An Extension to the Dual-Stack Lite in <xref target="RFC7598" format="default"/>).</li>
Architecture" <xref target="RFC7596"></xref> (DHCPv6 options defined <li>"Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE):
in <xref target="RFC7598"></xref>).</t> A DHCPv6-Based Prioritization Mechanism" <xref target="RFC8026" format
="default"/>.</li>
<t>"Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): <li>"Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6
A DHCPv6-Based Prioritization Mechanism" <xref Multicast Network" <xref target="RFC8114" format="default"/> (DHCPv6 o
target="RFC8026"></xref>.</t> ptions
defined in <xref target="RFC8115" format="default"/>).</li>
<t>"Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 </ul>
Multicast Network" <xref target="RFC8114"></xref> (DHCPv6 options
defined in <xref target="RFC8115"></xref>).</t>
</list></t>
<t>The contents of the attributes defined in this document have a 1:1 <t>The contents of the attributes defined in this document have a 1:1
mapping into the fields of the various DHCPv6 options in <xref mapping into the fields of the various DHCPv6 options in <xref target="RFC
target="RFC7598"></xref>, <xref target="RFC8026"></xref>, and <xref 7598" format="default"/>, <xref target="RFC8026" format="default"/>, and <xref t
target="RFC8115"></xref>. Table 1 shows how the DHCPv6 options map to arget="RFC8115" format="default"/>. <xref target="Table1"/> shows how the DHCPv6
options map to
the corresponding RADIUS attribute. For detailed mappings between each the corresponding RADIUS attribute. For detailed mappings between each
DHCPv6 option field and the corresponding RADIUS Attribute or field, see DHCPv6 option field and the corresponding RADIUS attribute or field, see
<xref target="tlv-field-map"></xref>.</t> <xref target="tlv-field-map" format="default"/>.</t>
<t><figure
title="Table 1: Mapping between DHCPv6 Options and RADIUS Attributes">
<artwork align="center"><![CDATA[+----------------------------+-------
-------------------------+
| DHCPv6 Option | RADIUS Attribute |
+----------------------------+--------------------------------+
| OPTION_S46_RULE (89) | Softwire46-Rule |
| OPTION_S46_BR (90) | Softwire46-BR |
| OPTION_S46_DMR (91) | Softwire46-DMR |
| OPTION_S46_V4V6BIND (92) | Softwire46-V4V6Bind |
| OPTION_S46_PORTPARAMS (93) | Softwire46-PORTPARAMS |
| OPTION_S46_PRIORITY (111) | Softwire46-Priority |
| OPTION_V6_PREFIX64 (113) | Softwire46-Multicast |
+----------------------------+--------------------------------+
]]></artwork>
</figure></t>
<t>A RADIUS attribute for Dual-Stack Lite <xref target="RFC6333"></xref> <table anchor="Table1">
is defined in <xref target="RFC6519"></xref>.</t> <name>Mapping between DHCPv6 Options and RADIUS&nbsp;Attributes</name>
<thead>
<tr>
<th>DHCPv6 Option</th>
<th>RADIUS Attribute</th>
</tr>
</thead>
<tbody>
<tr>
<td>&nbsp;OPTION_S46_RULE (89)</td>
<td>&nbsp;Softwire46-Rule</td>
</tr>
<tr>
<td>&nbsp;OPTION_S46_BR (90)</td>
<td>&nbsp;Softwire46-BR</td>
</tr>
<tr>
<td>&nbsp;OPTION_S46_DMR (91)</td>
<td>&nbsp;Softwire46-DMR</td>
</tr>
<tr>
<td>&nbsp;OPTION_S46_V4V6BIND (92)</td>
<td>&nbsp;Softwire46-V4V6Bind</td>
</tr>
<tr>
<td>&nbsp;OPTION_S46_PORTPARAMS (93)</td>
<td>&nbsp;Softwire46-PORTPARAMS</td>
</tr>
<tr>
<td>&nbsp;OPTION_S46_PRIORITY (111)</td>
<td>&nbsp;Softwire46-Priority</td>
</tr>
<tr>
<td>&nbsp;OPTION_V6_PREFIX64 (113)</td>
<td>&nbsp;Softwire46-Multicast</td>
</tr>
</tbody>
</table>
<t>A RADIUS attribute for Dual-Stack Lite <xref target="RFC6333" format="d
efault"/>
is defined in <xref target="RFC6519" format="default"/>.</t>
<t>This document targets deployments where a trusted relationship is in <t>This document targets deployments where a trusted relationship is in
place between the RADIUS client and server.</t> place between the RADIUS client and server.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Terminology"> <name>Terminology</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <t>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
"OPTIONAL" in this document are to be interpreted as described in BCP 14 IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
<xref target="RFC2119"></xref> <xref target="RFC8174"></xref> when, and NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
only when, they appear in all capitals, as shown here.</t> RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be interpreted as
described in BCP&nbsp;14 <xref target="RFC2119" format="default"/> <xref tar
get="RFC8174" format="default"/>
when, and only when, they appear in all capitals, as shown here.
</t>
<t>The reader should be familiar with the concepts and terms defined in <t>The reader should be familiar with the concepts and terms defined in
<xref target="RFC7596"></xref>, <xref target="RFC7597"></xref>, <xref <xref target="RFC7596" format="default"/>, <xref target="RFC7597" format="
target="RFC7599"></xref>, and <xref target="RFC8026"></xref>.</t> default"/>, <xref target="RFC7599" format="default"/>, and <xref target="RFC8026
" format="default"/>.</t>
<t>The terms "multicast Basic Bridging BroadBand" element (mB4) and <t>The terms "multicast Basic Bridging BroadBand" element (mB4) and
"multicast Address Family Transition Router" element (mAFTR) are defined "multicast Address Family Transition Router" element (mAFTR) are defined
in <xref target="RFC8114"></xref>.</t> in <xref target="RFC8114" format="default"/>.</t>
<t>Softwire46 (S46) is used throughout to denote any of the IPv4-in-IPv6 <t>Softwire46 (S46) is used throughout to denote any of the IPv4-in-IPv6
softwire mechanisms listed above. Additionally, the following softwire mechanisms listed above. Additionally, the following
abbreviations are used within the document:<list style="symbols"> abbreviations are used within the document:</t>
<t>BNG: Broadband Network Gateway</t> <dl spacing="normal" indent="10">
<dt>BNG:</dt><dd>Broadband Network Gateway</dd>
<t>BR: Border Relay</t> <dt>BR:</dt><dd>Border Relay</dd>
<dt>CE:</dt><dd>Customer Edge</dd>
<t>CE: Customer Edge</t> <dt>CoA:</dt><dd>Change-of-Authorization </dd>
<dt>DMR:</dt><dd>Default Mapping Rule</dd>
<t>DMR: Default Mapping Rule</t> <dt>EA:</dt><dd>Embedded Address</dd>
<dt>lwAFTR:</dt><dd>Lightweight Address Family Transition Router</dd>
<t>lwAFTR: Lightweight AFTR</t> <dt>MAP-E:</dt><dd>Mapping of Address and Port with Encapsulation</dd>
<dt>MAP-T:</dt><dd>Mapping of Address and Port using Translation</dd>
<t>PSID: Port Set Identifier</t> <dt>PSID:</dt><dd>Port Set Identifier</dd>
<dt>TLV:</dt><dd>Type, Length, Value</dd>
<t>TLV: Type, Length, Value</t> </dl>
<t>MAP-E: Mapping of Address and Port with Encapsulation</t>
<t>MAP-T: Mapping of Address and Port using Translation</t>
</list></t>
</section> </section>
<section numbered="true" toc="default">
<section title="New RADIUS Attributes"> <name>New RADIUS Attributes</name>
<t>This section defines the following attributes: <list style="numbers"> <t>This section defines the following attributes: </t>
<t>Softwire46-Configuration Attribute (<xref <ol spacing="normal" type="1">
target="conf-attr"></xref>): <vspace blankLines="1" />This attribute <li>
<t>Softwire46-Configuration Attribute (<xref target="conf-attr" format
="default"/>): </t>
<t>This attribute
carries the configuration information for MAP-E, MAP-T, and carries the configuration information for MAP-E, MAP-T, and
Lightweight 4over6. The configuration information for each Lightweight 4over6. The configuration information for each
Softwire46 mechanism is carried in the corresponding Softwire46 Softwire46 mechanism is carried in the corresponding Softwire46
attributes. Different attributes are required for each Softwire46 attributes. Different attributes are required for each Softwire46
mechanism.</t> mechanism.</t>
</li>
<t>Softwire46-Priority Attribute (<xref <li>
target="s46-prio-attr"></xref>): <vspace blankLines="1" />Depending <t>Softwire46-Priority Attribute (<xref target="s46-prio-attr" format=
"default"/>): </t>
<t>Depending
on the deployment scenario, a client may support several different on the deployment scenario, a client may support several different
Softwire46 mechanisms. Therefore, a client may request configuration Softwire46 mechanisms. Therefore, a client may request configuration
for more than one Softwire46 mechanism at a time. The for more than one Softwire46 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 <xref target="RFC8026"></xref>.</t> OPTION_S46_PRIORITY defined in <xref target="RFC8026" format="default"
/>.</t>
<t>Softwire46-Multicast Attribute (<xref </li>
target="s46-mcast-attr"></xref>): <vspace blankLines="1" />This <li>
attribute conveys the IPv6 prefixes to be used in <xref <t>Softwire46-Multicast Attribute (<xref target="s46-mcast-attr" forma
target="RFC8114"></xref> to synthesize IPv4-embedded IPv6 addresses. t="default"/>): </t>
<t>This
attribute conveys the IPv6 prefixes to be used in <xref target="RFC811
4" format="default"/> to synthesize IPv4-embedded IPv6 addresses.
The BNG uses the IPv6 prefixes returned in the RADIUS The BNG uses the IPv6 prefixes returned in the RADIUS
Softwire46-Multicast Attribute to populate the DHCPv6 PREFIX64 Softwire46-Multicast Attribute to populate the DHCPv6 PREFIX64
Option <xref target="RFC8115"></xref>.</t> Option <xref target="RFC8115" format="default"/>.</t>
</list></t> </li>
</ol>
<t>All of these attributes are allocated from the RADIUS "Extended Type" <t>All of these attributes are allocated from the RADIUS "Extended Type"
code space per <xref target="RFC6929"></xref>.</t> code space per <xref target="RFC6929" format="default"/>.</t>
<t>All of these attribute designs follow <xref target="RFC6158" format="de
<t>All of these attribute designs follow <xref target="RFC6158"></xref> fault"/>
and <xref target="RFC6929"></xref>.</t> and <xref target="RFC6929" format="default"/>.</t>
<t>This document adheres to the guidance in <xref target="RFC8044" format=
<t>This document adheres to <xref target="RFC8044"></xref> for defining "default"/> for defining
the new RADIUS attributes.</t> new RADIUS attributes.</t>
<section anchor="conf-attr" numbered="true" toc="default">
<section anchor="conf-attr" title="Softwire46-Configuration Attribute"> <name>Softwire46-Configuration Attribute</name>
<t>This attribute is of type "tlv", as defined in the RADIUS Protocol <t>This attribute is of type "tlv", as defined in "Remote Authentication
Extensions <xref target="RFC6929"></xref>. It contains some Dial-In User Service (RADIUS) Protocol
Extensions" <xref target="RFC6929" format="default"/>. It contains some
sub-attributes, with the following requirements:</t> sub-attributes, with the following requirements:</t>
<ul spacing="normal">
<t><list style="empty"> <li>The Softwire46-Configuration Attribute <bcp14>MUST</bcp14> contain
<t>The Softwire46-Configuration Attribute MUST contain one or more one or more
of the following attributes: Softwire46-MAP-E, Softwire46-MAP-T, of the following attributes: Softwire46-MAP-E, Softwire46-MAP-T,
and/or Softwire46-Lightweight-4over6.</t> and/or Softwire46-Lightweight-4over6.</li>
<li>The Softwire46-Configuration Attribute conveys the
<t>The Softwire46-Configuration Attribute conveys the
configuration information for MAP-E, MAP-T, or Lightweight 4over6. configuration information for MAP-E, MAP-T, or Lightweight 4over6.
The BNG SHALL use the configuration information returned in the The BNG <bcp14>SHALL</bcp14> use the configuration information retur
RADIUS attribute to populate the DHCPv6 Softwire46 Container ned in the
Option(s) defined in Section 5 of <xref RADIUS attribute to populate the DHCPv6 Softwire46 container
target="RFC7598"></xref>.</t> option(s) defined in <xref target="RFC7598" sectionFormat="of" secti
on="5"/>.</li>
<t>The Softwire46-Configuration Attribute MAY appear in an <li>The Softwire46-Configuration Attribute <bcp14>MAY</bcp14> appear i
Access-Accept packet. It MAY also appear in an Access-Request n an
Access-Accept packet. It <bcp14>MAY</bcp14> also appear in an Access
-Request
packet to indicate a preferred Softwire46 configuration. However, packet to indicate a preferred Softwire46 configuration. However,
the server is not required to honor such a preference.</t> the server is not required to honor such a preference.</li>
<li>The Softwire46-Configuration Attribute <bcp14>MAY</bcp14> appear i
<t>The Softwire46-Configuration Attribute MAY appear in a n a
CoA-Request packet.</t> CoA-Request packet.</li>
<li>The Softwire46-Configuration Attribute <bcp14>MAY</bcp14> appear i
<t>The Softwire46-Configuration Attribute MAY appear in an n an
Accounting-Request packet.</t> Accounting-Request packet.</li>
<li>The Softwire46-Configuration Attribute <bcp14>MUST NOT</bcp14> app
<t>The Softwire46-Configuration Attribute MUST NOT appear in any ear in any
other RADIUS packet.</t> other RADIUS packet.</li>
</list></t> </ul>
<t>The Softwire46-Configuration Attribute is structured as <t>The Softwire46-Configuration Attribute is structured as
follows:</t> follows:</t>
<dl newline="true" spacing="normal">
<t><figure> <dt>Type</dt>
<artwork><![CDATA[ Type <dd>241</dd>
241 (To be confirmed by IANA). <dt>Length</dt>
<dd>
Length
Indicates the total length, in bytes, of all fields of Indicates the total length, in bytes, of all fields of
this attribute, including the Type, Length, Extended-Type, this attribute, including the Type, Length, Extended-Type,
and the entire length of the embedded attributes. and the entire length of the embedded attributes.</dd>
<dt>Extended-Type</dt>
Extended-Type <dd>9</dd>
TBD1 <dt>Value</dt>
<dd>
Value <t>
Contains one or more of the following attributes. Each attribute Contains one or more of the following attributes. Each attribute
type may appear at most once: type may appear once at most:
</t>
Softwire46-MAP-E <dl newline="true" spacing="normal">
<dt>Softwire46-MAP-E</dt>
<dd>
For configuring MAP-E clients. For the construction of For configuring MAP-E clients. For the construction of
this attribute, refer to Section 3.1.1.1. this attribute, refer to <xref target="etlv" format="default"/>.</dd>
<dt>Softwire46-MAP-T</dt>
Softwire46-MAP-T <dd>
For configuring MAP-T clients. For the construction of For configuring MAP-T clients. For the construction of
this attribute, refer to Section 3.1.1.2. this attribute, refer to <xref target="ttlv" format="default"/>.</dd>
<dt>Softwire46-Lightweight-4over6</dt>
Softwire46-Lightweight-4over6 <dd>
For configuring Lightweight 4over6 clients. For the For configuring Lightweight 4over6 clients. For the
construction of this attribute, refer to Section 3.1.1.3. construction of this attribute, refer to <xref target="ltlv" format="de
]]></artwork> fault"/>.</dd>
</figure></t> </dl>
</dd>
</dl>
<t>The Softwire46-Configuration Attribute is associated with the <t>The Softwire46-Configuration Attribute is associated with the
following identifier: 241.Extended-Type(TBD1).</t> following identifier: 241.9.</t>
<section anchor="s46-tlvs" numbered="true" toc="default">
<section anchor="s46-tlvs" title="Softwire46 Attributes"> <name>Softwire46 Attributes</name>
<t>The Softwire46 attributes can only be encapsulated in the <t>The Softwire46 attributes 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 more than one transition
mechanism at a time. There MUST be at least one Softwire46 attribute mechanism at a time. There <bcp14>MUST</bcp14> be at least one Softwir
encapsulated in one Softwire46-Configuration Attribute. There MUST e46 attribute
encapsulated in one Softwire46-Configuration Attribute. There <bcp14>M
UST</bcp14>
be at most one instance of each type of Softwire46 attribute be at most one instance of each type of Softwire46 attribute
encapsulated in one Softwire46-Configuration Attribute.</t> encapsulated in one Softwire46-Configuration Attribute.</t>
<t>There are three types of Softwire46 attributes, namely:</t>
<t>There are three types of Softwire46 attributes, namely:<list <ol spacing="normal" type="1">
style="numbers"> <li>Softwire46-MAP-E (<xref target="etlv" format="default"/>)</li>
<t>Softwire46-MAP-E (<xref target="etlv"></xref>)</t> <li>Softwire46-MAP-T (<xref target="ttlv" format="default"/>)</li>
<li>Softwire46-Lightweight 4over6 (<xref target="ltlv" format="defau
<t>Softwire46-MAP-T (<xref target="ttlv"></xref>)</t> lt"/>)</li>
</ol>
<t>Softwire46-Lightweight 4over6 (<xref <t>Each type of Softwire46 attribute contains a number of
target="ltlv"></xref>)</t> sub-attributes, defined in <xref target="s46-sub-tlv-format" format="d
</list>Each type of Softwire46 attribute contains a number of efault"/>. The hierarchy of the Softwire46
sub-attributes, defined in <xref attributes is shown in <xref target="Hierar" format="default"/>. <xre
target="s46-sub-tlv-format"></xref>. The hierarchy of the Softwire46 f target="s46-sub-tlvs" format="default"/> describes which sub-attributes are
attributes is shown in <xref target="Hierar"></xref>. <xref
target="s46-sub-tlvs"></xref> describes which sub-attributes are
mandatory, optional, or not permitted for each defined Softwire46 mandatory, optional, or not permitted for each defined Softwire46
attribute.</t> attribute.</t>
<figure anchor="Hierar">
<figure anchor="Hierar" title="Softwire46 Attributes Hierarchy"> <name>Softwire46 Attribute Hierarchy</name>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
/1.Rule-IPv6-Prefix /1.Rule-IPv6-Prefix
S / | S / |
o / | 1.Softwire46-Rule -----+ 2.Rule-IPv4-Prefix o / | 1.Softwire46-Rule --+ 2.Rule-IPv4-Prefix
f | Softwire46-MAP-E--+ | f | Softwire46-MAP-E--+ |
t | | 2.Softwire46-BR | 3.EA Length t | | 2.Softwire46-BR | 3.EA-Length
w | | \ w | | \
i | | /1.PSID-Offset i | | /1.PSID-Offset
r | | | r | | |
e | | 3.Softwire46-PORTPARAMS -----+ 2.PSID-Len e | | 3.Softwire46-PORTPARAMS -----+ 2.PSID-Len
- | \ | 4 | \ |
C | | 3.PSID 6 | | 3.PSID
o | \ - | \
n | C |
f | /1.Rule-IPv6-Prefix o | /1.Rule-IPv6-Prefix
i | / | n | / |
g | | 1.Softwire46-Rule------+ 2.Rule-IPv4-Prefix f | | 1.Softwire46-Rule---+ 2.Rule-IPv4-Prefix
u | Softwire46-MAP-T--+ | i | Softwire46-MAP-T--+ |
r | | 2.Softwire46-DMR | 3.EA Length g | | 2.Softwire46-DMR | 3.EA-Length
a | | \ u | | \
t | | /1.PSID-Offset r | | /1.PSID-Offset
i | | | a | | |
o | | 3.Softwire46-PORTPARAMS------+ 2.PSID-Len t | | 3.Softwire46-PORTPARAMS------+ 2.PSID-Len
n | \ | i | \ |
| | 3.PSID o | | 3.PSID
A | \ n | \
t | |
t | /1.IPv4-Address A | /1.IPv4-Address
r | / | t | / |
i | | 1.Softwire46-V4V6Bind -----+ 2.Bind-IPv6-Prefix t | | 1.Softwire46-V4V6Bind --+ 2.Bind-IPv6-Prefix
b | Softwire46- | \ r | Softwire46- | \
u | Lightweight-4over6+ 2.Softwire46-BR /1.PSID-Offset i | Lightweight-4over6+ 2.Softwire46-BR /1.PSID-Offset
t \ | | b \ | |
e | 3.Softwire46-PORTPARAMS ----+ 2.PSID-Len u | 3.Softwire46-PORTPARAMS ----+ 2.PSID-Len
\ | t \ |
| 3.PSID e | 3.PSID
\ \ ]]></artwork>
]]></artwork>
</figure> </figure>
<section anchor="etlv" numbered="true" toc="default">
<section anchor="etlv" title="Softwire46-MAP-E Attribute"> <name>Softwire46-MAP-E Attribute</name>
<t>Softwire46-MAP-E attribute is designed for carrying the <t> The Softwire46-MAP-E attribute is designed to carry the
configuration information for MAP-E. The structure of configuration information for MAP-E. The structure of
Softwire46-MAP-E is shown below:</t> Softwire46-MAP-E is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
1 1</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
<t>
Contains a set of sub-attributes, with the following requirements: Contains a set of sub-attributes, with the following requirements:
</t>
It MUST contain Softwire46-Rule, defined in Section 3.1.3.1. <t>
It <bcp14>MUST</bcp14> contain Softwire46-Rule, defined in <xref target="s4
It MUST contain Softwire46-BR, defined in Section 3.1.3.2. 6-rule-sub-tlv" format="default"/>.
</t>
It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5. <t>
]]></artwork> It <bcp14>MUST</bcp14> contain Softwire46-BR, defined in <xref target="s46b
</figure> r" format="default"/>.
</t>
<t>
It <bcp14>MAY</bcp14> contain Softwire46-PORTPARAMS, defined in <xref targe
t="s46param" format="default"/>.</t>
</dd>
</dl>
</section> </section>
<section anchor="ttlv" numbered="true" toc="default">
<section anchor="ttlv" title="Softwire46-MAP-T Attribute"> <name>Softwire46-MAP-T Attribute</name>
<t>Softwire46-MAP-T attribute is designed for carrying the <t>The Softwire46-MAP-T attribute is designed to carry the
configuration information for MAP-T. The structure of configuration information for MAP-T. The structure of
Softwire46-MAP-T is shown below:</t> Softwire46-MAP-T is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
2 2</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
<t>
Contains a set of sub-attributes, with the following requirements: Contains a set of sub-attributes, with the following requirements:
</t>
It MUST contain Softwire46-Rule, defined in Section 3.1.3.1. <t>
It <bcp14>MUST</bcp14> contain Softwire46-Rule, defined in <xref target="s4
It MUST contain Softwire46-DMR, defined in Section 3.1.3.3. 6-rule-sub-tlv" format="default"/>.
</t>
It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5. <t>
]]></artwork> It <bcp14>MUST</bcp14> contain Softwire46-DMR, defined in <xref target="s46
</figure> dmr" format="default"/>.
</t>
<t>
It <bcp14>MAY</bcp14> contain Softwire46-PORTPARAMS, defined in <xref targe
t="s46param" format="default"/>.</t>
</dd>
</dl>
</section> </section>
<section anchor="ltlv" numbered="true" toc="default">
<section anchor="ltlv" <name>Softwire46-Lightweight-4over6 Attribute</name>
title="Softwire46-Lightweight-4over6 Attribute"> <t>The Softwire46-Lightweight-4over6 attribute is designed to
<t>Softwire46-Lightweight-4over6 attribute is designed for carry the configuration information for Lightweight 4over6. The
carrying the configuration information for Lightweight 4over6. The
structure of Softwire46-Lightweight-4over6 is shown below:</t> structure of Softwire46-Lightweight-4over6 is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
3 3</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
<t>
Contains a set of sub-attributes as follows: Contains a set of sub-attributes as follows:
</t>
It MUST contain Softwire46-BR, defined in Section 3.1.3.2. <t>
It <bcp14>MUST</bcp14> contain Softwire46-BR, defined in <xref target="s46b
It MUST contain Softwire46-V4V6Bind, defined in Section 3.1.3.4. r" format="default"/>.
</t>
It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5. <t>
]]></artwork> It <bcp14>MUST</bcp14> contain Softwire46-V4V6Bind, defined in <xref target
</figure> ="s46bind" format="default"/>.
</t>
<t>
It <bcp14>MAY</bcp14> contain Softwire46-PORTPARAMS, defined in <xref targe
t="s46param" format="default"/>.</t>
</dd>
</dl>
</section> </section>
</section> </section>
<section anchor="s46-sub-tlvs" numbered="true" toc="default">
<section anchor="s46-sub-tlvs" title="Softwire46 Sub-Attributes"> <name>Softwire46 Sub-attributes</name>
<t>Table 2 shows which encapsulated sub-attributes are mandatory, <t><xref target="Table2"/> shows which encapsulated sub-attributes are
mandatory,
optional, or not permitted for each defined Softwire46 optional, or not permitted for each defined Softwire46
attribute.</t> attribute.</t>
<figure title="Table 2: Softwire46 Sub-Attributes"> <table anchor="Table2">
<artwork><![CDATA[+-----------------------+-------+-------+--------- <name>Softwire46 Sub-attributes</name>
-----------+ <thead>
| Sub-Attributes | MAP-E | MAP-T | Lightweight 4over6 | <tr>
+-----------------------+-------+-------+--------------------+ <th>Sub-attributes</th>
| Softwire46-BR | 1+ | 0 | 1+ | <th>MAP-E</th>
| Softwire46-Rule | 1 | 1 | 0 | <th>MAP-T</th>
| Softwire46-DMR | 0 | 1 | 0 | <th>Lightweight 4over6</th>
| Softwire46-V4V6Bind | 0 | 0 | 1 | </tr>
| Softwire46-PORTPARAMS | 0-1 | 0-1 | 0-1 | </thead>
+-----------------------+-------+-------+--------------------+ <tbody>
<tr>
]]></artwork> <td>Softwire46-BR</td>
</figure> <td>&nbsp;1+</td>
<td>&nbsp;0</td>
<t>The following table defines the meaning of Table 2 entries.</t> <td>&nbsp;1+</td>
</tr>
<tr>
<td>Softwire46-Rule</td>
<td>&nbsp;1</td>
<td>&nbsp;1</td>
<td>&nbsp;0</td>
</tr>
<tr>
<td>Softwire46-DMR</td>
<td>&nbsp;0</td>
<td>&nbsp;1</td>
<td>&nbsp;0</td>
</tr>
<tr>
<td>&nbsp;Softwire46-V4V6Bind</td>
<td>&nbsp;0</td>
<td>&nbsp;0</td>
<td>&nbsp;1</td>
</tr>
<tr>
<td>&nbsp;Softwire46-PORTPARAMS</td>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
</tr>
</tbody>
</table>
<t><figure> <t>The following list defines the meaning of the <xref target="Table2"
<artwork><![CDATA[0 Not Permitted /> entries.</t>
0-1 Optional, zero or one instance of the attribute <dl newline="false" spacing="compact" indent="6">
may be present. <dt>0</dt>
1 Mandatory, only one instance of the attribute <dd>Not permitted</dd>
must be present. <dt>0-1</dt>
1+ Mandatory, one or more instances of the attribute <dd>Optional; zero or one instance of the attribute may be present.<
may be present. /dd>
]]></artwork> <dt>1</dt>
</figure></t> <dd>Mandatory; only one instance of the attribute must be present.</
dd>
<dt>1+</dt>
<dd>Mandatory; one or more instances of the attribute may be present
.</dd>
</dl>
</section> </section>
<section anchor="s46-sub-tlv-format" numbered="true" toc="default">
<section anchor="s46-sub-tlv-format" <name>Specification of the Softwire46 Sub-attributes</name>
title="Specification of the Softwire46 Sub-Attributes"> <section anchor="s46-rule-sub-tlv" numbered="true" toc="default">
<section anchor="s46-rule-sub-tlv" title="Softwire46-Rule Attribute"> <name>Softwire46-Rule Attribute</name>
<t>Softwire46-Rule can only be encapsulated in Softwire46-MAP-E <t>Softwire46-Rule can only be encapsulated in Softwire46-MAP-E
(<xref target="etlv"></xref>) or Softwire46-MAP-T (<xref (<xref target="etlv" format="default"/>) or Softwire46-MAP-T (<xref
target="ttlv"></xref>). Depending on the deployment scenario, one target="ttlv" format="default"/>). Depending on the deployment scenario, one Bas
Basic Mapping Rule (BMR) and zero or more Forwarding Mapping Rules ic Mapping Rule (BMR) and zero or more Forwarding Mapping Rules (FMRs) <bcp14>MU
(FMRs) MUST be included in one Softwire46-MAP-E or ST</bcp14> be included in Softwire46-MAP-E and Softwire46-MAP-T.</t>
Softwire46-MAP-T.</t>
<t>Each type of Softwire46-Rule also contains a number of <t>Each type of Softwire46-Rule also contains a number of
sub-attributes, including Rule-IPv6-Prefix, Rule-IPv4-Prefix, and sub-attributes, including Rule-IPv6-Prefix, Rule-IPv4-Prefix, and
EA-Length. The structure of the sub-attributes for Softwire46-Rule EA-Length. The structure of the sub-attributes for Softwire46-Rule
is defined in <xref target="s46-rule-sub-tlvs"></xref>.</t> is defined in <xref target="s46-rule-sub-tlvs" format="default"/>.</
t>
<t>Defining multiple TLV-types achieves the same design goals as <t>Defining multiple TLV types achieves the same design goals as
the "Softwire46 Rule Flags" defined in Section 4.1 of <xref the "Softwire46 Rule Flags" defined in <xref target="RFC7598" sectio
target="RFC7598"></xref>. Using TLV-type set to 5 is equivalent to nFormat="of" section="4.1"/>. Using a TLV type set to 5 is equivalent
setting the F-flag in the OPTION_S46_RULE S46 Rule Flags to setting the F flag in the OPTION_S46_RULE S46 Rule Flags
field.</t> field.</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
4 Basic Mapping Rule only (not to be used for forwarding) <t>
5 Forwarding Permitted Mapping Rule 4 Basic Mapping Rule only (not to be used for forwarding)</t>
<t>
TLV-Length 5 Forwarding Permitted Mapping Rule</t>
</dd>
<dt>TLV-Length</dt>
<dd>
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Softwire46-Rule is of type tlv (Section 3.13 of The attribute Softwire46-Rule is of type "tlv" (<xref target="RFC8044" sect
[RFC8044]). ionFormat="of" section="3.13"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
<t>
This field contains a set of attributes as follows: This field contains a set of attributes as follows:
</t>
Rule-IPv6-Prefix <dl newline="true" spacing="normal">
<dt>Rule-IPv6-Prefix</dt>
<dd>
This attribute contains the IPv6 prefix for use in the MAP rule. This attribute contains the IPv6 prefix for use in the MAP rule.
Refer to Section 3.1.4.1. Refer to <xref target="v6prefix" format="default"/>.</dd>
<dt>Rule-IPv4-Prefix</dt>
Rule-IPv4-Prefix <dd>
This attribute contains the IPv4 prefix for use in the MAP rule. This attribute contains the IPv4 prefix for use in the MAP rule.
Refer to Section 3.1.4.2. Refer to <xref target="v4prefix" format="default"/>.</dd>
<dt>EA-Length</dt>
EA-Length <dd>
This attribute contains the Embedded-Address (EA) bit length. This attribute contains the Embedded Address (EA) bit length.
Refer to Section 3.1.4.3. Refer to <xref target="ea-length" format="default"/>.</dd>
]]></artwork> </dl>
</figure> </dd>
</dl>
</section> </section>
<section anchor="s46br" numbered="true" toc="default">
<section anchor="s46br" title="Softwire46-BR Attribute"> <name>Softwire46-BR Attribute</name>
<t>Softwire46-BR can only be encapsulated in Softwire46-MAP-E <t>Softwire46-BR can only be encapsulated in Softwire46-MAP-E
(<xref target="etlv"></xref>) or Softwire46-Lightweight-4over6 (<xref target="etlv" format="default"/>) or Softwire46-Lightweight-4
(<xref target="ltlv"></xref>).</t> over6
(<xref target="ltlv" format="default"/>).</t>
<t>There MUST be at least one Softwire46-BR included in each <t>There <bcp14>MUST</bcp14> be at least one Softwire46-BR included
in each
Softwire46-MAP-E or Softwire46-Lightweight-4over6.</t> Softwire46-MAP-E or Softwire46-Lightweight-4over6.</t>
<t>The structure of Softwire46-BR is shown below:</t> <t>The structure of Softwire46-BR is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
6 6</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
18 octets 18 octets</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Softwire46-BR is of type ip6addr (Section 3.9 of The attribute Softwire46-BR is of type "ipv6addr" (<xref target="RFC8044"
[RFC8044]). sectionFormat="of" section="3.9"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
br-ipv6-address. A fixed-length field of 16 octets that br-ipv6-address. A fixed-length field of 16 octets that
specifies the IPv6 address for the Softwire46 Border Relay (BR).]]></artwo specifies the IPv6 address for the Softwire46 Border Relay (BR).</dd>
rk> </dl>
</figure>
</section> </section>
<section anchor="s46dmr" numbered="true" toc="default">
<section anchor="s46dmr" title="Softwire46-DMR Attribute"> <name>Softwire46-DMR Attribute</name>
<t>Softwire46-DMR may only appear in Softwire46-MAP-T (<xref <t>Softwire46-DMR may only appear in Softwire46-MAP-T (<xref target=
target="ttlv"></xref>). There MUST be exactly one Softwire46-DMR "ttlv" format="default"/>). There <bcp14>MUST</bcp14> be exactly one Softwire46-
DMR
included in one Softwire46-MAP-T.</t> included in one Softwire46-MAP-T.</t>
<t>The structure of Softwire46-DMR is shown below:</t> <t>The structure of Softwire46-DMR is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
7 7</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
4 + length of dmr-ipv6-prefix specified in octets. 4 + length of dmr-ipv6-prefix specified in octets.</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Softwire46-DMR is of type ipv6pref (Section 3.10 of The attribute Softwire46-DMR is of type "ipv6prefix" (<xref target="RFC804
[RFC8044]). 4" sectionFormat="of" section="3.10"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
A variable-length (dmr-prefix6-len) field A variable-length (dmr-prefix6-len) field
specifying the IPv6 prefix (dmr-ipv6-prefix) for the BR. This field specifying the IPv6 prefix (dmr-ipv6-prefix) for the BR. This field
is right-padded with zeros to the nearest octet boundary when is right-padded with zeros to the nearest octet boundary when
dmr-prefix6-len is not divisible by 8. Prefixes with length from dmr-prefix6-len is not divisible by 8. Prefixes with lengths from
0 to 96 are allowed. 0 to 96 are allowed.</dd>
]]></artwork> </dl>
</figure>
</section> </section>
<section anchor="s46bind" numbered="true" toc="default">
<section anchor="s46bind" title="Softwire46-V4V6Bind Attribute"> <name>Softwire46-V4V6Bind Attribute</name>
<t>Softwire46-V4V6Bind may only be encapsulated in <t>Softwire46-V4V6Bind may only be encapsulated in
Softwire46-Lightweight-4over6 (<xref target="ltlv"></xref>). There Softwire46-Lightweight-4over6 (<xref target="ltlv" format="default"/
MUST be exactly one Softwire46-V4V6Bind included in each >). There
<bcp14>MUST</bcp14> be exactly one Softwire46-V4V6Bind included in e
ach
Softwire46-Lightweight-4over6.</t> Softwire46-Lightweight-4over6.</t>
<t>The structure of Softwire46-V4V6Bind is shown below:</t> <t>The structure of Softwire46-V4V6Bind is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
8 8</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Softwire46-V4V6Bind is of type tlv (Section 3.13 of The attribute Softwire46-V4V6Bind is of type "tlv" (<xref target="RFC8044"
[RFC8044]). sectionFormat="of" section="3.13"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
<t>
This field contains a set of attributes as follows: This field contains a set of attributes as follows:
</t>
IPv4-Address <dl newline="true" spacing="normal">
<dt>IPv4-Address</dt>
<dd>
This attribute contains an IPv4 address, used to specify This attribute contains an IPv4 address, used to specify
the full or shared IPv4 address of the CE. Refer to the full or shared IPv4 address of the CE. Refer to
Section 3.1.5.1. <xref target="v4address" format="default"/>.</dd>
<dt>Bind-IPv6-Prefix</dt>
Bind-IPv6-Prefix <dd>
This attribute contains an IPv6 prefix used to indicate which This attribute contains an IPv6 prefix used to indicate which
configured prefix the Softwire46 CE should use for constructing configured prefix the Softwire46 CE should use for constructing
the softwire. Refer to Section 3.1.5.2. the softwire. Refer to <xref target="bindv6" format="default"/>.</dd>
]]></artwork> </dl>
</figure> </dd>
</dl>
</section> </section>
<section anchor="s46param" numbered="true" toc="default">
<section anchor="s46param" title="Softwire46-PORTPARAMS Attribute"> <name>Softwire46-PORTPARAMS Attribute</name>
<t>Softwire46-PORTPARAMS is optional. It is used to specify port <t>Softwire46-PORTPARAMS is optional. It is used to specify port
set information for IPv4 address sharing between clients. set information for IPv4 address sharing between clients.
Softwire46-PORTPARAMS MAY be included in any of the Softwire46 Softwire46-PORTPARAMS <bcp14>MAY</bcp14> be included in any of the S oftwire46
attributes.</t> attributes.</t>
<t>The structure of Softwire46-PORTPARAMS is shown below:</t> <t>The structure of Softwire46-PORTPARAMS is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ <dd>
TLV-Type 9</dd>
9 <dt>TLV-Length</dt>
<dd>
TLV-Length
Indicates the length of this attribute, including Indicates the length of this attribute, including
the TLV-Type, TLV-Length, and TLV-Value fields. the TLV-Type, TLV-Length, and TLV-Value fields.</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Softwire46-PORTPARAMS is of type tlv (Section 3.13 The attribute Softwire46-PORTPARAMS is of type "tlv" (<xref target="RFC804
of [RFC8044]). 4" sectionFormat="of" section="3.13"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
<t>
This field contains a set of attributes as follows: This field contains a set of attributes as follows:
</t>
PSID-Offset <dl newline="true" spacing="normal">
<dt>PSID-Offset</dt>
<dd>
This attribute specifies the numeric value for the Softwire46 This attribute specifies the numeric value for the Softwire46
algorithm's excluded port range/offset bits (a bits). Refer to algorithm's excluded port range/offset bits (a bits). Refer to
Section 3.1.6.1. <xref target="psid-offset" format="default"/>.</dd>
<dt>PSID-Len</dt>
PSID-Len <dd>
This attribute specifies the number of significant bits in the This attribute specifies the number of significant bits in the
PSID field (also known as 'k'). Refer to Section 3.1.6.2. PSID field (also known as 'k'). Refer to <xref target="psid-len" format
="default"/>.</dd>
PSID <dt>PSID</dt>
This attribute specifies PSID value. Refer to Section 3.1.6.3. <dd>
]]></artwork> This attribute specifies the PSID value. Refer to <xref target="psid" f
</figure> ormat="default"/>.</dd>
</dl>
</dd>
</dl>
</section> </section>
</section> </section>
<section anchor="s46-rule-sub-tlvs" numbered="true" toc="default">
<section anchor="s46-rule-sub-tlvs" <name>Sub-attributes for Softwire46-Rule</name>
title="Sub-Attributes for Sofwtire46-Rule">
<t>There are two types of Softwire46-Rule: the Basic Mapping Rule <t>There are two types of Softwire46-Rule: the Basic Mapping Rule
and the Forwarding Mapping Rule, indicated by the value in the and the Forwarding Mapping Rule, indicated by the value in the
TLV-Type field of Softwire46-Rule (<xref TLV-Type field of Softwire46-Rule (<xref target="s46-rule-sub-tlv" for
target="s46-rule-sub-tlv"></xref>).</t> mat="default"/>).</t>
<t>Each type of Softwire46-Rule also contains a number of <t>Each type of Softwire46-Rule also contains a number of
Sub-attributes as detailed in the following sub-sections.</t> sub-attributes as detailed in the following subsections.</t>
<section anchor="v6prefix" numbered="true" toc="default">
<section title="Rule-IPv6-Prefix Attribute"> <name>Rule-IPv6-Prefix Attribute</name>
<t>Rule-IPv6-Prefix is REQUIRED for every Softwire46-Rule. There <t>Rule-IPv6-Prefix is <bcp14>REQUIRED</bcp14> for every Softwire46-
MUST be exactly one Rule-IPv6-Prefix encapsulated in each type of Rule. There
<bcp14>MUST</bcp14> be exactly one Rule-IPv6-Prefix encapsulated in
each type of
Softwire46-Rule.</t> Softwire46-Rule.</t>
<t>Rule-IPv6-Prefix follows the framed IPv6 prefix designed in <t>Rule-IPv6-Prefix follows the framed IPv6 prefix designed in
<xref target="RFC3162"></xref> and <xref <xref target="RFC3162" format="default"/> and <xref target="RFC8044"
target="RFC8044"></xref>.</t> format="default"/>.</t>
<t>The structure of Rule-IPv6-Prefix is shown below:</t> <t>The structure of Rule-IPv6-Prefix is shown below:</t>
<dl newline="true" spacing="normal">
<t><figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
10 10</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
4 + length of rule-ipv6-prefix specified in octets. 4 + length of rule-ipv6-prefix specified in
octets.</dd>
Data Type <dt>Data Type</dt>
The attribute Rule-IPv6-Prefix is of type ipv6pref (Section 3.10 <dd>
of [RFC8044]). The attribute Rule-IPv6-Prefix is of type "ipv6prefix" (<xref target="RFC8
044" sectionFormat="of" section="3.10"/>).</dd>
TLV-Value <dt>TLV-Value</dt>
<dd>
A variable-length field that specifies an IPv6 A variable-length field that specifies an IPv6
prefix (rule-ipv6-prefix) appearing in the MAP rule. prefix (rule-ipv6-prefix) appearing in the MAP rule.</dd>
]]></artwork> </dl>
</figure></t>
</section> </section>
<section anchor="v4prefix" numbered="true" toc="default">
<section title="Rule-IPv4-Prefix Attribute"> <name>Rule-IPv4-Prefix Attribute</name>
<t>This attribute is used to convey the MAP Rule IPv4 prefix. The <t>This attribute is used to convey the MAP Rule IPv4 prefix. The
structure of Rule-IPv4-Prefix is shown below:</t> structure of Rule-IPv4-Prefix is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
11 11</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
4 + length of rule-ipv4-prefix specified in octets. 4 + length of rule-ipv4-prefix specified in octets.</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Rule-IPv4-Prefix is of type ipv4pref (Section 3.11 The attribute Rule-IPv4-Prefix is of type "ipv4prefix" (<xref target="RFC8
of [RFC8044]). 044" sectionFormat="of" section="3.11"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
A variable-length field that specifies A variable-length field that specifies
an IPv4 prefix (rule-ipv4-prefix) appearing in the MAP rule. an IPv4 prefix (rule-ipv4-prefix) appearing in the MAP rule.</dd>
]]></artwork> </dl>
</figure>
</section> </section>
<section anchor="ea-length" numbered="true" toc="default">
<section title="EA-Length Attribute"> <name>EA-Length Attribute</name>
<t>This attribute is used to convey the Embedded-Address (EA) bit <t>This attribute is used to convey the Embedded Address (EA) bit
length. The structure of EA-Length is shown below:</t> length. The structure of EA-Length is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
12 12</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
6 octets 6 octets</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute EA-Length is of type integer (Section 3.1 of The attribute EA-Length is of type "integer" (<xref target="RFC8044" secti
[RFC8044]). onFormat="of" section="3.1"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
EA-len; 32-bits long. Specifies the Embedded-Address (EA) bit EA-len; 32 bits long. Specifies the Embedded Address (EA) bit
length. Allowed values range from 0 to 48.]]></artwork> length. Allowed values range from 0 to 48.</dd>
</figure> </dl>
</section> </section>
</section> </section>
<section numbered="true" toc="default">
<section title="Attributes for Softwire46-v4v6Bind"> <name>Attributes for Softwire46-v4v6Bind</name>
<section title="IPv4-Address Attribute"> <section anchor="v4address" numbered="true" toc="default">
<t>The IPv4-Address MAY be used to specify the full or shared IPv4 <name>IPv4-Address Attribute</name>
<t>The IPv4-Address <bcp14>MAY</bcp14> be used to specify the full o
r shared IPv4
address of the CE.</t> address of the CE.</t>
<t>The structure of IPv4-Address is shown below:</t> <t>The structure of IPv4-Address is shown below:</t>
<dl newline="true" spacing="normal">
<t><figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ <dd>
TLV-Type 13</dd>
13 <dt>TLV-Length</dt>
<dd>
TLV-Length 6 octets</dd>
6 octets <dt>Data Type</dt>
<dd>
Data Type The attribute IPv4-Address is of type "ipv4addr" (<xref target="RFC8044" s
The attribute IPv4-Address is of type ipv4addr (Section 3.8 ectionFormat="of" section="3.8"/>).</dd>
of [RFC8044]). <dt>TLV-Value</dt>
<dd>
TLV-Value 32 bits long. Specifies the IPv4 address (ipv4-address) to
32-bits long. Specifies the IPv4 address (ipv4-address) to appear in Softwire46-V4V6Bind (<xref target="s46bind" format="default"/>).
appear in Softwire46-V4V6Bind (Section 3.1.3.4).]]></artwork> </dd>
</figure></t> </dl>
</section> </section>
<section anchor="bindv6" numbered="true" toc="default">
<section title="Bind-IPv6-Prefix Attribute"> <name>Bind-IPv6-Prefix Attribute</name>
<t>The Bind-IPv6-Prefix is used by the CE to identify the correct <t>The Bind-IPv6-Prefix is used by the CE to identify the correct
IPv6 prefix to be used as the tunnel source.</t> IPv6 prefix to be used as the tunnel source.</t>
<t>The structure of Bind-IPv6-Prefix is shown below:</t> <t>The structure of Bind-IPv6-Prefix is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
14 14</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
4 + length of bind-ipv6-prefix specified in octets. 4 + length of bind-ipv6-prefix specified in octets.</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Bind-IPv6-Prefix is of type ipv6pref (Section 3.10 The attribute Bind-IPv6-Prefix is of type "ipv6prefix" (<xref target="RFC8
of [RFC8044]). 044" sectionFormat="of" section="3.10"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
A variable-length field specifying the IPv6 A variable-length field specifying the IPv6
prefix or address for the Softwire46 CE (bind-ipv6-prefix). prefix or address for the Softwire46 CE (bind-ipv6-prefix).
This field is right-padded with zeros to the nearest octet This field is right-padded with zeros to the nearest octet
boundary when the prefix length is not divisible by 8.]]></artwork> boundary when the prefix length is not divisible by 8.</dd>
</figure> </dl>
</section> </section>
</section> </section>
<section numbered="true" toc="default">
<section title="Attributes for Softwire46-PORTPARAMS"> <name>Attributes for Softwire46-PORTPARAMS</name>
<section title="PSID-Offset Attribute"> <section anchor="psid-offset" numbered="true" toc="default">
<name>PSID-Offset Attribute</name>
<t>This attribute is used to convey the Port Set Identifier offset <t>This attribute is used to convey the Port Set Identifier offset
as defined in <xref target="RFC7597"></xref>. This attribute is as defined in <xref target="RFC7597" format="default"/>. This attrib
encoded in 32 bits as per the recommendation in Appendix A.2.1 of ute is
<xref target="RFC6158"></xref>.</t> encoded in 32 bits as per the recommendation in
<xref target="RFC6158" sectionFormat="of" section="A.2.1"/>.</t>
<t>The structure of PSID-Offset is shown below:</t> <t>The structure of PSID-Offset is shown below:</t>
<dl newline="true" spacing="normal">
<t><figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
15 15</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
6 octets 6 octets</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute PSID-Offset is of type integer (Section 3.1 The attribute PSID-Offset is of type "integer" (<xref target="RFC8044" sec
of [RFC8044]). tionFormat="of" section="3.1"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
Contains the PSID-Offset (8-bits) right <t>Contains the PSID-Offset (8 bits) right
justified, and the unused bits in this field MUST justified, and the unused bits in this field <bcp14>MUST</bcp14>
be set to zero. This field specifies the be set to zero. This field specifies the
numeric value for the Softwire46 algorithm's excluded numeric value for the Softwire46 algorithm's excluded
port range/offset bits (a bits), as per Section 5.1 port range/offset bits (a bits), as per
of [RFC7597]. <xref target="RFC7597" sectionFormat="of" section="5.1"/>.</t>
<t>
Default values for this field are specific to the Default values for this field are specific to the
Softwire mechanism being implemented and are defined softwire mechanism being implemented and are defined
in the relevant specification document.]]></artwork> in the relevant specification document.</t></dd>
</figure></t> </dl>
</section> </section>
<section anchor="psid-len" numbered="true" toc="default">
<section title="PSID-Len Attribute"> <name>PSID-Len Attribute</name>
<t>This attribute is used to convey the PSID length as defined in <t>This attribute is used to convey the PSID length as defined in
<xref target="RFC7597"></xref>. This attribute is encoded in 32 <xref target="RFC7597" format="default"/>. This attribute is encoded
bits as per the recommendation in Appendix A.2.1 of <xref in 32
target="RFC6158"></xref>.</t> bits as per the recommendation in <xref target="RFC6158" sectionForm
at="of" section="A.2.1"/>.</t>
<t>The structure of PSID-Len is shown below:</t> <t>The structure of PSID-Len is shown below:</t>
<dl newline="true" spacing="normal">
<t><figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
16 16</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
6 octets 6 octets</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute PSID-Len is of type integer (Section 3.1 The attribute PSID-Len is of type "integer" (<xref target="RFC8044" sectio
of [RFC8044]). nFormat="of" section="3.1"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
Contains the PSID-len (8-bits) right Contains the PSID-len (8 bits) right
justified, and the unused bits in this field MUST justified, and the unused bits in this field <bcp14>MUST</bcp14>
be set to zero. This field specifies the number of be set to zero. This field specifies the number of
significant bits in the PSID field (also known as significant bits in the PSID field (also known as
'k'). When set to 0, the PSID field is to be ignored. 'k'). When set to 0, the PSID field is to be ignored.
After the first 'a' bits, there are k bits in the After the first a bits, there are k bits in the
port number representing the value of the PSID. port number representing the value of the PSID.
Subsequently, the address sharing ratio would be Subsequently, the address-sharing ratio would be
2^k.]]></artwork> 2^k.</dd>
</figure></t> </dl>
</section> </section>
<section anchor="psid" numbered="true" toc="default">
<section title="PSID Attribute"> <name>PSID Attribute</name>
<t>This attribute is used to convey the PSID as defined in <xref <t>This attribute is used to convey the PSID as defined in <xref tar
target="RFC7597"></xref>. This attribute is encoded in 32 bits as get="RFC7597" format="default"/>. This attribute is encoded in 32 bits as
per the recommendation in Appendix A.2.1 of <xref per the recommendation in <xref target="RFC6158" sectionFormat="of"
target="RFC6158"></xref>.</t> section="A.2.1"/>.</t>
<t>The structure of PSID is shown below:</t> <t>The structure of PSID is shown below:</t>
<dl newline="true" spacing="normal">
<t><figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
17 17</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
6 octets 6 octets</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute PSID is of type integer (Section 3.1 The attribute PSID is of type "integer" (<xref target="RFC8044" sectionFor
of [RFC8044]). mat="of" section="3.1"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
Contains the PSID (16-bits) right justified, and the unused bits <t>
in this field MUST be set to zero. Contains the PSID (16 bits) right justified, and the unused bits
in this field <bcp14>MUST</bcp14> be set to zero.</t>
<t>
The PSID value algorithmically identifies a set of ports The PSID value algorithmically identifies a set of ports
assigned to a CE. The first k bits on the left of this assigned to a CE. The first k bits on the left of this
2-octet field is the PSID value. The remaining (16-k) bits 2-octet field are the PSID value. The remaining (16-k) bits
on the right are padding zeros.]]></artwork> on the right are padding zeros.
</figure></t> </t>
</dd>
</dl>
</section> </section>
</section> </section>
</section> </section>
<section anchor="s46-prio-attr" numbered="true" toc="default">
<section anchor="s46-prio-attr" title="Softwire46-Priority Attribute"> <name>Softwire46-Priority Attribute</name>
<t>The Softwire46-Priority Attribute includes an ordered list of <t>The Softwire46-Priority Attribute includes an ordered list of
Softwire46 mechanisms allowing the client to prioritize which Softwire46 mechanisms allowing the client to prioritize which
mechanism to use, corresponding to OPTION_S46_PRIORITY defined in mechanism to use, corresponding to OPTION_S46_PRIORITY defined in
<xref target="RFC8026"></xref>. The following requirements apply:</t> <xref target="RFC8026" format="default"/>. The following requirements ap
ply:</t>
<t><list style="empty"> <ul empty="true" spacing="normal">
<t>The Softwire46-Priority Attribute MAY appear in an <li>The Softwire46-Priority Attribute <bcp14>MAY</bcp14> appear in an
Access-Accept packet. It MAY also appear in an Access-Request Access-Accept packet. It <bcp14>MAY</bcp14> also appear in an Access
packet.</t> -Request
packet.</li>
<t>The Softwire46-Priority Attribute MAY appear in a CoA-Request <li>The Softwire46-Priority Attribute <bcp14>MAY</bcp14> appear in a C
packet.</t> oA-Request
packet.</li>
<t>The Softwire46-Priority Attribute MAY appear in an <li>The Softwire46-Priority Attribute <bcp14>MAY</bcp14> appear in an
Accounting-Request packet.</t> Accounting-Request packet.</li>
<li>The Softwire46-Priority Attribute <bcp14>MUST NOT</bcp14> appear i
<t>The Softwire46-Priority Attribute MUST NOT appear in any other n any other
RADIUS packet.</t> RADIUS packet.</li>
</list></t> </ul>
<t>The Softwire46-Priority Attribute is structured as follows:</t>
<t>The Softwrie46-Priority Attribute is structured as follows:<figure> <dl newline="true" spacing="normal">
<artwork><![CDATA[ Type <dt>Type</dt>
241 (To be confirmed by IANA) <dd>
241</dd>
Length <dt>Length</dt>
<dd>
Indicates the length of this attribute, Indicates the length of this attribute,
including the Type, Length, Extended-Type and Value fields. including the Type, Length, Extended-Type and Value fields.</dd>
<dt>Extended-Type</dt>
Extended-Type <dd>
TBD5 10</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
<t>
The attribute includes one or more Softwire46-Option-Code TLVs: The attribute includes one or more Softwire46-Option-Code TLVs:
A Softwire46-Priority Attribute MUST contain at least one A Softwire46-Priority Attribute <bcp14>MUST</bcp14> contain at least one
Softwire46-Option-Code TLV (Section 3.2.1). Softwire46-Option-Code TLV (<xref target="opc" format="default"/>).</t>
<t>
Softwire46 mechanisms are prioritized in the appearance order Softwire46 mechanisms are prioritized in the appearance order
of the in the Softwire46-Priority Attribute. That is, in the Softwire46-Priority Attribute. That is,
the first-appearing mechanism is most preferred. the first-appearing mechanism is most preferred.</t>
]]></artwork> </dd>
</figure></t> </dl>
<t>The Softwire46-Priority Attribute is associated with the following <t>The Softwire46-Priority Attribute is associated with the following
identifier: 241.Extended-Type (TBD5).</t> identifier: 241.10.</t>
<section anchor="opc" numbered="true" toc="default">
<section anchor="opc" title="Softwire46-Option-Code"> <name>Softwire46-Option-Code</name>
<t>This attribute is used to convey an option code assigned to a <t>This attribute is used to convey an option code assigned to a
Softwire46 mechanism <xref target="RFC8026"></xref>. This attribute Softwire46 mechanism <xref target="RFC8026" format="default"/>. This a
is encoded in 32 bits as per the recommendation in Appendix A.2.1 of ttribute
<xref target="RFC6158"></xref>.</t> is encoded in 32 bits as per the recommendation in
<xref target="RFC6158" sectionFormat="of" section="A.2.1"/>.</t>
<t>The structure of Softwire46-Option-Code is shown below:</t> <t>The structure of Softwire46-Option-Code is shown below:</t>
<dl newline="true" spacing="normal">
<t><figure> <dt>TLV-Type</dt>
<artwork><![CDATA[ TLV-Type <dd>
18 18</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
6 octets 6 octets</dd>
<dt>Data Type</dt>
Data Type <dd>
The attribute Softwire46-Option-Code is of type integer The attribute Softwire46-Option-Code is of type "integer"
(Section 3.1 of [RFC8044]). (<xref target="RFC8044" sectionFormat="of" section="3.1"/>).</dd>
<dt>TLV-Value</dt>
TLV-Value <dd>
A 32-bit IANA-registered option code representing a Softwire46 A 32-bit IANA-registered option code representing a Softwire46
mechanism (Softwire46-option-code). The codes and their mechanism (Softwire46-option-code). The codes and their
corresponding Softwire46 mechanisms are listed in Section 7.3.]]></artwork corresponding Softwire46 mechanisms are listed in <xref target="s46option"
> format="default"/>.</dd>
</figure></t> </dl>
<t></t>
</section> </section>
</section> </section>
<section anchor="s46-mcast-attr" numbered="true" toc="default">
<section anchor="s46-mcast-attr" title="Softwire46-Multicast Attribute"> <name>Softwire46-Multicast Attribute</name>
<t>The Softwire46-Multicast Attribute conveys the IPv6 prefixes to be <t>The Softwire46-Multicast Attribute conveys the IPv6 prefixes to be
used to synthesize multicast and unicast IPv4-embedded IPv6 addresses used to synthesize multicast and unicast IPv4-embedded IPv6 addresses
as per <xref target="RFC8114"></xref>. This attribute is of type "tlv" as per <xref target="RFC8114" format="default"/>. This attribute is of t ype "tlv"
and contains additional TLVs. The following requirements apply:</t> and contains additional TLVs. The following requirements apply:</t>
<ul spacing="normal">
<t><list style="empty"> <li>The BNG <bcp14>SHALL</bcp14> use the IPv6 prefixes returned in the
<t>The BNG SHALL use the IPv6 prefixes returned in the RADIUS RADIUS
Softwire46-Multicast Attribute to populate the DHCPv6 PREFIX64 Softwire46-Multicast Attribute to populate the DHCPv6 PREFIX64
Option <xref target="RFC8115"></xref>.</t> Option <xref target="RFC8115" format="default"/>.</li>
<li>This attribute <bcp14>MAY</bcp14> be used in Access-Request packet
<t>This attribute MAY be used in Access-Request packets as a hint s as a hint
to the RADIUS server. For example, if the BNG is pre-configured to the RADIUS server. For example, if the BNG is preconfigured
for Softwire46-Multicast, these prefixes may be inserted in the for 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 <bcp14>MAY</bcp14> ignore the hint sent
and it MAY assign a different Softwire46-Multicast Attribute.</t> by the BNG,
and it <bcp14>MAY</bcp14> assign a different Softwire46-Multicast At
<t>The Softwire46-Multicast Attribute MAY appear in an tribute.</li>
<li>The Softwire46-Multicast Attribute <bcp14>MAY</bcp14> appear in an
Access-Request, Access-Accept, CoA-Request, and Accounting-Request Access-Request, Access-Accept, CoA-Request, and Accounting-Request
packet.</t> packet.</li>
<li>The Softwire46-Multicast Attribute <bcp14>MUST NOT</bcp14> appear
<t>The Softwire46-Multicast Attribute MUST NOT appear in any other in any other
RADIUS packet.</t> RADIUS packet.</li>
<li>The Softwire46-Multicast Attribute <bcp14>MAY</bcp14> contain ASM-
<t>The Softwire46-Multicast Attribute MAY contain ASM-Prefix64 Prefix64
(<xref target="TLV0"></xref>), SSM-Prefix64 (<xref (<xref target="TLV0" format="default"/>), SSM-Prefix64 (<xref target
target="TLV1"></xref>), and U-Prefix64 (<xref ="TLV1" format="default"/>), and U-Prefix64 (<xref target="TLV2" format="default
target="TLV2"></xref>).</t> "/>).</li>
<li>The Softwire46-Multicast Attribute <bcp14>MUST</bcp14> include ASM
<t>The Softwire46-Multicast Attribute MUST include ASM-Prefix64 or -Prefix64 or
SSM-Prefix64, and it MAY include both.</t> SSM-Prefix64, and it <bcp14>MAY</bcp14> include both.</li>
<li>The U-Prefix64 <bcp14>MUST</bcp14> be present when SSM-Prefix64 is
<t>The U-Prefix64 MUST be present when SSM-Prefix64 is present. present.
U-Prefix64 MAY be present when ASM-Prefix64 is present.</t> U-Prefix64 <bcp14>MAY</bcp14> be present when ASM-Prefix64 is presen
</list></t> t.</li>
</ul>
<t>The Softwire46-Multicast Attribute is structured as follows:</t> <t>The Softwire46-Multicast Attribute is structured as follows:</t>
<dl newline="true" spacing="normal">
<figure> <dt>Type</dt>
<artwork><![CDATA[ <dd>
Type 241</dd>
241 (To be confirmed by IANA) <dt>Length</dt>
<dd>
Length
This field indicates the total length in bytes of all fields of This field indicates the total length in bytes of all fields of
this attribute, including the Type, Length, Extended-Type, and the this attribute, including the Type, Length, Extended-Type, and the
entire length of the embedded attributes. entire length of the embedded attributes.</dd>
<dt>Extended-Type</dt>
Extended-Type <dd>
TBD6 11</dd>
<dt>Value</dt>
Value <dd>
<t>
This field contains a set of attributes as follows: This field contains a set of attributes as follows:
</t>
ASM-Prefix64 <dl newline="true" spacing="normal">
<dt>ASM-Prefix64</dt>
<dd>
This attribute contains the Any-Source Multicast (ASM) This attribute contains the Any-Source Multicast (ASM)
IPv6 prefix. Refer to Section 3.3.1. IPv6 prefix. Refer to <xref target="TLV0" format="default"/>.</dd>
<dt>SSM-Prefix64</dt>
SSM-Prefix64 <dd>
This attribute contains the Source-Source Multicast (SSM) This attribute contains the Source-Source Multicast (SSM)
IPv6 prefix. Refer to Section 3.3.2. IPv6 prefix. Refer to <xref target="TLV1" format="default"/>.</dd>
<dt>U-Prefix64</dt>
U-Prefix64 <dd>
This attribute contains the IPv4 prefix used for address This attribute contains the IPv4 prefix used for address
translation. Refer to Section 3.3.3. translation. Refer to <xref target="TLV2" format="default"/>.</dd>
]]></artwork> </dl>
</figure> </dd>
</dl>
<t>The Softwire46-Multicast Attribute is associated with the following <t>The Softwire46-Multicast Attribute is associated with the following
identifier: 241.Extended-Type(TBD6).</t> identifier: 241.11.</t>
<section anchor="TLV0" numbered="true" toc="default">
<section anchor="TLV0" title="ASM-Prefix64 Attribute"> <name>ASM-Prefix64 Attribute</name>
<t>The ASM-Prefix64 attribute is structured as follows:</t> <t>The ASM-Prefix64 attribute is structured as follows:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<preamble></preamble> <dd>
19</dd>
<artwork><![CDATA[ <dt>TLV-Length</dt>
TLV-Type <dd>
19 16 octets. The length of asm-prefix64 must be /96 <xref target="RFC8115" f
ormat="default"/>.</dd>
TLV-Length <dt>Data Type</dt>
16 octets. The length of asm-prefix64 must be /96 [RFC8115]. <dd>
The attribute ASM-Prefix64 is of type "ipv6prefix" (<xref target="RFC8044"
Data Type sectionFormat="of" section="3.10"/>).</dd>
The attribute ASM-Prefix64 is of type ipv6prefix (Section 3.10 of <dt>TLV-Value</dt>
[RFC8044]). <dd>
TLV-Value
This field specifies the IPv6 multicast prefix (asm-prefix64) This field specifies the IPv6 multicast prefix (asm-prefix64)
to be used to synthesize the IPv4-embedded IPv6 addresses of the to be 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
prefix MUST belong to the ASM range. prefix <bcp14>MUST</bcp14> belong to the ASM range. </dd>
]]></artwork> </dl>
</figure>
</section> </section>
<section anchor="TLV1" numbered="true" toc="default">
<section anchor="TLV1" title="SSM-Prefix64 Attribute"> <name>SSM-Prefix64 Attribute</name>
<t>The SSM-Prefix64 attribute is structured as follows:</t> <t>The SSM-Prefix64 attribute is structured as follows:</t>
<dl newline="true" spacing="normal">
<figure> <dt>Type</dt>
<artwork><![CDATA[ Type <dd>
20 20</dd>
<dt>TLV-Length</dt>
TLV-Length <dd>
16 octets. The length of ssm-prefix64 must be /96 [RFC8115]. 16 octets. The length of ssm-prefix64 must be /96 <xref target="RFC8115" f
ormat="default"/>.</dd>
Data Type <dt>Data Type</dt>
The attribute SSM-Prefix64 is of type ipv6prefix (Section 3.10 of <dd>
[RFC8044]). The attribute SSM-Prefix64 is of type "ipv6prefix" (<xref target="RFC8044"
sectionFormat="of" section="3.10"/>).</dd>
TLV-Type <dt>TLV-Type</dt>
<dd>
This field specifies the IPv6 multicast prefix (ssm-prefix64) This field specifies the IPv6 multicast prefix (ssm-prefix64)
to be used to synthesize the IPv4-embedded IPv6 addresses of the to be 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
prefix MUST belong to the SSM range. prefix <bcp14>MUST</bcp14> belong to the SSM range. </dd>
]]></artwork> </dl>
</figure>
</section> </section>
<section anchor="TLV2" numbered="true" toc="default">
<section anchor="TLV2" title="U-Prefix64 Attribute"> <name>U-Prefix64 Attribute</name>
<t>The structure of U-Prefix64 is shown below:</t> <t>The structure of U-Prefix64 is shown below:</t>
<dl newline="true" spacing="normal">
<figure> <dt>TLV-Type</dt>
<preamble></preamble> <dd>
21</dd>
<artwork><![CDATA[ <dt>TLV-Length</dt>
TLV-Type <dd>
21 4 + length of unicast-prefix. As specified in <xref target="RFC6052" forma
t="default"/>,
TLV-Length the unicast-prefix prefix length <bcp14>MUST</bcp14> be set to 32, 40, 48,
4 + length of unicast-prefix. As specified in [RFC6052], 56, 64, or 96.</dd>
the unicast-prefix prefix-length MUST be set to 32, 40, 48, <dt>Data Type</dt>
56, 64, or 96. <dd>
The attribute U-Prefix64 is of type "ipv6prefix" (<xref target="RFC8044" s
Data Type ectionFormat="of" section="3.10"/>).</dd>
The attribute U-Prefix64 is of type ipv6prefix (Section 3.10 of <dt>TLV-Value</dt>
[RFC8044]). <dd>
TLV-Value
This field identifies the IPv6 unicast prefix (u-prefix64) to This field identifies the IPv6 unicast prefix (u-prefix64) to
be used in SSM mode for constructing the IPv4-embedded IPv6 be used in the SSM mode for constructing the IPv4-embedded IPv6
addresses representing the IPv4 multicast sources in the IPv6 addresses representing the IPv4 multicast sources in the IPv6
domain. It may also be used to extract the IPv4 address from the domain. It may also be used to extract the IPv4 address from the
received multicast data flows. ]]></artwork> received multicast data flows.</dd>
</figure> </dl>
</section> </section>
</section> </section>
</section> </section>
<section numbered="true" toc="default">
<section title="A Sample Configuration Process with RADIUS"> <name>A Sample Configuration Process with RADIUS</name>
<t><xref target="example"></xref> illustrates how the RADIUS and DHCPv6 <t><xref target="example" format="default"/> illustrates how the RADIUS an
d DHCPv6
protocols interwork to provide CE with softwire configuration protocols interwork to provide CE with softwire configuration
information.</t> information.</t>
<figure anchor="example">
<figure align="center" anchor="example" <name>Interaction between DHCPv6 and AAA Server with RADIUS&nbsp;Authent
title="Interaction between DHCPv6 and AAA Server with RADIUS authe ication</name>
ntication"> <artwork name="" type="" align="left" alt=""><![CDATA[
<artwork><![CDATA[ CE BNG AAA Server
CE BNG AAA Server | | |
| | | |-------1.DHCPv6 Solicit------->| |
|-------1.DHCPv6 Solicit------->| | |(ORO with unicast and/or | |
|(ORO with unicast and/or m'cast| | | multicast container option | |
| container option code(s)) | | | codes(s)) | |
| | | | |-------2.Access-Request------->|
| |-------2.Access-Request------->| | | (Softwire46-Configuration |
| | (Softwire46-Configuration | | | Attribute and/or |
| | Attribute and/or | | |Softwire46-Multicast Attribute)|
| |Softwire46-Multicast Attribute)| | | |
| | | | |<------3.Access-Accept---------|
| |<------3.Access-Accept---------| | | (Softwire46-Configuration |
| | (Softwire46-Configuration | | | Attribute and/or |
| | Attribute and/or | | |Softwire46-Multicast Attribute)|
| |Softwire46-Multicast Attribute)| | | |
| | | |<----4.DHCPv6 Advertisement----| |
|<----4.DHCPv6 Advertisement----| | | (container option(s)) | |
| (container option(s)) | | | | |
| | | |-------5.DHCPv6 Request------>| |
|-------5.DHCPv6 Request------>| | | (container option(s)) | |
| (container Option(s)) | | | | |
| | | |<--------6.DHCPv6 Reply--------| |
|<--------6.DHCPv6 Reply--------| | | (container option(s)) | |
| (container option(s)) | | | | |
| | | DHCPv6 RADIUS]]></artwork>
DHCPv6 RADIUS
]]></artwork>
</figure> </figure>
<ol spacing="normal" type="1">
<t><list style="numbers"> <li>The CE creates a DHCPv6 Solicit message. For unicast softwire
<t>The CE creates a DHCPv6 Solicit message. For unicast softwire
configuration, the message includes an OPTION_REQUEST_OPTION (6) configuration, the message includes an OPTION_REQUEST_OPTION (6)
with the Softwire46 Container option code(s) as defined in <xref with the Softwire46 Container option code(s) as defined in <xref targe
target="RFC7598"></xref>. OPTION_S46_CONT_MAPE (94) should be t="RFC7598" format="default"/>. OPTION_S46_CONT_MAPE (94) should be
included for MAP-E, OPTION_S46_CONT_MAPT (95) for MAP-T, and included for MAP-E, OPTION_S46_CONT_MAPT (95) for MAP-T, and
OPTION_S46_CONT_LW (96) for Lightweight 4over6. For multicast OPTION_S46_CONT_LW (96) for Lightweight 4over6. For multicast
configuration, the option number for OPTION_V6_PREFIX64 (113) is configuration, the option number for OPTION_V6_PREFIX64 (113) is
included in the client's ORO. The message is sent to the BNG.</t> included in the client's Option Request Option (ORO). The message is s ent to the BNG.</li>
<t>On receipt of the Solicit message, the BNG constructs a RADIUS <li>On receipt of the DHCPv6 Solicit message, the BNG constructs a RADIU S
Access-Request message containing a User-Name Attribute (1) Access-Request message containing a User-Name Attribute (1)
(containing either a CE MAC address, interface-id, or both), a (containing either a CE Media Access Control (MAC) address,
User-Password Attribute (2) (with a pre-configured shared password interface-id, or both) and a
between the CE and AAA server as defined in <xref User-Password Attribute (2) (with a preconfigured shared password
target="RFC2865"></xref>). The Softwire46-Configuration Attribute between the CE and AAA server as defined in <xref target="RFC2865" for
mat="default"/>). The Softwire46-Configuration Attribute
and/or Softwire46-Multicast Attribute are also included (as and/or Softwire46-Multicast Attribute are also included (as
requested by the client). The resulting message is sent to the AAA requested by the client). The resulting message is sent to the AAA
server.</t> server.</li>
<li>The AAA server authenticates the request. If this is successful,
<t>The AAA server authenticates the request. If this is successful, and a suitable configuration is available, an Access-Accept message
and suitable configuration is available, an Access-Accept message is is sent to the BNG containing the requested Softwire46-Configuration
sent to the BNG containing the requested Softwire46-Configuration
Attribute or Softwire46-Multicast Attribute. It is the Attribute or Softwire46-Multicast Attribute. It is the
responsibility of the AAA server to ensure the consistency of the responsibility of the AAA server to ensure the consistency of the
provided configuration.</t> provided configuration.</li>
<li>The BNG maps the received softwire configuration into the
<t>The BNG maps the received softwire configuration into the
corresponding fields in the DHCPv6 softwire configuration option(s). corresponding fields in the DHCPv6 softwire configuration option(s).
These are included in the DHCPv6 Advertise message which is sent to These are included in the DHCPv6 Advertise message, which is sent to
the CE.</t> the CE.</li>
<li>The CE sends a DHCPv6 Request message. In the ORO, the option
<t>The CE sends a DHCPv6 Request message. In the ORO, the option codes of any of the required softwire options that were received
code(s) of any of the required softwire options that were received in the DHCPv6 Advertise message are included.</li>
in the Advertise message are included.</t> <li>The BNG sends a DHCPv6 Reply message to the client containing the
softwire container option(s) enumerated in the ORO.</li>
<t>The BNG sends a DHCPv6 Reply message to the client containing the </ol>
softwire container option(s) enumerated in the ORO.</t> <t>The authorization operation could be done independently after the
</list></t>
<t>The authorization operation could be done independently, after the
authentication process. In this case, steps 1-5 are completed as above, authentication process. In this case, steps 1-5 are completed as above,
then the following steps are performed:</t> then the following steps are performed:</t>
<dl newline="false" spacing="normal" indent="5">
<t><list hangIndent="4" style="hanging"> <dt>6a.</dt>
<t hangText="6a.">When the BNG receives the DHCPv6 Request, it <dd>When the BNG receives the DHCPv6 Request, it
constructs a RADIUS Access-Request message, which contains a constructs a RADIUS Access-Request message, which contains a
Service-Type Attribute (6) with the value "Authorize Only" (17), the Service-Type Attribute (6) with the value "Authorize Only" (17), the
corresponding Softwire46-Configuration Attribute, and a State corresponding Softwire46-Configuration Attribute, and a State
Attribute obtained from the previous authentication process Attribute obtained from the previous authentication process
according to <xref target="RFC5080"></xref>. The resulting message according to <xref target="RFC5080" format="default"/>. The resulting
is sent to the AAA server.</t> message
is sent to the AAA server.</dd>
<t hangText="7a.">The AAA checks the authorization request. If it is <dt>7a.</dt>
<dd>The AAA server checks the authorization request. If it is
approved, an Access-Accept message is returned to the BNG with the approved, an Access-Accept message is returned to the BNG with the
corresponding Softwire46-Configuration Attribute.</t> corresponding Softwire46-Configuration Attribute.</dd>
<dt>8a.</dt>
<t hangText="8a.">The BNG sends a Reply message to the client <dd>The BNG sends a Reply message to the client
containing the softwire container options enumerated in the ORO.</t> containing the softwire container options enumerated in the ORO.</dd>
</list></t> </dl>
<t>In addition to the above, the following points need to be <t>In addition to the above, the following points need to be
considered:</t> considered:</t>
<ul spacing="normal">
<t><list style="symbols"> <li>In the configuration message flows described above, the
<t>In the configuration message flows described above the Message-Authenticator (type 80) <xref target="RFC2869" format="default
Message-Authenticator (type 80) <xref target="RFC2869"></xref> "/>
should be used to protect both Access-Request and Access-Accept should be used to protect both Access-Request and Access-Accept
messages.</t> messages.</li>
<li>If the BNG does not receive the corresponding
<t>If the BNG does not receive the corresponding Softwire46-Configuration Attribute in the Access-Accept message, it
Softwire46-Configuration Attribute in the Access-Accept message it
may fall back to creating the DHCPv6 softwire configuration options may fall back to creating the DHCPv6 softwire configuration options
using pre-configured Softwire46 configuration, if this is using the preconfigured Softwire46 configuration if this is
present.</t> present.</li>
<li>If the BNG receives an Access-Reject from the AAA server, then
<t>If the BNG receives an Access-Reject from the AAA server, then the Softwire46 configuration must not be supplied to the client.</li>
Softwire46 configuration must not be supplied to the client.</t> <li>As specified in <xref target="RFC8415" sectionFormat="of" section="1
8.2.5"/> ("Creation and Transmission of Rebind Messages") if the DHCPv6 server
<t>As specified in <xref target="RFC8415"></xref>, Section 18.2.5,
"Creation and Transmission of Rebind Messages", if the DHCPv6 server
to which the DHCPv6 Renew message was sent at time T1 has not to which the DHCPv6 Renew message was sent at time T1 has not
responded by time T2, the CE (DHCPv6 client) should enter the Rebind responded by time T2, the CE (DHCPv6 client) should enter the Rebind
state and attempt to contact any available server. In this state and attempt to contact any available server. In this
situation, a secondary BNG receiving the DHCPv6 message must situation, a secondary BNG receiving the DHCPv6 message must
initiate a new Access-Request message towards the AAA server. The initiate a new Access-Request message towards the AAA server. The
secondary BNG includes the Softwire46-Configuration Attribute in secondary BNG includes the Softwire46-Configuration Attribute in
this Access-Request message.</t> this Access-Request message.</li>
<li>For Lightweight 4over6, the CE's binding state needs to be
<t>For Lightweight 4over6, the CE's binding state needs to be
synchronized between the clients and the Lightweight AFTR synchronized between the clients and the Lightweight AFTR
(lwAFTR)/BR. This can be achieved in two ways: static (lwAFTR)/BR. This can be achieved in two ways: static
pre-configuration of the bindings on both the AAA server and lwAFTR, preconfiguration of the bindings on both the AAA server and lwAFTR
or on-demand whereby the AAA server updates the lwAFTR with the CE's or on demand, whereby the AAA server updates the lwAFTR with the CE's
binding state as it is created or deleted.</t> binding state as it is created or deleted.</li>
</list></t> </ul>
<t>In some deployments, the DHCP server may use the Accounting-Request <t>In some deployments, the DHCP server may use the Accounting-Request
to report to a AAA server the softwire configuration returned to a to report the softwire configuration returned to a
requesting host. It is the responsibility of the DHCP server to ensure requesting host to a AAA server. It is the responsibility of the DHCP serv
the consistency of the configuration provided to requesting hosts. er to ensure
the consistency of the configuration provided to the requesting hosts.
Reported data to a AAA server may be required for various operational Reported data to a AAA server may be required for various operational
purposes (e.g., regulatory).</t> purposes (e.g., regulatory).</t>
<t>A configuration change (e.g., BR address) may result in an exchange <t>A configuration change (e.g., BR address) may result in an exchange
of CoA-Requests between the BNG and the AAA server as shown in <xref of CoA-Requests between the BNG and the AAA server, as shown in <xref targ
target="coa"></xref>. Concretely, when the BNG receives a CoA-Request et="coa" format="default"/>. Concretely, when the BNG receives a CoA-Request
message containing Softwire46 attributes, it sends a DHCPv6 Reconfigure message containing Softwire46 attributes, it sends a DHCPv6 Reconfigure
message to the appropriate CE to inform that CE that an updated message to the appropriate CE to inform that CE that an updated
configuration is available. Upon receipt of such message, the CE sends a configuration is available. Upon receipt of such a message, the CE sends a
DHCPv6 Renew or Information-Request in order to receive the updated DHCPv6 Renew or Information-Request in order to receive the updated
Softwire46 configuration. In deployments where the BNG embeds a DHCPv6 Softwire46 configuration. In deployments where the BNG embeds a DHCPv6
relay, CoA-Requests can be used following the procedure specified in relay, CoA-Requests can be used following the procedure specified in
<xref target="RFC6977"></xref>. </t> <xref target="RFC6977" format="default"/>. </t>
<figure anchor="coa">
<t><figure anchor="coa" title="Change of Configuration Example"> <name>Change of Configuration Example</name>
<artwork><![CDATA[ CE BNG <artwork name="" type="" align="left" alt=""><![CDATA[
AAA Server CE BNG AAA Server
| | | | | |
|---DHCPv6 Solicit--------->| | |---DHCPv6 Solicit--------->| |
| |---Access-Request---------->| | |---Access-Request---------->|
| |<--Access-Accept------------| | |<--Access-Accept------------|
| |(Softwire46-Configuration | | |(Softwire46-Configuration |
| | Attribute ...) | | | Attribute ...) |
.... ....
| | | | | |
| |<-----CoA-Request-----------| | |<-----CoA-Request-----------|
| |(Softwire46-Configuration | | |(Softwire46-Configuration |
| | Attribute ...) | | | Attribute ...) |
| |------CoA-Response--------->| | |------CoA-Response--------->|
|<--DHCPv6 Reconfigure------| | |<--DHCPv6 Reconfigure------| |
| | | | | |
....]]></artwork> ....]]></artwork>
</figure></t> </figure>
</section> </section>
<section title="Table of Attributes"> <section numbered="true" toc="default">
<name>Table of Attributes</name>
<t>This document specifies three new RADIUS attributes, and their <t>This document specifies three new RADIUS attributes, and their
formats are as follows:</t> formats are as follows:</t>
<ul spacing="normal">
<t><list style="symbols"> <li>Softwire46-Configuration Attribute: 241.9</li>
<t>Softwire46-Configuration Attribute: 241.TBD1</t> <li>Softwire46-Priority Attribute: 241.10</li>
<li>Softwire46-Multicast Attribute: 241.11</li>
<t>Softwire46-Priority Attribute: 241.TBD5</t> </ul>
<t><xref target="Table3"/> describes which attributes may be found in whic
<t>Softwire46-Multicast Attribute: 241.TBD6</t> h kinds of
</list></t>
<t>Table 3 describes which attributes may be found, in which kinds of
packets and in what quantity.</t> packets and in what quantity.</t>
<t><figure title="Table 3: Table of Attributes"> <table anchor="Table3">
<artwork><![CDATA[Request Accept Reject Challenge Acct CoA- # A <name>Table of Attributes</name>
ttribute <thead>
Req Req <tr>
0-1 0-1 0 0 0-1 0-1 241.TBD1 Softwire46- <th>Request</th>
Configuration <th>Accept</th>
0-1 0-1 0 0 0-1 0-1 241.TBD5 Softwire46- <th>Reject</th>
Priority <th>Challenge</th>
0-1 0-1 0 0 0-1 0-1 241.TBD6 Softwire46- <th>Acct Req</th>
Multicast <th>CoA-Req</th>
]]></artwork> <th>#</th>
</figure></t> <th>Attribute</th>
</tr>
</thead>
<tbody>
<tr>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
<td>0</td>
<td>&nbsp;0</td>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
<td>&nbsp;241.9</td>
<td>Softwire46-&zwsp;Configuration</td>
</tr>
<tr>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
<td>0</td>
<td>&nbsp;0</td>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
<td>&nbsp;241.10</td>
<td>Softwire46-&zwsp;Priority</td>
</tr>
<tr>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
<td>0</td>
<td>&nbsp;0</td>
<td>&nbsp;0-1</td>
<td>&nbsp;0-1</td>
<td>&nbsp;241.11</td>
<td>Softwire46-&zwsp;Multicast</td>
</tr>
</tbody>
</table>
<t></t>
</section> </section>
<section anchor="Security" numbered="true" toc="default">
<section anchor="Security" title="Security Considerations"> <name>Security Considerations</name>
<t>Section 9 of <xref target="RFC7596"></xref> discusses security issues <t><xref target="RFC7596" sectionFormat="of" section="9"/> discusses secur
related to Lightweight 4over6, Section 10 of <xref ity issues
target="RFC7597"></xref> discusses security issues related to MAP-E, related to Lightweight 4over6; <xref target="RFC7597" sectionFormat="of" s
Section 13 of <xref target="RFC7599"></xref> discusses security issues ection="10"/> discusses security issues related to MAP-E;
related to MAP-T, and Section 9 of <xref target="RFC8114"></xref> <xref target="RFC7599" sectionFormat="of" section="13"/> discusses securi
ty issues
related to MAP-T; and <xref target="RFC8114" sectionFormat="of" section="9
"/>
discusses security issues related to the delivery of IPv4 multicast discusses security issues related to the delivery of IPv4 multicast
services to IPv4 clients over an IPv6 multicast network.</t> services to IPv4 clients over an IPv6 multicast network.</t>
<t>This document does not introduce any security issues inherently <t>This document does not introduce any security issues inherently
different from those already identified in Section 8 of <xref different from those already identified in <xref target="RFC2865" sectionF
target="RFC2865"></xref> and Section 6 of <xref target="RFC5176"></xref> ormat="of" section="8"/> and <xref target="RFC5176" sectionFormat="of" section="
6"/>
for CoA messages. Known security vulnerabilities of the RADIUS protocol for CoA messages. Known security vulnerabilities of the RADIUS protocol
discussed in Section 7 of <xref target="RFC2607"></xref> and Section 7 discussed in <xref target="RFC2607" sectionFormat="of" section="7"/> and
of <xref target="RFC2869"></xref> apply to this specification. These <xref target="RFC2869" sectionFormat="of" section="7"/> apply to this spec
ification. These
well-established properties of the RADIUS protocol place some well-established properties of the RADIUS protocol place some
limitations on how it can safely be used, since there is some inherent limitations on how it can safely be used, since there is some inherent
requirement to trust the counterparty to not misbehave.</t> requirement to trust the counterparty to not misbehave.</t>
<t>Accordingly, this document targets deployments where a trusted <t>Accordingly, this document targets deployments where a trusted
relationship is in place between the RADIUS client and server with relationship is in place between the RADIUS client and server, with
communication optionally secured by IPsec or Transport Layer Security communication optionally secured by IPsec or Transport Layer Security
(TLS) <xref target="RFC6614"></xref>. The use of IPsec <xref (TLS) <xref target="RFC6614" format="default"/>. The use of IPsec <xref ta
target="RFC4301"></xref> for providing security when RADIUS is carried rget="RFC4301" format="default"/> for providing security when RADIUS is carried
in IPv6 is discussed in <xref target="RFC3162"></xref>.</t> in IPv6 is discussed in <xref target="RFC3162" format="default"/>.</t>
<t>Security considerations for interactions between a Softwire46 CE and <t>Security considerations for interactions between a Softwire46 CE and
the BNG are discussed in Section 9 of <xref target="RFC7598"></xref> the BNG are discussed in <xref target="RFC7598" sectionFormat="of" section
(DHCPv6 options for configuration of softwire46 address and port-mapped ="9"/>
clients), Section 3 of <xref target="RFC8026"></xref> (DHCPv6-based (DHCPv6 options for the configuration of Softwire46 address and port-mappe
Softwire46 prioritization mechanism), and Section 5 of <xref d
target="RFC8115"></xref> (DHCPv6 options for configuration of clients), <xref target="RFC8026" sectionFormat="of" section="3"/> (a DHCPv
6-based
Softwire46 prioritization mechanism), and <xref target="RFC8115" sectionFo
rmat="of" section="5"/> (DHCPv6 options for configuration of
IPv4-embedded IPv6 prefixes).</t> IPv4-embedded IPv6 prefixes).</t>
</section> </section>
<section anchor="IANA" numbered="true" toc="default">
<section anchor="IANA" title="IANA Considerations"> <name>IANA Considerations</name>
<t>IANA is requested to make new code point assignments for RADIUS <t>IANA has made new code point assignments for RADIUS
attributes as described in the following subsections. The assignments attributes as described in the following subsections. The assignments
should use the RADIUS registry available at should use the RADIUS registry available at
https://www.iana.org/assignments/radius-types/.</t> &lt;<eref target="https://www.iana.org/assignments/radius-types/"/>&gt;.</
t>
<section title="New RADIUS Attributes"> <section numbered="true" toc="default">
<t>This document requests IANA to assign the Attribute Types defined <name>New RADIUS Attributes</name>
in this document from the RADIUS namespace as described in the "IANA <t>IANA has assigned the attribute types defined
Considerations" section of <xref target="RFC3575"></xref>, in in this document from the RADIUS namespace as described in Section <xref
accordance with BCP 26 <xref target="RFC8126"></xref>.</t> target="RFC3575" section="2" sectionFormat="bare">IANA Considerations</xref> of
<xref target="RFC3575"/>, in
<t>This document requests that IANA register three new RADIUS accordance with BCP 26 <xref target="RFC8126" format="default"/>.</t>
attributes, from the "Short Extended Space" of <xref <t>IANA has registered three new RADIUS
target="RFC6929"></xref>. The attributes are: Softwire46-Configuration attributes from the "Short Extended Space" section of <xref target="RFC6
929" format="default"/>. The attributes are the Softwire46-Configuration
Attribute, Softwire46-Priority Attribute, and Softwire46-Multicast Attribute, Softwire46-Priority Attribute, and Softwire46-Multicast
Attribute:</t> Attribute:</t>
<figure> <table anchor="Table4">
<artwork><![CDATA[ Type Description Data Type <name>New RADIUS Attributes</name>
Reference <thead>
---- ----------- --------- --------- <tr>
241.TBD1 Softwire46-Configuration tlv Section 3.1 <th>Type</th>
241.TBD5 Softwire46-Priority tlv Section 3.2 <th>Description</th>
241.TBD6 Softwire46-Multicast tlv Section 3.3]]></artwork> <th>Data Type</th>
</figure> <th>Reference</th>
</section> </tr>
</thead>
<tbody>
<tr>
<td>&nbsp;241.9</td>
<td>&nbsp;Softwire46-Configuration</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="conf-attr"/></td>
</tr>
<tr>
<td>&nbsp;241.10</td>
<td>&nbsp;Softwire46-Priority</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="s46-prio-attr"/></td>
</tr>
<tr>
<td>&nbsp;241.11</td>
<td>&nbsp;Softwire46-Multicast</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="s46-mcast-attr"/></td>
</tr>
</tbody>
</table>
<section title="RADIUS Softwire46 Configuration and Multicast Attributes"> </section>
<t>IANA is requested to create a new registry called "RADIUS <section numbered="true" toc="default">
<name>RADIUS Softwire46 Configuration and Multicast Attributes</name>
<t>IANA has created a new registry called "RADIUS
Softwire46 Configuration and Multicast Attributes".</t> Softwire46 Configuration and Multicast Attributes".</t>
<t>All attributes in this registry have one or more parent RADIUS <t>All attributes in this registry have one or more parent RADIUS
attributes in nesting (refer to <xref target="RFC6929"></xref>).</t> attributes in nesting (refer to <xref target="RFC6929" format="default"/
>).</t>
<t>This registry must be initially populated with the following <t>This registry has been initially populated with the following
values:</t> values:</t>
<t><figure> <table anchor="Table5">
<artwork><![CDATA[Value Description Data Type <name>RADIUS Softwire46 Configuration and Multicast Attributes</name>
Reference <thead>
0 Reserved <tr>
1 Softwire46-MAP-E tlv Section 3.1.1.1 <th>Value</th>
2 Softwire46-MAP-T tlv Section 3.1.1.2 <th>Description</th>
3 Softwire46-Lightweight-4over6 tlv Section 3.1.1.3 <th>Data Type</th>
4 Softwire46-Rule (BMR) tlv Section 3.1.3.1 <th>Reference</th>
5 Softwire46-Rule (FMR) tlv Section 3.1.3.1 </tr>
6 Softwire46-BR ipv6addr Section 3.1.3.2 </thead>
7 Softwire46-DMR ipv6prefix Section 3.1.3.3 <tbody>
8 Softwire46-V4V6Bind tlv Section 3.1.3.4 <tr>
9 Softwire46-PORTPARAMS tlv Section 3.1.3.5 <td>&nbsp;0</td>
10 Rule-IPv6-Prefix ipv6prefix Section 3.1.4.1 <td>&nbsp;Reserved</td>
11 Rule-IPv4-Prefix ipv4prefix Section 3.1.4.2 <td>&nbsp;</td>
12 EA-Length integer Section 3.1.4.3 <td>&nbsp;</td>
13 IPv4-Address ipv4addr Section 3.1.5.1 </tr>
14 Bind-IPv6-Prefix ipv6prefix Section 3.1.5.2 <tr>
15 PSID-Offset integer Section 3.1.6.1 <td>&nbsp;1</td>
16 PSID-Len integer Section 3.1.6.2 <td>&nbsp;Softwire46-MAP-E</td>
17 PSID integer Section 3.1.6.3 <td>&nbsp;tlv</td>
18 Softwire46-Option-Code integer Section 3.2.1 <td>&nbsp;<xref target="etlv"/></td>
19 ASM-Prefix64 ipv6prefix Section 3.3.1 </tr>
20 SSM-Prefix64 ipv6prefix Section 3.3.2 <tr>
21 U-Prefix64 ipv6prefix Section 3.3.3 <td>&nbsp;2</td>
22-255 Unassigned]]></artwork> <td>&nbsp;Softwire46-MAP-T</td>
</figure></t> <td>&nbsp;tlv</td>
<td>&nbsp;<xref target="ttlv"/></td>
</tr>
<tr>
<td>&nbsp;3</td>
<td>&nbsp;Softwire46-Lightweight-4over6</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="ltlv"/></td>
</tr>
<tr>
<td>&nbsp;4</td>
<td>&nbsp;Softwire46-Rule (BMR)</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="s46-rule-sub-tlv"/></td>
</tr>
<tr>
<td>&nbsp;5</td>
<td>&nbsp;Softwire46-Rule (FMR)</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="s46-rule-sub-tlv"/></td>
</tr>
<tr>
<td>&nbsp;6</td>
<td>&nbsp;Softwire46-BR</td>
<td>&nbsp;ipv6addr</td>
<td>&nbsp;<xref target="s46br"/></td>
</tr>
<tr>
<td>&nbsp;7</td>
<td>&nbsp;Softwire46-DMR</td>
<td>&nbsp;ipv6prefix</td>
<td>&nbsp;<xref target="s46dmr"/></td>
</tr>
<tr>
<td>&nbsp;8</td>
<td>&nbsp;Softwire46-V4V6Bind</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="s46bind"/></td>
</tr>
<tr>
<td>&nbsp;9</td>
<td>&nbsp;Softwire46-PORTPARAMS</td>
<td>&nbsp;tlv</td>
<td>&nbsp;<xref target="s46param"/></td>
</tr>
<tr>
<td>&nbsp;10</td>
<td>&nbsp;Rule-IPv6-Prefix</td>
<td>&nbsp;ipv6prefix</td>
<td>&nbsp;<xref target="v6prefix"/></td>
</tr>
<tr>
<td>&nbsp;11</td>
<td>&nbsp;Rule-IPv4-Prefix</td>
<td>&nbsp;ipv4prefix</td>
<td>&nbsp;<xref target="v4prefix"/></td>
</tr>
<tr>
<td>&nbsp;12</td>
<td>&nbsp;EA-Length</td>
<td>&nbsp;integer</td>
<td>&nbsp;<xref target="ea-length"/></td>
</tr>
<tr>
<td>&nbsp;13</td>
<td>&nbsp;IPv4-Address</td>
<td>&nbsp;ipv4addr</td>
<td>&nbsp;<xref target="v4address"/></td>
</tr>
<tr>
<td>&nbsp;14</td>
<td>&nbsp;Bind-IPv6-Prefix</td>
<td>&nbsp;ipv6prefix</td>
<td>&nbsp;<xref target="bindv6"/></td>
</tr>
<tr>
<td>&nbsp;15</td>
<td>&nbsp;PSID-Offset</td>
<td>&nbsp;integer</td>
<td>&nbsp;<xref target="psid-offset"/></td>
</tr>
<tr>
<td>&nbsp;16</td>
<td>&nbsp;PSID-Len</td>
<td>&nbsp;integer</td>
<td>&nbsp;<xref target="psid-len"/></td>
</tr>
<tr>
<td>&nbsp;17</td>
<td>&nbsp;PSID</td>
<td>&nbsp;integer</td>
<td>&nbsp;<xref target="psid"/></td>
</tr>
<tr>
<td>&nbsp;18</td>
<td>&nbsp;Softwire46-Option-Code</td>
<td>&nbsp;integer</td>
<td>&nbsp;<xref target="opc"/></td>
</tr>
<tr>
<td>&nbsp;19</td>
<td>&nbsp;ASM-Prefix64</td>
<td>&nbsp;ipv6prefix</td>
<td>&nbsp;<xref target="TLV0"/></td>
</tr>
<tr>
<td>&nbsp;20</td>
<td>&nbsp;SSM-Prefix64</td>
<td>&nbsp;ipv6prefix</td>
<td>&nbsp;<xref target="TLV1"/></td>
</tr>
<tr>
<td>&nbsp;21</td>
<td>&nbsp;U-Prefix64</td>
<td>&nbsp;ipv6prefix</td>
<td>&nbsp;<xref target="TLV2"/></td>
</tr>
<tr>
<td>&nbsp;22-255</td>
<td>&nbsp;Unassigned</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tbody>
</table>
<t>The registration procedure for this registry is Standards Action as <t>The registration procedure for this registry is Standards Action as
defined in <xref target="RFC8126"></xref>.</t> defined in <xref target="RFC8126" format="default"/>.</t>
</section> </section>
<section anchor="s46option" numbered="true" toc="default">
<section title="Softwire46 Mechanisms and Their Identifying Option Codes"> <name>Softwire46 Mechanisms and Their Identifying Option Codes</name>
<t>The Softwire46-Priority Attribute conveys an ordered list of option <t>The Softwire46-Priority Attribute conveys an ordered list of option
codes assigned to Softwire46 mechanisms, for which IANA is requested codes assigned to Softwire46 mechanisms, for which IANA has
to create and maintain a new registry entitled "Option Codes Permitted created and will maintain a new registry titled "Option Codes Permitted
in the Softwire46-Priority Attribute".</t> in the Softwire46-Priority Attribute".</t>
<t><xref target="Table6"/> shows the initial version of allowed option c
<t>Table 4 shows the initial version of allowed option codes, and the odes and the
Softwire46 mechanisms that they represent. The option code for DS-Lite Softwire46 mechanisms that they represent. The option code for DS-Lite
is derived from the IANA allocated RADIUS Attribute Type value for is derived from the IANA-allocated RADIUS Attribute Type value for
DS-Lite <xref target="RFC6519"></xref>. The option codes for MAP-E, DS-Lite <xref target="RFC6519" format="default"/>. The option codes for
MAP-E,
MAP-T, and Lightweight 4over6 are the TLV-Type values for the MAP-E, MAP-T, and Lightweight 4over6 are the TLV-Type values for the MAP-E,
MAP-T, and Lightweight 4over6 attributes defined in <xref MAP-T, and Lightweight 4over6 attributes defined in <xref target="s46-tl
target="s46-tlvs"></xref>.</t> vs" format="default"/>.</t>
<table anchor="Table6">
<figure title="Table 4: Option Codes to S46 Mechanisms"> <name>Option Codes to S46 Mechanisms</name>
<artwork><![CDATA[ +-----------+--------------------+-------- <thead>
---+ <tr>
|Option Code|Softwire46 Mechanism| Reference | <th>Option Code</th>
+-----------+--------------------+-----------+ <th>Softwire46 Mechanism</th>
| 1 | MAP-E | RFC7597 | <th>Reference</th>
| 2 | MAP-T | RFC7599 | </tr> </thead> <tbody> <tr>
| 3 | Lightweight 4over6 | RFC7596 | <td>&nbsp;1</td>
| 144 | DS-Lite | RFC6519 | <td>&nbsp;MAP-E</td>
+-----------+--------------------+-----------+ <td>&nbsp;<xref target="RFC7597"/></td>
]]></artwork> </tr>
</figure> <tr>
<td>&nbsp;2</td>
<td>&nbsp;MAP-T</td>
<td>&nbsp;<xref target="RFC7599"/></td>
</tr>
<tr>
<td>&nbsp;3</td>
<td>&nbsp;Lightweight 4over6</td>
<td>&nbsp;<xref target="RFC7596"/></td>
</tr>
<tr>
<td>&nbsp;144</td>
<td>&nbsp;DS-Lite</td>
<td>&nbsp;<xref target="RFC6519"/></td>
</tr>
</tbody>
</table>
<t>Additional option codes may be added to this list in the future <t>Additional option codes may be added to this list in the future
using the IETF Review process described in Section 4.8 of <xref using the IETF Review process described in <xref target="RFC8126" sectio
target="RFC8126"></xref>.</t> nFormat="of" section="4.8"/>.</t>
</section> </section>
</section> </section>
<section title="Contributing Authors">
<figure>
<artwork><![CDATA[Bing Liu
Huawei Technologies Co., Ltd
Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095
P.R. China
Email: leo.liubing@huawei.com
Peter Deacon
IEA Software, Inc.
P.O. Box 1170
Veradale, WA 99037
USA
Email: peterd@iea-software.com
Qiong Sun
China Telecom
Beijing China
Email: sunqiong@ctbri.com.cn
Qi Sun
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-6278-5822
Email: sunqibupt@gmail.com
Cathy Zhou
Huawei Technologies
Bantian, Longgang District
Shenzhen 518129
Email: cathy.zhou@huawei.com
Tina Tsou
Huawei Technologies(USA)
2330 Central Expressway
Santa Clara, CA 95050
USA
Email: Tina.Tsou.Zouting@huawei.com
ZiLong Liu
Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-6278-5822
Email: liuzilong8266@126.com
Yong Cui
Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-62603059
Email: yong@csnet1.cs.tsinghua.edu.cn ]]></artwork>
</figure>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>The authors would like to thank the valuable comments made by Peter
Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan, Qian Wang, Wei
Meng, Cui Wang, Alan Dekok, Stefan Winter, and Yu Tianpeng to this
document.</t>
<t>This document was merged with <xref
target="I-D.sun-softwire-lw4over6-radext"></xref> and <xref
target="I-D.wang-radext-multicast-radius-ext"></xref>, thanks to
everyone who contributed to this document.</t>
<t>This document was produced using the xml2rfc tool <xref
target="RFC7991"></xref>.</t>
<t>Many thanks to Al Morton, Bernie Volz, Joel Halpern, and Donald
Eastlake for the review.</t>
</section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <displayreference target="I-D.wang-radext-multicast-radius-ext" to="RADIUS-E
<?rfc include='reference.RFC.2119'?> XT"/>
<displayreference target="I-D.sun-softwire-lw4over6-radext" to="LIGHTWEIGHT
<?rfc include='reference.RFC.2865'?> -4OVER6"/>
<?rfc include='reference.RFC.3162'?>
<?rfc include='reference.RFC.8415'?>
<?rfc include='reference.RFC.3575'?>
<?rfc include='reference.RFC.5080'?>
<?rfc include='reference.RFC.8126'?>
<?rfc include='reference.RFC.6052'?>
<?rfc include='reference.RFC.6158'?>
<?rfc include='reference.RFC.6929'?>
<?rfc include='reference.RFC.8026'?>
<?rfc include='reference.RFC.8044'?>
<?rfc include='reference.RFC.8115'?>
<?rfc include='reference.RFC.8174'?>
<?rfc include='reference.RFC.5176'?>
</references>
<references title="Informative References">
<?rfc include='reference.RFC.2869'?>
<?rfc include='reference.RFC.6614'?>
<?rfc include='reference.RFC.7596'?>
<?rfc include='reference.RFC.8114'?>
<?rfc include='reference.RFC.7597'?>
<?rfc include='reference.RFC.7598'?>
<?rfc include='reference.RFC.7599'?>
<?rfc include='reference.RFC.2607'?> <references>
<name>References</name>
<?rfc include='reference.RFC.7991'?> <references>
<name>Normative References</name>
<?rfc include='reference.RFC.4301'?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2865.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3162.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3575.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5080.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5176.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6052.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6158.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6929.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8026.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8044.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8115.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8415.
xml"/>
</references>
<references>
<name>Informative References</name>
<?rfc include='reference.RFC.6346'?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
2607.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
2869.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
4301.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
6333.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
6346.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
6519.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
6614.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
6977.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
7596.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
7597.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
7598.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
7599.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
8114.xml"/>
<?rfc include='reference.RFC.6333'?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.wang -radext-multicast-radius-ext.xml"/>
<?rfc include='reference.RFC.6519'?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.sun- softwire-lw4over6-radext.xml"/>
<?rfc include='reference.RFC.6977'?> <!-- <?rfc include='reference.I-D.wang-radext-multicast-radius-ext'?>; E xpired -->
<?rfc include='reference.I-D.wang-radext-multicast-radius-ext'?> <!-- <?rfc include='reference.I-D.sun-softwire-lw4over6-radext'?>; Expi red -->
<?rfc include='reference.I-D.sun-softwire-lw4over6-radext'?> </references>
</references> </references>
<section anchor="tlv-field-map" title="DHCPv6 to RADIUS Field Mappings"> <section anchor="tlv-field-map" numbered="true" toc="default">
<name>DHCPv6 to RADIUS Field Mappings</name>
<t>The following sections detail the mappings between the softwire <t>The following sections detail the mappings between the softwire
DHCPv6 option fields and the relevant RADIUS attributes as defined in DHCPv6 option fields and the relevant RADIUS attributes as defined in
this document.</t> this document.</t>
<section numbered="true" toc="default">
<name>OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field Mappings</na
me>
<section title="OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field Mapp <table align="center">
ings"> <name>OPTION_S46_RULE to Softwire46-Rule Sub-TLV Field Mappings</name>
<t></t> <thead>
<tr>
<texttable> <th align="center">OPTION_S46_RULE Field</th>
<ttcol align="center">OPTION_S46_RULE Field</ttcol> <th align="center">Softwire46-Rule Name</th>
<th align="center">TLV Subfield</th>
<ttcol align="center">Softwire46-Rule Name</ttcol> </tr>
</thead>
<ttcol align="center">TLV Subfield</ttcol> <tbody>
<tr>
<c>flags</c> <td align="center">flags</td>
<td align="center">N/A</td>
<c>N/A</c> <td align="center">TLV-type (4, 5)</td>
</tr>
<c>TLV-type (TBD7, TBD8)</c> <tr>
<td align="center">ea-len</td>
<c>ea-len</c> <td align="center">EA-Length</td>
<td align="center">EA-len</td>
<c>EA-Length</c> </tr>
<tr>
<c>EA-len</c> <td align="center">prefix4-len</td>
<td align="center">Rule-IPv4-Prefix</td>
<c>prefix4-len</c> <td align="center">Prefix-Length</td>
</tr>
<c>Rule-IPv4-Prefix</c> <tr>
<td align="center">ipv4-prefix</td>
<c>Prefix-Length</c> <td align="center">Rule-IPv4-Prefix</td>
<td align="center">rule-ipv4-prefix</td>
<c>ipv4-prefix</c> </tr>
<tr>
<c>Rule-IPv4-Prefix</c> <td align="center">prefix6-len</td>
<td align="center">Rule-IPv6-Prefix</td>
<c>rule-ipv4-prefix</c> <td align="center">Prefix-Length</td>
</tr>
<c>prefix6-len</c> <tr>
<td align="center">ipv6-prefix</td>
<c>Rule-IPv6-Prefix</c> <td align="center">Rule-IPv6-Prefix</td>
<td align="center">rule-ipv6-prefix</td>
<c>Prefix-Length</c> </tr>
</tbody>
<c>ipv6-prefix</c> </table>
<c>Rule-IPv6-Prefix</c>
<c>rule-ipv6-prefix</c>
</texttable>
</section> </section>
<section numbered="true" toc="default">
<section title="OPTION_S46_BR (90) to Softwire46-BR Field Mappings"> <name>OPTION_S46_BR (90) to Softwire46-BR Field Mappings</name>
<texttable> <table align="center">
<ttcol align="center">OPTION_S46_BR Field</ttcol> <name>OPTION_S46_BR to Softwire46-BR Field Mappings</name>
<thead>
<ttcol align="center">Softwire46-BR Subfield</ttcol> <tr>
<th align="center">OPTION_S46_BR Field</th>
<c>br-ipv6-address</c> <th align="center">Softwire46-BR Subfield</th>
</tr>
<c>br-ipv6-address</c> </thead>
</texttable> <tbody>
<tr>
<td align="center">br-ipv6-address</td>
<td align="center">br-ipv6-address</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="OPTION_S46_DMR (91) to Softwire46-DMR"> <name>OPTION_S46_DMR (91) to Softwire46-DMR</name>
<texttable> <table align="center">
<ttcol align="center">OPTION_S46_BR Field</ttcol> <name>OPTION_S46_DMR to Softwire46-DMR Field Mappings</name>
<thead>
<ttcol align="center">Softwire46-DMR Subfield</ttcol> <tr>
<th align="center">OPTION_S46_DMR Field</th>
<c>dmr-prefix6-len</c> <th align="center">Softwire46-DMR Subfield</th>
</tr>
<c>dmr-prefix6-len</c> </thead>
<tbody>
<c>dmr-ipv6-prefix</c> <tr>
<td align="center">dmr-prefix6-len</td>
<c>dmr-ipv6-prefix</c> <td align="center">dmr-prefix6-len</td>
</texttable> </tr>
<tr>
<td align="center">dmr-ipv6-prefix</td>
<td align="center">dmr-ipv6-prefix</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind"> <name>OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind</name>
<texttable> <table align="center">
<ttcol align="center">OPTION_S46_V4V6BIND Field</ttcol> <name>OPTION_S46_V4V6BIND to Softwire46-V4V6Bind Field&nbsp;Mappings</n
ame>
<ttcol align="center">Softwire46-V4V6Bind Name</ttcol> <thead>
<tr>
<ttcol align="center">TLV Subfield</ttcol> <th align="center">OPTION_S46_V4V6BIND Field</th>
<th align="center">Softwire46-V4V6Bind Name</th>
<c>ipv4-address</c> <th align="center">TLV Subfield</th>
</tr>
<c>IPv4-Address</c> </thead>
<tbody>
<c>ipv4-address</c> <tr>
<td align="center">ipv4-address</td>
<c>bindprefix6-len</c> <td align="center">IPv4-Address</td>
<td align="center">ipv4-address</td>
<c>Bind-IPv6-Prefix</c> </tr>
<tr>
<c>Prefix-Length</c> <td align="center">bindprefix6-len</td>
<td align="center">Bind-IPv6-Prefix</td>
<c>bind-ipv6-prefix</c> <td align="center">Prefix-Length</td>
</tr>
<c>Bind-IPv6-Prefix</c> <tr>
<td align="center">bind-ipv6-prefix</td>
<c>bind-ipv6-prefix</c> <td align="center">Bind-IPv6-Prefix</td>
</texttable> <td align="center">bind-ipv6-prefix</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field <name>OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field Mappings
Mappings"> </name>
<texttable> <table align="center">
<ttcol align="center">OPTION_S46_PORTPARAMS Field</ttcol> <name>OPTION_S46_PORTPARAMS to Softwire46-PORTPARAMS Field&nbsp;Mapping
s</name>
<ttcol align="center">Softwire46-PORTPARAMS Name</ttcol> <thead>
<tr>
<ttcol align="center">TLV Subfield</ttcol> <th align="center">OPTION_S46_PORTPARAMS Field</th>
<th align="center">Softwire46-PORTPARAMS Name</th>
<c>offset</c> <th align="center">TLV Subfield</th>
</tr>
<c>PSID-Offset</c> </thead>
<tbody>
<c>PSID-Offset</c> <tr>
<td align="center">offset</td>
<c>PSID-len</c> <td align="center">PSID-Offset</td>
<td align="center">PSID-Offset</td>
<c>PSID-Len</c> </tr>
<tr>
<c>PSID-len</c> <td align="center">PSID-len</td>
<td align="center">PSID-Len</td>
<c>PSID</c> <td align="center">PSID-len</td>
</tr>
<c>PSID</c> <tr>
<td align="center">PSID</td>
<c>PSID</c> <td align="center">PSID</td>
</texttable> <td align="center">PSID</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field M <name>OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field Mappings<
appings"> /name>
<texttable> <table align="center">
<ttcol align="center">OPTION_S46_PRIORITY Field</ttcol> <name>OPTION_S46_PRIORITY to Softwire46-PORTPARAMS Field Mappings</name
>
<ttcol align="center">Softwire46-Priority Attribute Subfield</ttcol> <thead>
<tr>
<c>s46-option-code</c> <th align="center">OPTION_S46_PRIORITY Field</th>
<th align="center">Softwire46-Priority Attribute Subfield</th>
<c>Softwire46-option-code</c> </tr>
</texttable> </thead>
<tbody>
<tr>
<td align="center">s46-option-code</td>
<td align="center">Softwire46-option-code</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<name>OPTION_V6_PREFIX64 (113) to Softwire46-Multicast Attribute Field M
appings</name>
<table align="center">
<name>OPTION_V6_PREFIX64 to Softwire46-Multicast Field Mappings</name>
<thead>
<tr>
<th align="center">OPTION_V6_PREFIX64 Field</th>
<th align="center">Softwire46-Multicast Attribute TLV
Name</th>
<th align="center">TLV Subfield</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center">asm-length</td>
<td align="center">ASM-Prefix64</td>
<td align="center">Prefix-Length</td>
</tr>
<tr>
<td align="center">ASM_mPrefix64</td>
<td align="center">ASM-Prefix64</td>
<td align="center">asm-prefix64</td>
</tr>
<tr>
<td align="center">ssm-length</td>
<td align="center">SSM-Prefix64</td>
<td align="center">Prefix-Length</td>
</tr>
<tr>
<td align="center">SSM_mPrefix64</td>
<td align="center">SSM-Prefix64</td>
<td align="center">ssm-prefix64</td>
</tr>
<tr>
<td align="center">unicast-length</td>
<td align="center">U-Prefix64</td>
<td align="center">Prefix-Length</td>
</tr>
<tr>
<td align="center">uPrefix64</td>
<td align="center">U-Prefix64</td>
<td align="center">u-prefix64</td>
</tr>
</tbody>
</table>
</section>
</section>
<section anchor="Acknowledgements" numbered="false" toc="default">
<name>Acknowledgements</name>
<t>The authors would like to thank Peter Lothberg, Wojciech Dec, Ian
Farrer, Suresh Krishnan, Qian Wang, Wei Meng, Cui Wang, Alan Dekok,
Stefan Winter, and Yu Tianpeng for their valuable comments regarding this
document.</t>
<t>This document was merged with <xref target="I-D.sun-softwire-lw4over6-r
adext" format="default"/> and <xref target="I-D.wang-radext-multicast-radius-ext
" format="default"/>. Thanks to
everyone who contributed to this document.</t>
<section title="OPTION_V6_PREFIX64 (113) to Softwire46-Multicast Attribute <t>Many thanks to Al Morton, Bernie Volz, Joel Halpern, and Donald
Field Mappings"> Eastlake for the review.</t>
<texttable> </section>
<ttcol align="center">OPTION_V6_PREFIX64 Field</ttcol> <section numbered="false" toc="default">
<name>Contributors</name>
<ttcol align="center">Softwire46-Multicast Attribute TLV
Name</ttcol>
<ttcol align="center">TLV Subfield</ttcol>
<c>asm-length</c>
<c>ASM-Prefix64</c>
<c>Prefix-Length</c>
<c>ASM_mPrefix64</c>
<c>ASM-Prefix64</c>
<c>asm-prefix64</c>
<c>ssm-length</c>
<c>SSM-Prefix64</c>
<c>Prefix-Length</c> <artwork name="" type="" align="left" alt="">
Bing Liu
Huawei Technologies Co., Ltd.
China
<c>SSM_mPrefix64</c> Email: leo.liubing@huawei.com</artwork>
<artwork name="" type="" align="left" alt="">
Peter Deacon
IEA Software, Inc.
United States of America
<c>SSM-Prefix64</c> Email: peterd@iea-software.com</artwork>
<artwork name="" type="" align="left" alt="">
Qiong Sun
China Telecom
China
<c>ssm-prefix64</c> Email: sunqiong@ctbri.com.cn</artwork>
<artwork name="" type="" align="left" alt="">
Qi Sun
Tsinghua University
China
<c>unicast-length</c> Email: sunqibupt@gmail.com</artwork>
<artwork name="" type="" align="left" alt="">
Cathy Zhou
Huawei Technologies
China
<c>U-Prefix64</c> Email: cathy.zhou@huawei.com</artwork>
<artwork name="" type="" align="left" alt="">
Tina Tsou
Huawei Technologies (USA)
United States of America
<c>Prefix-Length</c> Email: Tina.Tsou.Zouting@huawei.com</artwork>
<artwork name="" type="" align="left" alt="">
ZiLong Liu
Tsinghua University
China
<c>uPrefix64</c> Email: liuzilong8266@126.com</artwork>
<artwork name="" type="" align="left" alt="">
Yong Cui
Tsinghua University
China
<c>U-Prefix64</c> Email: yong@csnet1.cs.tsinghua.edu.cn</artwork>
<c>u-prefix64</c>
</texttable>
</section>
</section> </section>
</back> </back>
</rfc> </rfc>
 End of changes. 261 change blocks. 
1501 lines changed or deleted 1752 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/