Another ATM Signaling Protocol for IP (IP-SVC)
draft-fujikawa-ipsvc-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kenji Fujikawa | ||
| Last updated | 1996-11-07 (Latest revision 1996-05-06) | ||
| 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 memo describes IP-SVC that is another ATM signaling protocol for implementing IP protocols. IP-SVC restricts the range of signaling to an IP subnet, and this restriction makes the IP-SVC structure simple. IP-SVC provides easy implementation of the mechanism of ARP and IP multicasting without any servers. IP-SVC can not establish VCs across IP subnet boundaries by itself. However, adapting CSRs (Cell Switching Routers) with RSVP (Resource ReSerVation Protocol) enables end-to-end VC establishment across IP subnet boundaries in IP/ATM LANs based on IP-SVC. This method also shows one solution of RSVP over ATM.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)