draft-ietf-mboned-glop-extensions-00.txt		draft-ietf-mboned-glop-extensions-01.txt
	Network Working Group David Meyer		Network Working Group David Meyer
	INTERNET DRAFT Cisco Systems		INTERNET DRAFT Cisco Systems
	Category Best Current Practices		Category Best Current Practices
	March, 2001		April, 2001
	Extended Allocations in 233/8		Extended Allocations in 233/8
	<draft-ietf-mboned-glop-extensions-00.txt>		<draft-ietf-mboned-glop-extensions-01.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 3, line 11		skipping to change at page 3, line 11
	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].
	5. Overview		5. Overview
	http://www.iana.org/cgi-bin/multicast.pl defines a mechanism for		http://www.iana.org/cgi-bin/multicast.pl defines a mechanism for
	allocation of multicast addresses that are generally for use in		allocation of multicast addresses that are generally for use in
	network control applications (a more general description of these		network control applications (a more general description of these
	policies can be found in [GUIDELINES]). It is envisioned that those		policies can be found in [GUIDELINES]). It is envisioned that those
	addresses allocated from the EGLOP space (233.242.0.0/24 -		addresses allocated from the EGLOP space (233.242.0.0 -
	233.255.255.0/24) will be used by applications that cannot use		233.255.255.255) will be used by applications that cannot use
	Administratively Scoped Addressing [RFC2365], GLOP Addressing		Administratively Scoped Addressing [RFC2365], GLOP Addressing
	[RFC2770], or Source Specific Multicast (SSM) [SSM].		[RFC2770], or Source Specific Multicast (SSM) [SSM].
	6. Assignment Criteria		6. Assignment Criteria
	An application for a globally scoped IPv4 multicast addresses issued		Globally scoped IPv4 multicast addresses in the EGLOP space are
	by a Regional Registry (RIR). The applicant MUST		allocated by a Regional Registry (RIR). An applicant MUST, as per
			[IANA], show that the request cannot be satisfied using
	(i). Show that the request cannot be satisfied using		Administratively Scoped addressing [RFC2365], GLOP addressing
	Administratively Scoped addressing, GLOP addressing,		[RFC2770], or SSM [SSM]. The fine-grained allocation policy is left
	or SSM.		to the allocating RIR.
	(ii). Request IP address space from upstream provider
	(iii). Request IP address space from provider's provider
	If the request cannot be satisfied by (i)-(iii) above, the RIR MAY
	consider allocation from the range 233.242.0.0 - 233.255.255.0.
	Address space allocation size is the responsibility of the allocating
	RIR. The blocks MUST BE be issued on appropriate CIDR boundaries.
	Prefixes shorter than /21 should not be allocated.
	Because the number of available IPv4 multicast addresses on the
	Internet is extremely limited, many factors must be considered in the
	determination of address space allocations. Therefore, multicast
	address space MUST be allocated using a slow-start model. Allocations
	SHOULD be based on justified need, not solely on a predicted customer
	base. In particular, delayed deployment of a given technology (e.g.
	SSM) is not a basis for assignment of addresses from the EGLOP space.
	7. Security Considerations		7. Security Considerations
	Security issues are not discussed in this memo.		Security issues are not discussed in this memo.
	8. Acknowledgments		8. Acknowledgments
			Mirjam Kuehne and Randy Bush provided many insightful comments on
			earlier versions of this document.
	9. Author's Address:		9. Author's Address:
	David Meyer		David Meyer
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 Tasman Drive		170 Tasman Drive
	San Jose, CA, 95134		San Jose, CA, 95134
	Email: dmm@cisco.com		Email: dmm@cisco.com
	10. References		10. References
	[IANA] http://www.isi.edu/in-notes/iana/assignments/multicast-addresses		[IANA] http://www.iana.org
	[RFC1930] J. Hawkinson and T. Bates, "Guidelines for		[RFC1930] J. Hawkinson and T. Bates, "Guidelines for
	creation, selection, and registration of an		creation, selection, and registration of an
	Autonomous System (AS)", RFC 1930, March 1996.		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.
	[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,
	skipping to change at page 4, line 45		skipping to change at page 4, line 31
	2365, July, 1998.		2365, July, 1998.
	[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
	[SSM] Holbrook, H., and Cain, B., "Source-Specific Multicast		[SSM] Holbrook, H., and Cain, B., "Source-Specific Multicast
	for IP", draft-holbrook-ssm-arch-01.txt, Work in		for IP", draft-holbrook-ssm-arch-02.txt, Work in
	progress.		progress.
	[GUIDELINES] IANA Guidelines for IPv4 Multicast Address		[GUIDELINES] Albanna, Z., et. al, "IANA Guidelines for IPv4 Multicast
	Allocation, draft-albanna-iana-IPv4-mcast-guidelines-00.txt,		Address Allocation",
			draft-ietf-mboned-iana-ipv4-mcast-guidelines-00.txt,
	Work in progress.		Work in progress.
	11. Full Copyright Statement		11. 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
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/