Scoping Filters for Source-Specific Multicast
draft-holbrook-ssm-scoping-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hugh Holbrook | ||
| Last updated | 2003-10-22 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a method of providing scope-limited Source- Specific Multicast (SSM) channels by filtering at boundary routers. The filtering prevents SSM traffic from being forwarded through a scope boundary. Each administrative domain that wishes to enforce scoping can choose the sub-range of SSM channels that it wishes to scope -- no globally-scoped address range is defined. The method described here does not require extending the current SSM range allocation to include a new 'scoped SSM' range. The method described is primarily intended to provide scoping for IPv4 SSM channels, since IPv6 integrates multicast scoping into the basic addressing architecture.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)