References from draft-jennings-core-senml
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 13 |
References Referenced by |
normatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
BCP 26 |
References Referenced by |
normatively references | ||
draft-arkko-core-dev-urn |
Uniform Resource Names for Device Identifiers
References Referenced by |
informatively references | ||
draft-greevenbosch-appsawg-cbor-cddl |
Concise data definition language (CDDL): a notational convention to express CBOR data structures
References Referenced by |
Informational | informatively references | |
draft-ietf-core-links-json |
Representing Constrained RESTful Environments (CoRE) Link Format in JSON and CBOR
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2141 |
URN Syntax
References Referenced by |
Proposed Standard | informatively 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 4122 |
A Universally Unique IDentifier (UUID) URN Namespace
References Referenced by |
Proposed Standard | informatively references | |
RFC 4627 |
The application/json Media Type for JavaScript Object Notation (JSON)
References Referenced by |
Informational | normatively references | |
RFC 4648 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Proposed Standard | normatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 5952 |
A Recommendation for IPv6 Address Text Representation
References Referenced by |
Proposed Standard | informatively references | |
RFC 6690 |
Constrained RESTful Environments (CoRE) Link Format
References Referenced by |
Proposed Standard | informatively references | |
RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
RFC 7049 |
Concise Binary Object Representation (CBOR)
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 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7303 |
XML Media Types
References Referenced by |
Proposed Standard | normatively references | |
RFC 7721 |
Security and Privacy Considerations for IPv6 Address Generation Mechanisms
References Referenced by |
Informational | informatively references | |
STD 66 |
References Referenced by |
informatively references |