Skip to main content

Survey of Domain Verification Techniques using DNS
draft-sahib-domain-verification-techniques-02

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Shivan Kaul Sahib , Shumon Huque
Last updated 2021-12-12 (Latest revision 2021-06-10)
Replaced by draft-ietf-dnsop-domain-verification-techniques, draft-ietf-dnsop-domain-verification-techniques, draft-ietf-dnsop-domain-verification-techniques
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Many services on the Internet need to verify ownership or control of domains in the Domain Name System (DNS) [RFC1034] [RFC1035]. This verification often relies on adding or editing DNS records within the domain. This document surveys various techniques in wide use today, the pros and cons of each, and possible improvements. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/ShivanKaul/draft-sahib-domain-verification- techniques.

Authors

Shivan Kaul Sahib
Shumon Huque

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)