< draft-ietf-dime-app-design-guide-12.txt		draft-ietf-dime-app-design-guide-13.txt >
	Diameter Maintanence and V. Fajardo, Ed.		Diameter Maintanence and Extensions V. Fajardo
	Extensions (DIME)		(DIME)
	Internet-Draft H. Tschofenig		Internet-Draft H. Tschofenig
	Intended status: Informational Nokia Siemens Networks		Intended status: Informational Nokia Siemens Networks
	Expires: March 5, 2011 L. Morand		Expires: July 14, 2012 L. Morand, Ed.
	Orange Labs		Orange Labs
	September 1, 2010		January 11, 2012
	Diameter Applications Design Guidelines		Diameter Applications Design Guidelines
	draft-ietf-dime-app-design-guide-12.txt		draft-ietf-dime-app-design-guide-13
	Abstract		Abstract
	The Diameter Base protocol provides updated rules on how to extend		The Diameter Base protocol provides facilities for protocol
	Diameter by modifying and/or deriving from existing applications or		extensibility enabling to define new Diameter applications or modify
	creating entirely new applications. This is a companion document to		existing applications. This document is a companion document to the
	the Diameter Base protocol that further explains and clarifies these		Diameter Base protocol that further explains and clarifies the rules
	rules. It is meant as a guidelines document and therefore it does		to extend the Diameter Base protocol. It is meant as a guidelines
	not add, remove or change existing rules.		document and therefore it does not add, remove or change existing
			rules.
			Requirements Language
			The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
			"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
			document are to be interpreted as described in [RFC2119].
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted 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). 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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 March 5, 2011.		This Internet-Draft will expire on July 14, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2012 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5		3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4. Adding a new command . . . . . . . . . . . . . . . . . . . . . 7		4. Adding a new command . . . . . . . . . . . . . . . . . . . . . 8
	5. Deleting a Command . . . . . . . . . . . . . . . . . . . . . . 8		5. Deleting a Command . . . . . . . . . . . . . . . . . . . . . . 9
	6. Reusing Existing Commands . . . . . . . . . . . . . . . . . . 9		6. Reusing Existing Commands . . . . . . . . . . . . . . . . . . 10
	6.1. Adding AVPs to a Command . . . . . . . . . . . . . . . . . 9		6.1. Adding AVPs to a Command . . . . . . . . . . . . . . . . . 10
	6.2. Deleting AVPs from a Command . . . . . . . . . . . . . . . 10		6.2. Deleting AVPs from a Command . . . . . . . . . . . . . . . 11
	7. Reusing Existing AVPs . . . . . . . . . . . . . . . . . . . . 12		7. Reusing Existing AVPs . . . . . . . . . . . . . . . . . . . . 13
	8. Rules for new Applications . . . . . . . . . . . . . . . . . . 13		8. Rules for new Applications . . . . . . . . . . . . . . . . . . 14
	8.1. Use of Application-Id in a Message . . . . . . . . . . . . 13		8.1. Use of Application-Id in a Message . . . . . . . . . . . . 14
	8.2. Application Specific Session State Machine . . . . . . . . 14		8.2. Application Specific Session State Machine . . . . . . . . 15
	9. End-to-End Applications Capabilities Exchange . . . . . . . . 15		9. End-to-End Applications Capabilities Exchange . . . . . . . . 16
	10. Diameter Accounting Support . . . . . . . . . . . . . . . . . 16		10. Diameter Accounting Support . . . . . . . . . . . . . . . . . 17
	11. Generic Diameter Extensions . . . . . . . . . . . . . . . . . 18		11. Generic Diameter Extensions . . . . . . . . . . . . . . . . . 19
	12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20		12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
	13. Security Considerations . . . . . . . . . . . . . . . . . . . 21		13. Security Considerations . . . . . . . . . . . . . . . . . . . 22
	14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22		14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 23
	15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23		15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 24
	16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24		16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25
	16.1. Normative References . . . . . . . . . . . . . . . . . . . 24		16.1. Normative References . . . . . . . . . . . . . . . . . . . 25
	16.2. Informative References . . . . . . . . . . . . . . . . . . 25		16.2. Informative References . . . . . . . . . . . . . . . . . . 26
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
	1. Introduction		1. Introduction
	The Diameter Base protocol document defines rules on how one would		The Diameter Base protocol provides facilities to extend the Diameter
	extend Diameter (see Section 1.2 of [I-D.ietf-dime-rfc3588bis]). In		Base protocol (see Section 1.3 of [I-D.ietf-dime-rfc3588bis]). In
	the context of this document, extending Diameter means one of the		the context of this document, extending Diameter means one of the
	following:		following:
	1. A new functionality is being added to an existing Diameter		1. A new functionality is being added to an existing Diameter
	application without defining a new application.		application without defining a new application.
	2. A new Diameter application is being defined by extending an		2. A new Diameter application is being defined by extending an
	existing application.		existing application.
	3. A completely new application is being defined that has nothing in		3. A completely new application is being defined that has nothing in
	skipping to change at page 24, line 18 ¶		skipping to change at page 25, line 18 ¶
	[I-D.ietf-dime-diameter-qos]		[I-D.ietf-dime-diameter-qos]
	Sun, D., McCann, P., Tschofenig, H., ZOU), T., Doria, A.,		Sun, D., McCann, P., Tschofenig, H., ZOU), T., Doria, A.,
	and G. Zorn, "Diameter Quality of Service Application",		and G. Zorn, "Diameter Quality of Service Application",
	draft-ietf-dime-diameter-qos-15 (work in progress),		draft-ietf-dime-diameter-qos-15 (work in progress),
	March 2010.		March 2010.
	[I-D.ietf-dime-mip6-integrated]		[I-D.ietf-dime-mip6-integrated]
	Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,		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",
	draft-ietf-dime-mip6-integrated-12 (work in progress),		draft-ietf-dime-mip6-integrated-12 (work in progress),
	January 2009.		January 2009.
	[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-17 (work in progress),		draft-ietf-dime-mip6-split-17 (work in progress),
	April 2009.		April 2009.
	[I-D.ietf-dime-qos-attributes]		[I-D.ietf-dime-qos-attributes]
	Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,		Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,
	and A. Lior, "Traffic Classification and Quality of		and A. Lior, "Traffic Classification and Quality of
	Service Attributes for Diameter",		Service Attributes for Diameter",
	draft-ietf-dime-qos-attributes-15 (work in progress),		draft-ietf-dime-qos-attributes-15 (work in progress),
	December 2009.		December 2009.
	[I-D.ietf-dime-rfc3588bis]		[I-D.ietf-dime-rfc3588bis]
	Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,		Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,
	"Diameter Base Protocol", draft-ietf-dime-rfc3588bis-24		"Diameter Base Protocol", draft-ietf-dime-rfc3588bis-29
	(work in progress), August 2010.		(work in progress), August 2011.
			[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
			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.
	[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.		[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
	Loughney, "Diameter Credit-Control Application", RFC 4006,		Loughney, "Diameter Credit-Control Application", RFC 4006,
	August 2005.		August 2005.
	[TS29.228]		[TS29.228]
	3GPP, "IMS Cx and Dx interfaces : signalling flows and		3rd Generation Partnership Project, "3GPP TS 29.228;
	message contents", 3GPP TS 29.228 Version 7.0.0 2006.		Technical Specification Group Core Network and Terminals;
			IP Multimedia (IM) Subsystem Cx and Dx Interfaces;
			Signalling flows and message contents",
			<http://www.3gpp.org/ftp/Specs/html-info/29272.htm>.
	[TS29.229]		[TS29.229]
	3GPP, "IMS Cx and Dx interfaces based on the Diameter		3rd Generation Partnership Project, "3GPP TS 29.229;
	protocol; Protocol details", 3GPP TS 29.229 Version		Technical Specification Group Core Network and Terminals;
	7.0.0 2006.		Cx and Dx interfaces based on the Diameter protocol;
			Protocol details",
			<http://www.3gpp.org/ftp/Specs/html-info/29229.htm>.
	[TS29.328]		[TS29.328]
	3GPP, "IMS Sh interface : signalling flows and message		3rd Generation Partnership Project, "3GPP TS 29.328;
	content", 3GPP TS 29.328 Version 6.8.0 2005.		Technical Specification Group Core Network and Terminals;
			IP Multimedia (IM) Subsystem Sh interface; signalling
			flows and message content",
			<http://www.3gpp.org/ftp/Specs/html-info/29328.htm>.
	[TS29.329]		[TS29.329]
	3GPP, "IMS Sh interface based on the Diameter protocol;		3rd Generation Partnership Project, "3GPP TS 29.329;
	Protocol details", 3GPP TS 29.329 Version 6.6.0 2005.		Technical Specification Group Core Network and Terminals;
			Sh Interface based on the Diameter protocol; Protocol
			details",
			<http://www.3gpp.org/ftp/Specs/html-info/29329.htm>.
	16.2. Informative References		16.2. Informative References
	[I-D.asveren-dime-dupcons]		[I-D.asveren-dime-dupcons]
	Asveren, T., "Diameter Duplicate Detection Cons.",		Asveren, T., "Diameter Duplicate Detection Cons.",
	draft-asveren-dime-dupcons-00 (work in progress),		draft-asveren-dime-dupcons-00 (work in progress),
	August 2006.		August 2006.
	[I-D.calhoun-diameter-res-mgmt]		[I-D.calhoun-diameter-res-mgmt]
	Calhoun, P., "Diameter Resource Management Extensions",		Calhoun, P., "Diameter Resource Management Extensions",
	draft-calhoun-diameter-res-mgmt-08.txt (work in progress),		draft-calhoun-diameter-res-mgmt-08.txt (work in progress),
	March 2001.		March 2001.
	Authors' Addresses		Authors' Addresses
	Victor Fajardo (editor)		Victor Fajardo
	Email: vf0213@gmail.com		Email: vf0213@gmail.com
	Hannes Tschofenig		Hannes Tschofenig
	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@gmx.net		Email: Hannes.Tschofenig@gmx.net
	URI: http://www.tschofenig.priv.at		URI: http://www.tschofenig.priv.at
	Lionel Morand		Lionel Morand (editor)
	Orange Labs		Orange Labs
	Phone: +33 1 4529 6257		Phone: +33 1 4529 6257
	Email: lionel.morand@orange-ftgroup.com		Email: lionel.morand@orange-ftgroup.com
End of changes. 17 change blocks.
	52 lines changed or deleted		73 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/