References from draft-haleplidis-bcause-forces-gap-analysis
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.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
BCP 14 |
References Referenced by |
informatively references | ||
draft-cuspdt-rtgwg-cu-separation-infor-model |
Information Model of Control-Plane and User-Plane Separation BNG
References Referenced by |
normatively references | ||
draft-cuspdt-rtgwg-cusp-requirements |
Requirements for Control Plane and User Plane Separated BNG Protocol
References Referenced by |
normatively references | ||
draft-ietf-quic-transport |
QUIC: A UDP-Based Multiplexed and Secure Transport
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | informatively references | |
RFC 3746 |
Forwarding and Control Element Separation (ForCES) Framework
References Referenced by |
Informational | normatively references | |
RFC 5810 |
Forwarding and Control Element Separation (ForCES) Protocol Specification
References Referenced by |
Proposed Standard | normatively references | |
RFC 5811 |
SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 5812 |
Forwarding and Control Element Separation (ForCES) Forwarding Element Model
References Referenced by |
Proposed Standard | normatively references | |
RFC 7121 |
High Availability within a Forwarding and Control Element Separation (ForCES) Network Element
References Referenced by |
Proposed Standard | normatively references |