Skip to main content

References from draft-ietf-uta-rfc6125bis

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 195
References Referenced by
normatively references
draft-ietf-add-svcb-dns Service Binding Mapping for DNS Servers
References Referenced by
Proposed Standard informatively references
draft-ietf-dnsop-svcb-https Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
References Referenced by
Proposed Standard informatively references
FYI 36
References Referenced by
informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2782 A DNS RR for specifying the location of services (DNS SRV)
References Referenced by
Proposed Standard normatively references
RFC 2818 HTTP Over TLS
References Referenced by
Informational informatively references
RFC 3261 SIP: Session Initiation Protocol
References Referenced by
Proposed Standard informatively references
RFC 3403 Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database
References Referenced by
Proposed Standard informatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 4291 IP Version 6 Addressing Architecture
References Referenced by
Draft Standard normatively references
RFC 4343 Domain Name System (DNS) Case Insensitivity Clarification
References Referenced by
Proposed Standard informatively references
RFC 4514 Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names
References Referenced by
Proposed Standard normatively references
RFC 4592 The Role of Wildcards in the Domain Name System
References Referenced by
Proposed Standard normatively references
RFC 4985 Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name
References Referenced by
Proposed Standard normatively references
RFC 5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
References Referenced by
Proposed Standard normatively references
RFC 5630 The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 5890 Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework
References Referenced by
Proposed Standard normatively references
RFC 5891 Internationalized Domain Names in Applications (IDNA): Protocol
References Referenced by
Proposed Standard normatively references
RFC 5922 Domain Certificates in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 6120 Extensible Messaging and Presence Protocol (XMPP): Core
References Referenced by
Proposed Standard informatively references
RFC 6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
References Referenced by
Proposed Standard informatively references
RFC 6186 Use of SRV Records for Locating Email Submission/Access Services
References Referenced by
Proposed Standard informatively references
RFC 6698 The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
References Referenced by
Proposed Standard informatively references
RFC 7301 Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension
References Referenced by
Proposed Standard informatively references
RFC 7858 Specification for DNS over Transport Layer Security (TLS)
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 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard informatively references
RFC 8555 Automatic Certificate Management Environment (ACME)
References Referenced by
Proposed Standard informatively references
RFC 8689 SMTP Require TLS Option
References Referenced by
Proposed Standard informatively references
RFC 8915 Network Time Security for the Network Time Protocol
References Referenced by
Proposed Standard informatively references
RFC 9000 QUIC: A UDP-Based Multiplexed and Secure Transport
References Referenced by
Proposed Standard informatively references
RFC 9001 Using TLS to Secure QUIC
References Referenced by
Proposed Standard informatively references
RFC 9147 The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
References Referenced by
Proposed Standard informatively references
RFC 9345 Delegated Credentials for TLS and DTLS
References Referenced by
Proposed Standard informatively references
STD 13
References Referenced by
normatively references
STD 5
References Referenced by
normatively references
STD 66
References Referenced by
normatively references
STD 68
References Referenced by
informatively references
STD 97
References Referenced by
informatively references