Skip to main content

References to rfc8288

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 CoAP Protocol Indication
References Referenced by
normatively references
draft-engi-siptrunkingcapability-link The 'sipTrunkingCapability' Link Relation Type
References Referenced by
normatively references
draft-ietf-calext-ical-relations Support for iCalendar Relationships
References Referenced by
Proposed Standard normatively references
draft-ietf-calext-subscription-upgrade Calendar subscription upgrades
References Referenced by
Proposed Standard normatively references
draft-ietf-core-observe-multicast-notifications Observe Notifications as CoAP Multicast Responses
References Referenced by
normatively references
draft-ietf-core-oscore-edhoc Profiling EDHOC for CoAP and OSCORE
References Referenced by
normatively references
draft-ietf-httpbis-bcp56bis Building Protocols with HTTP
References Referenced by
Best Current Practice normatively references Downref
draft-ietf-httpbis-retrofit Retrofit Structured Fields for HTTP
References Referenced by
Proposed Standard normatively references
draft-ietf-regext-rdap-jscontact Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses
References Referenced by
Proposed Standard normatively references
draft-ietf-sacm-coswid Concise Software Identification Tags
References Referenced by
Proposed Standard normatively references
draft-ietf-wish-whip WebRTC-HTTP ingestion protocol (WHIP)
References Referenced by
normatively references
draft-irtf-t2trg-rest-iot Guidance on RESTful Design for Internet of Things Systems
References Referenced by
Informational normatively references
draft-koster-rep Robots Exclusion Protocol
References Referenced by
Proposed Standard normatively references
draft-spinosa-urn-lex A Uniform Resource Name (URN) Namespace for Sources of Law (LEX)
References Referenced by
Informational normatively references
RFC 8555 Automatic Certificate Management Environment (ACME)
References Referenced by
Proposed Standard normatively references
RFC 8574 cite-as: A Link Relation to Convey a Preferred URI for Referencing
References Referenced by
Informational normatively references
RFC 8594 The Sunset HTTP Header Field
References Referenced by
Informational normatively references
RFC 8613 Object Security for Constrained RESTful Environments (OSCORE)
References Referenced by
Proposed Standard normatively references
RFC 8631 Link Relation Types for Web Services
References Referenced by
Informational normatively references
RFC 8977 Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging
References Referenced by
Proposed Standard normatively references
RFC 8982 Registration Data Access Protocol (RDAP) Partial Response
References Referenced by
Proposed Standard normatively references
RFC 8984 JSCalendar: A JSON Representation of Calendar Data
References Referenced by
Proposed Standard normatively references
RFC 9083 JSON Responses for the Registration Data Access Protocol (RDAP)
References Referenced by
Internet Standard normatively references Downref
RFC 9176 Constrained RESTful Environments (CoRE) Resource Directory
References Referenced by
Proposed Standard normatively references
draft-ietf-core-coral The Constrained RESTful Application Language (CoRAL)
References Referenced by
informatively references
draft-ietf-core-href Constrained Resource Identifiers
References Referenced by
informatively references
draft-ietf-httpapi-rfc7807bis Problem Details for HTTP APIs
References Referenced by
informatively references
draft-ietf-httpbis-semantics HTTP Semantics
References Referenced by
Internet Standard informatively references
RFC 8336 The ORIGIN HTTP/2 Frame
References Referenced by
Proposed Standard informatively references
RFC 8820 URI Design and Ownership
References Referenced by
Best Current Practice informatively references