< draft-ietf-dime-group-signaling-08.txt		draft-ietf-dime-group-signaling-09.txt >
	Diameter Maintenance and Extensions (DIME) M. Jones		Diameter Maintenance and Extensions (DIME) M. Jones
	Internet-Draft		Internet-Draft
	Intended status: Standards Track M. Liebsch		Intended status: Standards Track M. Liebsch
	Expires: September 14, 2017		Expires: March 19, 2018
	L. Morand		L. Morand
	March 13, 2017		September 15, 2017
	Diameter Group Signaling		Diameter Group Signaling
	draft-ietf-dime-group-signaling-08.txt		draft-ietf-dime-group-signaling-09.txt
	Abstract		Abstract
	In large network deployments, a single Diameter node can support over		In large network deployments, a single Diameter node can support over
	a million concurrent Diameter sessions. Recent use cases have		a million concurrent Diameter sessions. Recent use cases have
	revealed the need for Diameter nodes to apply the same operation to a		revealed the need for Diameter nodes to apply the same operation to a
	large group of Diameter sessions concurrently. The Diameter base		large group of Diameter sessions concurrently. The Diameter base
	protocol commands operate on a single session so these use cases		protocol commands operate on a single session so these use cases
	could result in many thousands of command exchanges to enforce the		could result in many thousands of command exchanges to enforce the
	same operation on each session in the group. In order to reduce		same operation on each session in the group. In order to reduce
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	extensions to achieve this signaling optimization.		extensions to achieve this signaling optimization.
	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 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 September 14, 2017.		This Internet-Draft will expire on March 19, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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		(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
	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 . . . . . . . . . . . . . . . . . . . . . . . . 3
	skipping to change at page 21, line 28 ¶		skipping to change at page 21, line 28 ¶
	McMurry for their valuable comments to early versions of this draft.		McMurry for their valuable comments to early versions of this draft.
	Furthermore, authors thank Steve Donovan and Mark Bales for the		Furthermore, authors thank Steve Donovan and Mark Bales for the
	thorough review and comments on advanced versions of the WG document,		thorough review and comments on advanced versions of the WG document,
	which helped a lot to improve this specification.		which helped a lot to improve this specification.
	12. Normative References		12. Normative References
	[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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[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,
	DOI 10.17487/RFC4005, August 2005,		DOI 10.17487/RFC4005, August 2005,
	<http://www.rfc-editor.org/info/rfc4005>.		<https://www.rfc-editor.org/info/rfc4005>.
	[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,		[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
	Ed., "Diameter Base Protocol", RFC 6733,		Ed., "Diameter Base Protocol", RFC 6733,
	DOI 10.17487/RFC6733, October 2012,		DOI 10.17487/RFC6733, October 2012,
	<http://www.rfc-editor.org/info/rfc6733>.		<https://www.rfc-editor.org/info/rfc6733>.
	Appendix A. Session Management -- Exemplary Session State Machine		Appendix A. Session Management -- Exemplary Session State Machine
	A.1. Use of groups for the Authorization Session State Machine		A.1. Use of groups for the Authorization Session State Machine
	Section 8.1 in [RFC6733] defines a set of finite state machines,		Section 8.1 in [RFC6733] defines a set of finite state machines,
	representing the life cycle of Diameter sessions, and which MUST be		representing the life cycle of Diameter sessions, and which MUST be
	observed by all Diameter implementations that make use of the		observed by all Diameter implementations that make use of the
	authentication and/or authorization portion of a Diameter		authentication and/or authorization portion of a Diameter
	application. This section defines, as example, additional state		application. This section defines, as example, additional state
End of changes. 9 change blocks.
	9 lines changed or deleted		9 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/