Policy Guided Prefixes with Routing In Fat Trees
draft-atlas-rift-pgp-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2019-04-25 (latest revision 2018-10-22)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-atlas-rift-pgp-00.txt

Abstract

In a fat tree, it can be sometimes desirable to guide traffic to particular destinations or keep specific flows to certain paths. In RIFT, this traffic steering/engineering is done by using policy- guided prefixes with their associated communities. Routes based on policy-guided prefixes are preferred over regular routes. Any node can originate a policy-guided prefix and advertise it in both north and south directions, and the calculation in both directions are distance vector based.

Authors

Alia Atlas (akatlas@gmail.com)
Zhaohui Zhang (zzhang@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)