draft-ietf-mboned-iana-ipv4-mcast-guidelines-03.txt		draft-ietf-mboned-iana-ipv4-mcast-guidelines-04.txt
	Network Working Group Zaid Albanna		Network Working Group Zaid Albanna
	INTERNET DRAFT Juniper Networks		INTERNET DRAFT Juniper Networks
	Kevin Almeroth		Kevin Almeroth
	UCSB		UCSB
	David Meyer		David Meyer
	Sprint		Sprint
	Michelle Schipper		Michelle Schipper
	IANA		IANA
	Category Best Current Practices		Category Best Current Practices
	June, 2001		July, 2001
	IANA Guidelines for IPv4 Multicast Address Assignments		IANA Guidelines for IPv4 Multicast Address Assignments
	<draft-ietf-mboned-iana-ipv4-mcast-guidelines-03.txt>		<draft-ietf-mboned-iana-ipv4-mcast-guidelines-04.txt>
	1. Status of this Memo		1. Status of this Memo
	This document specifies an Internet Best Current Practices for the		This document specifies an Internet Best Current Practices for the
	Internet Community, and requests discussion and suggestions for		Internet Community, and requests discussion and suggestions for
	improvements. Distribution of this memo is unlimited.		improvements. Distribution of this memo is unlimited.
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC 2026.		all provisions of Section 10 of RFC 2026.
	skipping to change at page 2, line 38		skipping to change at page 2, line 38
	MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SHALL NOT,		MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SHALL NOT,
	SHOULD, SHOULD NOT are to be interpreted as defined in RFC 2119		SHOULD, SHOULD NOT are to be interpreted as defined in RFC 2119
	[RFC2119].		[RFC2119].
	In general, due to the relatively small size of the IPv4 multicast		In general, due to the relatively small size of the IPv4 multicast
	addresses space, further assignment of IPv4 multicast address space		addresses space, further assignment of IPv4 multicast address space
	is recommended only in limited circumstances. Specifically, the IANA		is recommended only in limited circumstances. Specifically, the IANA
	should only assign addresses in those cases where the dynamic		should only assign addresses in those cases where the dynamic
	selection (SDP/SAP), GLOP, SSM or Administratively Scoped address		selection (SDP/SAP), GLOP, SSM or Administratively Scoped address
	spaces cannot be used. The guidelines described below are reflected		spaces cannot be used. The guidelines described below are reflected
	in http://www.iana.org/assignments/multicast-addresses.		in http://www.iana.org/numbers.html.
	5. Definition of Current Assignment Practice		5. Definition of Current Assignment Practice
	Unlike IPv4 unicast address assignment, where blocks of addresses are		Unlike IPv4 unicast address assignment, where blocks of addresses are
	delegated to regional registries, IPv4 multicast addresses are		delegated to regional registries, IPv4 multicast addresses are
	assigned directly by the IANA. Current assignments appear as follows		assigned directly by the IANA. Current assignments appear as follows
	[IANA]:		[IANA]:
	224.0.0.0 - 224.0.0.255 (224.0.0/24) Local Network Control Block		224.0.0.0 - 224.0.0.255 (224.0.0/24) Local Network Control Block
	224.0.1.0 - 224.0.1.255 (224.0.1/24) Internetwork Control Block		224.0.1.0 - 224.0.1.255 (224.0.1/24) Internetwork Control Block
	224.0.2.0 - 224.0.255.0 AD-HOC Block		224.0.2.0 - 224.0.255.0 AD-HOC Block
	224.1.0.0 - 224.1.255.255 (224.1/16) ST Multicast Groups		224.1.0.0 - 224.1.255.255 (224.1/16) ST Multicast Groups
	224.2.0.0 - 224.2.255.255 (224.2/16) SDP/SAP Block		224.2.0.0 - 224.2.255.255 (224.2/16) SDP/SAP Block
	224.252.0.0 - 224.255.255.255 DIS Transient Block		224.252.0.0 - 224.255.255.255 DIS Transient Block
	225.0.0.0 - 225.255.255.255 (225/8) MALLOC Block		225.0.0.0 - 231.255.255.255 RESERVED
	226.0.0.0 - 231.255.255.255 RESERVED
	232.0.0.0 - 232.255.255.255 (232/8) Source Specific Multicast Block		232.0.0.0 - 232.255.255.255 (232/8) Source Specific Multicast Block
	233.0.0.0 - 233.255.255.255 (233/8) GLOP Block		233.0.0.0 - 233.255.255.255 (233/8) GLOP Block
	234.0.0.0 - 238.255.255.255 RESERVED		234.0.0.0 - 238.255.255.255 RESERVED
	239.0.0.0 - 239.255.255.255 (239/8) Administratively Scoped Block		239.0.0.0 - 239.255.255.255 (239/8) Administratively Scoped Block
	The IANA generally assigns addresses from the Local Network Control,		The IANA generally assigns addresses from the Local Network Control,
	Internetwork Control, and AD-HOC blocks. Assignment guidelines for		Internetwork Control, and AD-HOC blocks. Assignment guidelines for
	each of these blocks, as well as for the MALLOC, Source Specific		each of these blocks, as well as for the Source Specific Multicast,
	Multicast, GLOP and Administratively Scoped Blocks, are described		GLOP and Administratively Scoped Blocks, are described below.
	below.
	6. Local Network Control Block (224.0.0/24)		6. Local Network Control Block (224.0.0/24)
	Addresses in the Local Network Control block are used for protocol		Addresses in the Local Network Control block are used for protocol
	control traffic that is not forwarded off link. Examples of this type		control traffic that is not forwarded off link. Examples of this type
	of use include OSPFIGP All Routers (224.0.0.5) [RFC2328].		of use include OSPFIGP All Routers (224.0.0.5) [RFC2328].
	6.1. Assignment Guidelines		6.1. Assignment Guidelines
	Pursuant to section 4.4.2 of RFC 2780 [RFC2780], assignments from the		Pursuant to section 4.4.2 of RFC 2780 [RFC2780], assignments from the
	skipping to change at page 5, line 6		skipping to change at page 5, line 6
	via applications like the session directory tool (such as SDR [SDR]).		via applications like the session directory tool (such as SDR [SDR]).
	9.1. Assignment Guidelines		9.1. Assignment Guidelines
	Since addresses in the SDP/SAP block are chosen randomly from the		Since addresses in the SDP/SAP block are chosen randomly from the
	range of addresses not already in use [RFC2974], no IANA assignment		range of addresses not already in use [RFC2974], no IANA assignment
	policy is required. Note that while no additional IANA assignment is		policy is required. Note that while no additional IANA assignment is
	required, addresses in the SDP/SAP block are explicitly for use by		required, addresses in the SDP/SAP block are explicitly for use by
	SDP/SAP and MUST NOT be used for other purposes.		SDP/SAP and MUST NOT be used for other purposes.
	10. MALLOC Block (225/8)		10. Source Specific Multicast Block (232/8)
	Addresses in the MALLOC block are dynamically assigned by the MALLOC
	suite of protocols [RFC2908]. This assignment is temporary and MUST
	BE reviewed annually.
	10.1. Assignment Guidelines
	Since addresses in the MALLOC block are chosen by elements of the
	MALLOC architecture, no IANA assignment policy is required. Note that
	while no additional IANA assignment is required, addresses in the
	MALLOC block are explicitly for assignment by MALLOC servers and MUST
	NOT be used for other purposes.
	11. Source Specific Multicast Block (232/8)
	The Source Specific Multicast (SSM) is an extension of IP Multicast		The Source Specific Multicast (SSM) is an extension of IP Multicast
	in which traffic is forwarded to receivers from only those multicast		in which traffic is forwarded to receivers from only those multicast
	sources for which the receivers have explicitly expressed interest,		sources for which the receivers have explicitly expressed interest,
	and is primarily targeted at one-to-many (broadcast) applications.		and is primarily targeted at one-to-many (broadcast) applications.
			Note that this block as initially assigned to the VMTP transient
			groups [IANA].
	11.1. Assignment Guidelines		10.1. Assignment Guidelines
	Because the SSM model essentially makes the entire multicast address		Because the SSM model essentially makes the entire multicast address
	space local to the host, no IANA assignment policy is required. Note,		space local to the host, no IANA assignment policy is required. Note,
	however, that while no additional IANA assignment is required,		however, that while no additional IANA assignment is required,
	addresses in the SSM block are explicitly for use by SSM and MUST NOT		addresses in the SSM block are explicitly for use by SSM and MUST NOT
	be used for other purposes.		be used for other purposes.
	12. GLOP Block (233/8)		11. GLOP Block (233/8)
	Addresses in the GLOP block are globally scoped statically assigned		Addresses in the GLOP block are globally scoped statically assigned
	addresses. The assignment is made by mapping a domain's autonomous		addresses. The assignment is made by mapping a domain's autonomous
	system number into the middle two octets of 233.X.Y.0/24. The mapping		system number into the middle two octets of 233.X.Y.0/24. The mapping
	and assignment is defined in [RFC2770].		and assignment is defined in [RFC2770].
	12.1. Assignment Guidelines		11.1. Assignment Guidelines
	Because addresses in the GLOP block are algorithmically preassigned,		Because addresses in the GLOP block are algorithmically pre-assigned,
	no IANA assignment policy is required. Note that while no additional		no IANA assignment policy is required. In addition, RFC 3138
	IANA assignment is required, addresses in the GLOP block are assigned		[RFC3138] delegates assignment of the GLOP sub-block mapped by the
	for use as defined in RFC 2770 and MUST NOT be used for other		RFC 1930 [RFC1930] private AS space (233.252.0.0 - 233.255.255.255)
	purposes.		to the Internet Routing Registries. Note that while no additional
			IANA assignment is required, addresses in the GLOP block are
			assigned for use as defined in RFC 2770 and MUST NOT be used for
			other purposes.
	13. Administratively Scoped Address Block (239/8)		12. Administratively Scoped Address Block (239/8)
	Addresses in the Administratively Scoped Address block are for local		Addresses in the Administratively Scoped Address block are for local
	use within a domain and are described in [RFC2365].		use within a domain and are described in [RFC2365].
	13.1. Assignment Guidelines		12.1. Assignment Guidelines
	Since addresses in this block are local to a domain, no IANA		Since addresses in this block are local to a domain, no IANA
	assignment policy is required.		assignment policy is required.
	13.1.1. Relative Offsets		12.1.1. Relative Offsets
	The relative offsets [RFC2365] are used to ensure that a service can		The relative offsets [RFC2365] are used to ensure that a service can
	be located independent of the extent of the enclosing scope (see RFC		be located independent of the extent of the enclosing scope (see RFC
	2770 for details). Since there are only 256 such offsets, the IANA		2770 for details). Since there are only 256 such offsets, the IANA
	should only assign a relative offset to a protocol that provides an		should only assign a relative offset to a protocol that provides an
	infra-structure supporting service. Examples of such services include		infra-structure supporting service. Examples of such services include
	the Session Announcement Protocol [RFC2974]. Pursuant to section		the Session Announcement Protocol [RFC2974]. Pursuant to section
	4.4.2 of RFC 2780 [RFC2780], assignments of Relative Offsets follow		4.4.2 of RFC 2780 [RFC2780], assignments of Relative Offsets follow
	an Expert Review, IESG Approval or Standards Action process. See		an Expert Review, IESG Approval or Standards Action process. See
	[IANA] for the current set of assignments.		[IANA] for the current set of assignments.
	14. Annual Review		13. Annual Review
	Given the dynamic nature of IPv4 multicast and its associated infra-		Given the dynamic nature of IPv4 multicast and its associated infra-
	structure, and the previously undocumented IPv4 multicast address		structure, and the previously undocumented IPv4 multicast address
	assignment guidelines, the IANA should conduct an annual review of		assignment guidelines, the IANA should conduct an annual review of
	currently assigned addresses.		currently assigned addresses.
	14.1. Address Reclamation		13.1. Address Reclamation
	During the review described above, addresses that were mis-assigned		During the review described above, addresses that were mis-assigned
	should, where possible, be reclaimed or reassigned.		should, where possible, be reclaimed or reassigned.
	The IANA should also review assignments in the AD-HOC, DIS Transient		The IANA should also review assignments in the AD-HOC, DIS Transient
	Groups, and ST Multicast Groups blocks and reclaim those addresses		Groups, and ST Multicast Groups blocks and reclaim those addresses
	that are not in use on the global Internet (i.e, those applications		that are not in use on the global Internet (i.e, those applications
	which can use SSM, GLOP, or Administratively Scoped addressing, or		which can use SSM, GLOP, or Administratively Scoped addressing, or
	are not globally routed).		are not globally routed).
	15. Use of IANA Reserved Addresses		14. Use of IANA Reserved Addresses
	Applications MUST NOT use addressing in the IANA reserved blocks.		Applications MUST NOT use addressing in the IANA reserved blocks.
	16. Appeals Process		15. Security Considerations
	Appeals of this process are to be handled in accordance with Section
	6.5 of RFC 2026 [RFC2026].
	17. Security Considerations
	The assignment guidelines described in this document do not alter the		The assignment guidelines described in this document do not alter the
	security properties of either the Any Source or Source Specific		security properties of either the Any Source or Source Specific
	multicast service models.		multicast service models.
	18. Acknowledgments		16. Acknowledgments
	The authors would like to thank Joe St. Sauver, John Meylor, Randy		The authors would like to thank Joe St. Sauver, John Meylor, Randy
	Bush, and Thomas Narten for their constructive feedback and comments.		Bush, and Thomas Narten for their constructive feedback and comments.
	19. Author's Address:		17. Author's Address:
	Zaid Albanna		Zaid Albanna
	1149 N. Mathilda Ave		1149 N. Mathilda Ave
	Sunnyvale, CA. 94089		Sunnyvale, CA. 94089
	zaid@juniper.net		zaid@juniper.net
	Kevin Almeroth		Kevin Almeroth
	UC Santa Barbara		UC Santa Barbara
	Santa Barbara, CA.		Santa Barbara, CA.
	Email: almeroth@cs.ucsb.edu		Email: almeroth@cs.ucsb.edu
	skipping to change at page 8, line 33		skipping to change at page 8, line 5
	Sprint E|Solutions		Sprint E|Solutions
	Email: dmm@sprint.net		Email: dmm@sprint.net
	Michelle Schipper		Michelle Schipper
	IANA Administrator		IANA Administrator
	Internet Assigned Numbers Authority		Internet Assigned Numbers Authority
	4676 Admiralty Way, Suite 330		4676 Admiralty Way, Suite 330
	Marina del Rey, CA 90292		Marina del Rey, CA 90292
	iana@iana.org		iana@iana.org
	20. References		18. References
	[IANA] http://www.iana.org/assignments/multicast-addresses		[IANA] http://www.iana.org/numbers.html
	[RFC1190] C. Topolcic, "Experimental Internet Stream		[RFC1190] C. Topolcic, "Experimental Internet Stream
	Protocol, Version 2 (ST-II)", RFC 1190, October,		Protocol, Version 2 (ST-II)", RFC 1190, October,
	1990.		1990.
			[RFC1930] J. Hawkinson and T. Bates, "Guidelines for
			creation, selection, and registration of an
			Autonomous System (AS)", RFC 1930, March 1996.
	[RFC2026] S. Bradner, "The Internet Standards Process --		[RFC2026] S. Bradner, "The Internet Standards Process --
	Revision 3", RFC2026, October 1996.		Revision 3", RFC2026, October 1996.
	[RFC2030] Mills, D., Simple Network Time Protocol (SNTP) Version 4		[RFC2030] Mills, D., Simple Network Time Protocol (SNTP) Version 4
	for IPv4, IPv6 and OSI", D. Mills, October 1996.		for IPv4, IPv6 and OSI", D. Mills, October 1996.
	[RFC2119] S. Bradner, "Key words for use in RFCs to		[RFC2119] S. Bradner, "Key words for use in RFCs to
	Indicate Requirement Levels", RFC 2119, March,		Indicate Requirement Levels", RFC 2119, March,
	1997.		1997.
	skipping to change at page 9, line 25		skipping to change at page 8, line 47
	Dynamic Client Allocation Protocol (MADCAP), December		Dynamic Client Allocation Protocol (MADCAP), December
	1999.		1999.
	[RFC2770] D. Meyer, and P. Lothberg, "GLOP Addressing in 233/8",		[RFC2770] D. Meyer, and P. Lothberg, "GLOP Addressing in 233/8",
	RFC 2770, February, 2000		RFC 2770, February, 2000
	[RFC2780] S. Bradner and V. Paxson, "IANA Allocation Guidelines		[RFC2780] S. Bradner and V. Paxson, "IANA Allocation Guidelines
	For Values In the Internet Protocol and Related		For Values In the Internet Protocol and Related
	Headers", RFC2780, March, 2000		Headers", RFC2780, March, 2000
	[RFC2908] D. Thaler, M. Handley, D.Estrin, "Theh Internet Multicast		[RFC2908] D. Thaler, M. Handley, D.Estrin, "The Internet Multicast
	Address Allocation Architecture", RFC 2908, September 2000.		Address Allocation Architecture", RFC 2908, September 2000.
			[RFC2909] D. Thaler, M. Handley, D.Estrin, "The Multicast
			Address-Set Claim (MASC) Protocol, RFC 2909,
			September 2000.
	[RFC2974] M. Handley, C. Perkins, E. Whelan, "Session		[RFC2974] M. Handley, C. Perkins, E. Whelan, "Session
	Announcement Protocol", RFC 2974, October 2000.		Announcement Protocol", RFC 2974, October 2000.
			[RFC3818] D. Meyer, "Extended Assignments in 233/8", RFC
			3818, June, 2001.
	[SDR] http://www.aciri.org/sdr/		[SDR] http://www.aciri.org/sdr/
	21. Full Copyright Statement		19. Full Copyright Statement
	Copyright (C) The Internet Society (2001). All Rights Reserved.		Copyright (C) The Internet Society (2001). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
End of changes.
This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/