[go: up one dir, main page]

Skip to main content

References from draft-tishkin-hmtp

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
RFC 2034 SMTP Service Extension for Returning Enhanced Error Codes
References Referenced by
Proposed Standard informatively 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 informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3030 SMTP Service Extensions for Transmission of Large and Binary MIME Messages
References Referenced by
Proposed Standard normatively references
RFC 3207 SMTP Service Extension for Secure SMTP over Transport Layer Security
References Referenced by
Proposed Standard informatively references
RFC 3339 Date and Time on the Internet: Timestamps
References Referenced by
Proposed Standard normatively references
RFC 3461 Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)
References Referenced by
Draft Standard normatively references
RFC 3463 Enhanced Mail System Status Codes
References Referenced by
Draft Standard normatively references
RFC 3464 An Extensible Message Format for Delivery Status Notifications
References Referenced by
Draft Standard normatively references
RFC 3553 An IETF URN Sub-namespace for Registered Protocol Parameters
References Referenced by
Best Current Practice normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 4033 DNS Security Introduction and Requirements
References Referenced by
Proposed Standard normatively references
RFC 4648 The Base16, Base32, and Base64 Data Encodings
References Referenced by
Proposed Standard normatively references
RFC 4865 SMTP Submission Service Extension for Future Message Release
References Referenced by
Proposed Standard informatively references
RFC 4954 SMTP Service Extension for Authentication
References Referenced by
Proposed Standard informatively references
RFC 5321 Simple Mail Transfer Protocol
References Referenced by
Draft Standard normatively references
RFC 5322 Internet Message Format
References Referenced by
Draft Standard normatively references
RFC 5598 Internet Mail Architecture
References Referenced by
Informational normatively references
RFC 5890 Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework
References Referenced by
Proposed Standard normatively references
RFC 6152 SMTP Service Extension for 8-bit MIME Transport
References Referenced by
Internet Standard normatively references
RFC 6376 DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Internet Standard normatively references
RFC 6409 Message Submission for Mail
References Referenced by
Internet Standard normatively references
RFC 6522 The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages
References Referenced by
Internet Standard informatively references
RFC 6531 SMTP Extension for Internationalized Email
References Referenced by
Proposed Standard normatively references
RFC 6532 Internationalized Email Headers
References Referenced by
Proposed Standard normatively references
RFC 6585 Additional HTTP Status Codes
References Referenced by
Proposed Standard normatively references
RFC 6749 The OAuth 2.0 Authorization Framework
References Referenced by
Proposed Standard normatively references
RFC 6750 The OAuth 2.0 Authorization Framework: Bearer Token Usage
References Referenced by
Proposed Standard normatively references
RFC 6797 HTTP Strict Transport Security (HSTS)
References Referenced by
Proposed Standard informatively references
RFC 7208 Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
References Referenced by
Proposed Standard informatively references
RFC 7489 Domain-based Message Authentication, Reporting, and Conformance (DMARC)
References Referenced by
Informational informatively references
RFC 7493 The I-JSON Message Format
References Referenced by
Proposed Standard normatively references
RFC 7505 A "Null MX" No Service Resource Record for Domains That Accept No Mail
References Referenced by
Proposed Standard informatively references
RFC 7617 The 'Basic' HTTP Authentication Scheme
References Referenced by
Proposed Standard normatively references
RFC 7672 SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)
References Referenced by
Proposed Standard informatively references
RFC 8098 Message Disposition Notification
References Referenced by
Internet 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 8301 Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM)
References Referenced by
Proposed Standard informatively references
RFC 8461 SMTP MTA Strict Transport Security (MTA-STS)
References Referenced by
Proposed Standard informatively references
RFC 8463 A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)
References Referenced by
Proposed Standard normatively references
RFC 8551 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification
References Referenced by
Proposed Standard informatively references
RFC 8552 Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves
References Referenced by
Best Current Practice normatively references
RFC 8601 Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard informatively references
RFC 8615 Well-Known Uniform Resource Identifiers (URIs)
References Referenced by
Proposed Standard normatively references
RFC 8620 The JSON Meta Application Protocol (JMAP)
References Referenced by
Proposed Standard informatively references
RFC 8621 The JSON Meta Application Protocol (JMAP) for Mail
References Referenced by
Proposed Standard informatively references
RFC 8689 SMTP Require TLS Option
References Referenced by
Proposed Standard normatively references
RFC 8792 Handling Long Lines in Content of Internet-Drafts and RFCs
References Referenced by
Informational informatively references
RFC 9051 Internet Message Access Protocol (IMAP) - Version 4rev2
References Referenced by
Proposed Standard informatively references
RFC 9110 HTTP Semantics
References Referenced by
Internet Standard normatively references
RFC 9111 HTTP Caching
References Referenced by
Internet Standard normatively references
RFC 9113 HTTP/2
References Referenced by
Proposed Standard normatively references
RFC 9114 HTTP/3
References Referenced by
Proposed Standard informatively references
RFC 9421 HTTP Message Signatures
References Referenced by
Proposed Standard normatively references
RFC 9457 Problem Details for HTTP APIs
References Referenced by
Proposed Standard normatively references
RFC 9460 Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
References Referenced by
Proposed Standard normatively references
RFC 9525 Service Identity in TLS
References Referenced by
Proposed Standard normatively references
RFC 9530 Digest Fields
References Referenced by
Proposed Standard normatively references
RFC 9580 OpenPGP
References Referenced by
Proposed Standard informatively references
RFC 9728 OAuth 2.0 Protected Resource Metadata
References Referenced by
Proposed Standard normatively references