Skip to main content

References from draft-farrkingel-pce-questions

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
draft-farrkingel-pce-abno-architecture A PCE-Based Architecture for Application-Based Network Operations
References Referenced by
Informational informatively references
draft-ietf-alto-server-discovery Application-Layer Traffic Optimization (ALTO) Server Discovery
References Referenced by
Proposed Standard informatively references
draft-ietf-idr-ls-distribution North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by
Proposed Standard informatively references
draft-ietf-karp-routing-tcp-analysis Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
References Referenced by
Informational informatively references
draft-ietf-pce-stateful-pce Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
References Referenced by
Proposed Standard informatively references
RFC 3060 Policy Core Information Model -- Version 1 Specification
References Referenced by
Proposed Standard informatively references
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels
References Referenced by
Proposed Standard informatively references
RFC 3460 Policy Core Information Model (PCIM) Extensions
References Referenced by
Proposed Standard informatively references
RFC 3630 Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by
Proposed Standard informatively references
RFC 3812 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)
References Referenced by
Proposed Standard informatively references
RFC 4203 OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by
Proposed Standard informatively references
RFC 4397 A Lexicography for the Interpretation of Generalized Multiprotocol Label Switching (GMPLS) Terminology within the Context of the ITU-T's Automatically Switched Optical Network (ASON) Architecture
References Referenced by
Informational informatively references
RFC 4655 A Path Computation Element (PCE)-Based Architecture
References Referenced by
Informational normatively references
RFC 4657 Path Computation Element (PCE) Communication Protocol Generic Requirements
References Referenced by
Informational informatively references
RFC 4674 Requirements for Path Computation Element (PCE) Discovery
References Referenced by
Informational informatively references
RFC 4726 A Framework for Inter-Domain Multiprotocol Label Switching Traffic Engineering
References Referenced by
Informational informatively references
RFC 4802 Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base
References Referenced by
Proposed Standard informatively references
RFC 4848 Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)
References Referenced by
Proposed Standard informatively references
RFC 4974 Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls
References Referenced by
Proposed Standard informatively references
RFC 5088 OSPF Protocol Extensions for Path Computation Element (PCE) Discovery
References Referenced by
Proposed Standard informatively references
RFC 5089 IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery
References Referenced by
Proposed Standard informatively references
RFC 5152 A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
References Referenced by
Proposed Standard informatively references
RFC 5212 Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
References Referenced by
Informational informatively references
RFC 5305 IS-IS Extensions for Traffic Engineering
References Referenced by
Proposed Standard informatively references
RFC 5307 IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by
Proposed Standard informatively references
RFC 5394 Policy-Enabled Path Computation Framework
References Referenced by
Informational informatively references
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by
Proposed Standard normatively references
RFC 5441 A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched Paths
References Referenced by
Proposed Standard informatively references
RFC 5557 Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization
References Referenced by
Proposed Standard informatively references
RFC 5623 Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering
References Referenced by
Informational normatively references
RFC 6006 Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
References Referenced by
Proposed Standard informatively references
RFC 6241 Network Configuration Protocol (NETCONF)
References Referenced by
Proposed Standard informatively references
RFC 6805 The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLS
References Referenced by
Informational normatively references