References to RFC 2216
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 9275 |
An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector
References Referenced by |
Experimental | informatively references | |
RFC 2210 |
The Use of RSVP with IETF Integrated Services
References Referenced by |
Proposed Standard | Reference | |
RFC 2211 |
Specification of the Controlled-Load Network Element Service
References Referenced by |
Proposed Standard | Reference | |
RFC 2212 |
Specification of Guaranteed Quality of Service
References Referenced by |
Proposed Standard | Reference | |
RFC 2215 |
General Characterization Parameters for Integrated Service Network Elements
References Referenced by |
Proposed Standard | Reference | |
RFC 2381 |
Interoperation of Controlled-Load Service and Guaranteed Service with ATM
References Referenced by |
Proposed Standard | Reference | |
RFC 2816 |
A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies
References Referenced by |
Informational | Reference | |
RFC 2997 |
Specification of the Null Service Type
References Referenced by |
Proposed Standard | Reference | |
RFC 3006 |
Integrated Services in the Presence of Compressible Flows
References Referenced by |
Proposed Standard | Reference | |
RFC 3148 |
A Framework for Defining Empirical Bulk Transfer Capacity Metrics
References Referenced by |
Informational | Reference | |
RFC 3198 |
Terminology for Policy-Based Management
References Referenced by |
Informational | Reference | |
RFC 3272 |
Overview and Principles of Internet Traffic Engineering
References Referenced by |
Informational | Reference |