RFC 3038: VCID Notification over ATM link for LDP
In plain English — editorial summary, not part of the RFC
This document specifies the procedures for the communication of VCID values between neighboring ATM-LSRs that must occur in order to ensure this property. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3038
- Published
- January 2001
- Authors
- K. Nagami; Y. Katsube; N. Demizu; H. Esaki; P. Doolan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
- Updated by:
- RFC 7274
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3035MPLS using LDP and ATM VC SwitchingCurrent
January 2001
- RFC 3107Carrying Label Information in BGP-4Obsoleted
May 2001
- RFC 3212Constraint-Based LSP Setup using LDPUpdated
January 2002
- RFC 2844OSPF over ATM and Proxy-PARCurrent
May 2000
- RFC 3355Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5)Current
September 2002
- RFC 3478Graceful Restart Mechanism for Label Distribution ProtocolCurrent
February 2003
- RFC 3479Fault Tolerance for the Label Distribution Protocol (LDP)Current
February 2003
- RFC 3815Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)Current
June 2004
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?