References from draft-newton-json-content-rules

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
draft-cordell-jcr-co-constraints Co-Constraints for JSON Content Rules
Refs Ref'd by
Possible Reference
RFC 1166 Internet numbers
Refs Ref'd by
Informational normatively references
RFC 3339 Date and Time on the Internet: Timestamps
Refs Ref'd by
Proposed Standard normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
Refs Ref'd by
Internet Standard normatively references
RFC 4234 Augmented BNF for Syntax Specifications: ABNF
Refs Ref'd by
Draft Standard normatively references
RFC 4627 The application/json Media Type for JavaScript Object Notation (JSON)
Refs Ref'd by
Informational Possible Reference
RFC 4648 The Base16, Base32, and Base64 Data Encodings
Refs Ref'd by
Proposed Standard normatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
Refs Ref'd by
Internet Standard Possible Reference
RFC 5322 Internet Message Format
Refs Ref'd by
Draft Standard normatively references
RFC 5952 A Recommendation for IPv6 Address Text Representation
Refs Ref'd by
Proposed Standard normatively references
RFC 7159 The JavaScript Object Notation (JSON) Data Interchange Format
Refs Ref'd by
Proposed Standard normatively references
RFC 7492 Analysis of Bidirectional Forwarding Detection (BFD) Security According to the Keying and Authentication for Routing Protocols (KARP) Design Guidelines
Refs Ref'd by
Informational Possible Reference
STD 66 Uniform Resource Identifier (URI): Generic Syntax
Refs Ref'd by
Internet Standard normatively references