IPv4 Multicast Unusable Group And Source Addresses
draft-ietf-mboned-ipv4-mcast-unusable-01
| Document | Type | Expired Internet-Draft (mboned WG) | |
|---|---|---|---|
| Author | Bill Nickless | ||
| Last updated | 2003-12-10 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-mboned-ipv4-mcast-unusable-01.txt
https://www.ietf.org/archive/id/draft-ietf-mboned-ipv4-mcast-unusable-01.txt
Abstract
Some IPv4 multicast datagrams should not be routed, either within an administrative domain or between administrative domains. A list of those restrictions is supplied here. These restrictions SHOULD be respected by IPv4 multicast applications and included in network device access control lists. IANA should permanently reserve certain address ranges.
Authors
Bill Nickless (nickless@mcs.anl.gov)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)