< draft-ietf-softwire-map-radius-24.txt		draft-ietf-softwire-map-radius-25.txt >
	Softwire S. Jiang, Ed.		Softwire S. Jiang, Ed.
	Internet-Draft Huawei Technologies Co., Ltd		Internet-Draft Huawei Technologies Co., Ltd
	Intended status: Standards Track Y. Fu, Ed.		Intended status: Standards Track Y. Fu, Ed.
	Expires: December 2, 2019 CNNIC		Expires: December 15, 2019 CNNIC
	C. Xie		C. Xie
	China Telecom		China Telecom
	T. Li		T. Li
	Tsinghua University		Tsinghua University
	M. Boucadair, Ed.		M. Boucadair, Ed.
	Orange		Orange
	May 31, 2019		June 13, 2019
	RADIUS Attributes for Address plus Port (A+P) based Softwire Mechanisms		RADIUS Attributes for Address plus Port (A+P) based Softwire Mechanisms
	draft-ietf-softwire-map-radius-24		draft-ietf-softwire-map-radius-25
	Abstract		Abstract
	IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity		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 co-existence
	period. DHCPv6 options have been defined for configuring clients for		period. DHCPv6 options have been defined for configuring clients for
	Lightweight 4over6, Mapping of Address and Port with Encapsulation,		Lightweight 4over6, Mapping of Address and Port with Encapsulation,
	and Mapping of Address and Port using Translation unicast softwire		and Mapping of Address and Port using Translation unicast softwire
	mechanisms, and also multicast softwires. However, in many networks,		mechanisms, and also multicast softwires. However, in many networks,
	configuration information is stored in an Authentication,		configuration information is stored in an Authentication,
	skipping to change at page 2, line 7 ¶		skipping to change at page 2, line 7 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on December 2, 2019.		This Internet-Draft will expire on December 15, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 29 ¶		skipping to change at page 2, line 29 ¶
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3. New RADIUS Attributes . . . . . . . . . . . . . . . . . . . . 6		3. New RADIUS Attributes . . . . . . . . . . . . . . . . . . . . 6
	3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6		3.1. Softwire46-Configuration Attribute . . . . . . . . . . . 7
	3.1.1. Softwire46 Attributes . . . . . . . . . . . . . . . . 8		3.1.1. Softwire46 Attributes . . . . . . . . . . . . . . . . 8
	3.1.1.1. Softwire46-MAP-E Attribute . . . . . . . . . . . 10		3.1.1.1. Softwire46-MAP-E Attribute . . . . . . . . . . . 10
	3.1.1.2. Softwire46-MAP-T Attribute . . . . . . . . . . . 10		3.1.1.2. Softwire46-MAP-T Attribute . . . . . . . . . . . 10
	3.1.1.3. Softwire46-Lightweight-4over6 Attribute . . . . . 11		3.1.1.3. Softwire46-Lightweight-4over6 Attribute . . . . . 11
	3.1.2. Softwire46 Sub-Attributes . . . . . . . . . . . . . . 11		3.1.2. Softwire46 Sub-Attributes . . . . . . . . . . . . . . 11
	3.1.3. Specification of the Softwire46 Sub-Attributes . . . 12		3.1.3. Specification of the Softwire46 Sub-Attributes . . . 12
	3.1.3.1. Softwire46-Rule Attribute . . . . . . . . . . . . 12		3.1.3.1. Softwire46-Rule Attribute . . . . . . . . . . . . 12
	3.1.3.2. Softwire46-BR Attribute . . . . . . . . . . . . . 13		3.1.3.2. Softwire46-BR Attribute . . . . . . . . . . . . . 13
	3.1.3.3. Softwire46-DMR Attribute . . . . . . . . . . . . 13		3.1.3.3. Softwire46-DMR Attribute . . . . . . . . . . . . 14
	3.1.3.4. Softwire46-V4V6Bind Attribute . . . . . . . . . . 14		3.1.3.4. Softwire46-V4V6Bind Attribute . . . . . . . . . . 14
	3.1.3.5. Softwire46-PORTPARAMS Attribute . . . . . . . . . 14		3.1.3.5. Softwire46-PORTPARAMS Attribute . . . . . . . . . 15
	3.1.4. Sub-Attributes for Sofwtire46-Rule . . . . . . . . . 15		3.1.4. Sub-Attributes for Sofwtire46-Rule . . . . . . . . . 16
	3.1.4.1. Rule-IPv6-Prefix Attribute . . . . . . . . . . . 15		3.1.4.1. Rule-IPv6-Prefix Attribute . . . . . . . . . . . 16
	3.1.4.2. Rule-IPv4-Prefix Attribute . . . . . . . . . . . 16		3.1.4.2. Rule-IPv4-Prefix Attribute . . . . . . . . . . . 17
	3.1.4.3. EA-Length Attribute . . . . . . . . . . . . . . . 16		3.1.4.3. EA-Length Attribute . . . . . . . . . . . . . . . 17
	3.1.5. Attributes for Softwire46-v4v6Bind . . . . . . . . . 17		3.1.5. Attributes for Softwire46-v4v6Bind . . . . . . . . . 18
	3.1.5.1. IPv4-Address Attribute . . . . . . . . . . . . . 17		3.1.5.1. IPv4-Address Attribute . . . . . . . . . . . . . 18
	3.1.5.2. Bind-IPv6-Prefix Attribute . . . . . . . . . . . 17		3.1.5.2. Bind-IPv6-Prefix Attribute . . . . . . . . . . . 18
	3.1.6. Attributes for Softwire46-PORTPARAMS . . . . . . . . 18		3.1.6. Attributes for Softwire46-PORTPARAMS . . . . . . . . 19
	3.1.6.1. PSID-Offset Attribute . . . . . . . . . . . . . . 18		3.1.6.1. PSID-Offset Attribute . . . . . . . . . . . . . . 19
	3.1.6.2. PSID-Len Attribute . . . . . . . . . . . . . . . 19		3.1.6.2. PSID-Len Attribute . . . . . . . . . . . . . . . 20
	3.1.6.3. PSID Attribute . . . . . . . . . . . . . . . . . 19		3.1.6.3. PSID Attribute . . . . . . . . . . . . . . . . . 20
	3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 20		3.2. Softwire46-Priority Attribute . . . . . . . . . . . . . . 21
	3.2.1. Softwire46-Option-Code . . . . . . . . . . . . . . . 21		3.2.1. Softwire46-Option-Code . . . . . . . . . . . . . . . 22
	3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22		3.3. Softwire46-Multicast Attribute . . . . . . . . . . . . . 23
	3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 23		3.3.1. ASM-Prefix64 Attribute . . . . . . . . . . . . . . . 24
	3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 24		3.3.2. SSM-Prefix64 Attribute . . . . . . . . . . . . . . . 25
	3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 24		3.3.3. U-Prefix64 Attribute . . . . . . . . . . . . . . . . 25
	4. A Sample Configuration Process with RADIUS . . . . . . . . . 24		4. A Sample Configuration Process with RADIUS . . . . . . . . . 25
	5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 27		5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 28
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 28		6. Security Considerations . . . . . . . . . . . . . . . . . . . 29
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
	7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 29		7.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 30
	7.2. RADIUS Softwire46 Configuration and Multicast Attributes 29		7.2. RADIUS Softwire46 Configuration and Multicast Attributes 30
	7.3. Softwire46 Mechanisms and Their Identifying Option Codes 30		7.3. Softwire46 Mechanisms and Their Identifying Option Codes 31
	8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 31		8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 32
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
	10.1. Normative References . . . . . . . . . . . . . . . . . . 33		10.1. Normative References . . . . . . . . . . . . . . . . . . 34
	10.2. Informative References . . . . . . . . . . . . . . . . . 34		10.2. Informative References . . . . . . . . . . . . . . . . . 35
	Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 36		Appendix A. DHCPv6 to RADIUS Field Mappings . . . . . . . . . . 37
	A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field		A.1. OPTION_S46_RULE (89) to Softwire46-Rule Sub-TLV Field
	Mappings . . . . . . . . . . . . . . . . . . . . . . . . 36
	A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings . . . 36
	A.3. OPTION_S46_DMR (91) to Softwire46-DMR . . . . . . . . . . 36
	A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind . . . . . 36
	A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field
	Mappings . . . . . . . . . . . . . . . . . . . . . . . . 37		Mappings . . . . . . . . . . . . . . . . . . . . . . . . 37
			A.2. OPTION_S46_BR (90) to Softwire46-BR Field Mappings . . . 37
			A.3. OPTION_S46_DMR (91) to Softwire46-DMR . . . . . . . . . . 37
			A.4. OPTION_S46_V4V6BIND (92) to Softwire46-V4V6Bind . . . . . 38
			A.5. OPTION_S46_PORTPARAMS (93) to Softwire46-PORTPARAMS Field
			Mappings . . . . . . . . . . . . . . . . . . . . . . . . 38
	A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field		A.6. OPTION_S46_PRIORITY (111) to Softwire46-PORTPARAMS Field
	Mappings . . . . . . . . . . . . . . . . . . . . . . . . 37		Mappings . . . . . . . . . . . . . . . . . . . . . . . . 38
	A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast		A.7. OPTION_V6_PREFIX64 (113) to Softwire46-Multicast
	Attribute Field Mappings . . . . . . . . . . . . . . . . 37		Attribute Field Mappings . . . . . . . . . . . . . . . . 38
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39
	1. Introduction		1. Introduction
	Providers have started deploying and transitioning to IPv6. Several		Providers have started deploying and transitioning to IPv6. Several
	IPv4 service continuity mechanisms based on the Address plus Port		IPv4 service continuity mechanisms based on the Address plus Port
	(A+P) [RFC6346] have been proposed for providing unicast IPv4 over		(A+P) [RFC6346] have been proposed for providing unicast IPv4 over
	IPv6-only infrastructure, such as Mapping of Address and Port with		IPv6-only infrastructure, such as Mapping of Address and Port with
	Encapsulation (MAP-E) [RFC7597], Mapping of Address and Port using		Encapsulation (MAP-E) [RFC7597], Mapping of Address and Port using
	Translation (MAP-T) [RFC7599], and Lightweight 4over6 [RFC7596].		Translation (MAP-T) [RFC7599], and Lightweight 4over6 [RFC7596].
	Also, [RFC8114] specifies a generic solution for the delivery of IPv4		Also, [RFC8114] specifies a generic solution for the delivery of IPv4
	skipping to change at page 4, line 15 ¶		skipping to change at page 4, line 15 ¶
	network, a Broadband Network Gateway (BNG) acts as the access gateway		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 AAA		for users. That is, the BNG acts as both an AAA client to the AAA
	server, and a DHCPv6 server for DHCPv6 messages sent by clients.		server, and a DHCPv6 server for DHCPv6 messages sent by clients.
	Throughout this document, the term BNG describes a device		Throughout this document, the term BNG describes a device
	implementing both the AAA client and DHCPv6 server functions.		implementing both the AAA client and DHCPv6 server functions.
	Since IPv4-in-IPv6 softwire configuration information is stored in an		Since IPv4-in-IPv6 softwire configuration information is stored in an
	AAA server, and user configuration information is mainly transmitted		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.		information from the AAA servers to BNGs so that they can be provided
			to CEs using the existing DHCPv6 options.
	The RADIUS attributes defined in this document provide configuration		The RADIUS attributes defined in this document provide configuration
	to populate the corresponding DHCPv6 options for unicast and		to populate the corresponding DHCPv6 options for unicast and
	multicast softwire configuration, specifically:		multicast softwire configuration, specifically:
	o "Mapping of Address and Port with Encapsulation (MAP-E)" [RFC7597]		o "Mapping of Address and Port with Encapsulation (MAP-E)" [RFC7597]
	(DHCPv6 options defined in [RFC7598]).		(DHCPv6 options defined in [RFC7598]).
	o "Mapping of Address and Port using Translation (MAP-T)" [RFC7599]		o "Mapping of Address and Port using Translation (MAP-T)" [RFC7599]
	(DHCPv6 options defined in [RFC7598]).		(DHCPv6 options defined in [RFC7598]).
	skipping to change at page 5, line 22 ¶		skipping to change at page 5, line 22 ¶
	| OPTION_S46_PORTPARAMS (93) | Softwire46-PORTPARAMS |		| OPTION_S46_PORTPARAMS (93) | Softwire46-PORTPARAMS |
	| OPTION_S46_PRIORITY (111) | Softwire46-Priority |		| OPTION_S46_PRIORITY (111) | Softwire46-Priority |
	| OPTION_V6_PREFIX64 (113) | Softwire46-Multicast |		| OPTION_V6_PREFIX64 (113) | Softwire46-Multicast |
	+----------------------------+--------------------------------+		+----------------------------+--------------------------------+
	Table 1: Mapping between DHCPv6 Options and RADIUS Attributes		Table 1: Mapping between DHCPv6 Options and RADIUS Attributes
	A RADIUS attribute for Dual-Stack Lite [RFC6333] is defined in		A RADIUS attribute for Dual-Stack Lite [RFC6333] is defined in
	[RFC6519].		[RFC6519].
			This document targets deployments where a trusted relationship is in
			place between the RADIUS client and server.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in		"OPTIONAL" in this document are to be interpreted as described in BCP
	[RFC2119] [RFC8174] when, and only when, they appear in all capitals,		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	as shown here.		capitals, as shown here.
	The reader should be familiar with the concepts and terms defined in		The reader should be familiar with the concepts and terms defined in
	[RFC7596], [RFC7597], [RFC7599], and [RFC8026].		[RFC7596], [RFC7597], [RFC7599], and [RFC8026].
	The terms "multicast Basic Bridging BroadBand" element (mB4) and		The terms "multicast Basic Bridging BroadBand" element (mB4) and
	"multicast Address Family Transition Router" element (mAFTR) are		"multicast Address Family Transition Router" element (mAFTR) are
	defined in [RFC8114].		defined in [RFC8114].
	Softwire46 (S46) is used throughout to denote any of the IPv4-in-IPv6		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
	skipping to change at page 6, line 25 ¶		skipping to change at page 6, line 27 ¶
	This attribute carries the configuration information for MAP-E,		This attribute carries the configuration information for MAP-E,
	MAP-T, and Lightweight 4over6. The configuration information for		MAP-T, and Lightweight 4over6. The configuration information for
	each Softwire46 mechanism is carried in the corresponding		each Softwire46 mechanism is carried in the corresponding
	Softwire46 attributes. Different attributes are required for		Softwire46 attributes. Different attributes are required for
	each Softwire46 mechanism.		each Softwire46 mechanism.
	2. Softwire46-Priority Attribute (Section 3.2):		2. Softwire46-Priority Attribute (Section 3.2):
	Depending on the deployment scenario, a client may support		Depending on the deployment scenario, a client may support
	several different Softwire46 mechanisms and so request		several different Softwire46 mechanisms. Therefore, a client may
	configuration for more than one Softwire46 mechanism at a time.		request configuration for more than one Softwire46 mechanism at a
	The Softwire46-Priority Attribute contains information allowing		time. The Softwire46-Priority Attribute contains information
	the client to prioritize which mechanism to use, corresponding to		allowing the client to prioritize which mechanism to use,
	OPTION_S46_PRIORITY defined in [RFC8026].		corresponding to OPTION_S46_PRIORITY defined in [RFC8026].
	3. Softwire46-Multicast Attribute (Section 3.3):		3. Softwire46-Multicast Attribute (Section 3.3):
	This attribute conveys the IPv6 prefixes to be used in [RFC8114]		This attribute conveys the IPv6 prefixes to be used in [RFC8114]
	to synthesize IPv4-embedded IPv6 addresses. The BNG uses the		to synthesize IPv4-embedded IPv6 addresses. The BNG uses the
	IPv6 prefixes returned in the RADIUS Softwire46-Multicast		IPv6 prefixes returned in the RADIUS Softwire46-Multicast
	Attribute to populate the DHCPv6 PREFIX64 Option [RFC8115].		Attribute to populate the DHCPv6 PREFIX64 Option [RFC8115].
	All of these attributes are allocated from the RADIUS "Extended Type"		All of these attributes are allocated from the RADIUS "Extended Type"
	code space per [RFC6929].		code space per [RFC6929].
	skipping to change at page 7, line 12 ¶		skipping to change at page 7, line 18 ¶
	Extensions [RFC6929]. It contains some sub-attributes, with the		Extensions [RFC6929]. It contains some sub-attributes, with the
	following requirements:		following requirements:
	The Softwire46-Configuration Attribute MUST contain one or more of		The Softwire46-Configuration Attribute MUST contain one or more of
	the following attributes: Softwire46-MAP-E, Softwire46-MAP-T, and/		the following attributes: Softwire46-MAP-E, Softwire46-MAP-T, and/
	or Softwire46-Lightweight-4over6.		or Softwire46-Lightweight-4over6.
	The Softwire46-Configuration Attribute conveys the configuration		The Softwire46-Configuration Attribute conveys the configuration
	information for MAP-E, MAP-T, or Lightweight 4over6. The BNG		information for MAP-E, MAP-T, or Lightweight 4over6. The BNG
	SHALL use the configuration information returned in the RADIUS		SHALL use the configuration information returned in the RADIUS
	attribute to populate the DHCPv6 Softwire46 Container Option		attribute to populate the DHCPv6 Softwire46 Container Option(s)
	defined in Section 5 of [RFC7598].		defined in Section 5 of [RFC7598].
	The Softwire46-Configuration Attribute MAY appear in an Access-		The Softwire46-Configuration Attribute MAY appear in an Access-
	Accept packet. It MAY also appear in an Access-Request packet to		Accept packet. It MAY also appear in an Access-Request packet to
	indicate a preferred Softwire46 configuration. However, the		indicate a preferred Softwire46 configuration. However, the
	server is not required to honor such a preference.		server is not required to honor such a preference.
	The Softwire46-Configuration Attribute MAY appear in a CoA-Request		The Softwire46-Configuration Attribute MAY appear in a CoA-Request
	packet.		packet.
	The Softwire46-Configuration Attribute MAY appear in an		The Softwire46-Configuration Attribute MAY appear in an
	Accounting-Request packet.		Accounting-Request packet.
	The Softwire46-Configuration Attribute MUST NOT appear in any		The Softwire46-Configuration Attribute MUST NOT appear in any
	other RADIUS packet.		other RADIUS packet.
	The Softwire46-Configuration Attribute MUST only encapsulate one
	or more of the Softwire46 attributes defined in this document.
	The Softwire46-Configuration Attribute is structured as follows:		The Softwire46-Configuration Attribute is structured as follows:
	Type		Type
	241 (To be confirmed by IANA).		241 (To be confirmed by IANA).
	Length		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.
	skipping to change at page 11, line 35 ¶		skipping to change at page 11, line 35 ¶
	It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5.		It MAY contain Softwire46-PORTPARAMS, defined in Section 3.1.3.5.
	3.1.2. Softwire46 Sub-Attributes		3.1.2. Softwire46 Sub-Attributes
	Table 2 shows which encapsulated sub-attributes are mandatory,		Table 2 shows which encapsulated sub-attributes are mandatory,
	optional, or not permitted for each defined Softwire46 attribute.		optional, or not permitted for each defined Softwire46 attribute.
	+-----------------------+-------+-------+--------------------+		+-----------------------+-------+-------+--------------------+
	| Sub-Attributes | MAP-E | MAP-T | Lightweight 4over6 |		| Sub-Attributes | MAP-E | MAP-T | Lightweight 4over6 |
	+-----------------------+-------+-------+--------------------+		+-----------------------+-------+-------+--------------------+
	| Softwire46-BR | 1 | 0 | 1 |		| Softwire46-BR | 1+ | 0 | 1+ |
	| Softwire46-Rule | 1 | 1 | 0 |		| Softwire46-Rule | 1 | 1 | 0 |
	| Softwire46-DMR | 0 | 1 | 0 |		| Softwire46-DMR | 0 | 1 | 0 |
	| Softwire46-V4V6Bind | 0 | 0 | 1 |		| Softwire46-V4V6Bind | 0 | 0 | 1 |
	| Softwire46-PORTPARAMS | 0-1 | 0-1 | 0-1 |		| Softwire46-PORTPARAMS | 0-1 | 0-1 | 0-1 |
	+-----------------------+-------+-------+--------------------+		+-----------------------+-------+-------+--------------------+
	Table 2: Softwire46 Sub-Attributes		Table 2: Softwire46 Sub-Attributes
	The following table defines the meaning of Table 2 entries.		The following table defines the meaning of Table 2 entries.
	0 Not Permitted		0 Not Permitted
	0-1 Optional, zero or one instance of the attribute		0-1 Optional, zero or one instance of the attribute
	may be present.		may be present.
	1 Mandatory, only one instance of the attribute		1 Mandatory, only one instance of the attribute
	must be present.		must be present.
			1+ Mandatory, one or more instances of the attribute
			may be present.
	3.1.3. Specification of the Softwire46 Sub-Attributes		3.1.3. Specification of the Softwire46 Sub-Attributes
	3.1.3.1. Softwire46-Rule Attribute		3.1.3.1. Softwire46-Rule Attribute
	Softwire46-Rule can only be encapsulated in Softwire46-MAP-E		Softwire46-Rule can only be encapsulated in Softwire46-MAP-E
	(Section 3.1.1.1) or Softwire46-MAP-T (Section 3.1.1.2). Depending		(Section 3.1.1.1) or Softwire46-MAP-T (Section 3.1.1.2). Depending
	on the deployment scenario, one Basic Mapping Rule (BMR) and zero or		on the deployment scenario, one Basic Mapping Rule (BMR) and zero or
	more Forwarding Mapping Rules (FMRs) MUST be included in one		more Forwarding Mapping Rules (FMRs) MUST be included in one
	Softwire46-MAP-E or Softwire46-MAP-T.		Softwire46-MAP-E or Softwire46-MAP-T.
	skipping to change at page 13, line 44 ¶		skipping to change at page 14, line 34 ¶
	The structure of Softwire46-DMR is shown below:		The structure of Softwire46-DMR is shown below:
	TLV-Type		TLV-Type
	7		7
	TLV-Length		TLV-Length
	4 + length of dmr-ipv6-prefix specified in octets.		4 + length of dmr-ipv6-prefix specified in octets.
	Data Type		Data Type
	The attribute Softwire46-DMR is of type ip6pref (Section 3.10 of		The attribute Softwire46-DMR is of type ipv6pref (Section 3.10 of
	[RFC8044]).		[RFC8044]).
	TLV-Value		TLV-Value
	dmr-ipv6-prefix. A variable-length (dmr-prefix6-len) field		A variable-length (dmr-prefix6-len) field
	specifying the IPv6 prefix for the BR. This field is right-padded		specifying the IPv6 prefix (dmr-ipv6-prefix) for the BR. This field
	with zeros to the nearest octet boundary when dmr-prefix6-len		is right-padded with zeros to the nearest octet boundary when
	is not divisible by 8. Prefixes with length from 0 to 96 are allowed.		dmr-prefix6-len is not divisible by 8. Prefixes with length from
			0 to 96 are allowed.
	3.1.3.4. Softwire46-V4V6Bind Attribute		3.1.3.4. Softwire46-V4V6Bind Attribute
	Softwire46-V4V6Bind may only be encapsulated in Softwire46-		Softwire46-V4V6Bind may only be encapsulated in Softwire46-
	Lightweight-4over6 (Section 3.1.1.3). There MUST be exactly one		Lightweight-4over6 (Section 3.1.1.3). There MUST be exactly one
	Softwire46-V4V6Bind included in each Softwire46-Lightweight-4over6.		Softwire46-V4V6Bind included in each Softwire46-Lightweight-4over6.
	The structure of Softwire46-V4V6Bind is shown below:		The structure of Softwire46-V4V6Bind is shown below:
	TLV-Type		TLV-Type
	skipping to change at page 16, line 16 ¶		skipping to change at page 17, line 16 ¶
	10		10
	TLV-Length		TLV-Length
	4 + length of rule-ipv6-prefix specified in octets.		4 + length of rule-ipv6-prefix specified in octets.
	Data Type		Data Type
	The attribute Rule-IPv6-Prefix is of type ipv6pref (Section 3.10		The attribute Rule-IPv6-Prefix is of type ipv6pref (Section 3.10
	of [RFC8044]).		of [RFC8044]).
	TLV-Value		TLV-Value
	rule-ipv6-prefix. A variable-length field that specifies an IPv6		A variable-length field that specifies an IPv6
	prefix appearing in the MAP rule.		prefix (rule-ipv6-prefix) appearing in the MAP rule.
	3.1.4.2. Rule-IPv4-Prefix Attribute		3.1.4.2. Rule-IPv4-Prefix Attribute
	This attribute is used to convey the MAP Rule IPv4 prefix. The		This attribute is used to convey the MAP Rule IPv4 prefix. The
	structure of Rule-IPv4-Prefix is shown below:		structure of Rule-IPv4-Prefix is shown below:
	TLV-Type		TLV-Type
	11		11
	TLV-Length		TLV-Length
	4 + length of rule-ipv4-prefix specified in octets.		4 + length of rule-ipv4-prefix specified in octets.
	Data Type		Data Type
	The attribute Rule-IPv4-Prefix is of type ipv4pref (Section 3.11		The attribute Rule-IPv4-Prefix is of type ipv4pref (Section 3.11
	of [RFC8044]).		of [RFC8044]).
	TLV-Value		TLV-Value
	rule-ipv4-prefix. A variable-length field that pecifies		A variable-length field that specifies
	an IPv4 prefix appearing in the MAP rule.		an IPv4 prefix (rule-ipv4-prefix) appearing in the MAP rule.
	3.1.4.3. EA-Length Attribute		3.1.4.3. EA-Length Attribute
	This attribute is used to convey the Embedded-Address (EA) bit		This attribute is used to convey the Embedded-Address (EA) bit
	length. The structure of EA-Length is shown below:		length. The structure of EA-Length is shown below:
	TLV-Type		TLV-Type
	12		12
	TLV-Length		TLV-Length
	skipping to change at page 18, line 16 ¶		skipping to change at page 19, line 16 ¶
	14		14
	TLV-Length		TLV-Length
	4 + length of bind-ipv6-prefix specified in octets.		4 + length of bind-ipv6-prefix specified in octets.
	Data Type		Data Type
	The attribute Bind-IPv6-Prefix is of type ipv6pref (Section 3.10		The attribute Bind-IPv6-Prefix is of type ipv6pref (Section 3.10
	of [RFC8044]).		of [RFC8044]).
	TLV-Value		TLV-Value
	bind-ipv6-prefix. A variable-length field specifying the IPv6		A variable-length field specifying the IPv6
	prefix or address for the Softwire46 CE. This field is		prefix or address for the Softwire46 CE (bind-ipv6-prefix).
	right-padded with zeros to the nearest octet boundary		This field is right-padded with zeros to the nearest octet
	when the prefix length is not divisible by 8.		boundary when the prefix length is not divisible by 8.
	3.1.6. Attributes for Softwire46-PORTPARAMS		3.1.6. Attributes for Softwire46-PORTPARAMS
	3.1.6.1. PSID-Offset Attribute		3.1.6.1. PSID-Offset Attribute
	This attribute is used to convey the Port Set Identifier offset as		This attribute is used to convey the Port Set Identifier offset as
	defined in [RFC7597]. This attribute is encoded in 32 bits as per		defined in [RFC7597]. This attribute is encoded in 32 bits as per
	the recommendation in Appendix A.2.1 of [RFC6158].		the recommendation in Appendix A.2.1 of [RFC6158].
	The structure of PSID-Offset is shown below:		The structure of PSID-Offset is shown below:
	skipping to change at page 18, line 44 ¶		skipping to change at page 19, line 44 ¶
	TLV-Length		TLV-Length
	6 octets		6 octets
	Data Type		Data Type
	The attribute PSID-Offset is of type integer (Section 3.1		The attribute PSID-Offset is of type integer (Section 3.1
	of [RFC8044]).		of [RFC8044]).
	TLV-Value		TLV-Value
	Contains the PSID-Offset (8-bits) right		Contains the PSID-Offset (8-bits) right
	justified, and the unused bits in this field MUST		justified, and the unused bits in this field MUST
	be set to zero. This field that 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 Section 5.1
	of [RFC7597]. Allowed values are between 0 and 15.		of [RFC7597].
	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.		in the relevant specification document.
	3.1.6.2. PSID-Len Attribute		3.1.6.2. PSID-Len Attribute
	This attribute is used to convey the PSID length as defined in		This attribute is used to convey the PSID length as defined in
	[RFC7597]. This attribute is encoded in 32 bits as per the		[RFC7597]. This attribute is encoded in 32 bits as per the
	recommendation in Appendix A.2.1 of [RFC6158].		recommendation in Appendix A.2.1 of [RFC6158].
	skipping to change at page 21, line 21 ¶		skipping to change at page 22, line 21 ¶
	Extended-Type		Extended-Type
	TBD5		TBD5
	TLV-Value		TLV-Value
	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 MUST contain at least one
	Softwire46-Option-Code TLV (Section 3.2.1).		Softwire46-Option-Code TLV (Section 3.2.1).
	Softwire46 mechanisms are prioritized in the appearance order		Softwire46 mechanisms are prioritized in the appearance order
	of the in the Softwire46-Priority Attribute.		of the in the Softwire46-Priority Attribute. That is,
			the first-appearing mechanism is most preferred.
	The Softwire46-Priority Attribute is associated with the following		The Softwire46-Priority Attribute is associated with the following
	identifier: 241.Extended-Type (TBD5).		identifier: 241.Extended-Type (TBD5).
	3.2.1. Softwire46-Option-Code		3.2.1. Softwire46-Option-Code
	This attribute is used to convey an option code assigned to a		This attribute is used to convey an option code assigned to a
	Softwire46 mechanism [RFC8026]. This attribute is encoded in 32 bits		Softwire46 mechanism [RFC8026]. This attribute is encoded in 32 bits
	as per the recommendation in Appendix A.2.1 of [RFC6158].		as per the recommendation in Appendix A.2.1 of [RFC6158].
	skipping to change at page 23, line 20 ¶		skipping to change at page 24, line 20 ¶
	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.
	Extended-Type		Extended-Type
	TBD6		TBD6
	Value		Value
	This field contains a set of attributes as follows:		This field contains a set of attributes as follows:
	ASM-Prefix64		ASM-Prefix64
	This attribute contains the ASM IPv6 prefix. Refer to		This attribute contains the Any-Source Multicast (ASM)
	Section 3.3.1.		IPv6 prefix. Refer to Section 3.3.1.
	SSM-Prefix64		SSM-Prefix64
	This attribute contains the SSM IPv6 prefix. Refer to		This attribute contains the Source-Source Multicast (SSM)
	Section 3.3.2.		IPv6 prefix. Refer to Section 3.3.2.
	U-Prefix64		U-Prefix64
	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 Section 3.3.3.
	The Softwire46-Multicast Attribute is associated with the following		The Softwire46-Multicast Attribute is associated with the following
	identifier: 241.Extended-Type(TBD6).		identifier: 241.Extended-Type(TBD6).
	3.3.1. ASM-Prefix64 Attribute		3.3.1. ASM-Prefix64 Attribute
	The ASM-Prefix64 attribute is structured as follows:		The ASM-Prefix64 attribute is structured as follows:
	TLV-Type		TLV-Type
	19		19
	TLV-Length		TLV-Length
	16 octets. The length of asm-prefix64 must be to 96 [RFC8115].		16 octets. The length of asm-prefix64 must be /96 [RFC8115].
	Data Type		Data Type
	The attribute ASM-Prefix64 is of type ipv6prefix (Section 3.10 of		The attribute ASM-Prefix64 is of type ipv6prefix (Section 3.10 of
	[RFC8044]).		[RFC8044]).
	TLV-Value		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 MUST belong to the ASM range.
	3.3.2. SSM-Prefix64 Attribute		3.3.2. SSM-Prefix64 Attribute
	The SSM-Prefix64 attribute is structured as follows:		The SSM-Prefix64 attribute is structured as follows:
	Type		Type
	20		20
	TLV-Length		TLV-Length
	16 octets. The length of ssm-prefix64 must be to 96 [RFC8115].		16 octets. The length of ssm-prefix64 must be /96 [RFC8115].
	Data Type		Data Type
	The attribute SSM-Prefix64 is of type ipv6prefix (Section 3.10 of		The attribute SSM-Prefix64 is of type ipv6prefix (Section 3.10 of
	[RFC8044]).		[RFC8044]).
	TLV-Type		TLV-Type
	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 MUST belong to the SSM range.
	skipping to change at page 25, line 37 ¶		skipping to change at page 26, line 37 ¶
	|<--------6.DHCPv6 Reply--------| |		|<--------6.DHCPv6 Reply--------| |
	| (container option(s)) | |		| (container option(s)) | |
	| | |		| | |
	DHCPv6 RADIUS		DHCPv6 RADIUS
	Figure 2: Interaction between DHCPv6 and AAA Server with RADIUS		Figure 2: Interaction between DHCPv6 and AAA Server with RADIUS
	authentication		authentication
	1. The CE creates a DHCPv6 Solicit message. For unicast softwire		1. 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 codes as defined in		with the Softwire46 Container option code(s) as defined in
	[RFC7598]. OPTION_S46_CONT_MAPE (94) should be included for MAP-		[RFC7598]. OPTION_S46_CONT_MAPE (94) should be included for MAP-
	E, OPTION_S46_CONT_MAPT (95) for MAP-T, and OPTION_S46_CONT_LW		E, OPTION_S46_CONT_MAPT (95) for MAP-T, and OPTION_S46_CONT_LW
	(96) for Lightweight 4over6. For multicast configuration, the		(96) for Lightweight 4over6. For multicast configuration, the
	option number for OPTION_V6_PREFIX64 (113) is included in the		option number for OPTION_V6_PREFIX64 (113) is included in the
	client's ORO. The message is sent to the BNG.		client's ORO. The message is sent to the BNG.
	2. On receipt of the Solicit message, the BNG constructs a RADIUS		2. On receipt of the Solicit message, the BNG constructs a RADIUS
	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 MAC address, interface-id, or both), a
	User-Password Attribute (2) (with a pre-configured shared		User-Password Attribute (2) (with a pre-configured shared
	password as defined in [RFC2865]. The Softwire46-Configuration		password between the CE and AAA server as defined in [RFC2865]).
	Attribute and/or Softwire46-Multicast Attribute are also included		The Softwire46-Configuration Attribute and/or
	(as requested by the client). The resulting message is sent to		Softwire46-Multicast Attribute are also included (as requested by
	the AAA server.		the client). The resulting message is sent to the AAA server.
	3. The AAA server authenticates the request. If this is successful,		3. The AAA server authenticates the request. If this is successful,
	and suitable configuration is available, an Access-Accept message		and suitable configuration is available, an Access-Accept message
	is sent to the BNG containing the requested		is sent to the BNG containing the requested
	Softwire46-Configuration Attribute or Softwire46-Multicast		Softwire46-Configuration Attribute or Softwire46-Multicast
	Attribute. It is the responsibility of the AAA server to ensure		Attribute. It is the responsibility of the AAA server to ensure
	the consistency of the provided configuration.		the consistency of the provided configuration.
	4. The BNG maps the received softwire configuration into the		4. The BNG maps the received softwire configuration into the
	corresponding fields in the DHCPv6 softwire configuration		corresponding fields in the DHCPv6 softwire configuration
	option(s). These are included in the DHCPv6 Advertise message		option(s). These are included in the DHCPv6 Advertise message
	which is sent to the CE.		which is sent to the CE.
	5. The CE sends a DHCPv6 Request message. In the ORO, the option		5. The CE sends a DHCPv6 Request message. In the ORO, the option
	code(s) of any of the required softwire options that were		code(s) of any of the required softwire options that were
	received in the Advertise message are included.		received in the Advertise message are included.
	6. The BNG sends a Reply message to the client containing the		6. The BNG sends a DHCPv6 Reply message to the client containing the
	softwire container options enumerated in the ORO.		softwire container option(s) enumerated in the ORO.
	The authorization operation could also be done independently, after		The authorization operation could be done independently, after the
	the authentication process. In this case, steps 1-5 are completed as		authentication process. In this case, steps 1-5 are completed as
	above, then the following steps are performed:		above, then the following steps are performed:
	6a. When the BNG receives the DHCPv6 Request, it constructs a RADIUS		6a. When the BNG receives the DHCPv6 Request, it constructs a RADIUS
	Access-Request message, which contains a Service-Type Attribute		Access-Request message, which contains a Service-Type Attribute
	(6) with the value "Authorize Only" (17), the corresponding		(6) with the value "Authorize Only" (17), the corresponding
	Softwire46-Configuration Attribute, and a State Attribute		Softwire46-Configuration Attribute, and a State Attribute
	obtained from the previous authentication process according to		obtained from the previous authentication process according to
	[RFC5080]. The resulting message is sent to the AAA server.		[RFC5080]. The resulting message is sent to the AAA server.
	7a. The AAA checks the authorization request. If it is approved, an		7a. The AAA checks the authorization request. If it is approved, an
	Access-Accept message is returned to the BNG with the		Access-Accept message is returned to the BNG with the
	corresponding Softwire46-Configuration Attribute.		corresponding Softwire46-Configuration Attribute.
	8a. The BNG sends a Reply message to the client containing the		8a. The BNG sends a Reply message to the client containing the
	softwire container options enumerated in the ORO.		softwire container options enumerated in the ORO.
	In addition to the above, the following points need to be considered:		In addition to the above, the following points need to be considered:
	o In both the configuration message flows described above the		o In the configuration message flows described above the Message-
	Message-authenticator (type 80) [RFC2869] SHOULD be used to		Authenticator (type 80) [RFC2869] should be used to protect both
	protect both Access-Request and Access-Accept messages.		Access-Request and Access-Accept messages.
	o If the BNG does not receive the corresponding		o 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		may fall back to creating the DHCPv6 softwire configuration
	options using pre-configured Softwire46 configuration, if this is		options using pre-configured Softwire46 configuration, if this is
	present.		present.
	o If the BNG receives an Access-Reject from the AAA server, then		o If the BNG receives an Access-Reject from the AAA server, then
	Softwire46 configuration MUST NOT be supplied to the client.		Softwire46 configuration must not be supplied to the client.
	o As specified in [RFC8415], Section 18.2.5, "Creation and		o As specified in [RFC8415], Section 18.2.5, "Creation and
	Transmission of Rebind Messages", if the DHCPv6 server to which		Transmission of Rebind Messages", if the DHCPv6 server to which
	the DHCPv6 Renew message was sent at time T1 has not responded by		the DHCPv6 Renew message was sent at time T1 has not responded by
	time T2, the CE (DHCPv6 client) SHOULD enter the Rebind state and		time T2, the CE (DHCPv6 client) should enter the Rebind state and
	attempt to contact any available server. In this situation, a		attempt to contact any available server. In this situation, a
	secondary BNG receiving the DHCPv6 message MUST initiate a new		secondary BNG receiving the DHCPv6 message must initiate a new
	Access-Request message towards the AAA server. The secondary BNG		Access-Request message towards the AAA server. The secondary BNG
	includes the Softwire46-Configuration Attribute in this Access-		includes the Softwire46-Configuration Attribute in this Access-
	Request message.		Request message.
	o For Lightweight 4over6, the subscriber's binding state needs to be		o 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 pre-		(lwAFTR)/BR. This can be achieved in two ways: static pre-
	configuration of the bindings on both the AAA server and lwAFTR,		configuration of the bindings on both the AAA server and lwAFTR,
	or on-demand whereby the AAA server updates the lwAFTR with the		or on-demand whereby the AAA server updates the lwAFTR with the
	subscriber's binding state as it is created or deleted.		CE's binding state as it is created or deleted.
	In some deployments, the DHCP server may use the Accounting-Request		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 to a AAA server the softwire configuration returned to a
	requesting host. It is the responsibility of the DHCP server to		requesting host. It is the responsibility of the DHCP server to
	ensure the consistency of the configuration provided to requesting		ensure the consistency of the configuration provided to requesting
	hosts. Reported data to a AAA server may be required for various		hosts. Reported data to a AAA server may be required for various
	operational purposes (e.g., regulatory).		operational purposes (e.g., regulatory).
	5. Table of Attributes		5. Table of Attributes
	skipping to change at page 28, line 25 ¶		skipping to change at page 29, line 25 ¶
	6. Security Considerations		6. Security Considerations
	Section 9 of [RFC7596] discusses security issues related to		Section 9 of [RFC7596] discusses security issues related to
	Lightweight 4over6, Section 10 of [RFC7597] discusses security issues		Lightweight 4over6, Section 10 of [RFC7597] discusses security issues
	related to MAP-E, Section 13 of [RFC7599] discusses security issues		related to MAP-E, Section 13 of [RFC7599] discusses security issues
	related to MAP-T, and Section 9 of [RFC8114] discusses security		related to MAP-T, and Section 9 of [RFC8114] discusses security
	issues related to the delivery of IPv4 multicast services to IPv4		issues related to the delivery of IPv4 multicast services to IPv4
	clients over an IPv6 multicast network.		clients over an IPv6 multicast network.
	This document does not introduce any security issue other than the		Generic RADIUS security considerations are discussed in Section 8 of
	ones already identified in RADIUS documents [RFC2865] and [RFC5176]		[RFC2865] and Section 6 of [RFC5176] for CoA messages. Known
	for CoA messages. Known security vulnerabilities of the RADIUS		security vulnerabilities of the RADIUS protocol discussed in
	protocol discussed in [RFC2607], [RFC2865], and [RFC2869] apply to		Section 7 of [RFC2607] and Section 7 of [RFC2869] apply to this
	this specification.		specification.
	This document targets deployments where a trusted relationship is in		This document targets deployments where a trusted relationship is in
	place between the RADIUS client and server with communication		place between the RADIUS client and server with communication
	optionally secured by IPsec or Transport Layer Security (TLS)		optionally secured by IPsec or Transport Layer Security (TLS)
	[RFC6614]. The use of IPsec [RFC4301] for providing security when		[RFC6614]. The use of IPsec [RFC4301] for providing security when
	RADIUS is carried in IPv6 is discussed in [RFC3162].		RADIUS is carried in IPv6 is discussed in [RFC3162].
	Security considerations for interactions between a Softwire46 CE and		Security considerations for interactions between a Softwire46 CE and
	the BNG are discussed in Section 9 of [RFC7598] (DHCPv6 options for		the BNG are discussed in Section 9 of [RFC7598] (DHCPv6 options for
	configuration of softwire46 address and port-mapped clients),		configuration of softwire46 address and port-mapped clients),
	skipping to change at page 32, line 41 ¶		skipping to change at page 33, line 41 ¶
	Email: yong@csnet1.cs.tsinghua.edu.cn		Email: yong@csnet1.cs.tsinghua.edu.cn
	9. Acknowledgements		9. Acknowledgements
	The authors would like to thank the valuable comments made by Peter		The authors would like to thank the valuable comments made by Peter
	Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan, Qian Wang, Wei		Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan, Qian Wang, Wei
	Meng, Cui Wang, Alan Dekok, Stefan Winter, and Yu Tianpeng to this		Meng, Cui Wang, Alan Dekok, Stefan Winter, and Yu Tianpeng to this
	document.		document.
	This document was merged with draft-sun-softwire-lw4over6-radext-01		This document was merged with [I-D.sun-softwire-lw4over6-radext] and
	and draft-wang-radext-multicast-radius-ext-00, thanks to everyone who		[I-D.wang-radext-multicast-radius-ext], thanks to everyone who
	contributed to this document.		contributed to this document.
	This document was produced using the xml2rfc tool [RFC7991].		This document was produced using the xml2rfc tool [RFC7991].
	Many thanks to Al Morton, Bernie Volz, Joel Halpern, and Donald		Many thanks to Al Morton, Bernie Volz, Joel Halpern, and Donald
	Eastlake for the review.		Eastlake for the review.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	skipping to change at page 34, line 36 ¶		skipping to change at page 35, line 36 ¶
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,		[RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,
	Richardson, M., Jiang, S., Lemon, T., and T. Winters,		Richardson, M., Jiang, S., Lemon, T., and T. Winters,
	"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",		"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
	RFC 8415, DOI 10.17487/RFC8415, November 2018,		RFC 8415, DOI 10.17487/RFC8415, November 2018,
	<https://www.rfc-editor.org/info/rfc8415>.		<https://www.rfc-editor.org/info/rfc8415>.
	10.2. Informative References		10.2. Informative References
			[I-D.sun-softwire-lw4over6-radext]
			Xie, C., Sun, Q., Qiong, Q., Zhou, C., Tsou, T., and Z.
			Liu, "Radius Extension for Lightweight 4over6", draft-sun-
			softwire-lw4over6-radext-01 (work in progress), March
			2014.
			[I-D.wang-radext-multicast-radius-ext]
			Wang, Q., Meng, W., Wang, C., and M. Boucadair, "RADIUS
			Extensions for IPv4-Embedded Multicast and Unicast IPv6
			Prefixes", draft-wang-radext-multicast-radius-ext-00 (work
			in progress), December 2015.
	[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy		[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
	Implementation in Roaming", RFC 2607,		Implementation in Roaming", RFC 2607,
	DOI 10.17487/RFC2607, June 1999,		DOI 10.17487/RFC2607, June 1999,
	<https://www.rfc-editor.org/info/rfc2607>.		<https://www.rfc-editor.org/info/rfc2607>.
	[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS		[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
	Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,		Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,
	<https://www.rfc-editor.org/info/rfc2869>.		<https://www.rfc-editor.org/info/rfc2869>.
	[RFC4301] Kent, S. and K. Seo, "Security Architecture for the		[RFC4301] Kent, S. and K. Seo, "Security Architecture for the
End of changes. 47 change blocks.
	107 lines changed or deleted		124 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/