References from RFC 9244
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 |
---|---|---|---|---|
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2330 |
Framework for IP Performance Metrics
References Referenced by |
Informational | informatively references | |
RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
RFC 4732 |
Internet Denial-of-Service Considerations
References Referenced by |
Informational | informatively references | |
RFC 4960 |
Stream Control Transmission Protocol
References Referenced by |
Proposed Standard | informatively references | |
RFC 5612 |
Enterprise Number for Documentation Use
References Referenced by |
Informational | informatively references | |
RFC 5646 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | normatively references | |
RFC 6020 |
YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6991 |
Common YANG Data Types
References Referenced by |
Proposed Standard | normatively references | |
RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7641 |
Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language
References Referenced by |
Proposed Standard | normatively references | |
RFC 7959 |
Block-Wise Transfers in the Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7970 |
The Incident Object Description Exchange Format Version 2
References Referenced by |
Proposed Standard | normatively references | |
RFC 8040 |
RESTCONF Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8340 |
YANG Tree Diagrams
References Referenced by |
Best Current Practice | informatively references | |
RFC 8345 |
A YANG Data Model for Network Topologies
References Referenced by |
Proposed Standard | normatively references | |
RFC 8525 |
YANG Library
References Referenced by |
Proposed Standard | informatively references | |
RFC 8612 |
DDoS Open Threat Signaling (DOTS) Requirements
References Referenced by |
Informational | informatively references | |
RFC 8783 |
Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
References Referenced by |
Proposed Standard | normatively references | |
RFC 8791 |
YANG Data Structure Extensions
References Referenced by |
Proposed Standard | normatively references | |
RFC 8811 |
DDoS Open Threat Signaling (DOTS) Architecture
References Referenced by |
Informational | informatively references | |
RFC 8903 |
Use Cases for DDoS Open Threat Signaling
References Referenced by |
Informational | informatively references | |
RFC 8949 |
Concise Binary Object Representation (CBOR)
References Referenced by |
Internet Standard | normatively references | |
RFC 9132 |
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
References Referenced by |
Proposed Standard | normatively references | |
RFC 9133 |
Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
References Referenced by |
Proposed Standard | informatively references |