References from draft-ietf-dots-data-channel

This is an experimental product. 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.

Reference type help

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 normatively references
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
BCP 195 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by
Best Current Practice normatively references
BCP 215 YANG Tree Diagrams
References Referenced by
Best Current Practice informatively references
BCP 219 DNS Terminology
References Referenced by
Best Current Practice informatively references
draft-ietf-dots-architecture Distributed-Denial-of-Service Open Threat Signaling (DOTS) Architecture
References Referenced by
Informational informatively references
draft-ietf-dots-server-discovery Distributed-Denial-of-Service 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-netconf-restconf-client-server RESTCONF Client and Server Models
References Referenced by
informatively references
RFC 1122 Requirements for Internet Hosts - Communication Layers
References Referenced by
Internet Standard 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 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard informatively references
RFC 4034 Resource Records for the DNS Security Extensions
References Referenced by
Proposed Standard informatively 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 normatively 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 5925 The TCP Authentication Option
References Referenced by
Proposed Standard informatively references
RFC 6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
References Referenced by
Proposed Standard normatively references
RFC 6520 Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Heartbeat Extension
References Referenced by
Proposed Standard informatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by
Proposed Standard normatively references
RFC 7525 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by
Best Current Practice normatively references
RFC 7858 Specification for DNS over Transport Layer Security (TLS)
References Referenced by
Proposed Standard informatively references
RFC 7950 The YANG 1.1 Data Modeling Language
References Referenced by
Proposed Standard normatively references
RFC 7951 JSON Encoding of Data Modeled with YANG
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 8259 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard normatively references
RFC 8340 YANG Tree Diagrams
References Referenced by
Best Current Practice informatively references
RFC 8484 DNS Queries over HTTPS (DoH)
References Referenced by
Proposed Standard informatively references
RFC 8499 DNS Terminology
References Referenced by
Best Current Practice informatively references
RFC 8519 YANG Data Model for Network Access Control Lists (ACLs)
References Referenced by
Proposed Standard normatively references
RFC 8612 DDoS Open Threat Signaling (DOTS) Requirements
References Referenced by
Informational informatively references
STD 3 Requirements for Internet Hosts - Application and Support
References Referenced by
Internet Standard informatively references
STD 66 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard informatively references
STD 90 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard normatively references