References to rfc5988

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-dunglas-mercure The Mercure Protocol
References Referenced by
normatively references
draft-dunglas-vulcain The Vulcain Protocol
References Referenced by
normatively references
draft-ietf-calext-ical-relations Support for iCalendar Relationships
References Referenced by
normatively references
draft-ietf-calext-icalendar-series Support for Series in iCalendar
References Referenced by
Proposed Standard normatively references
draft-ietf-calext-serverside-subscriptions Serverside Subscriptions
References Referenced by
normatively references
draft-ietf-calext-subscription-upgrade Calendar subscription upgrades
References Referenced by
Proposed Standard normatively references
draft-irtf-t2trg-rest-iot RESTful Design for Internet of Things Systems
References Referenced by
Informational normatively references
draft-mcd-identifier-access-responce JSON Responses for the Industrial Internet Identifier Data Access Protocol (IIIDAP)
References Referenced by
normatively references
RFC 5989 A SIP Event Package for Subscribing to Changes to an HTTP Resource
References Referenced by
Proposed Standard normatively references
RFC 6249 Metalink/HTTP: Mirrors and Hashes
References Referenced by
Proposed Standard normatively references
RFC 6415 Web Host Metadata
References Referenced by
Proposed Standard normatively references
RFC 6573 The Item and Collection Link Relations
References Referenced by
Informational normatively references
RFC 6579 The 'disclosure' Link Relation Type
References Referenced by
Informational normatively references
RFC 6596 The Canonical Link Relation
References Referenced by
Informational normatively references
RFC 6690 Constrained RESTful Environments (CoRE) Link Format
References Referenced by
Proposed Standard normatively references
RFC 6861 The "create-form" and "edit-form" Link Relations
References Referenced by
Informational normatively references
RFC 6892 The 'describes' Link Relation Type
References Referenced by
Informational normatively references
RFC 6903 Additional Link Relation Types
References Referenced by
Informational normatively references
RFC 6906 The 'profile' Link Relation Type
References Referenced by
Informational normatively references
RFC 7033 WebFinger
References Referenced by
Proposed Standard normatively references
RFC 7089 HTTP Framework for Time-Based Access to Resource States -- Memento
References Referenced by
Informational normatively references
RFC 7252 The Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7395 An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for WebSocket
References Referenced by
Proposed Standard normatively references
RFC 7641 Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7725 An HTTP Status Code to Report Legal Obstacles
References Referenced by
Proposed Standard normatively references
RFC 8030 Generic Event Delivery Using HTTP Push
References Referenced by
Proposed Standard normatively references
RFC 8040 RESTCONF Protocol
References Referenced by
Proposed Standard 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
draft-wilde-linkset Linkset: Media Types and a Link Relation Type for Link Sets
References Referenced by
informatively references
RFC 6919 Further Key Words for Use in RFCs to Indicate Requirement Levels
References Referenced by
Experimental informatively references
RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by
Proposed Standard informatively references
RFC 7320 URI Design and Ownership
References Referenced by
Best Current Practice informatively references
RFC 7483 JSON Responses for the Registration Data Access Protocol (RDAP)
References Referenced by
Proposed Standard informatively references
RFC 7565 The 'acct' URI Scheme
References Referenced by
Proposed Standard informatively references
RFC 7807 Problem Details for HTTP APIs
References Referenced by
Proposed Standard informatively references
RFC 8187 Indicating Character Encoding and Language for HTTP Header Field Parameters
References Referenced by
Proposed Standard informatively references
RFC 8288 Web Linking
References Referenced by
Proposed Standard informatively references