Backtrace Messages for Label Switched Paths
draft-kishan-lsp-btrace-04
| Document | Type |
Expired Internet-Draft
(sub)
Expired & archived
|
|
|---|---|---|---|
| Authors | HariKishan Desineni , Kameswara Avasarala | ||
| Last updated | 2015-10-14 (Latest revision 2002-10-10) | ||
| RFC stream | Independent Submission | ||
| Intended RFC status | Experimental | ||
| Formats | |||
| Stream | ISE state | (None) | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Telechat date | (None) | ||
| Responsible AD | Alex D. Zinin | ||
| Send notices to | <harikishan.desineni@ericsson.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Label switched path (LSP) backtrace is a method to backtrack the paths followed by packets in a particular multi protocol label switching (MPLS) forwarding equivalence class (FEC). This document describes encoding and procedures for new label distribution protocol (LDP) messages, backtrace message and backtrace reply message used for performing LSP backtrace. Backtrace message is sent upstream for an established LSP. Backtrace message can be used for LDP LSPs as well as for constraint based label switched paths (CR-LSPs). Data requested through backtrace message is encoded into backtrace reply message. Backtrace reply message is sent in downstream direction. It always travels towards the tail end of an LSP. Backtrace mechanism described in this document can also be used for obtaining additional attributes of LSPs.
Authors
HariKishan Desineni
Kameswara Avasarala
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)