RIFT Applicability
draft-wei-rift-applicability-02
| Document | Type |
Replaced Internet-Draft
(rift WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yuehua Wei , Zheng Zhang , Dmitry Afanasiev , Tom Verhaeg , Jaroslaw Kowalczyk | ||
| Last updated | 2020-03-24 (Latest revision 2019-11-04) | ||
| Replaced by | draft-ietf-rift-applicability | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-rift-applicability | |
| 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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)