RFC 3180 (rfc3180) - Page 1 of 5
GLOP Addressing in 233/8
Alternative Format: Original Text Document
Network Working Group D. Meyer
Request for Comments: 3180 P. Lothberg
Obsoletes: 2770 Sprint
BCP: 53 September 2001
Category: Best Current Practice
GLOP Addressing in 233/8
Status of this Memo
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
This document defines the policy for the use of 233/8 for statically
assigned multicast addresses.
1. Introduction
It is envisioned that the primary use of this space will be many-to-
many applications. This allocation is in addition to those described
on [IANA] (e.g., [RFC 2365]). The IANA has allocated 223/8 as per RFC
2770 [RFC 2770]. This document obsoletes RFC 2770.
2. Problem Statement
Multicast addresses have traditionally been allocated by a dynamic
mechanism such as SDR [RFC 2974]. However, many current multicast
deployment models are not amenable to dynamic allocation. For
example, many content aggregators require group addresses that are
fixed on a time scale that is not amenable to allocation by a
mechanism such as described in [RFC 2974]. Perhaps more seriously,
since there is not general consensus by providers, content
aggregators, or application writers as to the allocation mechanism,
the Internet is left without a coherent multicast address allocation
scheme.
Meyer & Lothberg Best Current Practice