As per Relevance of the word multicast, we have this rfc below:
Network Working Group D.
Request for Comments: 3138
Category: Informational June 2001
Extended Assignments in 233/8
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This memo provides describes the mapping of the GLOP
corresponding to the private AS space
1.
RFC 2770 [RFC2770] describes an experimental policy for use of
class D address space using 233/8. The technique described
maps 16 bits of Autonomous System number (AS) into the middle
octets of 233/8 to yield a /24. While this technique has
successful, the assignments are inefficient in those cases in which
/24 is too small or the user doesn't have its own AS
RFC 1930 [RFC1930] defines the private AS space to be 64512
65535. This memo expands on RFC 2770 to allow routing registries
assign multicast addresses from the GLOP space corresponding to
RFC 1930 private AS space. This space will be referred to as
EGLOP (Extended GLOP) address space
This memo is a product of the Multicast Deployment Working
(MBONED) in the Operations and Management Area of the
Engineering Task Force. Submit comments to
or the authors
The terms "Specification Required", "Expert Review", "IESG Approval",
"IETF Consensus", and "Standards Action", are used in this memo
refer to the processes described in [RFC2434]. The keywords MUST
MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SHALL NOT
SHOULD, SHOULD NOT are to be interpreted as defined in RFC 2119
[RFC2119].
Meyer Informational [Page 1]
RFC 3138 Extended Assignments in 233/8 June 2001
2.
http://www.iana.org/assignments/multicast-addresses defines
mechanism for assignment of multicast addresses that are
for use in network control applications. It is envisioned that
addresses assigned from the EGLOP space (233.252.0.0 -
233.255.255.255) will be used by applications that cannot
Administratively Scoped Addressing [RFC2365], GLOP
[RFC2770], or Source Specific Multicast (Source Specific Multicast
or SSM, is an extension of IP Multicast in which traffic is
to receivers from only those multicast sources for which
receivers have explicitly expressed interest, and is
targeted at one-to-many (broadcast) applications).
3. Assignment
Globally scoped IPv4 multicast addresses in the EGLOP space
assigned by a Regional Registry (RIR). An applicant MUST, as
[IANA], show that the request cannot be satisfied
Administratively Scoped addressing [RFC2365], GLOP
[RFC2770], or SSM. The fine-grained assignment policy is left to
assigning RIR
4. Security
The assignment scheme described in this document does not effect
security properties of the the single source or any source
service models
5.
Kurt Kayser, Mirjam Kuehne, Michelle Schipper and Randy Bush
many insightful comments on earlier versions of this document
6. Author's
David
12502 Sunrise Valley
Reston VA, 20191
EMail: dmm@sprint.
Meyer Informational [Page 2]
RFC 3138 Extended Assignments in 233/8 June 2001
7.
[IANA] http://www.iana.org/assignments/multicast-
[RFC1930] Hawkinson J. and T. Bates, "Guidelines
creation, selection, and registration of
Autonomous System (AS)", RFC 1930, March 1996.
[RFC2026] Bradner, S., "The Internet Standards Process --
Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs
Indicate Requirement Levels", BCP 14, RFC 2119,
March 1997.
[RFC2365] Meyer, D., "Administratively Scoped IP Multicast",
RFC 2365, July 1998.
[RFC2770] Meyer, D. and P. Lothberg, "GLOP Addressing
233/8", RFC 2770, February 2000.
[RFC2780] Bradner, S. and V. Paxson, "IANA
Guidelines For Values In the Internet
and Related Headers", BCP 37, RFC 2780,
2000.
Meyer Informational [Page 3]
RFC 3138 Extended Assignments in 233/8 June 2001
Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Meyer Informational [Page 4]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
