RFC 4990: Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks
In plain English — editorial summary, not part of the RFC
This document clarifies the use of addresses in Generalized Multiprotocol Label Switching (GMPLS) networks. The aim is to facilitate interworking of GMPLS-capable Label Switching Routers (LSRs). The document is based on experience gained in implementation, interoperability testing, and deployment. The document describes how to interpret address and identifier fields within GMPLS protocols, and how to choose which addresses to set in those fields for specific control plane usage models. It also discusses how to handle IPv6 sources and destinations in the MPLS and GMPLS Traffic Engineering (TE) Management Information Base (MIB) modules. This document does not define new procedures or processes. Whenever this document makes requirements statements or recommendations, these are taken from normative text in the referenced RFCs. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4990
- Published
- September 2007
- Authors
- K. Shiomoto; R. Papneja; R. Rabbat
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5003Attachment Individual Identifier (AII) Types for AggregationCurrent
September 2007
- RFC 5004Avoid BGP Best Path Transitions from One External to AnotherCurrent
September 2007
- RFC 4974Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of CallsUpdated
August 2007
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 4971Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router InformationObsoleted
July 2007
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 5015Bidirectional Protocol Independent Multicast (BIDIR-PIM)Updated
October 2007
- RFC 4951Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover"Current
August 2007
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?