metasystema.org
CurrentINFORMATIONALIETF stream

RFC 3386: Network Hierarchy and Multilayer Survivability

In plain English — editorial summary, not part of the RFC

This document is the deliverable out of the Network Hierarchy and Survivability Techniques Design Team established within the Traffic Engineering Working Group. This team collected and documented current and near term requirements for survivability and hierarchy in service provider environments. For clarity, an expanded set of definitions is included. The team determined that there appears to be a need to define a small set of interoperable survivability approaches in packet and non-packet networks. Suggested approaches include path-based as well as one that repairs connections in proximity to the network fault. They operate primarily at a single network layer. For hierarchy, there did not appear to be a driving near-term need for work on 'vertical hierarchy,' defined as communication between network layers such as TDM/optical and MPLS. In particular, instead of direct exchange of signaling and routing between vertical layers, some looser form of coordination and communication, such as the specification of hold-off timers, is a nearer term need. For 'horizontal hierarchy' in data networks, there are several pressing needs. The requirement is to be able to set up many LSPs in a service provider network with hierarchical IGP. This is necessary to support layer 2 and layer 3 VPN services that require edge-to- edge signaling across a core network. Please send comments to te-wg@ops.ietf.org

Document record

Document ID
RFC3386
Published
November 2002
Authors
W. Lai; D. McDysan
Status
INFORMATIONAL
Stream
IETF
Area
sub
Pages
27
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3386-network-hierarchy-and-multilayer-survivability