References from draft-reddy-dots-home-network
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 122 |
Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan References Referenced by |
Best Current Practice | informatively references | |
BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
draft-ietf-dots-multihoming |
Multi-homing Deployment Considerations for Distributed-Denial-of-Service Open Threat Signaling (DOTS) References Referenced by |
informatively references | ||
draft-ietf-dots-requirements |
DDoS Open Threat Signaling (DOTS) Requirements References Referenced by |
Informational | informatively references | |
draft-ietf-dots-server-discovery |
DDoS Open Threat Signaling (DOTS) Agent Discovery References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-dots-signal-channel |
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-dots-use-cases |
Use cases for DDoS Open Threat Signaling References Referenced by |
Informational | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 3688 |
The IETF XML Registry References Referenced by |
Best Current Practice | normatively references | |
RFC 4340 |
Datagram Congestion Control Protocol (DCCP) References Referenced by |
Proposed Standard | informatively references | |
RFC 4632 |
Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan References Referenced by |
Best Current Practice | informatively 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 5575 |
Dissemination of Flow Specification Rules References Referenced by |
Proposed Standard | informatively references | |
RFC 6973 |
Privacy Considerations for Internet Protocols References Referenced by |
Informational | informatively references | |
RFC 7596 |
Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture References Referenced by |
Proposed Standard | informatively references | |
RFC 7597 |
Mapping of Address and Port with Encapsulation (MAP-E) References Referenced by |
Proposed Standard | informatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language References Referenced by |
Proposed Standard | normatively references | |
RFC 8071 |
NETCONF Call Home and RESTCONF Call Home References Referenced by |
Proposed Standard | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by |
Best Current Practice | normatively references | |
RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3 References Referenced by |
Proposed Standard | normatively references | |
RFC 8512 |
A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT) References Referenced by |
Proposed Standard | informatively references | |
RFC 8513 |
A YANG Data Model for Dual-Stack Lite (DS-Lite) References Referenced by |
Proposed Standard | informatively references |