Network Assigned Upstream-Label
draft-beeram-ccamp-network-assigned-upstream-label-03
| Document | Type |
Replaced Internet-Draft
(ccamp WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vishnu Pavan Beeram , Igor Bryskin | ||
| Last updated | 2014-10-05 (Latest revision 2014-07-03) | ||
| Replaced by | draft-ietf-ccamp-network-assigned-upstream-label | ||
| 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-ccamp-network-assigned-upstream-label | |
| 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 a GMPLS RSVP-TE protocol mechanism that enables the network to assign an upstream-label for a given LSP. This is useful in scenarios where a given node does not have sufficient information to assign the correct upstream-label on its own and needs to rely on the network to pick an appropriate label.
Authors
Vishnu Pavan Beeram
Igor Bryskin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)