< draft-ietf-dime-mip6-integrated-09.txt		draft-ietf-dime-mip6-integrated-10.txt >
	Diameter Maintenance and J. Korhonen		Diameter Maintenance and J. Korhonen
	Extensions (DIME) TeliaSonera		Extensions (DIME) TeliaSonera
	Internet-Draft J. Bournelle		Internet-Draft J. Bournelle
	Intended status: Standards Track Orange Labs		Intended status: Standards Track Orange Labs
	Expires: November 27, 2008 H. Tschofenig		Expires: March 9, 2009 H. Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
	C. Perkins		C. Perkins
			WiChorus
	K. Chowdhury		K. Chowdhury
	Starent Networks		Starent Networks
	May 26, 2008		September 5, 2008
	Diameter Mobile IPv6: Support for Network Access Server to Diameter		Diameter Mobile IPv6: Support for Network Access Server to Diameter
	Server Interaction		Server Interaction
	draft-ietf-dime-mip6-integrated-09.txt		draft-ietf-dime-mip6-integrated-10.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on November 27, 2008.		This Internet-Draft will expire on March 9, 2009.
			Copyright Notice
			Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	A Mobile IPv6 node requires a home agent address, a home address, and		A Mobile IPv6 node requires a home agent address, a home address, and
	a security association with its home agent before it can start		a security association with its home agent before it can start
	utilizing Mobile IPv6. RFC 3775 requires that some or all of these		utilizing Mobile IPv6. RFC 3775 requires that some or all of these
	parameters are statically configured. Mobile IPv6 bootstrapping work		parameters are statically configured. Mobile IPv6 bootstrapping work
	aims to make this information dynamically available to the Mobile		aims to make this information dynamically available to the Mobile
	Node. An important aspect of the Mobile IPv6 bootstrapping solution		Node. An important aspect of the Mobile IPv6 bootstrapping solution
	is to support interworking with existing authentication,		is to support interworking with existing authentication,
	authorization and accounting infrastructure. This document describes		authorization and accounting infrastructure. This document describes
	the MIPv6 bootstrapping using the Diameter Network Access Server		MIPv6 bootstrapping using the Diameter Network Access Server (NAS) to
	(NAS) to home Authentication, Authorization and Accounting server		home Authentication, Authorization and Accounting server (HAAA)
	(HAAA) interface.		interface.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3		2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
	3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5		3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	4. Commands, AVPs and Advertising Application Support . . . . . . 6		4. Commands, Attribute Value Pairs and Advertising
			Application Support . . . . . . . . . . . . . . . . . . . . . 6
	4.1. Advertising Application Support . . . . . . . . . . . . . 6		4.1. Advertising Application Support . . . . . . . . . . . . . 6
	4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 6		4.2. Attribute Value Pair Definitions . . . . . . . . . . . . . 6
	4.3. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 7		4.2.1. MIP6-Agent-Info . . . . . . . . . . . . . . . . . . . 6
	4.4. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 7		4.2.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 7
	4.5. Attribute Value Pair Definitions . . . . . . . . . . . . . 8		4.2.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 7
	4.5.1. MIP6-Agent-Info . . . . . . . . . . . . . . . . . . . 8		4.2.4. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . 7
	4.5.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 9		4.2.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 8
	4.5.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 9		5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	4.5.4. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . 9		5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 9
	4.5.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 9		5.2. Home Agent Assignment by the Diameter Server . . . . . . . 10
	5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 11		5.3. Home Agent Assignment by NAS or Diameter Server . . . . . 11
	5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 11		6. Attribute Value Pair Occurrence Tables . . . . . . . . . . . . 12
	5.2. Home Agent Assignment by the Diameter Server . . . . . . . 12		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
	5.3. Home Agent Assignment by NAS or Diameter Server . . . . . 12		7.1. Registration of new AVPs . . . . . . . . . . . . . . . . . 13
	6. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 14		7.2. New Registry: Mobility Capability . . . . . . . . . . . . 13
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14		8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	7.1. Registration of new AVPs . . . . . . . . . . . . . . . . . 14		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
	7.2. New Registry: Mobility Capability . . . . . . . . . . . . 14		10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 15		10.1. Normative References . . . . . . . . . . . . . . . . . . . 14
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15		10.2. Informative References . . . . . . . . . . . . . . . . . . 15
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
	10.1. Normative References . . . . . . . . . . . . . . . . . . . 15		Intellectual Property and Copyright Statements . . . . . . . . . . 17
	10.2. Informative References . . . . . . . . . . . . . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
	Intellectual Property and Copyright Statements . . . . . . . . . . 18
	1. Introduction		1. Introduction
	The Mobile IPv6 (MIPv6) specification [1] requires a Mobile Node (MN)		The Mobile IPv6 (MIPv6) specification [1] requires a Mobile Node (MN)
	to perform registration with a home agent (HA) with information about		to perform registration with a home agent (HA) with information about
	its current point of attachment (care-of address). The HA creates		its current point of attachment (care-of address). The HA creates
	and maintains binding between the MN's Home Address and the MN's		and maintains the binding between the MN's Home Address and the MN's
	Care-of Address.		Care-of Address.
	In order to register with a HA, the MN needs to know some information		In order to register with a HA, the MN needs to know some information
	such as the Home Link prefix, the HA address, the Home Address(es),		such as the Home Link prefix, the HA address, the Home Address(es),
	the Home Link prefix length and security association related		the Home Link prefix length and security association related
	information.		information.
	The aforementioned information may be statically configured.		The aforementioned information may be statically configured.
	However, static provisioning becomes an administrative burden for an		However, static provisioning becomes an administrative burden for an
	operator. Moreover, it does not address load balancing, failover,		operator. Moreover, it does not address load balancing, failover,
	opportunistic home link assignment and assignment of local HAs in		opportunistic home link assignment or assignment of local HAs in
	close proximity to the MN. Also the ability to react to sudden		close proximity to the MN. Also the ability to react to sudden
	environmental or topological changes is minimal. Static provisioning		environmental or topological changes is minimal. Static provisioning
	may not be desirable, in light of these limitations.		may not be desirable, in light of these limitations.
	Dynamic assignment of MIPv6 home registration information is a		Dynamic assignment of MIPv6 home registration information is a
	desirable feature for ease of deployment and network maintenance.		desirable feature for ease of deployment and network maintenance.
	For this purpose, the AAA infrastructure, which is used for access		For this purpose, the AAA infrastructure, which is used for access
	authentication, can be leveraged to assign some or all of the		authentication, can be leveraged to assign some or all of the
	necessary parameters. The Diameter server in Access Service		necessary parameters. The Diameter server in the Access Service
	Provider's (ASP) or in Mobility Service Provider's (MSP) network may		Provider's (ASP) or in the Mobility Service Provider's (MSP) network
	return these parameters to the AAA client. Regarding the		may return these parameters to the AAA client. Regarding the
	bootstrapping procedures, the AAA client might either be the NAS, in		bootstrapping procedures, the AAA client might either be the NAS, in
	case of the integrated scenario, or the HA, in case of the split		case of the integrated scenario, or the HA, in case of the split
	scenario [7]. The terms integrated and split are described in the		scenario [7]. The terms integrated and split are described in the
	terminology section and were introduced in [8] and [9].		terminology section and were introduced in [8] and [9].
	2. Terminology and Abbreviations		2. Terminology and Abbreviations
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC2119 [2].		document are to be interpreted as described in RFC2119 [2].
	General mobility terminology can be found in [10]. The following		General mobility terminology can be found in [10]. The following
	additional terms, as defined in [8], are used in this document:		additional terms below are either borrowed from [8][7] or introduced
			in this document:
	Access Service Authorizer (ASA):		Access Service Authorizer (ASA):
	A network operator that authenticates a MN and establishes the		A network operator that authenticates a MN and establishes the
	MN's authorization to receive Internet service.		MN's authorization to receive Internet service.
	Access Service Provider (ASP):		Access Service Provider (ASP):
	A network operator that provides direct IP packet forwarding to		A network operator that provides direct IP packet forwarding to
	and from the MN.		and from the MN.
	skipping to change at page 4, line 48 ¶		skipping to change at page 5, line 9 ¶
	Local AAA (LAAA):		Local AAA (LAAA):
	An authentication, authorization and accounting proxy located in		An authentication, authorization and accounting proxy located in
	the local (ASP) network.		the local (ASP) network.
	Visited AAA (VAAA):		Visited AAA (VAAA):
	An authentication, authorization and accounting proxy located in a		An authentication, authorization and accounting proxy located in a
	visited network i.e., in the visited realm. In a roaming case,		visited network i.e., in the visited realm. In a roaming case,
	the local Diameter proxy has the VAAA role.		the local Diameter proxy has the VAAA role (see Figure 1).
	3. Overview		3. Overview
	This document addresses the authentication, authorization and		This document addresses the authentication, authorization and
	accounting functionality required for the MIPv6 bootstrapping		accounting functionality required for the MIPv6 bootstrapping
	solutions outlined in [8] and focuses on the Diameter based AAA		solutions outlined in [8] and focuses on the Diameter based AAA
	functionality for the NAS to HAAA communication.		functionality for the NAS to HAAA communication.
	In the integrated scenario MIPv6 bootstrapping is provided as part of		In the integrated scenario MIPv6 bootstrapping is provided as part of
	the network access authentication procedure. Figure 1 shows the		the network access authentication procedure. Figure 1 shows the
	skipping to change at page 6, line 14 ¶		skipping to change at page 6, line 21 ¶
	When the Diameter server performs the authentication and		When the Diameter server performs the authentication and
	authorization for the network access it also determines whether the		authorization for the network access it also determines whether the
	user is authorized to the MIPv6 service. Based on the MIPv6 service		user is authorized to the MIPv6 service. Based on the MIPv6 service
	authorization and user's policy profile, the Diameter server may		authorization and user's policy profile, the Diameter server may
	return several MIPv6 bootstrapping related parameters to the NAS.		return several MIPv6 bootstrapping related parameters to the NAS.
	The NAS to HAAA interface described in this document is not tied to		The NAS to HAAA interface described in this document is not tied to
	DHCPv6 as the only mechanism to convey MIPv6 related configuration		DHCPv6 as the only mechanism to convey MIPv6 related configuration
	parameters from the NAS/Diameter client to the mobile node.		parameters from the NAS/Diameter client to the mobile node.
	4. Commands, AVPs and Advertising Application Support		4. Commands, Attribute Value Pairs and Advertising Application Support
	4.1. Advertising Application Support		4.1. Advertising Application Support
	This document does not define a new application. On the other hand		This document does not define a new application. On the other hand
	it defines a number of MIPv6 bootstrapping NAS to HAAA interface		it defines a number of AVPs used in the interface between NAS to HAAA
	(integrated scenario) related AVPs. These AVPs can be used with		for the integrated scenario of MIPv6 bootstrapping. These AVPs can
	present and future Diameter applications, where permitted by the		be used with any present and future Diameter applications, where
	command ABNF. The examples using existing applications and their		permitted by the command ABNF. The examples using existing
	commands in the following sections are for informational purposes		applications and their commands in the following sections are for
	only. The examples in this document reuse EAP [3] application and		informational purposes only. The examples in this document reuse the
	its respective commands.		EAP [3] application and its respective commands.
	4.2. Command Codes
	This document shows re-use of the Diameter EAP application commands
	[3] as an example of the MIPv6 bootstrapping NAS to HAAA interface.
	Refer to Section 6 and Figure 6 for AVP occurance definitions in
	Diameter commands. The following commands are used to carry MIPv6
	related bootstrapping AVPs:
	Command-Name Abbrev. Code Reference Application
	Diameter-EAP-Request DER 268 RFC 4072 EAP
	Diameter-EAP-Answer DEA 268 RFC 4072 EAP
	Figure 2: MIPv6 Bootstrapping NAS to HAAA Interface Command Codes
	When the Re-Auth-Request (RAR), Re-Auth-Answer (RAA), Session-
	Termination-Request (STR), Session-Termination-Answer (STA), Abort-
	Session-Request (ASR), Abort-Session-Answer (ASA), Accounting-Request
	(ACR), and Accounting-Answer (ACA) commands are used together with
	the MIPv6 bootstrapping NAS to HAAA interface, they follow the rules
	defined in RFC 3588 [4] and the rules for the specific Diameter
	application the AVPs defined in this document are used with. The
	accounting commands use the Application Identifier value of 3
	(Diameter Base Accounting); the others use 0 (Diameter Common
	Messages).
	All request messages SHOULD contain the User-Name AVP containing the
	identity of the MN in NAI format. It is out of scope how the NAS
	finds out the MN identity. The NAS could, for example, use the MN
	identity provided by the network access authentication mechanism.
	4.3. Diameter-EAP-Request (DER)
	The Diameter-EAP-Request (DER) message [3], indicated by the Command-
	Code field set to 268 and the 'R' bit set in the Command Flags field,
	is sent by the NAS to the Diameter server to initiate a network
	access authentication and authorization procedure. The DER message
	format is the same as defined in [3]. The message MAY include
	optional MIPv6 bootstrapping AVPs:
	<Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY >
	< Session-Id >
	{ Auth-Application-Id }
	{ Origin-Host }
	{ Origin-Realm }
	{ Destination-Realm }
	{ Auth-Request-Type }
	* [ MIP6-Agent-Info ]
	* [ MIP6-Home-Link-Prefix ]
	[ MIP6-Feature-Vector ]
	[ User-Name ]
	[ Destination-Host ]
	...
	* [ AVP ]
	4.4. Diameter-EAP-Answer (DEA)
	The Diameter-EAP-Answer (DEA) message defined in [3], indicated by
	the Command-Code field set to 268 and 'R' bit cleared in the Command
	Flags field, is sent in response to the Diameter-EAP-Request message
	(DER). If the network access authentication procedure was successful
	then the response MAY include any set of bootstrapping AVPs.
	The DEA message format is the same as defined in [3] with an addition
	of optional MIPv6 bootstrapping AVPs:
	<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
	< Session-Id >
	{ Auth-Application-Id }
	{ Auth-Request-Type }
	{ Result-Code }
	{ Origin-Host }
	{ Origin-Realm }
	* [ MIP6-Agent-Info ]
	* [ MIP6-Home-Link-Prefix ]
	[ MIP6-Feature-Vector ]
	[ User-Name ]
	...
	* [ AVP ]
	4.5. Attribute Value Pair Definitions		4.2. Attribute Value Pair Definitions
	4.5.1. MIP6-Agent-Info		4.2.1. MIP6-Agent-Info
	The MIP6-Agent-Info AVP (AVP code TBD) is type of Grouped and		The MIP6-Agent-Info AVP (AVP code TBD) is type of Grouped and
	contains necessary information to assign a HA to the MN. When the		contains necessary information to assign a HA to the MN. When the
	MIP6-Agent-Info AVP is present in a message, it MUST contain either		MIP6-Agent-Info AVP is present in a message, it MUST contain either
	the MIP-Home-Agent-Address AVP or the MIP-Home-Agent-Host AVP, or		the MIP-Home-Agent-Address AVP or the MIP-Home-Agent-Host AVP, or
	both AVPs. The grouped AVP has the following grammar:		both AVPs. The grouped AVP has the following grammar:
	<MIP6-Agent-Info> ::= < AVP Header: TBD >		<MIP6-Agent-Info> ::= < AVP Header: TBD >
	[ MIP-Home-Agent-Address ]		*2[ MIP-Home-Agent-Address ]
	[ MIP-Home-Agent-Host ]		[ MIP-Home-Agent-Host ]
	* [ AVP ]		* [ AVP ]
	If both MIP-Home-Agent-Address and MIP-Home-Agent-Host APVs are		If both MIP-Home-Agent-Address and MIP-Home-Agent-Host APVs are
	present in the MIP6-Agent-Info, the MIP-Home-Agent-Address SHOULD		present in the MIP6-Agent-Info, the MIP-Home-Agent-Address SHOULD
	have a precedence over the MIP-Home-Agent-Host. The reason for this		have a precedence over the MIP-Home-Agent-Host. The reason for this
	recommendation is that the MIP-Home-Agent-Address points to a		recommendation is that the MIP-Home-Agent-Address points to a
	specific home agent, where as the MIP-Home-Agent-Host may point to a		specific home agent, where as the MIP-Home-Agent-Host may point to a
	group of HAs located at within the same realm. A Diameter client or		group of HAs located at within the same realm. A Diameter client or
	an agent may use the MIP-Home-Agent-Host AVP, for instance, to find		an agent may use the MIP-Home-Agent-Host AVP, for instance, to find
	out the realm where the HA is located.		out the realm where the HA is located.
	This AVP MAY also be attached by the NAS or by intermediating		This AVP MAY also be attached by the NAS or by intermediating
	Diameter proxies in a request message when sent to the Diameter		Diameter proxies in a request message when sent to the Diameter
	server as a hint of a locally assigned HA. This AVP MAY also be		server as a hint of a locally assigned HA. This AVP MAY also be
	attached by the intermediating Diameter proxies in a reply message		attached by the intermediating Diameter proxies in a reply message
	from the Diameter server, if locally assigned HAs are authorized by		from the Diameter server, if locally assigned HAs are authorized by
	the Diameter server.		the Diameter server.
	4.5.2. MIP-Home-Agent-Address AVP		4.2.2. MIP-Home-Agent-Address AVP
	The MIP-Home-Agent-Address AVP (AVP Code 334 [5]) is of type Address		The MIP-Home-Agent-Address AVP (AVP Code 334 [4]) is of type Address
	and contains the HA address. The Diameter server MAY decide to		and contains IPv6 or IPv6 address of the HA. The Diameter server MAY
	assign a HA to the MN that is in close proximity to the point of		decide to assign a HA to the MN that is in close proximity to the
	attachment (e.g., determined by the NAS-Identifier AVP). There may		point of attachment (e.g., determined by the NAS-Identifier AVP).
	be other reasons for dynamically assigning HAs to the MN, for example		There may be other reasons for dynamically assigning HAs to the MN,
	to share the traffic load.		for example to share the traffic load.
	4.5.3. MIP-Home-Agent-Host AVP		4.2.3. MIP-Home-Agent-Host AVP
	The MIP-Home-Agent-Host AVP (AVP Code 348 [5]) is of type Grouped and		The MIP-Home-Agent-Host AVP (AVP Code 348 [4]) is of type Grouped and
	contains the identity of the assigned HA. Both the Destination-Realm		contains the identity of the assigned HA. Both the Destination-Realm
	and the Destination-Host AVP of the HA are included in the grouped		and the Destination-Host AVPs of the HA are included in the grouped
	AVP. The usage of this AVP is equivalent to the MIP-Home-Agent-		AVP. The usage of the MIP-Home-Agent-Host AVP is equivalent to the
	Address AVP but offers an additional level of indirection by using		MIP-Home-Agent-Address AVP but offers an additional level of
	the DNS infrastructure.		indirection by using the DNS infrastructure.
	Depending on the actual deployment and DNS configuration the		Depending on the actual deployment and DNS configuration the
	Destination-Host AVP MAY represent one or more home agents. It is		Destination-Host AVP MAY represent one or more home agents. It is
	RECOMMENDED that the Destination-Host AVP identifies exactly one HA.		RECOMMENDED that the Destination-Host AVP identifies exactly one HA.
	4.5.4. MIP6-Home-Link-Prefix AVP		It is RECOMMENDED that the MIP-Home-Agent-Host AVP is always included
			in the MIP6-Agent-Info AVP. In this way the HA address can be
			associated with the corresponding realm the HA belongs to.
			4.2.4. MIP6-Home-Link-Prefix AVP
	The MIP6-Home-Link-Prefix AVP (AVP Code TBD) is of type OctetString		The MIP6-Home-Link-Prefix AVP (AVP Code TBD) is of type OctetString
	and contains the Mobile IPv6 home network prefix information in		and contains the Mobile IPv6 home network prefix information in
	network byte order. The home network prefix MUST be encoded as the		network byte order. The home network prefix MUST be encoded as the
	8-bit prefix length information followed by the 128-bit field for the		8-bit prefix length information followed by the 128-bit field for the
	available home network prefix.		available home network prefix.
	4.5.5. MIP6-Feature-Vector AVP		4.2.5. MIP6-Feature-Vector AVP
	The MIP6-Feature-Vector AVP (AVP Code TBD) is of type Unsigned64 and		The MIP6-Feature-Vector AVP (AVP Code TBD) is of type Unsigned64 and
	contains a 64 bit flags field of supported capabilities of the NAS/		contains a 64 bit flags field of supported capabilities of the NAS/
	ASP. Sending and receiving the MIP6-Feature-Vector AVP with value 0		ASP. Sending and receiving the MIP6-Feature-Vector AVP with value 0
	MUST be supported, although that does not provide much guidance about		MUST be supported, although that does not provide much guidance about
	specific needs of bootstrapping.		specific needs of bootstrapping.
	The NAS MAY include this AVP to indicate capabilities of the NAS/ASP		The NAS MAY include this AVP to indicate capabilities of the NAS/ASP
	to the Diameter server. For example, the NAS may indicate that a		to the Diameter server. For example, the NAS may indicate that a
	local HA can be provided. Similarly, the Diameter server MAY include		local HA can be provided. Similarly, the Diameter server MAY include
	skipping to change at page 10, line 25 ¶		skipping to change at page 8, line 41 ¶
	When this flag is set in the request message, a local home agent		When this flag is set in the request message, a local home agent
	outside the home realm is requested and may be assigned to the MN.		outside the home realm is requested and may be assigned to the MN.
	When this flag is set by the Diameter server in the answer		When this flag is set by the Diameter server in the answer
	message, then the assignment of local HAs is authorized by the		message, then the assignment of local HAs is authorized by the
	Diameter server.		Diameter server.
	A local HA may be assigned by the NAS, LAAA or VAAA depending on		A local HA may be assigned by the NAS, LAAA or VAAA depending on
	the network architecture and the deployment.		the network architecture and the deployment.
	The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT		The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT
	capability and the MIP-Agent-Info AVP are used to assign HAs, either		(referred as LOCAL-bit in the examples) capability and the MIP-Agent-
	a local HA (L-HA) or a home network HA (H-HA). Below is an example		Info AVP (referred as HA-Info in the examples) are used to assign
	of a request message combinations as seen by the HAAA:		HAs, either a local HA (L-HA) or a home network HA (H-HA). Below is
			an example of a request message combinations as seen by the HAAA:
	LOCAL-bit HA-Info Meaning		LOCAL-bit HA-Info Meaning
	0 - ASP or [LV]AAA is not able to assign a L-HA		0 - ASP or [LV]AAA is not able to assign a L-HA
	0 L-HA Same as above. HA-Info must be ignored		0 L-HA Same as above. HA-Info must be ignored
	1 - ASP or [LV]AAA can/wishes to assign a L-HA		1 - ASP or [LV]AAA can/wishes to assign a L-HA
	1 L-HA Same as above but ASP or [LV]AAA also		1 L-HA Same as above but ASP or [LV]AAA also
	provides a hint of the assigned L-HA		provides a hint of the assigned L-HA
	Then the same as above for an answer message combinations as seen by		Then the same as above for an answer message combinations as seen by
	skipping to change at page 11, line 5 ¶		skipping to change at page 9, line 19 ¶
	LOCAL-bit HA-Info Meaning		LOCAL-bit HA-Info Meaning
	0 - No HA allowed -> no mobility		0 - No HA allowed -> no mobility
	0 H-HA L-HA is not allowed. HAAA assigns a H-HA		0 H-HA L-HA is not allowed. HAAA assigns a H-HA
	1 - L-HA is allowed. No HAAA or [LV]AAA assigned HA		1 - L-HA is allowed. No HAAA or [LV]AAA assigned HA
	1 L-HA L-HA is allowed. [LV]AAA also assigns a L-HA		1 L-HA L-HA is allowed. [LV]AAA also assigns a L-HA
	1 H-HA L-HA is allowed. HAAA also assigns a HA		1 H-HA L-HA is allowed. HAAA also assigns a HA
	1 H-HA L-HA is allowed. HAAA assigns a H-HA and		1 H-HA L-HA is allowed. HAAA assigns a H-HA and
	+ L-HA [LV]AAA also assigns also a L-HA		+ L-HA [LV]AAA also assigns also a L-HA
			A NAS should expect to possible receive multiple of the MIP6-Agent-
			Info AVPs.
	5. Examples		5. Examples
	5.1. Home Agent Assignment by the NAS		5.1. Home Agent Assignment by the NAS
	In this scenario we consider the case where the NAS wishes to		In this scenario we consider the case where the NAS wishes to
	allocate a local HA to the MN. The NAS will also inform the Diameter		allocate a local HA to the MN. The NAS will also inform the Diameter
	server about the HA address it has assigned to the visiting MN (e.g.,		server about the HA address it has assigned to the visiting MN (e.g.,
	2001:db8:1:c020::1). The Diameter-EAP-Request message therefore has		2001:db8:1:c020::1). The Diameter-EAP-Request message therefore has
	the MIP6-Feature-Vector with the LOCAL_HOME_AGENT_ASSIGNMENT and the		the MIP6-Feature-Vector with the LOCAL_HOME_AGENT_ASSIGNMENT and the
	MIP6_INTEGRATED set. The MIP6-Agent-Info AVP contains the MIP-Home-		MIP6_INTEGRATED set. The MIP6-Agent-Info AVP contains the MIP-Home-
	Agent-Address AVP with the address of the proposed HA.		Agent-Address AVP with the address of the proposed HA.
	Diameter		Diameter
	NAS Server		NAS/VAAA Server
	| |		| |
	| Diameter-EAP-Request |		| Diameter-EAP-Request |
	| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |		| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
	| | MIP6_INTEGRATED) |		| | MIP6_INTEGRATED) |
	| MIP6-Agent-Info{ |		| MIP6-Agent-Info{ |
	| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |		| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |
	| } |		| } |
	| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |		| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
	| EAP-Payload(EAP Start) |		| EAP-Payload(EAP Start) |
	|---------------------------------------------------------------->|		|---------------------------------------------------------------->|
	skipping to change at page 11, line 45 ¶		skipping to change at page 10, line 33 ¶
	| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |		| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
	| | MIP6_INTEGRATED) |		| | MIP6_INTEGRATED) |
	| Result-Code=DIAMETER_SUCCESS |		| Result-Code=DIAMETER_SUCCESS |
	| EAP-Payload(EAP Success) |		| EAP-Payload(EAP Success) |
	| EAP-Master-Session-Key |		| EAP-Master-Session-Key |
	| (authorization AVPs) |		| (authorization AVPs) |
	| ... |		| ... |
	|<----------------------------------------------------------------|		|<----------------------------------------------------------------|
	| |		| |
	Figure 3: Home Agent Assignment by NAS		Figure 2: Home Agent Assignment by NAS
	Depending on the Diameter server configuration and user's		Depending on the Diameter server configuration and user's
	subscription profile, the Diameter server either accepts or rejects		subscription profile, the Diameter server either accepts or rejects
	the proposal of locally HA allocated by the NAS will be used. In our		the local HA allocated by the NAS. In our example, the Diameter
	example, the Diameter server accepts the proposal and the the MIP6-		server accepts the proposal and the the MIP6-Feature-Vector AVP with
	Feature-Vector AVP with LOCAL_HOME_AGENT_ASSIGNMENT flag (together		LOCAL_HOME_AGENT_ASSIGNMENT flag (together with the MIP6_INTEGRATED
	with the MIP6_INTEGRATED flag) is set and returned to the NAS.		flag) is set and returned to the NAS.
	5.2. Home Agent Assignment by the Diameter Server		5.2. Home Agent Assignment by the Diameter Server
	In this scenario we consider the case where the NAS supports the		In this scenario we consider the case where the NAS supports the
	Diameter MIPv6 integrated scenario as defined in this document but		Diameter MIPv6 integrated scenario as defined in this document but
	does not offer local HA assignment. Hence, the MIP6-Feature-Vector		does not offer local HA assignment. Hence, the MIP6-Feature-Vector
	AVP only has the MIP6_INTEGRATED flag set. The Diameter server		AVP only has the MIP6_INTEGRATED flag set. The Diameter server
	allocates a HA to the mobile node and conveys the address in the MIP-		allocates a HA to the mobile node and conveys the address in the MIP-
	Home-Agent-Address AVP that is encapsulated in the MIP6-Agent-Info		Home-Agent-Address AVP that is encapsulated in the MIP6-Agent-Info
	AVP. Additionally, the MIP6-Feature-Vector AVP has the		AVP. Additionally, the MIP6-Feature-Vector AVP has the
	skipping to change at page 12, line 43 ¶		skipping to change at page 11, line 31 ¶
	| } |		| } |
	| MIP6-Feature-Vector=(MIP6_INTEGRATED) |		| MIP6-Feature-Vector=(MIP6_INTEGRATED) |
	| Result-Code=DIAMETER_SUCCESS |		| Result-Code=DIAMETER_SUCCESS |
	| EAP-Payload(EAP Success) |		| EAP-Payload(EAP Success) |
	| EAP-Master-Session-Key |		| EAP-Master-Session-Key |
	| (authorization AVPs) |		| (authorization AVPs) |
	| ... |		| ... |
	|<----------------------------------------------------------------|		|<----------------------------------------------------------------|
	| |		| |
	Figure 4: Home Agent Assignment by Diameter Server		Figure 3: Home Agent Assignment by Diameter Server
	5.3. Home Agent Assignment by NAS or Diameter Server		5.3. Home Agent Assignment by NAS or Diameter Server
	This section shows a message flow for the MIPv6 integrated scenario		This section shows another message flow for the MIPv6 integrated
	bootstrapping where the NAS informs the Diameter server that it is		scenario bootstrapping where the NAS informs the Diameter server that
	able to locally assign a HA to the MN. The Diameter server is able		it is able to locally assign a HA to the MN. The Diameter server is
	to provide a HA to the MN but also authorizes the assignment of local		able to provide a HA to the MN but also authorizes the assignment of
	HA. The Diameter server then replies to the NAS with HA related		local HA. The Diameter server then replies to the NAS with HA
	bootstrapping information.		related bootstrapping information.
	Whether the NAS/ASP then offers a locally assigned HA or the Diameter		Whether the NAS/ASP then offers a locally assigned HA or the Diameter
	server assigned HA to the MN is, in this example, based on the local		server assigned HA to the MN is, in this example, based on the local
	ASP policy.		ASP policy.
	Diameter		Diameter
	NAS Server		NAS/VAAA Server
	| |		| |
	| Diameter-EAP-Request |		| Diameter-EAP-Request |
	| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |		| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
	| | MIP6_INTEGRATED) |		| | MIP6_INTEGRATED) |
	| MIP6-Agent-Info{ |		| MIP6-Agent-Info{ |
	| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |		| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |
	| } |		| } |
	| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |		| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
	| EAP-Payload(EAP Start) |		| EAP-Payload(EAP Start) |
	|---------------------------------------------------------------->|		|---------------------------------------------------------------->|
	skipping to change at page 13, line 41 ¶		skipping to change at page 12, line 35 ¶
	| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |		| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
	| | MIP6_INTEGRATED) |		| | MIP6_INTEGRATED) |
	| Result-Code=DIAMETER_SUCCESS |		| Result-Code=DIAMETER_SUCCESS |
	| EAP-Payload(EAP Success) |		| EAP-Payload(EAP Success) |
	| EAP-Master-Session-Key |		| EAP-Master-Session-Key |
	| (authorization AVPs) |		| (authorization AVPs) |
	| ... |		| ... |
	|<----------------------------------------------------------------|		|<----------------------------------------------------------------|
	| |		| |
	Figure 5: Home Agent Assignment by NAS or Diameter Server		Figure 4: Home Agent Assignment by NAS or Diameter Server
	If the Diameter server does not accept locally assigned HA, the		If the Diameter server does not allow the MN to use a locally
	Diameter returns the MIP6-Feature-Vector AVP with		assigned HA, the Diameter returns the MIP6-Feature-Vector AVP with
	LOCAL_HOME_AGENT_ASSIGNMENT bit unset and HA address it plans to		the LOCAL_HOME_AGENT_ASSIGNMENT bit unset and HA address it allocated
	allocate for the MN.		to the MN.
	6. AVP Occurrence Tables		6. Attribute Value Pair Occurrence Tables
	The following table lists the additional MIPv6 bootstrapping NAS to		Figure 5 lists the MIPv6 bootstrapping NAS to HAAA interface AVPs,
	HAAA interface AVPs that may be present in any Diameter application		along with a specification determining how many of each new AVP may
	request and answer commands, where permitted by the command ABNF.		be included in a Diameter command. They may be present in any
			Diameter application request and answer commands, where permitted by
			the command ABNF.
	+-----------+		+-----------+
	| Command |		| Command |
	|-----+-----+		|-----+-----+
	Attribute Name | Req | Ans |		Attribute Name | Req | Ans |
	-------------------------------|-----+-----|		-------------------------------|-----+-----|
	MIP6-Agent-Info | 0+ | 0+ |		MIP6-Agent-Info | 0+ | 0+ |
	MIP6-Feature-Vector | 0-1 | 0-1 |		MIP6-Feature-Vector | 0-1 | 0-1 |
	MIP6-Home-Link-Prefix | 0+ | 0+ |		MIP6-Home-Link-Prefix | 0+ | 0+ |
	+-----+-----+		+-----+-----+
	Figure 6: Generic Request and Answer Commands AVP Table		Figure 5: Generic Request and Answer Commands AVP Table
	7. IANA Considerations		7. IANA Considerations
	7.1. Registration of new AVPs		7.1. Registration of new AVPs
	This specification defines the following new AVPs:		This specification defines the following new AVPs:
	MIP6-Agent-Info is set to TBD		MIP6-Agent-Info is set to TBD
	MIP6-Feature-Vector is set to TBD		MIP6-Feature-Vector is set to TBD
	MIP6-Home-Link-Prefix is set to TBD		MIP6-Home-Link-Prefix is set to TBD
	7.2. New Registry: Mobility Capability		7.2. New Registry: Mobility Capability
	IANA is requested to create a new registry for the Mobility		IANA is requested to create a new registry for the Mobility
	Capability as described in Section 4.5.5.		Capability as described in Section 4.2.5.
	Token | Value | Description		Token | Value | Description
	----------------------------------+----------------------+------------		----------------------------------+----------------------+------------
	MIP6_INTEGRATED | 0x0000000000000001 | [RFC TBD]		MIP6_INTEGRATED | 0x0000000000000001 | [RFC TBD]
	LOCAL_HOME_AGENT_ASSIGNMENT | 0x0000000000000002 | [RFC TBD]		LOCAL_HOME_AGENT_ASSIGNMENT | 0x0000000000000002 | [RFC TBD]
	Available for Assignment via IANA | 2^x |		Available for Assignment via IANA | 2^x |
	Allocation rule: Only numeric values that are 2^x (power of two) are		Allocation rule: Only numeric values that are 2^x (power of two,
	allowed based on the allocation policy described below.		where x >= 2) are allowed based on the allocation policy described
			below.
	Following the policies outlined in [1] new values with a description		Following the example policies described in [11] new values for the
	of their semantic for usage with the MIP6-Feature-Vector AVP together		MIP6-Feature-Vector AVP will be assigned based on the "Specification
	with a Token will be assigned after Expert Review initiated by the		Required" policy. No mechanism to mark entries as "deprecated" is
	O&M Area Directors in consultation with the DIME working group chairs		envisioned.
	or the working group chairs of a designated successor working group.
	Updates can be provided based on expert approval only. A designated
	expert will be appointed by the O&M Area Directors. No mechanism to
	mark entries as "deprecated" is envisioned. Based on expert approval
	it is possible to delete entries from the registry.
	8. Security Considerations		8. Security Considerations
	The security considerations for the Diameter interaction required to		The security considerations for the Diameter interaction required to
	accomplish the integrated scenario are described in [11].		accomplish the integrated scenario are described in [12].
	Additionally, the security considerations of the Diameter base		Additionally, the security considerations of the Diameter base
	protocol [4], Diameter NASREQ application [6] / Diameter EAP [3]		protocol [5], Diameter NASREQ application [6] / Diameter EAP [3]
	application (with respect to network access authentication and the		application (with respect to network access authentication and the
	transport of keying material) are applicable to this document. This		transport of keying material) are applicable to this document.
	document does not introduce new security vulnerabilities.		Developers should insure that special attention is paid to
			configuring the security associations protecting the messages that
			enables the global positioning and allocation of home agents, for
			instance, as outlined in section 5.
	9. Acknowledgements		9. Acknowledgements
	This document is heavily based on the ongoing work for RADIUS MIPv6		This document is heavily based on the ongoing work for RADIUS MIPv6
	interaction. Hence, credits go to respective authors for their work		interaction. Hence, credits go to respective authors for their work
	with draft-ietf-mip6-radius. Furthermore, the author would like to		with draft-ietf-mip6-radius. Furthermore, the author would like to
	thank the authors of draft-le-aaa-diameter-mobileipv6 (Franck Le,		thank the authors of draft-le-aaa-diameter-mobileipv6 (Franck Le,
	Basavaraj Patil, Charles E. Perkins, Stefano Faccin) for their work		Basavaraj Patil, Charles E. Perkins, Stefano Faccin) for their work
	in context of MIPv6 Diameter interworking. Their work influenced		in context of MIPv6 Diameter interworking. Their work influenced
	this document. Jouni Korhonen would like to thank Academy of Finland		this document. Jouni Korhonen would like to thank Academy of Finland
	skipping to change at page 16, line 9 ¶		skipping to change at page 14, line 47 ¶
	[1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in		[1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
	IPv6", RFC 3775, June 2004.		IPv6", RFC 3775, June 2004.
	[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997.		Levels", BCP 14, RFC 2119, March 1997.
	[3] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible		[3] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
	Authentication Protocol (EAP) Application", RFC 4072,		Authentication Protocol (EAP) Application", RFC 4072,
	August 2005.		August 2005.
	[4] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko,		[4] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P.
	"Diameter Base Protocol", RFC 3588, September 2003.
	[5] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P.
	McCann, "Diameter Mobile IPv4 Application", RFC 4004,		McCann, "Diameter Mobile IPv4 Application", RFC 4004,
	August 2005.		August 2005.
			[5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko,
			"Diameter Base Protocol", RFC 3588, September 2003.
	[6] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter		[6] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter
	Network Access Server Application", RFC 4005, August 2005.		Network Access Server Application", RFC 4005, August 2005.
	10.2. Informative References		10.2. Informative References
	[7] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6		[7] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
	Bootstrapping in Split Scenario", RFC 5026, October 2007.		Bootstrapping in Split Scenario", RFC 5026, October 2007.
	[8] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping		[8] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping
	Mobile IPv6 (MIPv6)", RFC 4640, September 2006.		Mobile IPv6 (MIPv6)", RFC 4640, September 2006.
	[9] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R.		[9] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R.
	Lopez, "AAA Goals for Mobile IPv6",		Lopez, "AAA Goals for Mobile IPv6",
	draft-ietf-mext-aaa-ha-goals-01 (work in progress), May 2008.		draft-ietf-mext-aaa-ha-goals-01 (work in progress), May 2008.
	[10] Manner, J. and M. Kojo, "Mobility Related Terminology",		[10] Manner, J. and M. Kojo, "Mobility Related Terminology",
	RFC 3753, June 2004.		RFC 3753, June 2004.
	[11] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the		[11] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
			Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
			[12] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the
	Integrated Scenario",		Integrated Scenario",
	draft-ietf-mip6-bootstrapping-integrated-dhc-06 (work in		draft-ietf-mip6-bootstrapping-integrated-dhc-06 (work in
	progress), April 2008.		progress), April 2008.
	Authors' Addresses		Authors' Addresses
	Jouni Korhonen		Jouni Korhonen
	TeliaSonera		TeliaSonera
	Teollisuuskatu 13		Teollisuuskatu 13
	Sonera FIN-00051		Sonera FIN-00051
	skipping to change at page 17, line 23 ¶		skipping to change at page 16, line 23 ¶
	Nokia Siemens Networks		Nokia Siemens Networks
	Linnoitustie 6		Linnoitustie 6
	Espoo 02600		Espoo 02600
	Finland		Finland
	Phone: +358 (50) 4871445		Phone: +358 (50) 4871445
	Email: Hannes.Tschofenig@nsn.com		Email: Hannes.Tschofenig@nsn.com
	URI: http://www.tschofenig.priv.at		URI: http://www.tschofenig.priv.at
	Charles E. Perkins		Charles E. Perkins
			WiChorus
	Phone: +1-650-496-4402		Phone: +1-650-496-4402
	Email: charliep@computer.org		Email: charliep@wichorus.com
	Kuntal Chowdhury		Kuntal Chowdhury
	Starent Networks		Starent Networks
	30 International Place		30 International Place
	Tewksbury MA 01876		Tewksbury MA 01876
	US		US
	Phone: +1 214 550 1416		Phone: +1 214 550 1416
	Email: kchowdhury@starentnetworks.com		Email: kchowdhury@starentnetworks.com
	skipping to change at line 799 ¶		skipping to change at page 17, line 44 ¶
	attempt made to obtain a general license or permission for the use of		attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
			Acknowledgment
			Funding for the RFC Editor function is provided by the IETF
			Administrative Support Activity (IASA).
End of changes. 50 change blocks.
	199 lines changed or deleted		132 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/