References from draft-ietf-calext-jscalendar

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 13 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by
Best Current Practice normatively references
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
BCP 26 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
BCP 47 Tags for Identifying Languages
References Referenced by
Best Current Practice normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2392 Content-ID and Message-ID Uniform Resource Locators
References Referenced by
Proposed Standard normatively references
RFC 2397 The "data" URL scheme
References Referenced by
Proposed Standard normatively references
RFC 3339 Date and Time on the Internet: Timestamps
References Referenced by
Proposed Standard normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 4122 A Universally Unique IDentifier (UUID) URN Namespace
References Referenced by
Proposed Standard normatively references
RFC 4589 Location Types Registry
References Referenced by
Proposed Standard normatively references
RFC 4648 The Base16, Base32, and Base64 Data Encodings
References Referenced by
Proposed Standard normatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
RFC 5545 Internet Calendaring and Scheduling Core Object Specification (iCalendar)
References Referenced by
Proposed Standard normatively references
RFC 5546 iCalendar Transport-Independent Interoperability Protocol (iTIP)
References Referenced by
Proposed Standard normatively references
RFC 5646 Tags for Identifying Languages
References Referenced by
Best Current Practice normatively references
RFC 5870 A Uniform Resource Identifier for Geographic Locations ('geo' URI)
References Referenced by
Proposed Standard normatively references
RFC 6047 iCalendar Message-Based Interoperability Protocol (iMIP)
References Referenced by
Proposed Standard normatively references
RFC 6376 DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Internet Standard informatively references
RFC 6838 Media Type Specifications and Registration Procedures
References Referenced by
Best Current Practice normatively references
RFC 6901 JavaScript Object Notation (JSON) Pointer
References Referenced by
Proposed Standard normatively references
RFC 7265 jCal: The JSON Format for iCalendar
References Referenced by
Proposed Standard informatively references
RFC 7493 The I-JSON Message Format
References Referenced by
Proposed Standard normatively references
RFC 7529 Non-Gregorian Recurrence Rules in the Internet Calendaring and Scheduling Core Object Specification (iCalendar)
References Referenced by
Proposed Standard normatively references
RFC 7808 Time Zone Data Distribution Service
References Referenced by
Proposed Standard normatively references
RFC 7986 New Properties for iCalendar
References Referenced by
Proposed Standard informatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard normatively references
RFC 8288 Web Linking
References Referenced by
Proposed Standard normatively references
STD 66 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
STD 68 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
STD 76 DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Internet Standard informatively references
STD 90 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard normatively references