Requirements for IP Multicast Session Announcement in the Internet
draft-asaeda-mboned-session-announcement-req-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2008-07-06 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-asaeda-mboned-session-announcement-req-00.txt
Abstract
The Session Announcement Protocol (SAP) [3] was used to announce information for all available multicast sessions to the prospective receiver in an experimental network. It is usefull and easy to use, but difficult to control the SAP message transmission in a wide area network. This document describes the several major limitations SAP has and the requirement of multicast session announcement in the global Internet.
Authors
Hitoshi Asaeda
(Asaeda@wide.ad.jp)
Vincent Roca
(vincent.roca@inrialpes.fr)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)