draft-ietf-regext-simple-registration-reporting-05.txt   draft-ietf-regext-simple-registration-reporting-06.txt 
Internet Engineering Task Force J. Yee, Ed. Internet Engineering Task Force J. Yee, Ed.
Internet-Draft J. Galvin Internet-Draft J. Galvin
Intended status: Informational Afilias Intended status: Informational Donuts
Expires: 20 August 2022 16 February 2022 Expires: 8 September 2022 7 March 2022
Simple Registration Reporting Simple Registration Reporting
draft-ietf-regext-simple-registration-reporting-05 draft-ietf-regext-simple-registration-reporting-06
Abstract Abstract
Domain name registries (the producer) and registrars (the consumer) Domain name registries (the producer) and registrars (the consumer)
report to each other by sharing bulk information through files. This report to each other by sharing bulk information through files. This
document creates two IANA registries to establish a standard document creates two IANA registries to establish a standard
reporting mechanism between domain name registries and registrars. reporting mechanism between domain name registries and registrars.
The first IANA registry lists standard data elements and their syntax The first IANA registry lists standard data elements and their syntax
for inclusion in the files. The second IANA registry lists standard for inclusion in the files. The second IANA registry lists standard
reports based on the standard data elements. Each report is a file reports based on the standard data elements. Each report is a file
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 20 August 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 4, line 21 skipping to change at page 4, line 21
evolution of the reports and adding additional report definitions as evolution of the reports and adding additional report definitions as
needed. needed.
Each report definition MUST use only the data elements defined in the Each report definition MUST use only the data elements defined in the
data element aforementioned data element registry, including all data element aforementioned data element registry, including all
future reports. Note that a produced report MAY include data future reports. Note that a produced report MAY include data
elements that are not registered, as specified below. Future reports elements that are not registered, as specified below. Future reports
and future data elements may be specified in their own individual and future data elements may be specified in their own individual
documents, updating the IANA registries as needed. documents, updating the IANA registries as needed.
The mechanism for the distribution aof and access to the files is a The mechanism for the distribution of and access to the files is a
matter of local policy. matter of local policy.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Data Element Specification 2. Data Element Specification
skipping to change at page 5, line 31 skipping to change at page 5, line 31
The transaction identifier issued by an EPP Server. The format MUST The transaction identifier issued by an EPP Server. The format MUST
conform to "type:trIDStringType" as specified in RFC 5730 [RFC5730]. conform to "type:trIDStringType" as specified in RFC 5730 [RFC5730].
2.1.3. Domain 2.1.3. Domain
This is the domain name in an EPP RFC 5731 [RFC5731] domain object This is the domain name in an EPP RFC 5731 [RFC5731] domain object
and it MUST be in A-Label format. and it MUST be in A-Label format.
2.1.4. Transaction_Type 2.1.4. Transaction_Type
The type of transform action made to the domain object (create, The type of transform action made to the domain object (e.g., create,
delete, update, transfer, renew) as specified in RFC 5730 [RFC5730] delete, update, transfer, renew) as specified in RFC 5730 [RFC5730]
Section 2.9.3. Section 2.9.3.
2.1.5. Object_Type 2.1.5. Object_Type
The object type involved in the report. In the EPP environment, an The object type involved in the report. In the EPP environment, an
object could be domain RFC 5731 [RFC5731], contact RFC 5733 object could be domain RFC 5731 [RFC5731], contact RFC 5733
[RFC5733], or host RFC 5732 [RFC5732]. [RFC5733], or host RFC 5732 [RFC5732].
2.1.6. DateTime 2.1.6. DateTime
skipping to change at page 34, line 21 skipping to change at page 34, line 21
DOI 10.17487/RFC3552, July 2003, DOI 10.17487/RFC3552, July 2003,
<https://www.rfc-editor.org/info/rfc3552>. <https://www.rfc-editor.org/info/rfc3552>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226, IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<https://www.rfc-editor.org/info/rfc5226>. <https://www.rfc-editor.org/info/rfc5226>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors would like to thank Roger Carney, Jody Kolker, and The authors would like to thank Roger Carney, Jody Kolker, Tobias
bestpractice.domains for their reviews and suggestions. Sattler, and bestpractice.domains for their reviews and suggestions.
Appendix B. File Naming Convention Appendix B. File Naming Convention
TBD on file naming convention suggestion TBD on file naming convention suggestion
Authors' Addresses Authors' Addresses
Joseph Yee (editor) Joseph Yee (editor)
Afilias Donuts
Toronto Toronto
Canada Canada
Email: jyee@afilias.info Email: jyee@afilias.info
James Galvin James Galvin
Afilias Donuts
Horsham, PA Horsham, PA
United States United States
Email: jgalvin@donuts.email
Email: jgalvin@afilias.info
 End of changes. 10 change blocks. 
11 lines changed or deleted 10 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/