draft-ietf-dime-pmip6-01.txt		draft-ietf-dime-pmip6-02.txt
	Diameter Maintenance and J. Korhonen, Ed.		Diameter Maintenance and J. Korhonen, Ed.
	Extensions (DIME) Nokia Siemens Network		Extensions (DIME) Nokia Siemens Network
	Internet-Draft J. Bournelle		Internet-Draft J. Bournelle
	Intended status: Standards Track Orange Labs		Intended status: Standards Track Orange Labs
	Expires: September 7, 2009 K. Chowdhury		Expires: October 18, 2009 K. Chowdhury
	Starent Networks		Starent Networks
	A. Muhanna		A. Muhanna
	Nortel		Nortel
	U. Meyer		U. Meyer
	RWTH Aachen		RWTH Aachen
	March 6, 2009		April 16, 2009
	Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility		Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility
	Anchor Interaction with Diameter Server		Anchor Interaction with Diameter Server
	draft-ietf-dime-pmip6-01.txt		draft-ietf-dime-pmip6-02.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 40		skipping to change at page 1, line 40
	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 September 7, 2009.		This Internet-Draft will expire on October 18, 2009.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 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 in effect on the date of		Provisions Relating to IETF Documents in effect on the date of
	publication of this document (http://trustee.ietf.org/license-info).		publication of this document (http://trustee.ietf.org/license-info).
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document.		and restrictions with respect to this document.
	Abstract		Abstract
	This specification defines the Diameter support for the Proxy Mobile		This specification defines the Diameter support for the Proxy Mobile
	IPv6 and the corresponding mobility service session setup. The		IPv6 and the corresponding mobility service session setup. The
	policy information needed by the Proxy Mobile IPv6 is defined in		policy information needed by the Proxy Mobile IPv6 is defined in
	mobile node's policy profile, which could be downloaded from the		mobile node's policy profile, which could be downloaded from the
	Diameter server to the Mobile Access Gateway once the mobile node		Diameter server to the Mobile Access Gateway once the mobile node
	skipping to change at page 3, line 32		skipping to change at page 3, line 32
	5.2. LMA-to-HAAA Interface . . . . . . . . . . . . . . . . . . 11		5.2. LMA-to-HAAA Interface . . . . . . . . . . . . . . . . . . 11
	5.2.1. Authorization of the Proxy Binding Update . . . . . . 12		5.2.1. Authorization of the Proxy Binding Update . . . . . . 12
	6. Proxy Mobile IPv6 Session Management . . . . . . . . . . . . . 12		6. Proxy Mobile IPv6 Session Management . . . . . . . . . . . . . 12
	6.1. Session-Termination-Request . . . . . . . . . . . . . . . 13		6.1. Session-Termination-Request . . . . . . . . . . . . . . . 13
	6.2. Session-Termination-Answer . . . . . . . . . . . . . . . . 13		6.2. Session-Termination-Answer . . . . . . . . . . . . . . . . 13
	6.3. Abort-Session-Request . . . . . . . . . . . . . . . . . . 13		6.3. Abort-Session-Request . . . . . . . . . . . . . . . . . . 13
	6.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . . . 13		6.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . . . 13
	7. Attribute Value Pair Occurrence Tables . . . . . . . . . . . . 13		7. Attribute Value Pair Occurrence Tables . . . . . . . . . . . . 13
	7.1. MAG-to-HAAA Interface . . . . . . . . . . . . . . . . . . 14		7.1. MAG-to-HAAA Interface . . . . . . . . . . . . . . . . . . 14
	7.2. LMA-to-HAAA Interface . . . . . . . . . . . . . . . . . . 14		7.2. LMA-to-HAAA Interface . . . . . . . . . . . . . . . . . . 14
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14		8. Example Signaling Flows . . . . . . . . . . . . . . . . . . . 14
	8.1. Attribute Value Pair Codes . . . . . . . . . . . . . . . . 14		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
	8.2. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 15		9.1. Attribute Value Pair Codes . . . . . . . . . . . . . . . . 16
	8.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 15		9.2. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 16
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 15		9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 16
	10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15		10. Security Considerations . . . . . . . . . . . . . . . . . . . 16
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16		11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
	11.1. Normative References . . . . . . . . . . . . . . . . . . . 16		12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	11.2. Informative References . . . . . . . . . . . . . . . . . . 16		12.1. Normative References . . . . . . . . . . . . . . . . . . . 17
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17		12.2. Informative References . . . . . . . . . . . . . . . . . . 17
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
	1. Introduction		1. Introduction
	In the Proxy Mobile IPv6 (PMIPv6) protocol [RFC5213] and IPv4 support		In the Proxy Mobile IPv6 (PMIPv6) protocol [RFC5213] and IPv4 support
	for Proxy Mobile IPv6 [I-D.ietf-netlmm-pmip6-ipv4-support] a Mobile		for Proxy Mobile IPv6 [I-D.ietf-netlmm-pmip6-ipv4-support] a Mobile
	Access Gateway (MAG) performs a proxy registration with a Local		Access Gateway (MAG) performs a proxy registration with a Local
	Mobility Anchor (LMA) on behalf of the mobile node (MN). In order to		Mobility Anchor (LMA) on behalf of the mobile node (MN). In order to
	perform the proxy registration the MAG needs the IP address of the		perform the proxy registration the MAG needs the IP address of the
	LMA, possibly MN's Home Network Prefix(es) (MN-HNP), MN's IPv4 home		LMA, possibly MN's Home Network Prefix(es) (MN-HNP), MN's IPv4 home
	address (IPv4-MN-HoA), DHCP server address and other PMIPv6 specific		address (IPv4-MN-HoA), DHCP server address and other PMIPv6 specific
	skipping to change at page 14, line 43		skipping to change at page 14, line 43
	MIP6-Agent-Info | 0-1 | 0-1 |		MIP6-Agent-Info | 0-1 | 0-1 |
	MIP6-Feature-Vector | 0-1 | 0-1 |		MIP6-Feature-Vector | 0-1 | 0-1 |
	Calling-Station-Id | 0-1 | 0 |		Calling-Station-Id | 0-1 | 0 |
	Service-Selection | 0-1 | 0-1 |		Service-Selection | 0-1 | 0-1 |
	User-Name | 0-1 | 0-1 |		User-Name | 0-1 | 0-1 |
	+-------+-------+		+-------+-------+
	Figure 3: LMA-to-HAAA Interface Generic Diameter Request and Answer		Figure 3: LMA-to-HAAA Interface Generic Diameter Request and Answer
	Commands AVPs		Commands AVPs
	8. IANA Considerations		8. Example Signaling Flows
	8.1. Attribute Value Pair Codes		Figure 4 shows a signaling flow example during PMIPv6 bootstrapping
			using the AAA interactions defined in this specification. In step
			(1) of this example, the MN is authenticated to PMIPv6 domain using
			EAP-based authentication. The MAG to the HAAA signaling uses the
			Diameter EAP Application. During step (2), the LMA uses Diameter
			NASREQ application to authorize the MN with the HAAA server.
			The MAG-to-HAAA AVPs, as listed in Section 7.1 are used during step
			(1). These AVPs are included only in the DER message which starts
			the EAP exchange and in the corresponding DEA message which
			successfully completes this EAP exchange. The LMA-to-HAAA AVPs, as
			listed in Section 7.2, are used during step (2). Step (2) is used to
			authorize the MN request for the mobility service and update the HAAA
			server with the assigned LMA information. In addition, this step may
			be used to dynamically assist in the assignment of the MN-HNP.
			MN MAG/NAS LMA HAAA
			| | | |
			| L2 attach | | |
			|-------------------->| | |
			| EAP/req-identity | | |
			|<--------------------| | |
			| EAP/res-identity | DER + MAG-to-HAAA AVPs | s
			|-------------------->|---------------------------------------->| t
			| EAP/req #1 | DEA (EAP request #1) | e
			|<--------------------|<----------------------------------------| p
			| EAP/res #2 | DER (EAP response #2) |
			|-------------------->|---------------------------------------->| 1
			: : : :
			: : : :
			| EAP/res #N | DER (EAP response #N) |
			|-------------------->|---------------------------------------->|
			| EAP/success | DEA (EAP success) + MAG-to-HAAA AVPs |
			|<--------------------|<----------------------------------------|
			: : : :
			: : : :
			| | PMIPv6 PBU | AAR + | s
			| |------------------->| LMA-to-HAAA AVPs | t
			| | |------------------->| e
			| | | AAA + | p
			| | | LMA-to-HAAA AVPs |
			| | PMIPv6 PBA |<-------------------| 2
			| RA |<-------------------| |
			|<--------------------| | |
			: : : :
			: : : :
			| IP connectivity | PMIPv6 tunnel up | |
			|---------------------|====================| |
			| | | |
			Figure 4: MAG and LMA Signaling Interaction with AAA server during
			PMIPv6 bootstrapping
			9. IANA Considerations
			9.1. Attribute Value Pair Codes
	This specification defines the following new AVPs:		This specification defines the following new AVPs:
	PMIP6-DHCP-Server-Address is set to TBD1		PMIP6-DHCP-Server-Address is set to TBD1
	PMIP6-IPv4-Home-Address is set to TBD2		PMIP6-IPv4-Home-Address is set to TBD2
	Mobile-Node-Identifier is set to TBD3		Mobile-Node-Identifier is set to TBD3
	Service-Configuration is set to TBD4		Service-Configuration is set to TBD4
	8.2. Namespaces		9.2. Namespaces
	This specification defines new values to the Mobility Capability		This specification defines new values to the Mobility Capability
	registry (see [RFC5447]) for use with the MIP6-Feature-Vector AVP:		registry (see [RFC5447]) for use with the MIP6-Feature-Vector AVP:
	Token | Value | Description		Token | Value | Description
	---------------------------------+----------------------+------------		---------------------------------+----------------------+------------
	PMIP6_SUPPORTED | 0x0000010000000000 | [RFC TBD]		PMIP6_SUPPORTED | 0x0000010000000000 | [RFC TBD]
	IP4_HOA_SUPPORTED | 0x0000020000000000 | [RFC TBD]		IP4_HOA_SUPPORTED | 0x0000020000000000 | [RFC TBD]
	LOCAL_MAG_ROUTING_SUPPORTED | 0x0000040000000000 | [RFC TBD]		LOCAL_MAG_ROUTING_SUPPORTED | 0x0000040000000000 | [RFC TBD]
	8.3. Result-Code AVP Values		9.3. Result-Code AVP Values
	This specification requests IANA to allocate a new value to the		This specification requests IANA to allocate a new value to the
	Result-Code AVP (AVP Code 268) address space within the Permanent		Result-Code AVP (AVP Code 268) address space within the Permanent
	Failures category (5xxx) defined in [RFC3588]:		Failures category (5xxx) defined in [RFC3588]:
	DIAMETER_PMIP6_AUTHORIZATION_FAILED is set to TBD5		DIAMETER_PMIP6_AUTHORIZATION_FAILED is set to TBD5
	9. Security Considerations		10. Security Considerations
	The security considerations of the Diameter Base protocol [RFC3588],		The security considerations of the Diameter Base protocol [RFC3588],
	Diameter EAP application [RFC4072], Diameter NASREQ application		Diameter EAP application [RFC4072], Diameter NASREQ application
	[RFC4005] and Diameter Mobile IPv6 integrated scenario bootstrapping		[RFC4005] and Diameter Mobile IPv6 integrated scenario bootstrapping
	[RFC5447] are applicable to this document.		[RFC5447] are applicable to this document.
	In general, the Diameter messages may be transported between the HA		In general, the Diameter messages may be transported between the HA
	and the Diameter server via one or more AAA brokers or Diameter		and the Diameter server via one or more AAA brokers or Diameter
	agents. In this case the HA to the Diameter server AAA communication		agents. In this case the HA to the Diameter server AAA communication
	rely on the security properties of the intermediate AAA brokers and		rely on the security properties of the intermediate AAA brokers and
	Diameter agents (such as proxies).		Diameter agents (such as proxies).
	10. Acknowledgements		11. Acknowledgements
	Jouni Korhonen would like to thank the TEKES GIGA program MERCoNe-		Jouni Korhonen would like to thank the TEKES GIGA program MERCoNe-
	project for providing funding to work on this document while he was		project for providing funding to work on this document while he was
	with TeliaSonera.		with TeliaSonera.
	11. References		12. References
	11.1. Normative References		12.1. Normative References
	[I-D.ietf-netlmm-pmip6-ipv4-support]		[I-D.ietf-netlmm-pmip6-ipv4-support]
	Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy		Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
	Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-09		Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-11
	(work in progress), January 2009.		(work in progress), April 2009.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.		[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
	Arkko, "Diameter Base Protocol", RFC 3588, September 2003.		Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
	[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,		[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
	"Diameter Network Access Server Application", RFC 4005,		"Diameter Network Access Server Application", RFC 4005,
	August 2005.		August 2005.
	skipping to change at page 16, line 37		skipping to change at page 17, line 45
	Network Access Identifier", RFC 4282, December 2005.		Network Access Identifier", RFC 4282, December 2005.
	[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,		[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
	and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.		and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
	[RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,		[RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
	and K. Chowdhury, "Diameter Mobile IPv6: Support for		and K. Chowdhury, "Diameter Mobile IPv6: Support for
	Network Access Server to Diameter Server Interaction",		Network Access Server to Diameter Server Interaction",
	RFC 5447, February 2009.		RFC 5447, February 2009.
	11.2. Informative References		12.2. Informative References
	[I-D.ietf-dime-mip6-split]		[I-D.ietf-dime-mip6-split]
	Korhonen, J., Tschofenig, H., Bournelle, J., Giaretta, G.,		Korhonen, J., Tschofenig, H., Bournelle, J., Giaretta, G.,
	and M. Nakhjiri, "Diameter Mobile IPv6: Support for Home		and M. Nakhjiri, "Diameter Mobile IPv6: Support for Home
	Agent to Diameter Server Interaction",		Agent to Diameter Server Interaction",
	draft-ietf-dime-mip6-split-16 (work in progress),		draft-ietf-dime-mip6-split-16 (work in progress),
	December 2008.		December 2008.
	[I-D.ietf-mext-binding-revocation]		[I-D.ietf-mext-binding-revocation]
	Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K.,		Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K.,
	and P. Yegani, "Binding Revocation for IPv6 Mobility",		and P. Yegani, "Binding Revocation for IPv6 Mobility",
	draft-ietf-mext-binding-revocation-03 (work in progress),		draft-ietf-mext-binding-revocation-05 (work in progress),
	January 2009.		March 2009.
	[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.		[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
	Levkowetz, "Extensible Authentication Protocol (EAP)",		Levkowetz, "Extensible Authentication Protocol (EAP)",
	RFC 3748, June 2004.		RFC 3748, June 2004.
	[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support		[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
	in IPv6", RFC 3775, June 2004.		in IPv6", RFC 3775, June 2004.
	[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.		[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
	Chowdhury, "Mobile Node Identifier Option for Mobile IPv6		Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
	(MIPv6)", RFC 4283, November 2005.		(MIPv6)", RFC 4283, November 2005.
End of changes. 18 change blocks.
	28 lines changed or deleted		84 lines changed or added
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/