Network Assigned Upstream-Label
draft-ietf-teas-network-assigned-upstream-label-02
| Document | Type | Expired Internet-Draft (teas WG) | |
|---|---|---|---|
| Author | Vishnu Pavan Beeram | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| Replaces | draft-ietf-ccamp-network-assigned-upstream-label | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Reviews |
RTGDIR Last Call review
(of
-06)
Has Nits
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-teas-network-assigned-upstream-label-02.txt
Abstract
This document discusses a GMPLS (Generalized Multi-Protocol Label Switching) RSVP-TE (Resource reSerVation Protocol with Traffic Engineering) protocol mechanism that enables the network to assign an upstream label for a bidirectional 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 downstream node to pick an appropriate label.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)