RFC 2907: MADCAP Multicast Scope Nesting State Option
In plain English — editorial summary, not part of the RFC
This document defines a new option to the Multicast Address Dynamic Client Allocation Protocol (MADCAP) to support nested scoping. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2907
- Published
- September 2000
- Authors
- R. Kermode
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2730Multicast Address Dynamic Client Allocation Protocol (MADCAP)Current
December 1999
- RFC 10028Updates to Dynamic IPv6 Multicast Address Group IDsCurrent
August 2026
- RFC 2908The Internet Multicast Address Allocation ArchitectureObsoleted
September 2000
- RFC 2909The Multicast Address-Set Claim (MASC) ProtocolCurrent
September 2000
- RFC 2914Congestion Control PrinciplesUpdated
September 2000
- RFC 2923TCP Problems with Path MTU DiscoveryCurrent
September 2000
- RFC 2887The Reliable Multicast Design Space for Bulk Data TransferCurrent
August 2000
- RFC 2961RSVP Refresh Overhead Reduction ExtensionsUpdated
April 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?