RFC 3496: Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering
In plain English — editorial summary, not part of the RFC
This document specifies a Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) signaling extension for support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3496
- Published
- March 2003
- Authors
- A. G. Malis; T. Hsiao
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdated
February 2003
- RFC 4873GMPLS Segment RecoveryUpdated
May 2007
- RFC 5710PathErr Message Triggered MPLS and GMPLS LSP ReroutesCurrent
January 2010
- RFC 2963A Rate Adaptive Shaper for Differentiated ServicesCurrent
October 2000
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)Updated
February 2003
- RFC 3468The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocolsCurrent
February 2003
- RFC 3308Layer Two Tunneling Protocol (L2TP) Differentiated Services ExtensionCurrent
November 2002
- RFC 3289Management Information Base for the Differentiated Services ArchitectureCurrent
June 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?