idnits 2.17.00 (12 Aug 2021) /tmp/idnits27969/draft-carney-regext-unavailable-domains-00.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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 9, 2016) is 2165 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4180' is defined on line 163, but no explicit reference was found in the text == Unused Reference: 'RFC7111' is defined on line 168, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 4180 ** Downref: Normative reference to an Informational RFC: RFC 7111 Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Registration Protocols Extensions R. Carney 3 Internet-Draft GoDaddy Inc. 4 Intended status: Standards Track J. Galvin 5 Expires: December 11, 2016 Afilias USA 6 June 9, 2016 8 Unavailable Domain Name File Format Specification 9 draft-carney-regext-unavailable-domains-00 11 Abstract 13 This document defines the file format for the storage of unavailable 14 domain names and related details for a top level domain name 15 registry. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on December 11, 2016. 34 Copyright Notice 36 Copyright (c) 2016 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Conventions Used in This Document . . . . . . . . . . . . 2 53 2. General File Format Elements . . . . . . . . . . . . . . . . 2 54 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3 56 3.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 3 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 58 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 59 6. Change History . . . . . . . . . . . . . . . . . . . . . . . 4 60 7. Normative References . . . . . . . . . . . . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 This document specifies a file format for the storage of unavailable 66 domain names and related details for a top level domain (TLD) name 67 registry, designed to facilitate interoperability and reusability 68 among domain name registries and registrars. 70 The increased number of domain name registries and registrars, the 71 greater number of reasons for domain names not being available, and 72 to make accommodations for possible real-time communications issues 73 between registries and registrars has driven the need for this 74 standard sharable file. 76 1.1. Conventions Used in This Document 78 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 79 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 80 document are to be interpreted as described in RFC 2119 [RFC2119]. 82 2. General File Format Elements 84 File format will be a comma separated values (CSV) file and MUST use 85 the US-ASCII character set. See informational RFC 4180 and RFC 7111 86 for details on the CSV file format. 88 Filename has two forms depending on content. For a file containing 89 only a list of unavailable domain names in one Top Level Domain (TLD) 90 the filename MUST be -unavailablenames-.csv. 91 For a file containing a list of unavailable domain names in multiple 92 Top Level Domains (TLDs) the filename MUST be unavailablenames-.csv. For an IDN TLD MUST be ace-encoded (i.e. in 94 the "xn--" format). MUST be the date and time 95 (in UTC) the file was created indicating that all the names in the 96 file were unavailable on that date at the time the file was created. 98 The first row MUST be the column headings: TLD, Domain Name, Status. 99 The remaining rows will contain the data (all unavailable names) from 100 the registry in the following structure: , , 101 . Where is the TLD of the domain name, 102 is the string of characters that represent the unavailable name, and 103 is one of four values (REGISTERED, REGISTRY RESERVED, POLICY 104 RESERVED, IDN VARIANT RESERVED). If the and/or 105 is an IDN it MUST be ace-encoded (i.e. in the "xn--" format). 107 All domain name labels that are not available for registration in the 108 SRS, for any reason, to the registrar channel MUST be included in 109 this file. 111 3. Examples 113 3.1. Single TLD File Example 115 Example of a file that contains unavailable domain names from a 116 single TLD. 118 FileName: example-unavailablenames-2016-05-01T010000.csv 120 TLD,Domain Name,Status 121 example,e.example,REGISTRY RESERVED 122 example,ex.example,POLICY RESERVED 123 example,example.example,REGISTERED 124 example,xn--4gqvdy3r.example,REGISTERED 126 3.2. Multiple TLDs File Example 128 Example of a file that contains unavailable domain names from 129 multiple TLDs. 131 FileName: unavailablenames-2016-05-01T010000.csv 133 TLD,Domain Name,Status 134 example,e.example,REGISTRY RESERVED 135 test,ex.test,POLICY RESERVED 136 another,xn--4gqvdy3r.another,REGISTERED 138 4. Security Considerations 140 The file format described in this document does not provide any 141 security services. 143 5. Acknowledgements 145 The authors wish to thank the following persons for their feedback 146 and suggestions: 148 o Christine Turner of GoDaddy Inc. 149 o Jody Kolker of GoDaddy Inc. 150 o Richard Merdinger of GoDaddy Inc. 151 o Mike Runcieman of Afilias Canada 152 o Wayne Beaver of Afilias USA 154 6. Change History 156 7. Normative References 158 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 159 Requirement Levels", BCP 14, RFC 2119, 160 DOI 10.17487/RFC2119, March 1997, 161 . 163 [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- 164 Separated Values (CSV) Files", RFC 4180, 165 DOI 10.17487/RFC4180, October 2005, 166 . 168 [RFC7111] Hausenblas, M., Wilde, E., and J. Tennison, "URI Fragment 169 Identifiers for the text/csv Media Type", RFC 7111, 170 DOI 10.17487/RFC7111, January 2014, 171 . 173 Authors' Addresses 175 Roger Carney 176 GoDaddy Inc. 177 14455 N. Hayden Rd. #219 178 Scottsdale, AZ 85260 179 US 181 Email: rcarney@godaddy.com 182 URI: http://www.godaddy.com 183 James Galvin 184 Afilias USA 185 300 Welsh Road, Building 3, Suite 105 186 Horsham, PA 19044 187 US 189 Email: jgalvin@afilias.info 190 URI: http://www.afilias.info