< draft-zorn-radius-logoff-10.txt		draft-zorn-radius-logoff-11.txt >
	Network Working Group G. Zorn		Network Working Group G. Zorn
	Internet-Draft Netcube Technologies		Internet-Draft Aruba Networks
	Updates: 2865 3576 A. Lior		Updates: 2865 5176 A. Lior
	(if approved) Bridgewater Systems		(if approved) Bridgewater Systems
	Intended status: Informational November 11, 2007		Intended status: Informational February 21, 2008
	Expires: May 14, 2008		Expires: August 24, 2008
	User Session Tracking in RADIUS		User Session Tracking in RADIUS
	draft-zorn-radius-logoff-10.txt		draft-zorn-radius-logoff-11.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 36 ¶		skipping to change at page 1, line 36 ¶
	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 May 14, 2008.		This Internet-Draft will expire on August 24, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	This document defines a set of new messages and attributes designed		This document defines a set of new messages and attributes designed
	to allow RADIUS servers to cleanly track user sessions.		to allow RADIUS servers to cleanly track user sessions.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Specification of Requirements . . . . . . . . . . . . . . . . 3		2. Specification of Requirements . . . . . . . . . . . . . . . . 3
	skipping to change at page 9, line 35 ¶		skipping to change at page 9, line 35 ¶
	Notification packet. The value of the Attribute in both messages		Notification packet. The value of the Attribute in both messages
	MUST be the same.		MUST be the same.
	The client MAY include this Attribute in the Access-Request packet		The client MAY include this Attribute in the Access-Request packet
	as a hint to the server regarding the value to be used in		as a hint to the server regarding the value to be used in
	subsequent messages; however, the server is not required to honor		subsequent messages; however, the server is not required to honor
	the hint.		the hint.
	Because the Session-Id Attribute completely identifies the session		Because the Session-Id Attribute completely identifies the session
	in question, it MAY also be used as a replacement for the session		in question, it MAY also be used as a replacement for the session
	identication attributes discussed in [RFC3576].		identication attributes discussed in [RFC5176].
	The Identifier field of the Session-Id Attribute SHOULD contain		The Identifier field of the Session-Id Attribute SHOULD contain
	UTF-8 encoded 10646 characters [RFC3629].		UTF-8 encoded 10646 characters [RFC3629].
	A summary of the Session-Id attribute format is shown below. The		A summary of the Session-Id attribute format is shown below. The
	fields are transmitted from left to right.		fields are transmitted from left to right.
	0 1 2		0 1 2
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 12, line 7 ¶		skipping to change at page 12, line 7 ¶
	Notification-Type is "Start") or completed (if the Notification-Type		Notification-Type is "Start") or completed (if the Notification-Type
	is "Stop" when they had not. If the server was limiting the number		is "Stop" when they had not. If the server was limiting the number
	of simultaneous sessions, this could enable one or more users to		of simultaneous sessions, this could enable one or more users to
	exceed their session quota and possibly lead to service being denied		exceed their session quota and possibly lead to service being denied
	to legitimate users.		to legitimate users.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[ERRMSG] Zorn, G., "RADIUS Error Messages",		[ERRMSG] Zorn, G., "RADIUS Error Messages",
	draft-zorn-radius-err-msg-07.txt (work in progress),		draft-zorn-radius-err-msg-09.txt (work in progress),
	April 2007.		February 2008.
	[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,		[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
	August 1980.		August 1980.
	[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.
	[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,		[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
	"Remote Authentication Dial In User Service (RADIUS)",		"Remote Authentication Dial In User Service (RADIUS)",
	RFC 2865, June 2000.		RFC 2865, June 2000.
	[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS		[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
	Extensions", RFC 2869, June 2000.		Extensions", RFC 2869, June 2000.
	[RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote		[RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote
	Authentication Dial In User Service)", RFC 3575,		Authentication Dial In User Service)", RFC 3575,
	July 2003.		July 2003.
	[RFC3576] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
	Aboba, "Dynamic Authorization Extensions to Remote
	Authentication Dial In User Service (RADIUS)", RFC 3576,
	July 2003.
	[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO		[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
	10646", STD 63, RFC 3629, November 2003.		10646", STD 63, RFC 3629, November 2003.
			[RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
			Aboba, "Dynamic Authorization Extensions to Remote
			Authentication Dial In User Service (RADIUS)", RFC 5176,
			January 2008.
	8.2. Informative References		8.2. Informative References
	[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.		[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.
	Authors' Addresses		Authors' Addresses
	Glen Zorn		Glen Zorn
	Netcube Technologies		Aruba Networks
	1310 East Thomas Street #306		1322 Crossman Avenue
	Seattle, WA 98102		Sunnyvale, CA 94089-1113
	US		USA
	Phone: +1 (206) 377-9035		Email: gwz@arubanetworks.com
	Email: gwz@netcube.com
	Avi Lior		Avi Lior
	Bridgewater Systems		Bridgewater Systems
	303 Terry Fox Drive		303 Terry Fox Drive
	Ottawa, ON K2K 3J1		Ottawa, ON K2K 3J1
	Canada		Canada
	Phone: +1 (613) 591-6655		Phone: +1 (613) 591-6655
	Email: avi@bridgewatersystems.com		Email: avi@bridgewatersystems.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
End of changes. 12 change blocks.
	22 lines changed or deleted		21 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/