Skip to main content

References to BCP 90

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
draft-ietf-calext-subscription-upgrade
As rfc3864
Calendar subscription upgrades
References Referenced by
Proposed Standard normatively references
draft-ietf-lamps-header-protection
As rfc3864
Header Protection for Cryptographically Protected E-mail
References Referenced by
Proposed Standard normatively references
draft-melnikov-email-big-files
As rfc3864
Referencing big external files in email messages
References Referenced by
normatively references
draft-wells-origin-bound-one-time-codes Origin-Bound One-Time Codes
References Referenced by
normatively references
RFC 3865 A No Soliciting Simple Mail Transfer Protocol (SMTP) Service Extension
References Referenced by
Proposed Standard normatively references
RFC 3865
As rfc3864
A No Soliciting Simple Mail Transfer Protocol (SMTP) Service Extension
References Referenced by
Proposed Standard normatively references
RFC 4021 Registration of Mail and MIME Header Fields
References Referenced by
Proposed Standard normatively references
RFC 4249 Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components
References Referenced by
Informational normatively references
RFC 4408
As rfc3864
Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
References Referenced by
Experimental normatively references
RFC 4408 Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
References Referenced by
Experimental normatively references
RFC 5023 The Atom Publishing Protocol
References Referenced by
Proposed Standard normatively references
RFC 5023
As rfc3864
The Atom Publishing Protocol
References Referenced by
Proposed Standard normatively references
RFC 5064 The Archived-At Message Header Field
References Referenced by
Proposed Standard normatively references
RFC 5064
As rfc3864
The Archived-At Message Header Field
References Referenced by
Proposed Standard normatively references
RFC 5321 Simple Mail Transfer Protocol
References Referenced by
Draft Standard normatively references
RFC 5451 Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard normatively references
RFC 5504
As rfc3864
Downgrading Mechanism for Email Address Internationalization
References Referenced by
Experimental normatively references
RFC 5504 Downgrading Mechanism for Email Address Internationalization
References Referenced by
Experimental normatively references
RFC 5598
As rfc3864
Internet Mail Architecture
References Referenced by
Informational normatively references
RFC 5598 Internet Mail Architecture
References Referenced by
Informational normatively references
RFC 5789 PATCH Method for HTTP
References Referenced by
Proposed Standard normatively references
RFC 5789
As rfc3864
PATCH Method for HTTP
References Referenced by
Proposed Standard normatively references
RFC 5988
As rfc3864
Web Linking
References Referenced by
Proposed Standard normatively references
RFC 5988 Web Linking
References Referenced by
Proposed Standard normatively references
RFC 6068
As rfc3864
The 'mailto' URI Scheme
References Referenced by
Proposed Standard normatively references
RFC 6068 The 'mailto' URI Scheme
References Referenced by
Proposed Standard normatively references
RFC 6109 La Posta Elettronica Certificata - Italian Certified Electronic Mail
References Referenced by
Informational normatively references
RFC 6454
As rfc3864
The Web Origin Concept
References Referenced by
Proposed Standard normatively references
RFC 6454 The Web Origin Concept
References Referenced by
Proposed Standard normatively references
RFC 6455
As rfc3864
The WebSocket Protocol
References Referenced by
Proposed Standard normatively references
RFC 6455 The WebSocket Protocol
References Referenced by
Proposed Standard normatively references
RFC 6477 Registration of Military Message Handling System (MMHS) Header Fields for Use in Internet Mail
References Referenced by
Informational normatively references
RFC 6477
As rfc3864
Registration of Military Message Handling System (MMHS) Header Fields for Use in Internet Mail
References Referenced by
Informational normatively references
RFC 6638 Scheduling Extensions to CalDAV
References Referenced by
Proposed Standard normatively references
RFC 6638
As rfc3864
Scheduling Extensions to CalDAV
References Referenced by
Proposed Standard normatively references
RFC 6797
As rfc3864
HTTP Strict Transport Security (HSTS)
References Referenced by
Proposed Standard normatively references
RFC 6797 HTTP Strict Transport Security (HSTS)
References Referenced by
Proposed Standard normatively references
RFC 6857
As rfc3864
Post-Delivery Message Downgrading for Internationalized Email Messages
References Referenced by
Proposed Standard normatively references
RFC 6857 Post-Delivery Message Downgrading for Internationalized Email Messages
References Referenced by
Proposed Standard normatively references
RFC 7001 Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard normatively references
RFC 7208
As rfc3864
Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
References Referenced by
Proposed Standard normatively references
RFC 7208 Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
References Referenced by
Proposed Standard normatively references
RFC 7239 Forwarded HTTP Extension
References Referenced by
Proposed Standard normatively references
RFC 7239
As rfc3864
Forwarded HTTP Extension
References Referenced by
Proposed Standard normatively references
RFC 7240
As rfc3864
Prefer Header for HTTP
References Referenced by
Proposed Standard normatively references
RFC 7240 Prefer Header for HTTP
References Referenced by
Proposed Standard normatively references
RFC 7293 The Require-Recipient-Valid-Since Header Field and SMTP Service Extension
References Referenced by
Proposed Standard normatively references
RFC 7444 Security Labels in Internet Email
References Referenced by
Informational normatively references
RFC 7444
As rfc3864
Security Labels in Internet Email
References Referenced by
Informational normatively references
RFC 7601 Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard normatively references
RFC 7639
As rfc3864
The ALPN HTTP Header Field
References Referenced by
Proposed Standard normatively references
RFC 7639 The ALPN HTTP Header Field
References Referenced by
Proposed Standard normatively references
RFC 7809
As rfc3864
Calendaring Extensions to WebDAV (CalDAV): Time Zones by Reference
References Referenced by
Proposed Standard normatively references
RFC 7809 Calendaring Extensions to WebDAV (CalDAV): Time Zones by Reference
References Referenced by
Proposed Standard normatively references
RFC 8030 Generic Event Delivery Using HTTP Push
References Referenced by
Proposed Standard normatively references
RFC 8030
As rfc3864
Generic Event Delivery Using HTTP Push
References Referenced by
Proposed Standard normatively references
RFC 8288 Web Linking
References Referenced by
Proposed Standard normatively references
RFC 8288
As rfc3864
Web Linking
References Referenced by
Proposed Standard normatively references
RFC 8315 Cancel-Locks in Netnews Articles
References Referenced by
Proposed Standard normatively references
RFC 8315
As rfc3864
Cancel-Locks in Netnews Articles
References Referenced by
Proposed Standard normatively references
RFC 8473 Token Binding over HTTP
References Referenced by
Proposed Standard normatively references
RFC 8473
As rfc3864
Token Binding over HTTP
References Referenced by
Proposed Standard normatively references
RFC 8594 The Sunset HTTP Header Field
References Referenced by
Informational normatively references
RFC 8594
As rfc3864
The Sunset HTTP Header Field
References Referenced by
Informational normatively references
RFC 8601 Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard normatively references
RFC 8601
As rfc3864
Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard normatively references
RFC 8607
As rfc3864
Calendaring Extensions to WebDAV (CalDAV): Managed Attachments
References Referenced by
Informational normatively references
RFC 8607 Calendaring Extensions to WebDAV (CalDAV): Managed Attachments
References Referenced by
Informational normatively references
RFC 8942 HTTP Client Hints
References Referenced by
Experimental normatively references
RFC 8942
As rfc3864
HTTP Client Hints
References Referenced by
Experimental normatively references
RFC 9057
As rfc3864
Email Author Header Field
References Referenced by
Experimental normatively references
RFC 9057 Email Author Header Field
References Referenced by
Experimental normatively references
RFC 9228
As rfc3864
Delivered-To Email Header Field
References Referenced by
Experimental normatively references
draft-ietf-emailcore-rfc5322bis
As rfc3864
Internet Message Format
References Referenced by
Internet Standard informatively references
draft-ietf-httpbis-rfc6265bis
As rfc3864
Cookies: HTTP State Management Mechanism
References Referenced by
informatively references
draft-toomim-httpbis-braid-http Braid-HTTP: Synchronization for HTTP
References Referenced by
informatively references
RFC 4229 HTTP Header Field Registrations
References Referenced by
Informational informatively references
RFC 4395 Guidelines and Registration Procedures for New URI Schemes
References Referenced by
Best Current Practice informatively references
RFC 4871
As rfc3864
DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Proposed Standard informatively references
RFC 4871 DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Proposed Standard informatively references
RFC 4918
As rfc3864
HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
References Referenced by
Proposed Standard informatively references
RFC 4918 HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
References Referenced by
Proposed Standard informatively references
RFC 5322
As rfc3864
Internet Message Format
References Referenced by
Draft Standard informatively references
RFC 5322 Internet Message Format
References Referenced by
Draft Standard informatively references
RFC 5323 Web Distributed Authoring and Versioning (WebDAV) SEARCH
References Referenced by
Proposed Standard informatively references
RFC 5323
As rfc3864
Web Distributed Authoring and Versioning (WebDAV) SEARCH
References Referenced by
Proposed Standard informatively references
RFC 5518 Vouch By Reference
References Referenced by
Proposed Standard informatively references
RFC 5518
As rfc3864
Vouch By Reference
References Referenced by
Proposed Standard informatively references
RFC 5536
As rfc3864
Netnews Article Format
References Referenced by
Proposed Standard informatively references
RFC 5536 Netnews Article Format
References Referenced by
Proposed Standard informatively references
RFC 6265
As rfc3864
HTTP State Management Mechanism
References Referenced by
Proposed Standard informatively references
RFC 6265 HTTP State Management Mechanism
References Referenced by
Proposed Standard informatively references
RFC 6266 Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
References Referenced by
Proposed Standard informatively references
RFC 6266
As rfc3864
Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
References Referenced by
Proposed Standard informatively references
RFC 6376 DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Internet Standard informatively references
RFC 6376
As rfc3864
DomainKeys Identified Mail (DKIM) Signatures
References Referenced by
Internet Standard informatively references
RFC 6648
As rfc3864
Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
References Referenced by
Best Current Practice informatively references
RFC 6648 Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
References Referenced by
Best Current Practice informatively references
RFC 7034 HTTP Header Field X-Frame-Options
References Referenced by
Informational informatively references
RFC 7034
As rfc3864
HTTP Header Field X-Frame-Options
References Referenced by
Informational informatively references
RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by
Proposed Standard informatively references
RFC 7230
As rfc3864
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by
Proposed Standard informatively references
RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by
Proposed Standard informatively references
RFC 7232 Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
References Referenced by
Proposed Standard informatively references
RFC 7233 Hypertext Transfer Protocol (HTTP/1.1): Range Requests
References Referenced by
Proposed Standard informatively references
RFC 7234 Hypertext Transfer Protocol (HTTP/1.1): Caching
References Referenced by
Proposed Standard informatively references
RFC 7235 Hypertext Transfer Protocol (HTTP/1.1): Authentication
References Referenced by
Proposed Standard informatively references
RFC 7540 Hypertext Transfer Protocol Version 2 (HTTP/2)
References Referenced by
Proposed Standard informatively references
RFC 7540
As rfc3864
Hypertext Transfer Protocol Version 2 (HTTP/2)
References Referenced by
Proposed Standard informatively references
RFC 7595 Guidelines and Registration Procedures for URI Schemes
References Referenced by
Best Current Practice informatively references
RFC 7595
As rfc3864
Guidelines and Registration Procedures for URI Schemes
References Referenced by
Best Current Practice informatively references
RFC 7615 HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields
References Referenced by
Proposed Standard informatively references
RFC 7615
As rfc3864
HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields
References Referenced by
Proposed Standard informatively references
RFC 7694 Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
References Referenced by
Proposed Standard informatively references
RFC 7838 HTTP Alternative Services
References Referenced by
Proposed Standard informatively references
RFC 7912
As rfc3864
Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure
References Referenced by
Informational informatively references
RFC 7912 Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure
References Referenced by
Informational informatively references
RFC 8460
As rfc3864
SMTP TLS Reporting
References Referenced by
Proposed Standard informatively references
RFC 8460 SMTP TLS Reporting
References Referenced by
Proposed Standard informatively references
RFC 9110 HTTP Semantics
References Referenced by
Internet Standard informatively references
RFC 9110
As rfc3864
HTTP Semantics
References Referenced by
Internet Standard informatively references
RFC 9477
As rfc3864
Complaint Feedback Loop Address Header
References Referenced by
Experimental informatively references
RFC 4021
As rfc3864
Registration of Mail and MIME Header Fields
References Referenced by
Proposed Standard Possible Reference
RFC 4229
As rfc3864
HTTP Header Field Registrations
References Referenced by
Informational Possible Reference
RFC 7681 Email Exchange of Secondary School Transcripts
References Referenced by
Informational Reference
RFC 7681
As rfc3864
Email Exchange of Secondary School Transcripts
References Referenced by
Informational Reference