idnits 2.17.1 draft-brown-whoami-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 1, 2018) is 2156 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2818 (Obsoleted by RFC 9110) ** Obsolete normative reference: RFC 5785 (Obsoleted by RFC 8615) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Brown 3 Internet-Draft CentralNic Group plc 4 Intended status: Experimental June 1, 2018 5 Expires: December 3, 2018 7 WHOAMI: A Method For Identifying a Domain Operator's Contact Information 8 draft-brown-whoami-02 10 Abstract 12 This document proposes a method by which the operator of a domain may 13 publish their contact information in a discoverable and machine- 14 readable format. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on December 3, 2018. 33 Copyright Notice 35 Copyright (c) 2018 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 48 1.1. Conventions Used in This Document . . . . . . . . . . . . 2 49 2. WHOAMI Protocol . . . . . . . . . . . . . . . . . . . . . . . 2 50 2.1. URI Record . . . . . . . . . . . . . . . . . . . . . . . 3 51 2.1.1. URI Record with a data: scheme . . . . . . . . . . . 3 52 2.2. Well-Known URL . . . . . . . . . . . . . . . . . . . . . 3 53 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 54 4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4 55 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 56 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 58 6.2. Informative References . . . . . . . . . . . . . . . . . 5 59 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 5 60 A.1. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 5 61 A.2. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 5 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 64 1. Introduction 66 This document specifies a protocol which provides a way for the 67 operator of a domain name to publish their contact information in a 68 discoverable and machine-readable format. 70 It serves as a complementary service to WHOIS ([RFC3912]) and RDAP 71 ([RFC7480]), and differs in that it relies on self-publication by the 72 domain operator, rather than a centralised third party service. 74 1.1. Conventions Used in This Document 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in [RFC2119]. 80 2. WHOAMI Protocol 82 Domain Operators MAY publish a WHOAMI Record in conformance with this 83 specification. It may be published (a) at a URL indicated by a URI 84 record [RFC7553] published in the DNS (as described in Section 2.1), 85 or (b) at a well-known URL (as described in Section 2.2). 87 Software which consumes WHOAMI records SHOULD first perform a DNS 88 query for the URI record for a domain, falling back to the well-known 89 URL if the query does not return a positive result. 91 2.1. URI Record 93 Domain Operators MAY publish the URL of their WHOAMI record as a URI 94 record in the DNS. An example of such a record is below: 96 $ORIGIN example.com. 97 _nicname._tcp IN URI 10 1 https://example.com/whoami/whoami.vcf 99 Note: the Owner Name, Priority, Weight, Target and URI in the above 100 record are illustrative only. 102 The Service Tag of the URI record is constructed as per Section 4.1 103 of [RFC7553], with the "_nicname" tag being derived from the "Who Is 104 Protocol" entry in the "Service Name and Transport Protocol Port 105 Number Registry (see [RFC6335]). 107 2.1.1. URI Record with a data: scheme 109 Domain Operators MAY publish a record with a "data:" scheme 110 ([RFC2397]). This allows the WHOAMI record to be embedded in the URI 111 record itself. An example of such a URI is below: 113 data:text/vcard;charset=utf-8;base64,QkVHSU46VkNBUkQNClZFUlNJT046NC4w 114 DQpVSUQ6dXJuOnV1aWQ6NGZiZTg5NzEtMGJjMy00MjRjLTljMjYtMzZjM2UxZWZmNmIxD 115 QpGTjtQSUQ9MS4xOkouIERvZQ0KTjpEb2U7Si47OzsNCkVNQUlMO1BJRD0xLjE6amRvZU 116 BleGFtcGxlLmNvbQ0KQ0xJRU5UUElETUFQOjE7dXJuOnV1aWQ6NTNlMzc0ZDktMzM3ZS0 117 0NzI3LTg4MDMtYTFlOWMxNGUwNTU2DQpFTkQ6VkNBUkQ= 119 If a "data:" scheme is used, the MIME type of the data MUST be "text/ 120 vcard". 122 2.2. Well-Known URL 124 Domain Operators MAY publish their WHOAMI record at the following 125 URL: 127 http://example.com/.well-known/whoami/whoami.vcf 129 The "whoami" path segment has been registered in the "Well-Known URI 130 Registry" (see [RFC5785]). 132 It is RECOMMENDED that web servers which support HTTP over Transport 133 Layer Security (TLS, [RFC2818]) provide a 3xx redirect to the HTTPS 134 version of this URL. 136 Software which consumes WHOAMI records MUST follow 3xx redirections 137 return in server responses. 139 The Content-Type header of the server response MUST be "text/vcard". 141 3. Security Considerations 143 WHOAMI provides no security capabilities above and beyond those 144 provided by the underlying protocols it uses, namely DNS and HTTP. 146 WHOAMI records in general will not be confidential: while HTTPS 147 provides transport-layer security, unless some form of authentication 148 is used, WHOAMI records will be freely available to anyone who 149 requests them. Authentication of client requests is not covered by 150 this document. 152 The integrity of WHOAMI records served over DNS may be verified using 153 DNSSEC validation. The use of TLS ensures that records served over 154 HTTPS have not been modified in-transit. 156 4. Privacy Considerations 158 Since WHOAMI records are not private, the information included in a 159 WHOAMI record is exposed to the public. Domain owners should 160 therefore exercise caution when entering information into their 161 WHOAMI record. For example, rather than publishing the contact 162 informations of people, role-based contact information SHOULD be used 163 instead. 165 5. IANA Considerations 167 This specification registers the "whoami" well-known URI in the 168 "Well-Known URIs" registry as defined by [RFC5785]. 170 URI suffix: whoami 172 Change controller: IETF 174 Specification document(s): (this document) 176 Related information: no remarks 178 6. References 180 6.1. Normative References 182 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 183 Requirement Levels", BCP 14, RFC 2119, 184 DOI 10.17487/RFC2119, March 1997, 185 . 187 [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, 188 DOI 10.17487/RFC2397, August 1998, 189 . 191 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, 192 DOI 10.17487/RFC2818, May 2000, 193 . 195 [RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known 196 Uniform Resource Identifiers (URIs)", RFC 5785, 197 DOI 10.17487/RFC5785, April 2010, 198 . 200 [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. 201 Cheshire, "Internet Assigned Numbers Authority (IANA) 202 Procedures for the Management of the Service Name and 203 Transport Protocol Port Number Registry", BCP 165, 204 RFC 6335, DOI 10.17487/RFC6335, August 2011, 205 . 207 [RFC7553] Faltstrom, P. and O. Kolkman, "The Uniform Resource 208 Identifier (URI) DNS Resource Record", RFC 7553, 209 DOI 10.17487/RFC7553, June 2015, 210 . 212 6.2. Informative References 214 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 215 DOI 10.17487/RFC3912, September 2004, 216 . 218 [RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the 219 Registration Data Access Protocol (RDAP)", RFC 7480, 220 DOI 10.17487/RFC7480, March 2015, 221 . 223 Appendix A. Change History 225 A.1. Change from 01 to 02 227 1. Removed all the layer-9 stuff. 229 A.2. Change from 00 to 01 231 1. Fixed well-known URI registration, various typos. Improved 232 consistency of terminology. 234 Author's Address 236 Gavin Brown 237 CentralNic Group plc 238 35-39 Moorgate 239 London, England EC2R 6AR 240 GB 242 Phone: +44 20 33 88 0600 243 Email: gavin.brown@centralnic.com 244 URI: https://www.centralnic.com