RIFT Applicability
draft-ietf-rift-applicability-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Yuehua Wei , Zheng Zhang , Dmitry Afanasiev , Tom Verhaeg , Jaroslaw Kowalczyk , Pascal Thubert | ||
| Last updated | 2020-10-05 (Latest revision 2020-04-03) | ||
| Replaces | draft-wei-rift-applicability | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
INTDIR Last Call review
(of
-06)
by Ralf Weber
Ready w/issues
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| 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 document discusses the properties, applicability and operational considerations of RIFT in different network scenarios. It intends to provide a rough guide how RIFT can be deployed to simplify routing operations in Clos topologies and their variations.
Authors
Yuehua Wei
Zheng Zhang
Dmitry Afanasiev
Tom Verhaeg
Jaroslaw Kowalczyk
Pascal Thubert
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)