draft-ietf-regext-dnrd-objects-mapping-02.txt   draft-ietf-regext-dnrd-objects-mapping-03.txt 
Network Working Group G. Lozano Network Working Group G. Lozano
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Standards Track J. Gould Intended status: Standards Track J. Gould
Expires: April 27, 2020 C. Thippeswamy Expires: May 29, 2020 C. Thippeswamy
VeriSign VeriSign
Oct 25, 2019 Nov 26, 2019
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-02 draft-ietf-regext-dnrd-objects-mapping-03
Abstract Abstract
This document specifies the format, contents and semantics of Domain This document specifies the format, contents and semantics of Domain
Name Registration Data (DNRD) Escrow deposits for a Domain Name Name Registration Data (DNRD) Escrow deposits for a Domain Name
Registry. Registry.
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 April 27, 2020. This Internet-Draft will expire on May 29, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 12 skipping to change at page 2, line 12
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5
4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5
4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6
4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6
4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6
4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6 4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6
4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7 4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7
4.8. Internationalized and Localized Elements . . . . . . . . 12 4.8. Internationalized and Localized Elements . . . . . . . . 12
5. Object Description . . . . . . . . . . . . . . . . . . . . . 14 5. Object Description . . . . . . . . . . . . . . . . . . . . . 14
5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14
5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33
5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43
skipping to change at page 3, line 15 skipping to change at page 3, line 15
13. Security Considerations . . . . . . . . . . . . . . . . . . . 146 13. Security Considerations . . . . . . . . . . . . . . . . . . . 146
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 146 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 146
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 146 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 146
16. Change History . . . . . . . . . . . . . . . . . . . . . . . 147 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 147
16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02
to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 147 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 147
16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 147 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 147
16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 148 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 148
16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 148 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 148
16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 148 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 148
16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 149 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 150
16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 150 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 150
16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 150 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 151
16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 151 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 151
16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 151 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 151
16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 151 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 151
16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 151 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 151
16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 151 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 151
16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 151 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 151
16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 153
17. Example of a full deposit using the XML model . . . . . . . . 153 17. Example of a full deposit using the XML model . . . . . . . . 153
18. Example of differential deposit using the XML model . . . . . 158 18. Example of differential deposit using the XML model . . . . . 159
19. Example of a full deposit using the CSV model . . . . . . . . 160 19. Example of a full deposit using the CSV model . . . . . . . . 160
20. Example of differential deposit using the CSV model . . . . . 169 20. Example of differential deposit using the CSV model . . . . . 169
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 180 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 180
21.1. Normative References . . . . . . . . . . . . . . . . . . 180 21.1. Normative References . . . . . . . . . . . . . . . . . . 180
21.2. Informative References . . . . . . . . . . . . . . . . . 181 21.2. Informative References . . . . . . . . . . . . . . . . . 181
21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 182 21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182
1. Introduction 1. Introduction
skipping to change at page 5, line 8 skipping to change at page 5, line 11
represented using the CSV model can be referred to as the CSV represented using the CSV model can be referred to as the CSV
Domain Name with the XML namespace including csvDomain Domain Name with the XML namespace including csvDomain
(urn:ietf:params:xml:ns:csvDomain-1.0). (urn:ietf:params:xml:ns:csvDomain-1.0).
The data escrow deposit MAY contain a mix of both models but an The data escrow deposit MAY contain a mix of both models but an
object MUST be escrowed only in one model. object MUST be escrowed only in one model.
3. Terminology 3. Terminology
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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in BCP 14, [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
REGISTRY. In the context of this draft the definition will be REGISTRY. In the context of this draft the definition will be
overloaded (from the definition in the base protocol) to indicate an overloaded (from the definition in the base protocol) to indicate an
organization providing Registry Services for a REGISTRY-CLASS DOMAIN organization providing Registry Services for a REGISTRY-CLASS DOMAIN
NAME. NAME.
REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD)
or any other domain name at any level in the DNS tree for which a or any other domain name at any level in the DNS tree for which a
Registry (either directly or through and affiliate company) provides Registry (either directly or through and affiliate company) provides
Registry Services for other organizations or individuals. For Registry Services for other organizations or individuals. For
skipping to change at page 80, line 36 skipping to change at page 80, line 36
... ...
<rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain"
element="rdeDom:registrant" /> element="rdeDom:registrant" />
... ...
5.9. Header Object 5.9. Header Object
The Header Object is a pseudo-object that is used to specify the The Header Object is a pseudo-object that is used to specify the
number of objects in the repository at a specific point in time number of objects in the repository at a specific point in time
(watermark) regardless of the type of deposit: differential, full or (watermark) regardless of the type of deposit: differential, full or
incremental. The Header Object is only defined as XML but one header incremental. The Header Object may also be used to provide
object MUST always be present per escrow deposit regardless of using additional information on the contents of the deposit. The Header
XML Model or CSV Model. The Header Object is defined using the Object is only defined as XML but one header object MUST always be
<rdeHeader:header> element. present per escrow deposit regardless of using XML Model or CSV
Model. The Header Object is defined using the <rdeHeader:header>
element.
5.9.1. <rdeHeader:header> object 5.9.1. <rdeHeader:header> object
The <rdeHeader:header> contains the following elements: The <rdeHeader:header> contains the following elements:
o A choice of one of the elements defined in the o A choice of one of the elements defined in the
"repositoryTypeGroup" group element that indicates the unique "repositoryTypeGroup" group element that indicates the unique
identifier for the repository being escrowed. Possible elements identifier for the repository being escrowed. Possible elements
are: are:
skipping to change at page 82, line 5 skipping to change at page 82, line 7
elements for objects under "com.example" and lower levels. elements for objects under "com.example" and lower levels.
Omitting the "rcdn" attribute indicates that the total includes Omitting the "rcdn" attribute indicates that the total includes
all objects of the specified "uri" in the repository (e.g. the all objects of the specified "uri" in the repository (e.g. the
TLD, Registrar, or PPSP). TLD, Registrar, or PPSP).
* An OPTIONAL "registrarId" attribute indicates the identifier of * An OPTIONAL "registrarId" attribute indicates the identifier of
the sponsoring Registrar of the objects included in the <count> the sponsoring Registrar of the objects included in the <count>
element. In the case of an ICANN-accredited Registrar, the element. In the case of an ICANN-accredited Registrar, the
value MUST be the IANA Registrar ID assigned by ICANN. value MUST be the IANA Registrar ID assigned by ICANN.
o An OPTIONAL <contentTag> element that contains a tag that defines
the expected content in the deposit. The producer and consumer of
the deposits will coordinate the set of possible <contentTag>
element values.
Example of <rdeHeader:header> object referencing only the XML Model Example of <rdeHeader:header> object referencing only the XML Model
objects: objects:
... ...
<rdeHeader:header> <rdeHeader:header>
<rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:tld>test</rdeHeader:tld>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2</rdeHeader:count> uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeHost-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:rdeHost-1.0">1</rdeHeader:count>
skipping to change at page 95, line 17 skipping to change at page 95, line 17
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.2. RDE Domain Object 9.2. RDE Domain Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 103, line 7 skipping to change at page 103, line 7
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.4. RDE Host Object 9.4. RDE Host Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 108, line 21 skipping to change at page 108, line 21
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.6. RDE Contact Object 9.6. RDE Contact Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 117, line 42 skipping to change at page 117, line 42
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.8. RDE Registrar Object 9.8. RDE Registrar Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 125, line 26 skipping to change at page 125, line 26
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.10. RDE IDN Table Reference Objects 9.10. RDE IDN Table Reference Objects
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 129, line 20 skipping to change at page 129, line 20
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.12. EPP Parameters Object 9.12. EPP Parameters Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 131, line 8 skipping to change at page 131, line 8
type="epp:dcpType"/> type="epp:dcpType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.13. NNDN Object 9.13. NNDN Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 136, line 12 skipping to change at page 136, line 12
type="rdeCsv:fBooleanType" type="rdeCsv:fBooleanType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.15. Policy Object 9.15. Policy Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 137, line 36 skipping to change at page 137, line 36
<attribute name="scope" type="token" use="required"/> <attribute name="scope" type="token" use="required"/>
<attribute name="element" type="anyURI" use="required"/> <attribute name="element" type="anyURI" use="required"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.16. Header Object 9.16. Header Object
Copyright (c) 2011 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions modification, are permitted provided that the following conditions
are met: are met:
o Redistributions of source code must retain the above copyright o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright o Redistributions in binary form must reproduce the above copyright
skipping to change at page 138, line 49 skipping to change at page 138, line 49
substitutionGroup="rde:content"/> substitutionGroup="rde:content"/>
<!-- Content Type --> <!-- Content Type -->
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<group ref="rdeHeader:repositoryTypeGroup"/> <group ref="rdeHeader:repositoryTypeGroup"/>
<element name="count" type="rdeHeader:countType" <element name="count" type="rdeHeader:countType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<element name="contentTag" type="token"
minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<group name="repositoryTypeGroup"> <group name="repositoryTypeGroup">
<choice> <choice>
<element name="tld" type="eppcom:labelType" /> <element name="tld" type="eppcom:labelType" />
<element name="registrar" type="positiveInteger"/> <element name="registrar" type="positiveInteger"/>
<element name="ppsp" type="token"/> <element name="ppsp" type="token"/>
<element name="reseller" type="token"/> <element name="reseller" type="token"/>
</choice> </choice>
</group> </group>
skipping to change at page 153, line 27 skipping to change at page 153, line 33
definition examples. definition examples.
19. Added the choice between the use of the <csvRegistrar:fId> and 19. Added the choice between the use of the <csvRegistrar:fId> and
<csvRegistrar:fGurid> fields in the deletes "registrar" CSV <csvRegistrar:fGurid> fields in the deletes "registrar" CSV
definition to be consistent with the "registrar" CSV definition. definition to be consistent with the "registrar" CSV definition.
20. Made the <crRr> and <crDate> elements optional for the host and 20. Made the <crRr> and <crDate> elements optional for the host and
contact objects in the XML model to be consistent with the contact objects in the XML model to be consistent with the
domain object. domain object.
16.15. Changes REGEXT 02 to REGEXT 03
1. Added the optional element contentTag in the header object.
2. Editorial updates
17. Example of a full deposit using the XML model 17. Example of a full deposit using the XML model
Example of a full deposit using the XML model: Example of a full deposit using the XML model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="FULL" id="20101017001" prevId="20101010001" <rde:deposit type="FULL" id="20101017001" prevId="20101010001"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
skipping to change at page 181, line 19 skipping to change at page 181, line 33
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
August 2009, <https://www.rfc-editor.org/info/rfc5733>. August 2009, <https://www.rfc-editor.org/info/rfc5733>.
[RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
Security Extensions Mapping for the Extensible Security Extensions Mapping for the Extensible
Provisioning Protocol (EPP)", RFC 5910, Provisioning Protocol (EPP)", RFC 5910,
DOI 10.17487/RFC5910, May 2010, DOI 10.17487/RFC5910, May 2010,
<https://www.rfc-editor.org/info/rfc5910>. <https://www.rfc-editor.org/info/rfc5910>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
21.2. Informative References 21.2. Informative References
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981, DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>. <https://www.rfc-editor.org/info/rfc791>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
 End of changes. 26 change blocks. 
24 lines changed or deleted 46 lines changed or added

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