< draft-korhonen-dime-nai-routing-01.txt		draft-korhonen-dime-nai-routing-02.txt >
	Diameter Maintenance and J. Korhonen (ed.)		Diameter Maintenance and J. Korhonen (ed.)
	Extensions (DIME) TeliaSonera		Extensions (DIME) TeliaSonera
	Internet-Draft M. Jones		Internet-Draft M. Jones
	Intended status: Standards Track Bridgewater Systems		Intended status: Standards Track Bridgewater Systems
	Expires: April 21, 2009 L. Morand		Expires: April 30, 2009 L. Morand
	Orange Labs		Orange Labs
	T. Tsou		T. Tsou
	Huawei		Huawei
	October 18, 2008		October 27, 2008
	Diameter User-Name and Realm Based Request Routing Clarifications		Diameter User-Name and Realm Based Request Routing Clarifications
	draft-korhonen-dime-nai-routing-01.txt		draft-korhonen-dime-nai-routing-02.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 39 ¶		skipping to change at page 1, line 39 ¶
	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 April 21, 2009.		This Internet-Draft will expire on April 30, 2009.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2008).		Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	This specification clarifies the Diameter realm based request		This specification clarifies the Diameter realm based request
	routing. We focus on the case where a Network Access Identifier in		routing. We focus on the case where a Network Access Identifier in
	the User-Name AVP is used to populate the Destination-Realm AVP and		the User-Name AVP is used to populate the Destination-Realm AVP and
	skipping to change at page 2, line 19 ¶		skipping to change at page 2, line 19 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3		2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
	3. Problem Overview . . . . . . . . . . . . . . . . . . . . . . . 4		3. Problem Overview . . . . . . . . . . . . . . . . . . . . . . . 4
	4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 6		4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 6
	4.1. Interpretation of Decorated NAIs . . . . . . . . . . . . . 6		4.1. Interpretation of Decorated NAIs . . . . . . . . . . . . . 6
	4.2. Enhanced Request Routing Solution . . . . . . . . . . . . 6		4.2. Enhanced Request Routing Solution . . . . . . . . . . . . 6
	4.3. Backwards Compatibility Considerations . . . . . . . . . . 7		4.3. Backwards Compatibility Considerations . . . . . . . . . . 7
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 8		6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	8.1. Normative References . . . . . . . . . . . . . . . . . . . 8		8.1. Normative References . . . . . . . . . . . . . . . . . . . 8
	8.2. Informative References . . . . . . . . . . . . . . . . . . 8		8.2. Informative References . . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
	Intellectual Property and Copyright Statements . . . . . . . . . . 11		Intellectual Property and Copyright Statements . . . . . . . . . . 11
	1. Introduction		1. Introduction
	This specification clarifies the Diameter realm based request routing		This specification clarifies the Diameter realm based request routing
	defined in RFC 3588 [1]. We focus on the case where the Network		defined in RFC 3588 [1]. We focus on the case where the Network
	Access Identifier (NAI) [2] in the User-Name AVP is used to populate		Access Identifier (NAI) [2] in the User-Name AVP is used to populate
	the Destination-Realm AVP and the NAI contains more than one realm.		the Destination-Realm AVP and the NAI contains more than one realm.
	This particular case is possible when the NAI decoration is used to		This particular case is possible when the NAI decoration is used to
	skipping to change at page 6, line 15 ¶		skipping to change at page 6, line 15 ¶
	o Updating both Destination-Realm and User-Name AVPs based on the		o Updating both Destination-Realm and User-Name AVPs based on the
	Decorated NAI extracted from the User-Name AVP. The update would		Decorated NAI extracted from the User-Name AVP. The update would
	be done by intermediating Diameter agents that participate to		be done by intermediating Diameter agents that participate to
	realm based request routing. Specifically, this would concern		realm based request routing. Specifically, this would concern
	Diameter proxies.		Diameter proxies.
	o How Diameter agents could implement the handling of the NAI		o How Diameter agents could implement the handling of the NAI
	Decoration based routing enforcement in a way that is still		Decoration based routing enforcement in a way that is still
	backwards compatible with RFC 3588.		backwards compatible with RFC 3588.
			RFC 5113 [11] Section 2.3 also discusses NAI decoration related
			issues with EAP [12] in general.
	4. Solution Overview		4. Solution Overview
	This specification defines a solution for Diameter realm based		This specification defines a solution for Diameter realm based
	request routing with routing enforcement using the User-Name AVP NAI		request routing with routing enforcement using the User-Name AVP NAI
	Decoration. Diameter proxy agent implementations can claim		Decoration. Diameter proxy agent implementations can claim
	compliance using the solution described in this specification.		compliance using the solution described in this specification.
	4.1. Interpretation of Decorated NAIs		4.1. Interpretation of Decorated NAIs
	Implementations compliant to this specification MUST have an uniform		Implementations compliant to this specification MUST have an uniform
	skipping to change at page 9, line 25 ¶		skipping to change at page 9, line 32 ¶
	[8] 3GPP, "Numbering, addressing and identification", 3GPP		[8] 3GPP, "Numbering, addressing and identification", 3GPP
	TS 23.003 3.15.0, October 2006.		TS 23.003 3.15.0, October 2006.
	[9] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter		[9] 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] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible		[10] 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.
			[11] Arkko, J., Aboba, B., Korhonen, J., and F. Bari, "Network
			Discovery and Selection Problem", RFC 5113, January 2008.
			[12] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
			Levkowetz, "Extensible Authentication Protocol (EAP)",
			RFC 3748, June 2004.
	Authors' Addresses		Authors' Addresses
	Jouni Korhonen		Jouni Korhonen
	TeliaSonera		TeliaSonera
	Teollisuuskatu 15
	Sonera FIN-00051
	Finland
	Email: jouni.nospam@gmail.com		Email: jouni.nospam@gmail.com
	Mark Jones		Mark Jones
	Bridgewater Systems		Bridgewater Systems
	303 Terry Fox Drive		303 Terry Fox Drive
	Ottawa, Ontario K2K 3J1		Ottawa, Ontario K2K 3J1
	Canada		Canada
	Email: Mark.Jones@bridgewatersystems.com		Email: Mark.Jones@bridgewatersystems.com
	Lionel Morand		Lionel Morand
	Orange Labs		Orange Labs
	38-40 rue du general Leclerc		38-40 rue du general Leclerc
	Issy-moulineaux Cedex 9, 92794		Issy-moulineaux Cedex 9, 92794
	France		France
	Email: Lionel.morand@orange-ftgroup.com		Email: Lionel.morand@orange-ftgroup.com
	Tina Tsou		Tina Tsou
	Huawei		Huawei
End of changes. 11 change blocks.
	10 lines changed or deleted		17 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/