Post-Stack MPLS Network Action (MNA) Solution
draft-jags-mpls-ps-mna-hdr-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jaganbabu Rajamanickam , Rakesh Gandhi , Royi Zigler , Tony Li , Jie Dong | ||
| Last updated | 2023-09-11 (Latest revision 2023-03-10) | ||
| RFC stream | (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
This document defines the Post-Stack MPLS Network Action (MNA) solution for carrying Network Actions and Ancillary Data after the MPLS label stack based on In-Stack MNA solution defined in draft- ietf-mpls-mna-hdr. MPLS Network Actions can be used to influence packet forwarding decisions, carry additional OAM information in the MPLS packet or perform user-defined operations. This document addresses the MNA requirements specified in draft-ietf-mpls-mna- requirements. This document follows the MNA framework specified in draft-ietf-mpls-mna-fwk.
Authors
Jaganbabu Rajamanickam
Rakesh Gandhi
Royi Zigler
Tony Li
Jie Dong
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)