References from draft-murchison-jmap-sieve

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 14 Key words for use in RFCs to Indicate Requirement Levels
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 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 5228 Sieve: An Email Filtering Language
References Referenced by
Proposed Standard normatively references
RFC 5232 Sieve Email Filtering: Imap4flags Extension
References Referenced by
Proposed Standard informatively references
RFC 5435 Sieve Email Filtering: Extension for Notifications
References Referenced by
Proposed Standard normatively references
RFC 5463 Sieve Email Filtering: Ihave Extension
References Referenced by
Proposed Standard informatively references
RFC 5804 A Protocol for Remotely Managing Sieve Scripts
References Referenced by
Proposed Standard normatively references
RFC 6134 Sieve Extension: Externally Stored Lists
References Referenced by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8620 The JSON Meta Application Protocol (JMAP)
References Referenced by
Proposed Standard normatively references
STD 66 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references