References to draft-nottingham-rfc5988bis

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
draft-amsuess-core-transport-indication
As rfc8288
CoAP Protocol Indication
References Referenced by
normatively references
draft-amundsen-richardson-foster-alps
As rfc8288
Application-Level Profile Semantics (ALPS)
References Referenced by
normatively references
draft-ietf-calext-ical-relations
As rfc8288
Support for iCalendar Relationships
References Referenced by
Proposed Standard normatively references
draft-ietf-core-dynlink
As rfc8288
Dynamic Resource Linking for Constrained RESTful Environments
References Referenced by
normatively references
draft-ietf-core-observe-multicast-notifications
As rfc8288
Observe Notifications as CoAP Multicast Responses
References Referenced by
normatively references
draft-ietf-core-resource-directory
As rfc8288
CoRE Resource Directory
References Referenced by
Proposed Standard normatively references
draft-ietf-httpapi-deprecation-header
As rfc8288
The Deprecation HTTP Header Field
References Referenced by
normatively references
draft-ietf-httpapi-linkset
As rfc8288
Linkset: Media Types and a Link Relation Type for Link Sets
References Referenced by
Internet Standard normatively references Downref
draft-ietf-httpbis-bcp56bis
As rfc8288
Building Protocols with HTTP
References Referenced by
Best Current Practice normatively references Downref
draft-ietf-regext-rdap-jscontact
As rfc8288
Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses
References Referenced by
normatively references
draft-ietf-sacm-coswid
As rfc8288
Concise Software Identification Tags
References Referenced by
Proposed Standard normatively references
draft-irtf-t2trg-rest-iot
As rfc8288
RESTful Design for Internet of Things Systems
References Referenced by
Informational normatively references
draft-koster-rep
As rfc8288
Robots Exclusion Protocol
References Referenced by
Informational normatively references
draft-spinosa-urn-lex
As rfc8288
A Uniform Resource Name (URN) Namespace for Sources of Law (LEX)
References Referenced by
Informational normatively references
RFC 8555
As rfc8288
Automatic Certificate Management Environment (ACME)
References Referenced by
Proposed Standard normatively references
RFC 8574
As rfc8288
cite-as: A Link Relation to Convey a Preferred URI for Referencing
References Referenced by
Informational normatively references
RFC 8594
As rfc8288
The Sunset HTTP Header Field
References Referenced by
Informational normatively references
RFC 8613
As rfc8288
Object Security for Constrained RESTful Environments (OSCORE)
References Referenced by
Proposed Standard normatively references
RFC 8631
As rfc8288
Link Relation Types for Web Services
References Referenced by
Informational normatively references
RFC 8977
As rfc8288
Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging
References Referenced by
Proposed Standard normatively references
RFC 8982
As rfc8288
Registration Data Access Protocol (RDAP) Partial Response
References Referenced by
Proposed Standard normatively references
RFC 8984
As rfc8288
JSCalendar: A JSON Representation of Calendar Data
References Referenced by
Proposed Standard normatively references
RFC 9083
As rfc8288
JSON Responses for the Registration Data Access Protocol (RDAP)
References Referenced by
Internet Standard normatively references Downref
draft-ietf-core-href
As rfc8288
Constrained Resource Identifiers
References Referenced by
informatively references
draft-ietf-httpbis-semantics
As rfc8288
HTTP Semantics
References Referenced by
Proposed Standard informatively references
draft-svensson-profiled-representations
As rfc8288
Indicating, Discovering, Negotiating, and Writing Profiled Representations
References Referenced by
informatively references
RFC 8336
As rfc8288
The ORIGIN HTTP/2 Frame
References Referenced by
Proposed Standard informatively references
RFC 8820
As rfc8288
URI Design and Ownership
References Referenced by
Best Current Practice informatively references