LSP Attribute in ERO
draft-ietf-ccamp-lsp-attribute-ro-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Cyril Margaria , Giovanni Martinelli , Steve Balls , Ben Wright | ||
| Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
| Replaces | draft-margaria-ccamp-lsp-attribute-ero | ||
| Replaced by | draft-ietf-teas-lsp-attribute-ro, RFC 7570 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
LSP attributes can be specified or recorded for whole path, but they cannot be targeted to a specific hop. This document proposes alternative ways to extend the semantic for RSVP ERO object to target LSP attributes to a specific hop.
Authors
Cyril Margaria
Giovanni Martinelli
Steve Balls
Ben Wright
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)