Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks
RFC 5146
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Operation of a Multiprotocol Label Switching (MPLS) traffic engineering (TE) network as a client network to … Received changes through RFC Editor sync (changed abstract to 'Operation of a Multiprotocol Label Switching (MPLS) traffic engineering (TE) network as a client network to a Generalized MPLS (GMPLS) network has enhanced operational capabilities compared to those provided by a coexistent protocol model (i.e., operation of MPLS-TE over an independently managed transport layer). The GMPLS network may be a packet or a non-packet network, and may itself be a multi-layer network supporting both packet and non-packet technologies. An MPLS-TE Label Switched Path (LSP) originates and terminates on an MPLS Label Switching Router (LSR). The GMPLS network provides transparent transport for the end-to-end MPLS-TE LSP. This document describes a framework and Service Provider requirements for operating MPLS-TE networks over GMPLS networks. This memo provides information for the Internet community.') |
2015-10-14
|
(System) | Notify list changed from ccamp-chairs@ietf.org, draft-ietf-ccamp-mpls-gmpls-interwork-reqts@ietf.org to (None) |
2008-03-25
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2008-03-25
|
Amy Vezza | [Note]: 'RFC 5146' added by Amy Vezza |
2008-03-21
|
(System) | RFC published |