RFC 3696: Application Techniques for Checking and Transformation of Names

Many Internet applications have been designed to deduce top-level domains (or other domain name labels) from partial information. The introduction of new…

Read RFC 3696 on the RFC Editor

Outgoing relationships (14 related RFCs)

Normative reference — RFC 1035: Domain names - implementation and specification
Normative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Normative reference — RFC 1123: Requirements for Internet Hosts - Application and Support
Normative reference — RFC 3490: Internationalizing Domain Names in Applications (IDNA)
Normative reference — RFC 2822: Internet Message Format
Normative reference — RFC 1738: Uniform Resource Locators (URL)
Normative reference — RFC 2181: Clarifications to the DNS Specification
Normative reference — RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
Normative reference — RFC 2821: Simple Mail Transfer Protocol
Normative reference — RFC 3492: Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)
Normative reference — RFC 3491: Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)
Normative reference — RFC 2368: The mailto URL scheme
Normative reference — RFC 1535: A Security Problem and Proposed Correction With Widely Deployed DNS Software
Informative reference — RFC 1591: Domain Name System Structure and Delegation

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 4408: Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
Informatively referenced by — RFC 6943: Issues in Identifier Comparison for Security Purposes
Informatively referenced by — RFC 5536: Netnews Article Format