Skip to main content

References from draft-mailschema-mail-action-protocol

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
draft-ietf-sml-structured-email Structured Email
References Referenced by
Proposed Standard normatively references
RFC 2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by
Draft Standard normatively references
RFC 2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by
Draft Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2387 The MIME Multipart/Related Content-type
References Referenced by
Proposed Standard normatively references
RFC 5322 Internet Message Format
References Referenced by
Draft Standard normatively references
RFC 5646 Tags for Identifying Languages
References Referenced by
Best Current Practice normatively references
RFC 5890 Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework
References Referenced by
Proposed Standard normatively references
RFC 6234 US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)
References Referenced by
Informational normatively references
RFC 6376 DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Internet Standard normatively references
RFC 6454 The Web Origin Concept
References Referenced by
Proposed Standard normatively references
RFC 6531 SMTP Extension for Internationalized Email
References Referenced by
Proposed Standard normatively references
RFC 7493 The I-JSON Message Format
References Referenced by
Proposed Standard normatively references
RFC 7942 Improving Awareness of Running Code: The Implementation Status Section
References Referenced by
Best Current Practice informatively references
RFC 8058 Signaling One-Click Functionality for List Email Headers
References Referenced by
Proposed Standard informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8301 Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM)
References Referenced by
Proposed Standard normatively references
RFC 8463 A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)
References Referenced by
Proposed Standard normatively references
RFC 8601 Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard normatively references
RFC 8707 Resource Indicators for OAuth 2.0
References Referenced by
Proposed Standard normatively references
RFC 8785 JSON Canonicalization Scheme (JCS)
References Referenced by
Informational normatively references
RFC 8792 Handling Long Lines in Content of Internet-Drafts and RFCs
References Referenced by
Informational informatively references
RFC 9110 HTTP Semantics
References Referenced by
Internet Standard normatively references
RFC 9457 Problem Details for HTTP APIs
References Referenced by
Proposed Standard informatively references
RFC 9562 Universally Unique IDentifiers (UUIDs)
References Referenced by
Proposed Standard normatively references
RFC 9700 Best Current Practice for OAuth 2.0 Security
References Referenced by
Best Current Practice normatively references
RFC 9728 OAuth 2.0 Protected Resource Metadata
References Referenced by
Proposed Standard informatively references
RFC 9989 Domain-Based Message Authentication, Reporting, and Conformance (DMARC)
References Referenced by
Proposed Standard normatively references