draft-ietf-regext-datadictionary-00.txt   draft-ietf-regext-datadictionary-01.txt 
Network Working Group H. Flanagan, Ed. Network Working Group H. Flanagan, Ed.
Internet-Draft S. Crocker Internet-Draft S. Crocker
Intended status: Standards Track Edgemoor Research Institute Intended status: Standards Track Edgemoor Research Institute
Expires: 21 July 2022 17 January 2022 Expires: 8 September 2022 7 March 2022
DNS Data Dictionary Registration Data Dictionary
draft-ietf-regext-datadictionary-00 draft-ietf-regext-datadictionary-01
Abstract Abstract
Multiple applications related to the domain name system are built Multiple applications related to the registration of names and other
around a list of data elements. There is currently no unified public identifiers are built around a list of data elements. There is
list of these data elements, nor is there an organized and currently no unified public list of these data elements, nor is there
independent change control process. This document codifies the an organized and independent change control process. This document
multiple similar but not quite identical lists of data elements into codifies the multiple similar but not quite identical lists of data
a neutral DNS Data Dictionary to be maintained as an independent IANA elements into a neutral Data Dictionary to be maintained as an
Registry. independent IANA Registry. The Data Dictionary defines data elements
but does not specify which ones are to be used in any particular
application; the Data Dictionary is policy-neutral.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 21 July 2022. This Internet-Draft will expire on 8 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 22 skipping to change at page 2, line 16
provided without warranty as described in the Revised BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Data Element Specification . . . . . . . . . . . . . . . . . 4 2. Data Element Specification . . . . . . . . . . . . . . . . . 4
2.1. Element name: Domain Name . . . . . . . . . . . . . . . . 4 2.1. Element name: Domain Name . . . . . . . . . . . . . . . . 4
2.2. Element name: Registry . . . . . . . . . . . . . . . . . 4 2.2. Element name: Registry . . . . . . . . . . . . . . . . . 4
2.3. Element name: NS . . . . . . . . . . . . . . . . . . . . 4 2.3. Element name: NS . . . . . . . . . . . . . . . . . . . . 4
2.4. Element name: Registration Creation Date . . . . . . . . 4 2.4. Element name: Registration Creation Date . . . . . . . . 5
2.5. Element name: Registration Expiration Date . . . . . . . 5 2.5. Element name: Registration Expiration Date . . . . . . . 5
2.6. Element name: Registration Updated Date . . . . . . . . . 5 2.6. Element name: Registration Updated Date . . . . . . . . . 5
2.7. Element name: Registration Transfer Date . . . . . . . . 5 2.7. Element name: Registration Transfer Date . . . . . . . . 5
2.8. Element name: Protection . . . . . . . . . . . . . . . . 5 2.8. Element name: Protection . . . . . . . . . . . . . . . . 5
2.9. Element name: Nexus . . . . . . . . . . . . . . . . . . . 5 2.9. Element name: Nexus . . . . . . . . . . . . . . . . . . . 5
2.10. Element name: Person . . . . . . . . . . . . . . . . . . 5 2.10. Element name: Person . . . . . . . . . . . . . . . . . . 5
2.11. Element name: Personal . . . . . . . . . . . . . . . . . 5 2.11. Element name: Personal . . . . . . . . . . . . . . . . . 5
2.12. Element name: Status & Locks . . . . . . . . . . . . . . 5 2.12. Element name: Status & Locks . . . . . . . . . . . . . . 5
2.13. Element name: Source & Method . . . . . . . . . . . . . . 5 2.13. Element name: Source & Method . . . . . . . . . . . . . . 6
2.14. Element name: Payment History . . . . . . . . . . . . . . 5 2.14. Element name: Payment History . . . . . . . . . . . . . . 6
2.15. Element name: Transaction History . . . . . . . . . . . . 5 2.15. Element name: Transaction History . . . . . . . . . . . . 6
2.16. Element name: User Account ID . . . . . . . . . . . . . . 6 2.16. Element name: User Account ID . . . . . . . . . . . . . . 6
2.17. Element name: Reserved . . . . . . . . . . . . . . . . . 6 2.17. Element name: Reserved . . . . . . . . . . . . . . . . . 6
2.18. Element name: Name . . . . . . . . . . . . . . . . . . . 6 2.18. Element name: Name . . . . . . . . . . . . . . . . . . . 6
2.19. Element name: Org . . . . . . . . . . . . . . . . . . . . 6 2.19. Element name: Org . . . . . . . . . . . . . . . . . . . . 6
2.20. Element name: Street . . . . . . . . . . . . . . . . . . 6 2.20. Element name: Street . . . . . . . . . . . . . . . . . . 6
2.21. Element name: City . . . . . . . . . . . . . . . . . . . 6 2.21. Element name: City . . . . . . . . . . . . . . . . . . . 6
2.22. Element name: State/Province . . . . . . . . . . . . . . 6 2.22. Element name: State/Province . . . . . . . . . . . . . . 7
2.23. Element name: Postal code . . . . . . . . . . . . . . . . 6 2.23. Element name: Postal code . . . . . . . . . . . . . . . . 7
2.24. Element name: Country . . . . . . . . . . . . . . . . . . 6 2.24. Element name: Country . . . . . . . . . . . . . . . . . . 7
2.25. Element name: Phone . . . . . . . . . . . . . . . . . . . 7 2.25. Element name: Phone . . . . . . . . . . . . . . . . . . . 7
2.26. Element name: Phone ext . . . . . . . . . . . . . . . . . 7 2.26. Element name: Phone ext . . . . . . . . . . . . . . . . . 7
2.27. Element name: Fax . . . . . . . . . . . . . . . . . . . . 7 2.27. Element name: Fax . . . . . . . . . . . . . . . . . . . . 7
2.28. Element name: Fax ext . . . . . . . . . . . . . . . . . . 7 2.28. Element name: Fax ext . . . . . . . . . . . . . . . . . . 7
2.29. Element name: Email . . . . . . . . . . . . . . . . . . . 7 2.29. Element name: Email . . . . . . . . . . . . . . . . . . . 8
2.30. Element name: Email_or_phone . . . . . . . . . . . . . . 7 2.30. Element name: Email_or_phone . . . . . . . . . . . . . . 8
2.31. Element name: Registry UniqueID . . . . . . . . . . . . . 7 2.31. Element name: Registry UniqueID . . . . . . . . . . . . . 8
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
3.1. Report Specification . . . . . . . . . . . . . . . . . . 8 3.1. Report Specification . . . . . . . . . . . . . . . . . . 8
3.1.1. Designated Expert Evaluation Criteria . . . . . . . . 8 3.1.1. Designated Expert Evaluation Criteria . . . . . . . . 8
3.1.2. Registration Procedure . . . . . . . . . . . . . . . 9 3.1.2. Registration Procedure . . . . . . . . . . . . . . . 9
3.2. Initial assignments . . . . . . . . . . . . . . . . . . . 10 3.2. Initial assignments . . . . . . . . . . . . . . . . . . . 11
3.2.1. Data Element Definition in IANA Registry . . . . . . 10 3.2.1. Data Element Definition in IANA Registry . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12 5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12
6. Internationalization Considerations . . . . . . . . . . . . . 12 6. Internationalization Considerations . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 7. Draft Change Log . . . . . . . . . . . . . . . . . . . . . . 12
8. Normative References . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Informative References . . . . . . . . . . . . . . . . . 13
9.2. Normative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
The DNS Data Dictionary provides a common set of names and The DNS Data Dictionary provides a common set of names and
definitions for data elements which may be used in a DNS related definitions for data elements which may be used in a DNS related
protocol. The dictionary is intended to be inclusive and not protocol. The dictionary is intended to be inclusive and not
obligatory. That is, the existence of a data element in this obligatory. That is, the existence of a data element in this
dictionary does not imply the data element must be used or recognized dictionary does not imply the data element must be used or recognized
in any particular protocol. The items in this dictionary should in any particular protocol. The items in this dictionary should
represent the union for what is in existing relevant protocols, and represent the union for what is in existing relevant protocols, and
skipping to change at page 4, line 26 skipping to change at page 4, line 26
The name of the data element MUST be unique and this characteristic The name of the data element MUST be unique and this characteristic
MUST be enforced by the registry. The character encoding MUST be enforced by the registry. The character encoding
recommendation for data elements is specified in Section 3. recommendation for data elements is specified in Section 3.
The subsections below comprise an initial list of known data elements The subsections below comprise an initial list of known data elements
commonly being used in the templates. The title of the subsection is commonly being used in the templates. The title of the subsection is
the data element name for the data element. The combination of data the data element name for the data element. The combination of data
element type and data element name MUST be unique and MUST be element type and data element name MUST be unique and MUST be
processed as case insensitive in the IANA registry. processed as case insensitive in the IANA registry.
Note that the legal definition of any of the terms used in the data
dictionary, such as 'personally identifiable information' or 'legal
person', are to be determined locally. The organization using this
dictionary will record their interpretation in the appropriate
element.
2.1. Element name: Domain Name 2.1. Element name: Domain Name
This is the domain name in an EPP [RFC5731] domain object and it MUST This is the domain name as formatted according to the
be in A-Label format. Internationalized Domain Names for Applications (IDNA)
specification.[RFC5890]
See also "Domain name" in [RFC8499]. See also "Domain name" in [RFC8499].
2.2. Element name: Registry 2.2. Element name: Registry
The name of the registry. This data element is text/string with no The name of the registry. This data element is text/string with no
naming convention enforced. naming convention enforced.
See also "Registry" in [RFC8499]. See also "Registry" in [RFC8499].
2.3. Element name: NS 2.3. Element name: NS
The authoritative name server for the domain.[RFC1034] The authoritative name server for the domain.[RFC1034]
See also "Authoritative server" in [RFC8499] See also "Authoritative server" in [RFC8499]
2.4. Element name: Registration Creation Date 2.4. Element name: Registration Creation Date
The EPP status code (<domain:crDate>) for the domain registration The the date and time of domain object creation. Format TBD.
creation date.[RFC5731]
2.5. Element name: Registration Expiration Date 2.5. Element name: Registration Expiration Date
The EPP status code (<domain:exDate>) for the domain registration The date and time identifying the end of the domain object's
expiration date.[RFC5731] registration period. Format TBD.
2.6. Element name: Registration Updated Date 2.6. Element name: Registration Updated Date
The EPP status code (<domain:upDate>) for the domain registration The date and time of the most recent domain-object modification.
updated date.[RFC5731] Format TBD.
2.7. Element name: Registration Transfer Date 2.7. Element name: Registration Transfer Date
The EPP status code (<domain:trDate>) for the domain registration The date and time of the most recent successful domain-object
transfer date.[RFC5731] transfer. Format TBD.
2.8. Element name: Protection 2.8. Element name: Protection
The level of protection assigned to a domain registration. Definition is TBD.
2.9. Element name: Nexus 2.9. Element name: Nexus
The country, community, or geographic location of the account holder. Definition is TBD.
2.10. Element name: Person 2.10. Element name: Person
Indication that the rules regarding this registration apply as per Definition is TBD.
the registrant being a legal person or a natural person.
2.11. Element name: Personal 2.11. Element name: Personal
Definition is TBD.
2.12. Element name: Status & Locks 2.12. Element name: Status & Locks
The EPP Status codes (ex: clientTransferProhibited) related to Examples include the EPP (Section 2.3 of [RFC5731]) and RDAP
domain.[RFC5731] (Section 10.2.2 of [RFC9083]) codes (ex: clientTransferProhibited)
that describe the current state of a registered domain name and the
protocol actions that can (or cannot) be performed on the domain
name. A registered domain name MAY be associated with multiple
status values. Other managed objects, including name server and
contact objects, can also have status and lock values.
2.13. Element name: Source & Method 2.13. Element name: Source & Method
The back pointer from registry to registrant. Definition is TBD.
2.14. Element name: Payment History 2.14. Element name: Payment History
Information related to the customer's financial exchanges. Definition is TBD.
2.15. Element name: Transaction History 2.15. Element name: Transaction History
[Is this same as 2.4.2?] Definition is TBD.
2.16. Element name: User Account ID 2.16. Element name: User Account ID
This is a customer ID at the registrar, reseller, or privacy/proxy Definition is TBD.
provider, respectively.
2.17. Element name: Reserved 2.17. Element name: Reserved
[this field is an artifact of prior use which was determined to not [this field is an artifact of prior use which was determined to not
be necessary, but the field was left intact for future use] be necessary, but the field was left intact for future use]
2.18. Element name: Name 2.18. Element name: Name
Individual name is represented using character strings. These Individual name is represented using character strings. These
strings have a specified minimum length and a specified maximum strings have a specified minimum length and a specified maximum
skipping to change at page 12, line 24 skipping to change at page 12, line 49
requirements for their work. requirements for their work.
6. Internationalization Considerations 6. Internationalization Considerations
The character encoding for the file contents MUST use UTF-8. The character encoding for the file contents MUST use UTF-8.
Throughout this document A-LABEL is indicated as a SHOULD and that Throughout this document A-LABEL is indicated as a SHOULD and that
MUST be interpreted as follows. All domain name labels MUST be in MUST be interpreted as follows. All domain name labels MUST be in
A-LABEL format if it is possible to represent it as an A-LABEL, A-LABEL format if it is possible to represent it as an A-LABEL,
otherwise U-LABEL MAY be used. otherwise U-LABEL MAY be used.
7. Acknowledgements 7. Draft Change Log
-01: Updated abstract to clarify that this draft does not intend to
set policy.
-01: Updated definitions in 2.1, 2.4, 2.5, 2.6, 2.7 to remove
normative reference to the EPP spec.
-01: Updated 2. Data Element specification to note local
interpretation expected for any legal definitions.
-01: Added TBD to policy-related items, all data-related elements wrt
format.
-01: Moved several items from informative to normative references.
8. Acknowledgements
With many thanks to James Galvin and Rod Rasmussen for their advice With many thanks to James Galvin and Rod Rasmussen for their advice
and feedback on this data dictionary. and feedback on this data dictionary.
8. Normative References 9. References
9.1. Informative References
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009,
<https://www.rfc-editor.org/info/rfc5731>.
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
January 2019, <https://www.rfc-editor.org/info/rfc8499>.
[RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the
Registration Data Access Protocol (RDAP)", STD 95,
RFC 9083, DOI 10.17487/RFC9083, June 2021,
<https://www.rfc-editor.org/info/rfc9083>.
9.2. Normative References
[ISO19160-4] [ISO19160-4]
International Organization for Standardization, International Organization for Standardization,
"ISO19160-4: Addressing — Part 4: International postal "ISO19160-4: Addressing — Part 4: International postal
address components and template language", November 2017. address components and template language", November 2017.
[ISO3166-1] [ISO3166-1]
International Organization for Standardization, International Organization for Standardization,
"ISO3166-1: Codes for the representation of names of "ISO3166-1: Codes for the representation of names of
countries and their subdivisions -- Part1: Country codes", countries and their subdivisions -- Part1: Country codes",
skipping to change at page 13, line 18 skipping to change at page 14, line 27
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <https://www.rfc-editor.org/info/rfc3629>. 2003, <https://www.rfc-editor.org/info/rfc3629>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
DOI 10.17487/RFC5322, October 2008, DOI 10.17487/RFC5322, October 2008,
<https://www.rfc-editor.org/info/rfc5322>. <https://www.rfc-editor.org/info/rfc5322>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5890] Klensin, J., "Internationalized Domain Names for
Domain Name Mapping", STD 69, RFC 5731, Applications (IDNA): Definitions and Document Framework",
DOI 10.17487/RFC5731, August 2009, RFC 5890, DOI 10.17487/RFC5890, August 2010,
<https://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5890>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
January 2019, <https://www.rfc-editor.org/info/rfc8499>.
Authors' Addresses Authors' Addresses
Heather Flanagan (editor) Heather Flanagan (editor)
Edgemoor Research Institute Edgemoor Research Institute
Email: hlf@sphericalcowconsulting.com Email: hlf@sphericalcowconsulting.com
Steve Crocker Steve Crocker
Edgemoor Research Institute Edgemoor Research Institute
Email: steve@shinkuro.com Email: steve@shinkuro.com
 End of changes. 31 change blocks. 
60 lines changed or deleted 104 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/