draft-ietf-radext-ip-port-radius-ext-05.txt		draft-ietf-radext-ip-port-radius-ext-06.txt
	Network Working Group D. Cheng		Network Working Group D. Cheng
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Standards Track J. Korhonen		Intended status: Standards Track J. Korhonen
	Expires: October 25, 2015 Broadcom Corporation		Expires: April 21, 2016 Broadcom Corporation
	M. Boucadair		M. Boucadair
	France Telecom		France Telecom
	S. Sivakumar		S. Sivakumar
	Cisco Systems		Cisco Systems
	April 23, 2015		October 19, 2015
	RADIUS Extensions for IP Port Configuration and Reporting		RADIUS Extensions for IP Port Configuration and Reporting
	draft-ietf-radext-ip-port-radius-ext-05		draft-ietf-radext-ip-port-radius-ext-06
	Abstract		Abstract
	This document defines three new RADIUS attributes. For devices that		This document defines three new RADIUS attributes. For devices that
	implementing IP port ranges, these attributes are used to communicate		implementing IP port ranges, these attributes are used to communicate
	with a RADIUS server in order to configure and report TCP/UDP ports		with a RADIUS server in order to configure and report TCP/UDP ports
	and ICMP identifiers, as well as mapping behavior for specific hosts.		and ICMP identifiers, as well as mapping behavior for specific hosts.
	This mechanism can be used in various deployment scenarios such as		This mechanism can be used in various deployment scenarios such as
	CGN (Carrier Grade NAT), NAT64, Provider WLAN Gateway, etc.		CGN (Carrier Grade NAT), NAT64, Provider WLAN Gateway, etc.
	skipping to change at page 1, line 46		skipping to change at page 1, line 46
	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 October 25, 2015.		This Internet-Draft will expire on April 21, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 33, line 43		skipping to change at page 33, line 43
	Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful		Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful
	comments and suggestions.		comments and suggestions.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[IPFIX] IANA, "IP Flow Information Export (IPFIX) Entities",		[IPFIX] IANA, "IP Flow Information Export (IPFIX) Entities",
	<http://www.iana.org/assignments/ipfix/ipfix.xhtml>.		<http://www.iana.org/assignments/ipfix/ipfix.xhtml>.
	[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and		[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
	E. Lear, "Address Allocation for Private Internets", BCP		and E. Lear, "Address Allocation for Private Internets",
	5, RFC 1918, February 1996.		BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996,
			<http://www.rfc-editor.org/info/rfc1918>.
	[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,
			DOI 10.17487/RFC2119, March 1997,
			<http://www.rfc-editor.org/info/rfc2119>.
	[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,		[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
	June 1999.		DOI 10.17487/RFC2629, June 1999,
			<http://www.rfc-editor.org/info/rfc2629>.
	[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)", RFC		"Remote Authentication Dial In User Service (RADIUS)",
	2865, June 2000.		RFC 2865, DOI 10.17487/RFC2865, June 2000,
			<http://www.rfc-editor.org/info/rfc2865>.
	[RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.		[RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
	Aboba, "Dynamic Authorization Extensions to Remote		Aboba, "Dynamic Authorization Extensions to Remote
	Authentication Dial In User Service (RADIUS)", RFC 5176,		Authentication Dial In User Service (RADIUS)", RFC 5176,
	January 2008.		DOI 10.17487/RFC5176, January 2008,
			<http://www.rfc-editor.org/info/rfc5176>.
	[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User		[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User
	Service (RADIUS) Protocol Extensions", RFC 6929, April		Service (RADIUS) Protocol Extensions", RFC 6929,
	2013.		DOI 10.17487/RFC6929, April 2013,
			<http://www.rfc-editor.org/info/rfc6929>.
	[RFC7012] Claise, B. and B. Trammell, "Information Model for IP Flow		[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model
	Information Export (IPFIX)", RFC 7012, September 2013.		for IP Flow Information Export (IPFIX)", RFC 7012,
			DOI 10.17487/RFC7012, September 2013,
			<http://www.rfc-editor.org/info/rfc7012>.
	[TR-146] Broadband Forum, "TR-146: Subscriber Sessions",		[TR-146] Broadband Forum, "TR-146: Subscriber Sessions",
	<http://www.broadband-forum.org/technical/download/		<http://www.broadband-forum.org/technical/download/
	TR-146.pdf>.		TR-146.pdf>.
	9.2. Informative References		9.2. Informative References
	[I-D.gundavelli-v6ops-community-wifi-svcs]		[I-D.gundavelli-v6ops-community-wifi-svcs]
	Gundavelli, S., Grayson, M., Seite, P., and Y. Lee,		Gundavelli, S., Grayson, M., Seite, P., and Y. Lee,
	"Service Provider Wi-Fi Services Over Residential		"Service Provider Wi-Fi Services Over Residential
	Architectures", draft-gundavelli-v6ops-community-wifi-		Architectures", draft-gundavelli-v6ops-community-wifi-
	svcs-06 (work in progress), April 2013.		svcs-06 (work in progress), April 2013.
	[I-D.ietf-softwire-lw4over6]		[I-D.ietf-softwire-lw4over6]
	Cui, Y., Qiong, Q., Boucadair, M., Tsou, T., Lee, Y., and		Cui, Y., Qiong, Q., Boucadair, M., Tsou, T., Lee, Y., and
	I. Farrer, "Lightweight 4over6: An Extension to the DS-		I. Farrer, "Lightweight 4over6: An Extension to the DS-
	Lite Architecture", draft-ietf-softwire-lw4over6-13 (work		Lite Architecture", draft-ietf-softwire-lw4over6-13 (work
	in progress), November 2014.		in progress), November 2014.
	[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network		[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network
	Address Translator (Traditional NAT)", RFC 3022, January		Address Translator (Traditional NAT)", RFC 3022,
	2001.		DOI 10.17487/RFC3022, January 2001,
			<http://www.rfc-editor.org/info/rfc3022>.
	[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful		[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful
	NAT64: Network Address and Protocol Translation from IPv6		NAT64: Network Address and Protocol Translation from IPv6
	Clients to IPv4 Servers", RFC 6146, April 2011.		Clients to IPv4 Servers", RFC 6146, DOI 10.17487/RFC6146,
			April 2011, <http://www.rfc-editor.org/info/rfc6146>.
	[RFC6269] Ford, M., Boucadair, M., Durand, A., Levis, P., and P.		[RFC6269] Ford, M., Ed., Boucadair, M., Durand, A., Levis, P., and
	Roberts, "Issues with IP Address Sharing", RFC 6269, June		P. Roberts, "Issues with IP Address Sharing", RFC 6269,
	2011.		DOI 10.17487/RFC6269, June 2011,
			<http://www.rfc-editor.org/info/rfc6269>.
	[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-		[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
	Stack Lite Broadband Deployments Following IPv4		Stack Lite Broadband Deployments Following IPv4
	Exhaustion", RFC 6333, August 2011.		Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011,
			<http://www.rfc-editor.org/info/rfc6333>.
	[RFC6619] Arkko, J., Eggert, L., and M. Townsley, "Scalable		[RFC6619] Arkko, J., Eggert, L., and M. Townsley, "Scalable
	Operation of Address Translators with Per-Interface		Operation of Address Translators with Per-Interface
	Bindings", RFC 6619, June 2012.		Bindings", RFC 6619, DOI 10.17487/RFC6619, June 2012,
			<http://www.rfc-editor.org/info/rfc6619>.
	[RFC6887] Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P.		[RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and
	Selkirk, "Port Control Protocol (PCP)", RFC 6887, April		P. Selkirk, "Port Control Protocol (PCP)", RFC 6887,
	2013.		DOI 10.17487/RFC6887, April 2013,
			<http://www.rfc-editor.org/info/rfc6887>.
	[RFC6888] Perreault, S., Yamagata, I., Miyakawa, S., Nakagawa, A.,		[RFC6888] Perreault, S., Ed., Yamagata, I., Miyakawa, S., Nakagawa,
	and H. Ashida, "Common Requirements for Carrier-Grade NATs		A., and H. Ashida, "Common Requirements for Carrier-Grade
	(CGNs)", BCP 127, RFC 6888, April 2013.		NATs (CGNs)", BCP 127, RFC 6888, DOI 10.17487/RFC6888,
			April 2013, <http://www.rfc-editor.org/info/rfc6888>.
	[RFC6967] Boucadair, M., Touch, J., Levis, P., and R. Penno,		[RFC6967] Boucadair, M., Touch, J., Levis, P., and R. Penno,
	"Analysis of Potential Solutions for Revealing a Host		"Analysis of Potential Solutions for Revealing a Host
	Identifier (HOST_ID) in Shared Address Deployments", RFC		Identifier (HOST_ID) in Shared Address Deployments",
	6967, June 2013.		RFC 6967, DOI 10.17487/RFC6967, June 2013,
			<http://www.rfc-editor.org/info/rfc6967>.
	Authors' Addresses		Authors' Addresses
	Dean Cheng		Dean Cheng
	Huawei		Huawei
	2330 Central Expressway		2330 Central Expressway
	Santa Clara, California 95050		Santa Clara, California 95050
	USA		USA
	Email: dean.cheng@huawei.com		Email: dean.cheng@huawei.com
End of changes. 19 change blocks.
	32 lines changed or deleted		49 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/