IS-IS over IPv4
draft-ietf-isis-wg-over-ip-02
| Document | Type |
Expired Internet-Draft
(isis WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Atul Bansal , Tony Przygienda , Ajay Patel | ||
| Last updated | 1999-10-11 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 draft describes an optional implementation technique within IS-IS [ISO90, Cal90a, Cal90b] used today by several ISPs for routing within their clouds. IS-IS is an interior gateway routing protocol developed originally by OSI and used with IP extensions as IGP. This draft describes how to encapsulate IS-IS packets in IPv4 [Pos81] format. Such an encapsulation has many advantages, one of those being the possibility to run integrated IS-IS on anything that understands IPv4, including avian carriers [Wai90]. Encapsulation of IS-IS PDUs in IPv6 is outside the scope of this document.
Authors
Atul Bansal
Tony Przygienda
Ajay Patel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)