RTGWG PathID Engineering
draft-lt-rtgwg-pathid-engineering-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ting Liao , Ting Ao | ||
| Last updated | 2016-06-26 (Latest revision 2015-12-24) | ||
| 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
With the deployment of centralized control, the traffic scheduling can be easier to accomplish with PathID carried in the data plane. A PathID used to indicate a flow through a forwarding path which is not the default shortest path. It is encapsulated in the packet at the ingress node, carried to indicate the forwarding at the transit node and decapsulated at the egress node. This document describes how to accomplish flexible forwarding with PathID in traffic scheduling.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)