Skip to main content

References to draft-ietf-forces-protocol

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 5811
As rfc5810
SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) Protocol
References Referenced by
Proposed Standard normatively references
RFC 5812
As rfc5810
Forwarding and Control Element Separation (ForCES) Forwarding Element Model
References Referenced by
Proposed Standard normatively references
RFC 5813
As rfc5810
Forwarding and Control Element Separation (ForCES) MIB
References Referenced by
Proposed Standard normatively references
RFC 6041
As rfc5810
Forwarding and Control Element Separation (ForCES) Applicability Statement
References Referenced by
Informational normatively references
RFC 6053
As rfc5810
Implementation Report for Forwarding and Control Element Separation (ForCES)
References Referenced by
Informational normatively references
RFC 6369
As rfc5810
Forwarding and Control Element Separation (ForCES) Implementation Experience
References Referenced by
Informational normatively references
RFC 6956
As rfc5810
Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) Library
References Referenced by
Proposed Standard normatively references
RFC 6984
As rfc5810
Interoperability Report for Forwarding and Control Element Separation (ForCES)
References Referenced by
Informational normatively references
RFC 7121
As rfc5810
High Availability within a Forwarding and Control Element Separation (ForCES) Network Element
References Referenced by
Proposed Standard normatively references
RFC 7391
As rfc5810
Forwarding and Control Element Separation (ForCES) Protocol Extensions
References Referenced by
Proposed Standard normatively references
RFC 7408
As rfc5810
Forwarding and Control Element Separation (ForCES) Model Extension
References Referenced by
Proposed Standard normatively references
RFC 7409
As rfc5810
Forwarding and Control Element Separation (ForCES) Packet Parallelization
References Referenced by
Experimental normatively references
RFC 7729
As rfc5810
Forwarding and Control Element Separation (ForCES) Logical Functional Block (LFB) Subsidiary Management
References Referenced by
Proposed Standard normatively references
RFC 8013
As rfc5810
Forwarding and Control Element Separation (ForCES) Inter-FE Logical Functional Block (LFB)
References Referenced by
Proposed Standard normatively references
draft-song-opsawg-ifit-framework
As rfc5810
Framework for In-situ Flow Information Telemetry
References Referenced by
informatively references
RFC 7149
As rfc5810
Software-Defined Networking: A Perspective from within a Service Provider Environment
References Referenced by
Informational informatively references
RFC 7389
As rfc5810
Separation of Control and User Plane for Proxy Mobile IPv6
References Referenced by
Proposed Standard informatively references
RFC 7426
As rfc5810
Software-Defined Networking (SDN): Layers and Architecture Terminology
References Referenced by
Informational informatively references
RFC 7491
As rfc5810
A PCE-Based Architecture for Application-Based Network Operations
References Referenced by
Informational informatively references
RFC 8568
As rfc5810
Network Virtualization Research Challenges
References Referenced by
Informational informatively references