RFC 2730: Multicast Address Dynamic Client Allocation Protocol (MADCAP)
In plain English — editorial summary, not part of the RFC
This document defines a protocol, Multicast Address Dynamic Client Allocation Protocol (MADCAP), that allows hosts to request multicast addresses from multicast address allocation servers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2730
- Published
- December 1999
- Authors
- S. Hanna; B. Patel; M. Shah
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 53
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2907MADCAP Multicast Scope Nesting State OptionCurrent
September 2000
- RFC 3103Realm Specific IP: Protocol SpecificationCurrent
October 2001
- RFC 2701Nortel Networks Multi-link Multi-node PPP Bundle Discovery ProtocolCurrent
September 1999
- RFC 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 1999
- RFC 2649An LDAP Control and Schema for Holding Operation SignaturesCurrent
August 1999
- RFC 2847LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKMCurrent
June 2000
- RFC 2607Proxy Chaining and Policy Implementation in RoamingCurrent
June 1999
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 2000
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?