< draft-lior-radius-prepaid-extensions-19.txt		draft-lior-radius-prepaid-extensions-20.txt >
	Network Working Group A. Lior		Network Working Group A. Lior
	Internet-Draft Bridgewater Systems		Internet-Draft Bridgewater Systems
	Intended status: Informational P. Yegani		Intended status: Informational P. Yegani
	Expires: January 12, 2012 Juniper		Expires: May 3, 2012 Juniper
	K. Chowdhury		K. Chowdhury
	Starent Networks		Starent Networks
	H. Tschofenig		H. Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
	A. Pashalidis		A. Pashalidis
	KUL		KUL
	July 11, 2011		October 31, 2011
	Prepaid Extensions to Remote Authentication Dial-In User Service		Prepaid Extensions to Remote Authentication Dial-In User Service
	(RADIUS)		(RADIUS)
	draft-lior-radius-prepaid-extensions-19.txt		draft-lior-radius-prepaid-extensions-20.txt
	Abstract		Abstract
	This document specifies an extension to the Remote Authentication		This document specifies an extension to the Remote Authentication
	Dial-In User Service (RADIUS) protocol that enables service providers		Dial-In User Service (RADIUS) protocol that enables service providers
	to charge for prepaid services. The supported charging models		to charge for prepaid services. The supported charging models
	supported are volume-based, duration-based, and based on one-time		supported are volume-based, duration-based, and based on one-time
	events.		events.
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	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 January 12, 2012.		This Internet-Draft will expire on May 3, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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
	skipping to change at page 4, line 16 ¶		skipping to change at page 4, line 16 ¶
	This document specifies an extension to the RADIUS protocol that		This document specifies an extension to the RADIUS protocol that
	enables service providers to perform accounting and charging in an		enables service providers to perform accounting and charging in an
	"online" fashion. In particular, they enable the service provider to		"online" fashion. In particular, they enable the service provider to
	(a) ensure that subscriber's remaining funds suffice before the		(a) ensure that subscriber's remaining funds suffice before the
	service is delivered, and		service is delivered, and
	(b) interrupt service provision when the funds are exhausted.		(b) interrupt service provision when the funds are exhausted.
	Note that these capabilities are typically used in scenarios where		These capabilities are typically used in scenarios where the
	the subscriber maintains a prepaid account with the service provider;		subscriber maintains a prepaid account with the service provider;
	hence, this extension is called the "prepaid" extension for RADIUS.		hence, this extension is called the "prepaid" extension for RADIUS.
	The functionality described in this document is often referred as		The functionality described in this document is often referred as
	"online charging" in comparison to "offline charging" support		"online charging" in comparison to "offline charging" support
	provided by RFC 2866 [RFC2866].		provided by RFC 2866 [RFC2866].
			Note that this document does not follow the RADIUS design guidelines
			outlined in RFC 6158 [RFC6158] since this document predates RFC 6158
			and documents existing implementations.
	The extensions were designed with the following goals in mind:		The extensions were designed with the following goals in mind:
	o Make use of existing infrastructure as much as possible (including		o Make use of existing infrastructure as much as possible (including
	enabling the interworking of RADIUS-based and Diameter-based		enabling the interworking of RADIUS-based and Diameter-based
	infrastructures), and thereby limit the amount of necessary		infrastructures), and thereby limit the amount of necessary
	capital expenditures,		capital expenditures,
	o provide the ability to rate service requests in an "online"		o provide the ability to rate service requests in an "online"
	fashion,		fashion,
	skipping to change at page 69, line 5 ¶		skipping to change at page 68, line 8 ¶
	Levkowetz, "RFC 3748: Extensible Authentication Protocol",		Levkowetz, "RFC 3748: Extensible Authentication Protocol",
	June 2004.		June 2004.
	[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, "RFC 4006: Diameter Credit Control Application",		Loughney, "RFC 4006: Diameter Credit Control Application",
	August 2005.		August 2005.
	[RFC4849] Congdon, P., Sanchez, M., and B. Aboba, "RADIUS Filter		[RFC4849] Congdon, P., Sanchez, M., and B. Aboba, "RADIUS Filter
	Rule Attribute", RFC 4849, April 2007.		Rule Attribute", RFC 4849, April 2007.
			[RFC6158] DeKok, A. and G. Weber, "RADIUS Design Guidelines",
			BCP 158, RFC 6158, March 2011.
	Appendix A. Example flows		Appendix A. Example flows
	Note: This section is informative.		Note: This section is informative.
	This section presents certain example flows that involve the RADIUS		This section presents certain example flows that involve the RADIUS
	prepaid extensions. By no means is the intent of this section to		prepaid extensions. By no means is the intent of this section to
	specify or recommend business logic, rating strategies, and		specify or recommend business logic, rating strategies, and
	application-level behaviour. The intent of this section is purely to		application-level behaviour. The intent of this section is purely to
	illustrate some fictive scenarios and the RADIUS prepaid message		illustrate some fictive scenarios and the RADIUS prepaid message
	flows that could be associated with these scenarios. The contents of		flows that could be associated with these scenarios. The contents of
End of changes. 7 change blocks.
	6 lines changed or deleted		13 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/