WHOAMI: A Method For Identifying a Domain Operator's Contact Information
draft-brown-whoami-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

Internet Engineering Task Force                                 G. Brown
Internet-Draft                                      CentralNic Group plc
Intended status: Experimental                               June 1, 2018
Expires: December 3, 2018

WHOAMI: A Method For Identifying a Domain Operator's Contact Information
                         draft-brown-whoami-02

Abstract

   This document proposes a method by which the operator of a domain may
   publish their contact information in a discoverable and machine-
   readable format.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 3, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Brown                   Expires December 3, 2018                [Page 1]
Internet-Draft                   WHOAMI                        June 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   2
   2.  WHOAMI Protocol . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  URI Record  . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  URI Record with a data: scheme  . . . . . . . . . . .   3
     2.2.  Well-Known URL  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change History . . . . . . . . . . . . . . . . . . .   5
     A.1.  Change from 01 to 02  . . . . . . . . . . . . . . . . . .   5
     A.2.  Change from 00 to 01  . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   This document specifies a protocol which provides a way for the
   operator of a domain name to publish their contact information in a
   discoverable and machine-readable format.

   It serves as a complementary service to WHOIS ([RFC3912]) and RDAP
   ([RFC7480]), and differs in that it relies on self-publication by the
   domain operator, rather than a centralised third party service.

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  WHOAMI Protocol

   Domain Operators MAY publish a WHOAMI Record in conformance with this
   specification.  It may be published (a) at a URL indicated by a URI
   record [RFC7553] published in the DNS (as described in Section 2.1),
   or (b) at a well-known URL (as described in Section 2.2).

   Software which consumes WHOAMI records SHOULD first perform a DNS
   query for the URI record for a domain, falling back to the well-known
   URL if the query does not return a positive result.

Brown                   Expires December 3, 2018                [Page 2]
Internet-Draft                   WHOAMI                        June 2018

2.1.  URI Record

   Domain Operators MAY publish the URL of their WHOAMI record as a URI
   record in the DNS.  An example of such a record is below:

   $ORIGIN example.com.
   _nicname._tcp IN URI 10 1 https://example.com/whoami/whoami.vcf

   Note: the Owner Name, Priority, Weight, Target and URI in the above
   record are illustrative only.

   The Service Tag of the URI record is constructed as per Section 4.1
   of [RFC7553], with the "_nicname" tag being derived from the "Who Is
   Protocol" entry in the "Service Name and Transport Protocol Port
   Number Registry (see [RFC6335]).

2.1.1.  URI Record with a data: scheme