GLOP Addressing in 233/8

Metadata

Publisher: IETF
Doc Type: Best Practice
Pages: 5
Abstract: This document defines the policy for the use of 233/8 for statically e assigned multicast addresses. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date: 2001-09-01
Status Note: Best Current Practice
DOI: 10.17487/RFC3180
Link: https://doi.org/10.17487/RFC3180
Author(s): David Meyer
Peter Lothberg
Keyword(s): Multicast

Latest version of IETF RFC 3180

Document Versions — IETF RFC 3180

▶ IETF RFC 3180 (2001-09-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

Internet Assigned Numbers Authority [Active, Versionless]
IETF RFC 1797 [Active*]
IETF RFC 1930 [Active*]
IETF RFC 2365 [Active*]
IETF RFC 2374 [Superseded*]
IETF RFC 2730 [Active*]
IETF RFC 2770 [Superseded*]
IETF RFC 2909 [Active*]
IETF RFC 2974 [Active*]
IETF RFC 3138 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3180.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 3180, GLOP Addressing in 233/8. Available at https://doi.org/10.17487/RFC3180

Snippet:

IETF RFC 3180, GLOP Addressing in 233/8. Available at https://doi.org/10.17487/RFC3180

HTML (ISO 690 compliant)

Preview:

IETF RFC 3180, GLOP Addressing in 233/8. Available at https://doi.org/10.17487/RFC3180

Snippet:

<span class="citation"><cite>IETF RFC 3180</cite>, GLOP Addressing in 233/8. Available at <a href="https://doi.org/10.17487/RFC3180" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3180</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 3180, GLOP Addressing in 233/8
doi: 10.17487/RFC3180
url: https://doi.org/10.17487/RFC3180

Snippet:

<li>
<cite id="bib-rfc3180">IETF RFC 3180</cite>, GLOP Addressing in 233/8
<span class="doi">10.17487/RFC3180</span>
</li>

Referenced By

IETF RFC 3569 [Active*]
IETF RFC 5771 [Active*]