Skip to main content

References from draft-newton-json-content-rules

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
References Referenced by
Possible Reference
RFC 1166 Internet numbers
References Referenced by
Informational normatively references
RFC 3339 Date and Time on the Internet: Timestamps
References Referenced by
Proposed Standard normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 4234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Draft Standard normatively references
RFC 4627 The application/json Media Type for JavaScript Object Notation (JSON)
References Referenced by
Informational Possible Reference
RFC 4648 The Base16, Base32, and Base64 Data Encodings
References Referenced by
Proposed Standard normatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard Possible Reference
RFC 5322 Internet Message Format
References Referenced by
Draft Standard normatively references
RFC 5952 A Recommendation for IPv6 Address Text Representation
References Referenced by
Proposed Standard normatively references
RFC 7159 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced 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
References Referenced by
Informational Possible Reference
STD 66
References Referenced by
normatively references