draft-ietf-eppext-keyrelay-02.txt   draft-ietf-eppext-keyrelay-03.txt 
eppext H. Ribbers eppext H. Ribbers
Internet-Draft M. Groeneweg Internet-Draft M. Groeneweg
Intended status: Standards Track SIDN Intended status: Standards Track SIDN
Expires: November 1, 2015 R. Gieben Expires: December 11, 2015 R. Gieben
A. Verschuren A. Verschuren
April 30, 2015 June 09, 2015
Key Relay Mapping for the Extensible Provisioning Protocol Key Relay Mapping for the Extensible Provisioning Protocol
draft-ietf-eppext-keyrelay-02 draft-ietf-eppext-keyrelay-03
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
mapping for a key relay object that relays DNSSEC key material mapping for a key relay object that relays DNSSEC key material
between EPP clients using the poll queue defined in [RFC5730]. between EPP clients using the poll queue defined in [RFC5730].
This key relay mapping will help facilitate changing the DNS operator This key relay mapping will help facilitate changing the DNS operator
of a domain while keeping the DNSSEC chain of trust intact. of a domain while keeping the DNSSEC chain of trust intact.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 November 1, 2015. This Internet-Draft will expire on December 11, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
1.2. Secure Transfer of DNSSEC Key Material . . . . . . . . . 3 1.2. Secure Transfer of DNSSEC Key Material . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
2.1. DNSSEC Key Material . . . . . . . . . . . . . . . . . . . 4 2.1. DNSSEC Key Material . . . . . . . . . . . . . . . . . . . 4
2.1.1. <keyRelayData> element . . . . . . . . . . . . . . . 4 2.1.1. <keyRelayData> element . . . . . . . . . . . . . . . 4
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 5 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 5
3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 5 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 5
3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 8 3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 8
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 10 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 10
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 10 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 10
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 12 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 12 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
7.1. Normative References . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2. Informative References . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 13 Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 13
A.1. draft-gieben-epp-keyrelay-00 . . . . . . . . . . . . . . 13 A.1. draft-gieben-epp-keyrelay-00 . . . . . . . . . . . . . . 14
A.2. draft-gieben-epp-keyrelay-01 . . . . . . . . . . . . . . 14 A.2. draft-gieben-epp-keyrelay-01 . . . . . . . . . . . . . . 14
A.3. draft-gieben-epp-keyrelay-02 . . . . . . . . . . . . . . 14 A.3. draft-gieben-epp-keyrelay-02 . . . . . . . . . . . . . . 14
A.4. draft-gieben-epp-keyrelay-03 . . . . . . . . . . . . . . 14 A.4. draft-gieben-epp-keyrelay-03 . . . . . . . . . . . . . . 14
A.5. draft-ietf-eppext-keyrelay-00 . . . . . . . . . . . . . . 14 A.5. draft-ietf-eppext-keyrelay-00 . . . . . . . . . . . . . . 14
A.6. draft-ietf-eppext-keyrelay-01 . . . . . . . . . . . . . . 14 A.6. draft-ietf-eppext-keyrelay-01 . . . . . . . . . . . . . . 14
A.7. draft-ietf-eppext-keyrelay-02 . . . . . . . . . . . . . . 15 A.7. draft-ietf-eppext-keyrelay-02 . . . . . . . . . . . . . . 15
A.8. draft-ietf-eppext-keyrelay-03 . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
There are certain transactions initiated by a DNS-operator, which There are certain transactions initiated by a DNS-operator, which
require an authenticated exchange of information between DNS- require an authenticated exchange of information between DNS-
operators. Often, there is no direct channel between these parties operators. Often, there is no direct channel between these parties
or it is non-scalable and insecure. or it is non-scalable and insecure.
One such transaction is the exchange of DNSSEC key material when One such transaction is the exchange of DNSSEC key material when
skipping to change at page 4, line 23 skipping to change at page 4, line 23
+--------------------+ +---------------------+ +--------------------+ +---------------------+
| ^ | ^
EPP keyrelay | | EPP poll EPP keyrelay | | EPP poll
V | V |
+-----------------------------+ +-----------------------------+
| registry | | registry |
+-----------------------------+ +-----------------------------+
Figure 1: Transfer of DNSSEC key material. Figure 1: Transfer of DNSSEC key material.
There is no clear distinction in the EPP protocol between Registrars There is no distinction in the EPP protocol between Registrars and
and DNS-operators. Therefore the term EPP client will be used for DNS-operators, there is only mention of an EPP client and EPP server.
the interaction with the registry for relaying DNSSEC key material. Therefore the term EPP client will be used for the interaction with
the EPP server for relaying DNSSEC key material.
2. Object Attributes 2. Object Attributes
2.1. DNSSEC Key Material 2.1. DNSSEC Key Material
The DNSSEC key material is represented in EPP by a <keyRelayData> The DNSSEC key material is represented in EPP by a <keyRelayData>
element. element.
It is up to the gaining EPP client to select the keys that are needed It is up to the gaining EPP client to select the keys that are needed
to complete the intended transaction successfully. It is up to the to complete the intended transaction successfully. It is up to the
receiving EPP client to validate the correctness of the key material. receiving EPP client to validate the correctness of the key material.
The server is merely used as a relay channel. The server is merely used as a relay channel.
2.1.1. <keyRelayData> element 2.1.1. <keyRelayData> element
The <keyRelayData> contains the following elements: The <keyRelayData> contains the following elements:
o One or more REQUIRED <keyData> elements that contains the DNSSEC o One or more REQUIRED <keyData> element(s) that contains the DNSSEC
key material as described in [RFC5910], Section 4.2. key material as described in [RFC5910], Section 4.2. A server MAY
apply a server policy that specifies the number of <keyData>
elements that can be incorporated. When a server policy is
specified, a server SHOULD respond with an EPP result code 2308
"Data management policy violation".
o A REQUIRED <authInfo> element that contains authorization o A REQUIRED <authInfo> element that contains authorization
information associated with the domain object ([RFC5731], information associated with the domain object ([RFC5731],
Section 3.2.1). Section 3.2.1).
o An OPTIONAL <expiry> element that describes the expected lifetime o An OPTIONAL <expiry> element that describes the expected lifetime
of the relayed key(s) in the zone. The losing DNS operator can of the relayed key(s) in the zone. The losing DNS operator can
use this as an indication when to safely remove the inserted key use this as an indication when to safely remove the inserted key
material from the zone. This may be because the transaction that material from the zone. This may be because the transaction that
needed the insertion is either completed or has been abandoned if needed the insertion is either completed or has been abandoned if
skipping to change at page 5, line 49 skipping to change at page 6, line 9
The EPP <info> response for key relay objects is used in the EPP poll The EPP <info> response for key relay objects is used in the EPP poll
response, as described in [RFC5730]. The key relay object created response, as described in [RFC5730]. The key relay object created
with the <create> command, described in Section 3.2.1 is inserted with the <create> command, described in Section 3.2.1 is inserted
into the receiving client's poll queue. The receiving client will into the receiving client's poll queue. The receiving client will
receive the key relay object using the EPP <poll> command, as receive the key relay object using the EPP <poll> command, as
described in [RFC5730]. described in [RFC5730].
When a <poll> command has been processed successfully for a key relay When a <poll> command has been processed successfully for a key relay
poll message, the EPP <resData> element MUST contain a child poll message, the EPP <resData> element MUST contain a child
<keyrelay:infData> element that identifies the keyrelay namespace. <keyrelay:infData> element that is identified by the keyrelay
The <keyrelay:infData> element contains the following child elements: namespace. The <keyrelay:infData> element contains the following
child elements:
o A REQUIRED <name> element containing the domain name for which the o A REQUIRED <name> element containing the domain name for which the
DNSSEC key material is relayed. DNSSEC key material is relayed.
o A REQUIRED <keyRelayData> elements containing data to be relayed,
as defined in Section 2.1
o An OPTIONAL <keyrelay:crDate> element that contains the date and o An OPTIONAL <keyrelay:crDate> element that contains the date and
time of the submitted <create> command. time of the submitted <create> command.
o An OPTIONAL <keyrelay:reID> element that contains the identifier of o An OPTIONAL <keyrelay:reID> element that contains the identifier of
the client that requested the key relay. the client that requested the key relay.
o An OPTIONAL <keyrelay:acID> element that contains the identifier of o An OPTIONAL <keyrelay:acID> element that contains the identifier of
the client that SHOULD act upon the key relay. the client that SHOULD act upon the key relay.
Example <poll> response: Example <poll> response:
skipping to change at page 7, line 47 skipping to change at page 7, line 47
S: </keyrelay:crDate> S: </keyrelay:crDate>
S: <keyrelay:reID> S: <keyrelay:reID>
S: ClientX S: ClientX
S: </keyrelay:reID> S: </keyrelay:reID>
S: <keyrelay:acID> S: <keyrelay:acID>
S: ClientY S: ClientY
S: </keyrelay:acID> S: </keyrelay:acID>
S: </keyrelay:infData> S: </keyrelay:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>BCD-23456</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>65432-WXY</svTRID> S: <svTRID>54321-ZYX</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
3.1.3. EPP <transfer> Command 3.1.3. EPP <transfer> Command
Transfer semantics do not apply to key relay objects, so there is no Transfer semantics do not apply to key relay objects, so there is no
mapping defined for the EPP <transfer> command. mapping defined for the EPP <transfer> command.
3.2. EPP Transform Commands 3.2. EPP Transform Commands
skipping to change at page 8, line 36 skipping to change at page 8, line 36
provided domain name. provided domain name.
In addition to the standard EPP command elements, the <create> In addition to the standard EPP command elements, the <create>
command MUST contain a <keyrelay:create> element that identifies the command MUST contain a <keyrelay:create> element that identifies the
keyrelay namespace. The <keyrelay:create> element contains the keyrelay namespace. The <keyrelay:create> element contains the
following child elements: following child elements:
o A REQUIRED <keyrelay:name> element containing the domain name for o A REQUIRED <keyrelay:name> element containing the domain name for
which the DNSSEC key material is relayed. which the DNSSEC key material is relayed.
o A REQUIRED <keyrelay:keyRelayData> elements containing data to be o A REQUIRED <keyrelay:keyRelayData> element containing data to be
relayed, as defined in Section 2.1 relayed, as defined in Section 2.1
Example <create> command: Example <create> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:keyrelay="urn:ietf:params:xml:ns:keyrelay-1.0" C: xmlns:keyrelay="urn:ietf:params:xml:ns:keyrelay-1.0"
C: xmlns:s="urn:ietf:params:xml:ns:secDNS-1.1" C: xmlns:s="urn:ietf:params:xml:ns:secDNS-1.1"
C: xmlns:d="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:d="urn:ietf:params:xml:ns:domain-1.0">
C: <command> C: <command>
skipping to change at page 9, line 30 skipping to change at page 9, line 30
C: </keyrelay:keyData> C: </keyrelay:keyData>
C: <keyrelay:authInfo> C: <keyrelay:authInfo>
C: <d:pw>JnSdBAZSxxzJ</d:pw> C: <d:pw>JnSdBAZSxxzJ</d:pw>
C: </keyrelay:authInfo> C: </keyrelay:authInfo>
C: <keyrelay:expiry> C: <keyrelay:expiry>
C: <keyrelay:relative>P1M13D</keyrelay:relative> C: <keyrelay:relative>P1M13D</keyrelay:relative>
C: </keyrelay:expiry> C: </keyrelay:expiry>
C: </keyrelay:keyRelayData> C: </keyrelay:keyRelayData>
C: </keyrelay:create> C: </keyrelay:create>
C: </create> C: </create>
C: <clTRID>123456</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When a server has succesfully processed the <create> command it MUST When a server has succesfully processed the <create> command it MUST
respond with a standard EPP response. See [RFC5730], Section 2.6. respond with a standard EPP response. See [RFC5730], Section 2.6.
Example <create> response: Example <create> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
skipping to change at page 11, line 15 skipping to change at page 11, line 15
<import namespace="urn:ietf:params:xml:ns:domain-1.0" <import namespace="urn:ietf:params:xml:ns:domain-1.0"
schemaLocation="domain-1.0.xsd" /> schemaLocation="domain-1.0.xsd" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType" /> <element name="keyRelayData" type="keyrelay:keyRelayDataType" />
<element name="infData" type="keyrelay:infDataType" /> <element name="infData" type="keyrelay:infDataType" />
<element name="create" type="keyrelay:createType" /> <element name="create" type="keyrelay:createType" />
<complexType name="createType"> <complexType name="createType">
<sequence> <sequence>
<element name="name" type="eppcom:labelType" /> <element name="name" type="eppcom:labelType" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType" <element name="keyRelayData" type="keyrelay:keyRelayDataType" />
minOccurs="1" />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="infDataType"> <complexType name="infDataType">
<sequence> <sequence>
<element name="name" type="eppcom:labelType" minOccurs="1" /> <element name="name" type="eppcom:labelType" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType" <element name="keyRelayData" type="keyrelay:keyRelayDataType" />
minOccurs="1" />
<element name="crDate" type="dateTime"/> <element name="crDate" type="dateTime"/>
<element name="reID" type="eppcom:clIDType" /> <element name="reID" type="eppcom:clIDType" />
<element name="acID" type="eppcom:clIDType" /> <element name="acID" type="eppcom:clIDType" />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="keyRelayDataType"> <complexType name="keyRelayDataType">
<sequence> <sequence>
<element name="keyData" type="secDNS:keyDataType" minOccurs="1" <element name="keyData" type="secDNS:keyDataType" maxOccurs="unbounded" />
maxOccurs="unbounded" />
<element name="authInfo" type="domain:authInfoType" /> <element name="authInfo" type="domain:authInfoType" />
<element name="expiry" type="keyrelay:keyRelayExpiryType" minOccurs="0" /> <element name="expiry" type="keyrelay:keyRelayExpiryType" minOccurs="0" />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="keyRelayExpiryType"> <complexType name="keyRelayExpiryType">
<choice> <choice>
<element name="absolute" type="dateTime" /> <element name="absolute" type="dateTime" />
<element name="relative" type="duration" /> <element name="relative" type="duration" />
</choice> </choice>
</complexType> </complexType>
skipping to change at page 12, line 23 skipping to change at page 12, line 18
document. document.
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry 5.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: details of the registration are as follows:
Name of Extension: "Keyrelay Extension for the Extensible Name of Extension: "Key Relay Mapping for the Extensible Provisioning
Provisioning Protocol" Protocol"
Document status: Standards Track Document status: Standards Track
Reference: (insert reference to RFC version of this document) Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: IESG, iesg@ietf.org Registrant Name and Email Address: IESG, iesg@ietf.org
TLDs: Any TLDs: Any
IPR Disclosure: https://datatracker.ietf.org/ipr/2393/ IPR Disclosure: https://datatracker.ietf.org/ipr/2393/
skipping to change at page 13, line 12 skipping to change at page 13, line 5
<keyrelay:create> command if it detects the mechanism is being <keyrelay:create> command if it detects the mechanism is being
abused. abused.
For the <keyrelay:keyRelayData> data a correct <domain:authInfo> For the <keyrelay:keyRelayData> data a correct <domain:authInfo>
element SHOULD be used as an indication that putting the key material element SHOULD be used as an indication that putting the key material
on the receiving EPP clients poll queue is authorized by the on the receiving EPP clients poll queue is authorized by the
_registrant_ of that domain name. The authorization of EPP clients _registrant_ of that domain name. The authorization of EPP clients
to perform DNS changes is not covered in this I-D as it depends on to perform DNS changes is not covered in this I-D as it depends on
registry specific policy. registry specific policy.
7. References 7. Acknowledgements
7.1. Normative References We like to thank the following individuals for their valuable input,
review, constructive criticism in earlier revisions or support for
the concepts described in this document:
Maarten Wullink, Marco Davids, Ed Lewis, James Mitchell, David Peal,
Patrik Faltstrom, Klaus Malorny, James Gould, Patrick Mevzek, Seth
Goldman, Maarten Bosteels and Ulrich Wisser.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009. STD 69, RFC 5730, August 2009.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, August 2009. Domain Name Mapping", STD 69, RFC 5731, August 2009.
[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, May 2010. Provisioning Protocol (EPP)", RFC 5910, May 2010.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, February 2015. Provisioning Protocol", RFC 7451, February 2015.
7.2. Informative References 8.2. Informative References
[I-D.koch-dnsop-dnssec-operator-change] [I-D.koch-dnsop-dnssec-operator-change]
Koch, P., Sanz, M., and A. Verschuren, "Changing DNS Koch, P., Sanz, M., and A. Verschuren, "Changing DNS
Operators for DNSSEC signed Zones", draft-koch-dnsop- Operators for DNSSEC signed Zones", draft-koch-dnsop-
dnssec-operator-change-06 (work in progress), February dnssec-operator-change-06 (work in progress), February
2014. 2014.
Appendix A. Changelog Appendix A. Changelog
[This section should be removed by the RFC editor before publishing] [This section should be removed by the RFC editor before publishing]
skipping to change at page 15, line 14 skipping to change at page 15, line 17
3. Restructuring the document to make it more inline with existing 3. Restructuring the document to make it more inline with existing
EPP extensions. EPP extensions.
A.7. draft-ietf-eppext-keyrelay-02 A.7. draft-ietf-eppext-keyrelay-02
1. Updated the XML structure based on WG feedback 1. Updated the XML structure based on WG feedback
2. Updated the wording 2. Updated the wording
A.8. draft-ietf-eppext-keyrelay-03
1. Updated the document title in the EPP Extension Registry section
2. Restored Acknowledgement section, thanks to Marco Davids
3. Incorperated feedback from Patrick Mevzek
Authors' Addresses Authors' Addresses
Rik Ribbers Rik Ribbers
SIDN SIDN
Meander 501 Meander 501
Arnhem 6825 MD Arnhem 6825 MD
NL NL
Email: rik.ribbers@sidn.nl Email: rik.ribbers@sidn.nl
URI: https://www.sidn.nl/ URI: https://www.sidn.nl/
 End of changes. 24 change blocks. 
36 lines changed or deleted 56 lines changed or added

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