References from draft-jimenez-p2psip-coap-reload

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 14	References Referenced by		normatively references
BCP 26	References Referenced by		informatively references
draft-ietf-core-resource-directory	Constrained RESTful Environments (CoRE) Resource Directory References Referenced by	Proposed Standard	informatively references
draft-ietf-p2psip-concepts	Concepts and Terminology for Peer-to-Peer SIP (P2PSIP) References Referenced by	Informational	informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
RFC 3986	Uniform Resource Identifier (URI): Generic Syntax References Referenced by	Internet Standard	normatively references
RFC 5226	Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by	Best Current Practice	informatively references
RFC 5280	Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile References Referenced by	Proposed Standard	normatively references
RFC 6690	Constrained RESTful Environments (CoRE) Link Format References Referenced by	Proposed Standard	normatively references
RFC 6940	REsource LOcation And Discovery (RELOAD) Base Protocol References Referenced by	Proposed Standard	normatively references
RFC 7228	Terminology for Constrained-Node Networks References Referenced by	Informational	informatively references
RFC 7252	The Constrained Application Protocol (CoAP) References Referenced by	Proposed Standard	normatively references
STD 66	References Referenced by		normatively references