References from draft-ietf-dtn-ari
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 |
|---|---|---|---|---|
| draft-ietf-dtn-amm |
DTNMA Application Management Model (AMM) and Data Models
References Referenced by |
normatively references | ||
| draft-ietf-dtn-amp |
DTNMA Asynchronous Management Protocol (AMP)
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2483 |
URI Resolution Services Necessary for URN Resolution
References Referenced by |
Experimental | normatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3629 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4648 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4838 |
Delay-Tolerant Networking Architecture
References Referenced by |
Informational | informatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
| RFC 7320 |
URI Design and Ownership
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7595 |
Guidelines and Registration Procedures for URI Schemes
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively 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 8610 |
Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8742 |
Concise Binary Object Representation (CBOR) Sequences
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8792 |
Handling Long Lines in Content of Internet-Drafts and RFCs
References Referenced by |
Informational | informatively references | |
| RFC 8820 |
URI Design and Ownership
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8943 |
Concise Binary Object Representation (CBOR) Tags for Date
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8949 |
Concise Binary Object Representation (CBOR)
References Referenced by |
Internet Standard | normatively references | |
| RFC 9171 |
Bundle Protocol Version 7
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9675 |
Delay-Tolerant Networking Management Architecture (DTNMA)
References Referenced by |
Informational | informatively references |