References from draft-ietf-calext-jscalendar

This is an experimental product. 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
BCP 13	Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures Refs Ref'd by	Best Current Practice	normatively references
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
BCP 47	Tags for Identifying Languages Refs Ref'd by	Best Current Practice	normatively references
draft-apthorp-ical-tasks	Task Extensions to iCalendar Refs Ref'd by		informatively references
draft-ietf-calext-ical-relations	Support for iCalendar Relationships Refs Ref'd by		informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 2392	Content-ID and Message-ID Uniform Resource Locators Refs Ref'd by	Proposed Standard	normatively references
RFC 3339	Date and Time on the Internet: Timestamps Refs Ref'd by	Proposed Standard	normatively references
RFC 3986	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references
RFC 4122	A Universally Unique IDentifier (UUID) URN Namespace Refs Ref'd by	Proposed Standard	normatively references
RFC 4648	The Base16, Base32, and Base64 Data Encodings Refs Ref'd by	Proposed Standard	normatively references
RFC 4791	Calendaring Extensions to WebDAV (CalDAV) Refs Ref'd by	Proposed Standard	normatively references
RFC 5545	Internet Calendaring and Scheduling Core Object Specification (iCalendar) Refs Ref'd by	Proposed Standard	normatively references
RFC 5546	iCalendar Transport-Independent Interoperability Protocol (iTIP) Refs Ref'd by	Proposed Standard	normatively references
RFC 5646	Tags for Identifying Languages Refs Ref'd by	Best Current Practice	normatively references
RFC 5870	A Uniform Resource Identifier for Geographic Locations ('geo' URI) Refs Ref'd by	Proposed Standard	normatively references
RFC 6047	iCalendar Message-Based Interoperability Protocol (iMIP) Refs Ref'd by	Proposed Standard	normatively references
RFC 6838	Media Type Specifications and Registration Procedures Refs Ref'd by	Best Current Practice	normatively references
RFC 6901	JavaScript Object Notation (JSON) Pointer Refs Ref'd by	Proposed Standard	normatively references
RFC 7265	jCal: The JSON Format for iCalendar Refs Ref'd by	Proposed Standard	normatively references
RFC 7493	The I-JSON Message Format Refs Ref'd by	Proposed Standard	normatively references
RFC 7529	Non-Gregorian Recurrence Rules in the Internet Calendaring and Scheduling Core Object Specification (iCalendar) Refs Ref'd by	Proposed Standard	normatively references
RFC 7808	Time Zone Data Distribution Service Refs Ref'd by	Proposed Standard	normatively references
RFC 7986	New Properties for iCalendar Refs Ref'd by	Proposed Standard	normatively references
RFC 8259	The JavaScript Object Notation (JSON) Data Interchange Format Refs Ref'd by	Internet Standard	normatively references
RFC 8288	Web Linking Refs Ref'd by	Proposed Standard	normatively references
STD 66	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references
STD 90	The JavaScript Object Notation (JSON) Data Interchange Format Refs Ref'd by	Internet Standard	normatively references