draft-ietf-eppext-keyrelay-01.txt   draft-ietf-eppext-keyrelay-02.txt 
eppext R. Gieben eppext H. Ribbers
Internet-Draft Google Internet-Draft M. Groeneweg
Intended status: Standards Track M. Groeneweg Intended status: Standards Track SIDN
Expires: July 12, 2015 H. Ribbers Expires: November 1, 2015 R. Gieben
SIDN Labs
A. Verschuren A. Verschuren
January 8, 2015 April 30, 2015
Relay Extension for the Extensible Provisioning Protocol Key Relay Mapping for the Extensible Provisioning Protocol
draft-ietf-eppext-keyrelay-01 draft-ietf-eppext-keyrelay-02
Abstract Abstract
This document describes a generic Extensible Provisioning Protocol This document describes an Extensible Provisioning Protocol (EPP)
(EPP) extension for the purpose of relaying data between registrars. mapping for a key relay object that relays DNSSEC key material
between EPP clients using the poll queue defined in [RFC5730].
Furthermore, this document describes a specific implementation for
relaying DNSSEC key material between DNS operators (by means of their
respective registrars), to facilitate the change of DNS operator,
while keeping the DNSSEC chain of trust intact.
This I-D introduces a new generic command <relay> and an element This key relay mapping will help facilitate changing the DNS operator
<relayData>. For the specific implementation of relaying DNSSEC key of a domain while keeping the DNSSEC chain of trust intact.
material it introduces an extension of the <relayData> with a
<keyRelayData> element.
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 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 July 12, 2015. This Internet-Draft will expire on November 1, 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
1.2. Relaying Data . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Secure Transfer of DNSSEC Key Material . . . . . . . . . 3
1.2.1. Rationale For a New Command . . . . . . . . . . . . . 4 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
1.2.2. Extending <relayData> per use case . . . . . . . . . 4 2.1. DNSSEC Key Material . . . . . . . . . . . . . . . . . . . 4
1.3. Secure Transfer of DNSSEC Key Material . . . . . . . . . 4 2.1.1. <keyRelayData> element . . . . . . . . . . . . . . . 4
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 5 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5
2.1. DNSSEC Key Material . . . . . . . . . . . . . . . . . . . 5 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 5
3.1. EPP Transient Commands . . . . . . . . . . . . . . . . . 6 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 5
3.1.1. EPP <relay> Command . . . . . . . . . . . . . . . . . 6 3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 8
3.2. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8
3.2.1. EPP <poll> command . . . . . . . . . . . . . . . . . 7 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 10
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 10
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. Formal Syntax <relay> command and POLL response . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
4.2. Formal Syntax <keyRelayData> data . . . . . . . . . . . . 11 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1. Normative References . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . 13
7.2. Informative References . . . . . . . . . . . . . . . . . 13 7.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 . . . . . . . . . . . . . . 13
A.2. draft-gieben-epp-keyrelay-01 . . . . . . . . . . . . . . 13 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
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
There are certain transactions in the lifecycle of a domain name, There are certain transactions initiated by a DNS-operator, which
that require interaction between registrars but need registration require an authenticated exchange of information between DNS-
data from the registry. Since all registrars involved have a secure operators. Often, there is no direct channel between these parties
channel to the registry for maintaining the delegation, the registry or it is non-scalable and insecure.
can act as relay for such data to transfer securely and authoritative
between the registrars involved.
Currently these transactions aren't supported in the Extensible
Provisioning Protocol (EPP) [RFC5730]. One example of such a
transaction is the exchange of DNSSEC key material to keep the DNSSEC
chain of trust intact in case of a change of DNS-operator.
In this document we will define:
o A protocol extension that implements the relaying of data between One such transaction is the exchange of DNSSEC key material when
registrars through the existing authenticated EPP channel. This changing the DNS operator for DNSSEC signed zones. We suggest that
protocol extension introduces a new EPP command called <relay> DNS-operators use the administrative EPP channel to bootstrap the
with an element <relayData>. delegation by relaying DNSSEC key material for the zone.
o An extension to the <relayData> element called <keyRelayData> that In this document we define an EPP extension to support and automate
can be used for the relaying DNSSEC key material using the <relay> this transaction.
command.
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
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 BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented in order to develop a conforming character case presented in order to develop a conforming
implementation. implementation.
In examples, "C:" represents lines sent by a protocol client, and In examples, "C:" represents lines sent by a protocol client, and
"S:" represents lines returned by a protocol server. Indentation and "S:" represents lines returned by a protocol server. Indentation and
white space in examples is provided only to illustrate element white space in examples is provided only to illustrate element
relationships and is not a mandatory feature of this protocol. relationships and is not a mandatory feature of this protocol.
1.2. Relaying Data 1.2. Secure Transfer of DNSSEC Key Material
The <relay> command uses the existing authenticated EPP channel
between the registrar and the registry. Registrars can use this
secure channel for relaying data to other registrars. The registry
serves as an intermediary between two registrars (see Figure 1).
+-------------+ relayData +-------------+
| registrar X |~~~~~~~~~~~~>| registrar Y |
+-------------+ +-------------+
| ^
| EPP relay EPP poll |
v |
+-----------------------------+
| registry |
+-----------------------------+
Figure 1: Registry acting as a relay for secure data exchange between
registrars.
The <relay> command uploads data from a registrar X to the registry.
The uploaded data is then pushed onto the message queue of registrar
Y by the registry based on the information within the <relayData>
element of the <relay> command and the registration data maintained
by the registry.
The data to be relayed MUST relate to registration data of the
registry. The <relay> command is not intended to relay data that has
no relationship to registration data. We have e-mail for that.
If for some reason the registry cannot process the <relay> command,
an EPP error response MUST be returned. If the registry does process
the <relay> command it MUST put all elements of <relayData> on to the
message queue of registrar Y.
1.2.1. Rationale For a New Command
This new <relay> command can be best described as a "transient
command" as it only facilitates communication of data between two
registrars without changing the registration data at the registry.
No existing EPP command can be (re)used for this function. This
extension of EPP is in accordance to [RFC3735].
1.2.2. Extending <relayData> per use case
One MUST extend the <relayData> element per use case to define the
data to be relayed. In the extension, one MUST make provisions for
the registry how to determine the receiving registrar of the <relay>
command.
1.3. Secure Transfer of DNSSEC Key Material
Exchanging DNSSEC key material in preparation of a domain name Exchanging DNSSEC key material in preparation of a domain name
transfer is one of the phases in the lifecycle of a domain name transfer is one of the phases in the lifecycle of a domain name
[I-D.koch-dnsop-dnssec-operator-change]. [I-D.koch-dnsop-dnssec-operator-change].
DNS-operators need to exchange (through the gaining registrar) DNSSEC DNS-operators need to exchange DNSSEC key material before the
key material before the registration data can be changed. registration data can be changed to keep the DNSSEC chain of trust
intact. This exchange is normally initiated through the gaining
registrar.
The gaining and losing DNS operators could talk directly to each
other (the ~ arrow) to exchange the DNSKEY, but often there is no
trusted path between the two. As both can securely interact with the
registry over the administrative channel through the registrar, the
registry can act as a relay for the key material exchange.
+--------------------+ DNSKEY +---------------------+ +--------------------+ DNSKEY +---------------------+
|gaining DNS operator| ~~~~~~~~> | losing DNS operator | |gaining DNS operator| ~~~~~~~~> | losing DNS operator |
+--------------------+ +---------------------+ +--------------------+ +---------------------+
| ^ | ^
| | | |
V | V |
+--------------------+ +---------------------+ +--------------------+ +---------------------+
| gaining registrar | | registrar of record | | gaining registrar | | registrar of record |
+--------------------+ +---------------------+ +--------------------+ +---------------------+
| ^ | ^
EPP relay | | EPP poll EPP keyrelay | | EPP poll
V | V |
+-----------------------------+ +-----------------------------+
| registry | | registry |
+-----------------------------+ +-----------------------------+
Figure 2: Transfer of DNSSEC key material. Figure 1: Transfer of DNSSEC key material.
As the <relay> command uses a secure channel, it can be used as a
method for exchanging this DNSSEC key material securely (see
Figure 2).
The gaining and losing DNS operators could talk directly to each
other (the ~ arrow) to exchange the DNSKEY, but often there is no
trusted path between the two. As both can securely interact with the
registry over the administrative channel through the registrar, the
registry can act as a relay for the key material exchange.
This I-D contains an extension of the <relayData> element for this There is no clear distinction in the EPP protocol between Registrars
use case. and DNS-operators. Therefore the term EPP client will be used for
the interaction with the registry for relaying DNSSEC key material.
2. Object Attributes 2. Object Attributes
2.1. DNSSEC Key Material 2.1. DNSSEC Key Material
To transfer DNSSEC key material with the <relay> command the generic The DNSSEC key material is represented in EPP by a <keyRelayData>
<relayData> is extended with a <keyRelayData> element that contains element.
the data for relaying the key material. See Section 1.2.2.
This <keyRelayData> element REQUIRES a minimum of three child It is up to the gaining EPP client to select the keys that are needed
elements: to complete the intended transaction successfully. It is up to the
receiving EPP client to validate the correctness of the key material.
The server is merely used as a relay channel.
o A <name> element which contains the domain name for which we 2.1.1. <keyRelayData> element
upload the key. The registry MUST relay the <keyRelayData> to the
registrar of record of the provided domain name.
o One or more <keyData> elements that contains the DNSSEC key The <keyRelayData> contains the following elements:
material as described in [RFC5910], Section 4.2.
o An <authInfo> element that contains an authorization token o One or more REQUIRED <keyData> elements that contains the DNSSEC
([RFC5731], Section 3.2.1). This indicates that the registrar has key material as described in [RFC5910], Section 4.2.
authorization from the registrant to change the zone data, and a
possible future transfer is authorized. The registry MAY check if
the <authInfo> data is correct and if it does, it MUST return an
EPP error response if the authorization token is not correct.
And an OPTIONAL <expiry> child element. o A REQUIRED <authInfo> element that contains authorization
information associated with the domain object ([RFC5731],
Section 3.2.1).
o An <expiry> element that describes the expected lifetime of the o An OPTIONAL <expiry> element that describes the expected lifetime
relayed key(s) in the zone. The losing DNS operator can use this of the relayed key(s) in the zone. The losing DNS operator can
as an indication when to safely remove the inserted key material use this as an indication when to safely remove the inserted key
from the zone. This may be because the transaction that needed material from the zone. This may be because the transaction that
the insertion is either completed or has been abandoned if not needed the insertion is either completed or has been abandoned if
completed before this expire time. The <expiry> element MUST not completed before this expire time. The <expiry> element MUST
contain one of the following child elements: contain one of the following child elements:
* <absolute/>: The policy is valid from the current date and time * <absolute>: The policy is valid from the current date and time
until it expires on the specified date and time. until it expires on the specified date and time.
* <relative/>: The policy is valid from the current date and time * <relative>: The policy is valid from the current date and time
until the end of the specified duration. until the end of the specified duration.
3. EPP Command Mapping 3. EPP Command Mapping
3.1. EPP Transient Commands A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. The command
mapping described here is specifically for use in this key relay
mapping.
3.1.1. EPP <relay> Command 3.1. EPP Query Commands
The EPP <relay> command is a generic EPP command used for relaying EPP provides three commands to retrieve object information: <check>
data between registrars. It contains the data to be relayed and the to determine if an object is known to the server, <info> to retrieve
client transaction identifier. It has been designed to be extensible detailed information associated with an object, and <transfer> to
for usage in other use-cases. retrieve object transfer status information.
The <relay> command REQUIRES the following child elements: 3.1.1. EPP <check> Command
o One or more <relayData> elements containing data to be relayed. Check semantics do not apply to key relay objects, so there is no
mapping defined for the EPP <check> command and the EPP <check>
response.
o An OPTIONAL <clTRID> (client transaction identifier) element that 3.1.2. EPP <info> Command
MAY be used to uniquely identify the command to the registrar.
See [RFC5730], Section 2.5.
Example <relay> command: Info command semantics do not apply to the key relay objects, so
there is no mapping defined for the EPP <info> Command.
C:<?xml version="1.0" encoding=:UTF-8" standalone="no"?> The EPP <info> response for key relay objects is used in the EPP poll
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" response, as described in [RFC5730]. The key relay object created
C: xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" with the <create> command, described in Section 3.2.1 is inserted
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" into the receiving client's poll queue. The receiving client will
C: xmlns:r="urn:ietf:params:xml:ns:relay-1.0"> receive the key relay object using the EPP <poll> command, as
C: <extension> described in [RFC5730].
C: <r:relay xmlns:r="urn:ietf:params:xml:ns:relay-1.0">
C: <r:relayData>
C: <k:keyRelayData
C: xmlns:k="urn:ietf:params:xml:ns:keyrelay-1.0">
C: <k:name>example.org</k:name>
C: <k:keyData>
C: <secDNS:flags>256</secDNS:flags>
C: <secDNS:protocol>3</secDNS:protocol>
C: <secDNS:alg>8</secDNS:alg>
C: <secDNS:pubKey>
C: cmlraXN0aGViZXN0</secDNS:pubKey>
C: </k:keyData>
C: <k:authInfo>
C: <domain:pw>JnSdBAZSxxzJ</domain:pw>
C: </k:authInfo>
C: <k:expiry>
C: <k:relative>P1M13D</k:relative>
C: </k:expiry>
C: </k:keyRelayData>
C: </r:relayData>
C: <r:clTRID>ABC-12345</r:clTRID>
C: </r:relay>
C: </extension>
C:</epp>
3.2. EPP Query Commands When a <poll> command has been processed successfully for a key relay
poll message, the EPP <resData> element MUST contain a child
<keyrelay:infData> element that identifies the keyrelay namespace.
The <keyrelay:infData> element contains the following child elements:
This EPP extension does not change any command other than the EPP o A REQUIRED <name> element containing the domain name for which the
<poll> command response. DNSSEC key material is relayed.
3.2.1. EPP <poll> command o A REQUIRED <keyRelayData> elements containing data to be relayed,
as defined in Section 2.1
This extension adds elements to the response to a <poll> command with o An OPTIONAL <keyrelay:crDate> element that contains the date and
the "op" attribute set to "req". Specifically, a <panData> element time of the submitted <create> command.
is added to the <resData> section of the service message, containing
the following elements:
o A REQUIRED <relayData> element that contains the relayed data. o An OPTIONAL <keyrelay:reID> element that contains the identifier of
the client that requested the key relay.
o A REQUIRED <paDate> element that contains the date and time of the o An OPTIONAL <keyrelay:acID> element that contains the identifier of
submitted <relay> command. the client that SHOULD act upon the key relay.
o A REQUIRED <reID> element that contains the identifier of the Example <poll> response:
registrar that requested the data relay.
o A REQUIRED <acID> element that contains the identifier of the S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
registrar that SHOULD act upon the data relay. S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:keyrelay="urn:ietf:params:xml:ns:keyrelay-1.0"
S: xmlns:s="urn:ietf:params:xml:ns:secDNS-1.1"
S: xmlns:d="urn:ietf:params:xml:ns:domain-1.0">
S: <response>
S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate>
S: <msg>Keyrelay action completed successfully.</msg>
S: </msgQ>
S: <resData>
S: <keyrelay:infData>
S: <keyrelay:name>example.org</keyrelay:name>
S: <keyrelay:keyRelayData>
S: <keyrelay:keyData>
S: <s:flags>256</s:flags>
S: <s:protocol>3</s:protocol>
S: <s:alg>8</s:alg>
S: <s:pubKey>cmlraXN0aGViZXN0</s:pubKey>
S: </keyrelay:keyData>
S: <keyrelay:authInfo>
S: <d:pw>JnSdBAZSxxzJ</d:pw>
S: </keyrelay:authInfo>
S: <keyrelay:expiry>
S: <keyrelay:relative>P1M13D</keyrelay:relative>
S: </keyrelay:expiry>
S: </keyrelay:keyRelayData>
S: <keyrelay:crDate>
S: 1999-04-04T22:01:00.0Z
S: </keyrelay:crDate>
S: <keyrelay:reID>
S: ClientX
S: </keyrelay:reID>
S: <keyrelay:acID>
S: ClientY
S: </keyrelay:acID>
S: </keyrelay:infData>
S: </resData>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp>
Example <poll> response: 3.1.3. EPP <transfer> Command
S:<?xml version="1.0" encoding=:UTF-8" standalone="no"?> Transfer semantics do not apply to key relay objects, so there is no
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" mapping defined for the EPP <transfer> command.
S: xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <response>
S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate>
S: <msg>Relay action completed successfully.</msg>
S: </msgQ>
S: <resData>
S: <r:panData xmlns:r="urn:ietf:params:xml:ns:relay-1.0">
S: <r:relayData>
S: <k:keyRelayData
S: xmlns:k="urn:ietf:params:xml:ns:keyrelay-1.0">
S: <k:name>example.org</k:name>
S: <k:keyData>
S: <secDNS:flags>256</secDNS:flags>
S: <secDNS:protocol>3</secDNS:protocol>
S: <secDNS:alg>8</secDNS:alg>
S: <secDNS:pubKey>
S: cmlraXN0aGViZXN0</secDNS:pubKey>
S: </k:keyData>
S: <k:authInfo>
S: <domain:pw>JnSdBAZSxxzJ</domain:pw>
S: </k:authInfo>
S: <k:expiry>
S: <k:relative>P1M13D</k:relative>
S: </k:expiry>
S: </k:keyRelayData>
S: </r:relayData>
S: <r:paDate>1999-04-04T22:01:00.0Z</r:paDate>
S: <r:reID>ClientX</r:reID>
S: <r:acID>ClientY</r:acID>
S: </r:panData>
S: </resData>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp>
4. Formal Syntax 3.2. EPP Transform Commands
4.1. Formal Syntax <relay> command and POLL response EPP provides five commands to transform objects: <create> to create
an instance of an object, <delete> to delete an instance of an
object, <renew> to extend the validity period of an object,
<transfer> to manage object sponsorship changes, and <update> to
change information associated with an object.
<?xml version="1.0" encoding="UTF-8"?> 3.2.1. EPP <create> Command
<schema targetNamespace="urn:ietf:params:xml:ns:relay-1.0"
xmlns:r="urn:ietf:params:xml:ns:relay-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation> The EPP <create> command provides a transform operation that allows a
<documentation> client to create a key relay object that includes the domain name and
Extensible Provisioning Protocol v1.0 protocol DNSSEC key material to be relayed. When the <create> command is
extension schema for relaying data. validated, the server MUST insert an EPP <poll> message, using the
</documentation> key relay info response (See Section 3.1.2), in the receiving
</annotation> client's poll queue that belongs to the registrar on record of the
provided domain name.
<import namespace="urn:ietf:params:xml:ns:epp-1.0" In addition to the standard EPP command elements, the <create>
schemaLocation="epp-1.0.xsd" /> command MUST contain a <keyrelay:create> element that identifies the
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" keyrelay namespace. The <keyrelay:create> element contains the
schemaLocation="eppcom-1.0.xsd" /> following child elements:
<element name="relay" type="r:relayDataType" /> o A REQUIRED <keyrelay:name> element containing the domain name for
<element name="panData" type="r:relayPanDataType" /> which the DNSSEC key material is relayed.
<complexType name="relayDataType"> o A REQUIRED <keyrelay:keyRelayData> elements containing data to be
<sequence> relayed, as defined in Section 2.1
<element name="relayData" type="epp:extAnyType" />
<element name="clTRID" type="epp:trIDStringType"
minOccurs="0" />
</sequence>
</complexType>
<complexType name="relayPanDataType"> Example <create> command:
<sequence>
<element name="relayData" type="epp:extAnyType" />
<element name="paDate" type="dateTime" />
<element name="reID" type="eppcom:clIDType" />
<element name="acID" type="eppcom:clIDType" />
</sequence>
</complexType>
</schema>
4.2. Formal Syntax <keyRelayData> data C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-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:d="urn:ietf:params:xml:ns:domain-1.0">
C: <command>
C: <create>
C: <keyrelay:create>
C: <keyrelay:name>example.org</keyrelay:name>
C: <keyrelay:keyRelayData>
C: <keyrelay:keyData>
C: <s:flags>256</s:flags>
C: <s:protocol>3</s:protocol>
C: <s:alg>8</s:alg>
C: <s:pubKey>cmlraXN0aGViZXN0</s:pubKey>
C: </keyrelay:keyData>
C: <keyrelay:authInfo>
C: <d:pw>JnSdBAZSxxzJ</d:pw>
C: </keyrelay:authInfo>
C: <keyrelay:expiry>
C: <keyrelay:relative>P1M13D</keyrelay:relative>
C: </keyrelay:expiry>
C: </keyrelay:keyRelayData>
C: </keyrelay:create>
C: </create>
C: <clTRID>123456</clTRID>
C: </command>
C:</epp>
<?xml version="1.0" encoding="UTF-8"?> When a server has succesfully processed the <create> command it MUST
<schema targetNamespace="urn:ietf:params:xml:ns:keyrelay-1.0" respond with a standard EPP response. See [RFC5730], Section 2.6.
xmlns:k="urn:ietf:params:xml:ns:keyrelay-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation> Example <create> response:
<documentation>
Extensible Provisioning Protocol v1.0 protocol
extension schema for relaying DNSSEC key data.
</documentation>
</annotation>
<import namespace="urn:ietf:params:xml:ns:epp-1.0" S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
schemaLocation="epp-1.0.xsd" /> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" S: <response>
schemaLocation="eppcom-1.0.xsd" /> S: <result code="1000">
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1" S: <msg>Command completed successfully</msg>
schemaLocation="secdns-1.1.xsd" /> S: </result>
<import namespace="urn:ietf:params:xml:ns:domain-1.0" S: <trID>
schemaLocation="domain-1.0.xsd" /> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-ZYX</svTRID>
S: </trID>
S: </response>
S:</epp>
<element name="keyRelayData" type="k:keyRelayDataType" /> 3.2.2. EPP <delete> Command
<complexType name="keyRelayDataType"> Delete semantics do not apply to key relay objects, so there is no
<sequence> mapping defined for the EPP <delete> command and the EPP <delete>
<element name="name" type="eppcom:labelType" /> response.
<element name="keyData" type="secDNS:keyDataType"
minOccurs="1" 3.2.3. EPP <renew> Command
maxOccurs="unbounded" />
<element name="authInfo" type="domain:authInfoType" /> Renew semantics do not apply to key relay objects, so there is no
<element name="expiry" type="k:keyRelayExpiryType" mapping defined for the EPP <renew> command and the EPP <renew>
minOccurs="0" /> response.
</sequence>
</complexType> 3.2.4. EPP <transfer> Command
<complexType name="keyRelayExpiryType">
<choice> Transfer semantics do not apply to key relay objects, so there is no
<element name="absolute" type="dateTime" /> mapping defined for the EPP <transfer> command and the EPP <transfer>
<element name="relative" type="duration" /> response.
</choice>
</complexType> 3.2.5. EPP <update> Command
</schema>
Update semantics do not apply to key relay objects, so there is no
mapping defined for the EPP <update> command and the EPP <update>
response.
4. Formal Syntax
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:keyrelay-1.0"
xmlns:keyrelay="urn:ietf:params:xml:ns:keyrelay-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0 protocol
extension schema for relaying DNSSEC key material.
</documentation>
</annotation>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"
schemaLocation="epp-1.0.xsd" />
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd" />
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1"
schemaLocation="secdns-1.1.xsd" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0"
schemaLocation="domain-1.0.xsd" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType" />
<element name="infData" type="keyrelay:infDataType" />
<element name="create" type="keyrelay:createType" />
<complexType name="createType">
<sequence>
<element name="name" type="eppcom:labelType" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType"
minOccurs="1" />
</sequence>
</complexType>
<complexType name="infDataType">
<sequence>
<element name="name" type="eppcom:labelType" minOccurs="1" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType"
minOccurs="1" />
<element name="crDate" type="dateTime"/>
<element name="reID" type="eppcom:clIDType" />
<element name="acID" type="eppcom:clIDType" />
</sequence>
</complexType>
<complexType name="keyRelayDataType">
<sequence>
<element name="keyData" type="secDNS:keyDataType" minOccurs="1"
maxOccurs="unbounded" />
<element name="authInfo" type="domain:authInfoType" />
<element name="expiry" type="keyrelay:keyRelayExpiryType" minOccurs="0" />
</sequence>
</complexType>
<complexType name="keyRelayExpiryType">
<choice>
<element name="absolute" type="dateTime" />
<element name="relative" type="duration" />
</choice>
</complexType>
</schema>
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in RFC3688 [RFC3688]. conforming to a registry mechanism described in [RFC3688]. The
following URI assignment is requested of IANA:
Four URI assignments must be completed by the IANA. URI: urn:ietf:params:xml:ns:keyrelay-1.0
Registration request for the extension namespaces: Registrant Contact: See the "Author's Address" section of this
document.
URI: urn:ietf:params:xml:ns:keyrelay-1.0 XML: See the "Formal Syntax" section of this document.
URI: urn:ietf:params:xml:ns:relay-1.0
Registrant Contact: IESG 5.2. EPP Extension Registry
XML: None. Namespace URIs do not represent an XML specification. The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows:
Registration request for the extension XML schemas: Name of Extension: "Keyrelay Extension for the Extensible
Provisioning Protocol"
URI: urn:ietf:params:xml:schema:keyrelay-1.0 Document status: Standards Track
URI: urn:ietf:params:xml:schema:relay-1.0
Registrant Contact: IESG Reference: (insert reference to RFC version of this document)
XML: See the "Formal Syntax" section of this document. Registrant Name and Email Address: IESG, iesg@ietf.org
TLDs: Any
IPR Disclosure: https://datatracker.ietf.org/ipr/2393/
Status: Active
Notes: None
6. Security Considerations 6. Security Considerations
A registry MUST NOT perform any transformation on registration data A server SHOULD NOT perform any transformation on data under server
under registry management when processing a <relay> command. management when processing a <keyrelay:create> command.
Any registrar can use this mechanism to put data on the message queue Any EPP client can use this mechanism to put data on the message
of another registrar, allowing for the potential of a denial of queue of another EPP client, allowing for the potential of a denial
service attack. However this can, and SHOULD be detected by the of service attack. However this can, and SHOULD be detected by the
registry. A registry MAY set a server policy which limits or rejects server. A server MAY set a server policy which limits or rejects a
<relay> messages if it detects the mechanism is being abused. <keyrelay:create> command if it detects the mechanism is being
abused.
For the <keyRelayData> data a correct <authInfo> element SHOULD be For the <keyrelay:keyRelayData> data a correct <domain:authInfo>
used as an indication that putting the key material on the element SHOULD be used as an indication that putting the key material
registrar's message queue is authorized by the _registrant_ of that on the receiving EPP clients poll queue is authorized by the
domain name. This draft does not specify how this <authInfo> is _registrant_ of that domain name. The authorization of EPP clients
provided to the registrar. This depends on how the DNS operator is to perform DNS changes is not covered in this I-D as it depends on
authorised to perform DNS changes on behalf of the registrant through registry specific policy.
the registrar on record. This authorisation is not covered in this
I-D.
7. References 7. References
7.1. Normative References 7.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.
[RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Resource Records for the DNS Security Extensions",
RFC 4034, March 2005.
[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
Provisioning Protocol", RFC 7451, February 2015.
7.2. Informative References 7.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.
[RFC3735] Hollenbeck, S., "Guidelines for Extending the Extensible
Provisioning Protocol (EPP)", RFC 3735, March 2004.
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]
A.1. draft-gieben-epp-keyrelay-00 A.1. draft-gieben-epp-keyrelay-00
1. Initial document. 1. Initial document.
A.2. draft-gieben-epp-keyrelay-01 A.2. draft-gieben-epp-keyrelay-01
skipping to change at page 14, line 39 skipping to change at page 14, line 46
A.5. draft-ietf-eppext-keyrelay-00 A.5. draft-ietf-eppext-keyrelay-00
1. Added feedback from Seth Goldman and put him in the 1. Added feedback from Seth Goldman and put him in the
acknowledgement section. acknowledgement section.
2. IDnits formatting ajustments 2. IDnits formatting ajustments
A.6. draft-ietf-eppext-keyrelay-01 A.6. draft-ietf-eppext-keyrelay-01
1. Introducing the <relay> command, and thus seperating the data and 1. Introducing the <relay> command, and thus separating the data and
the command. the command.
2. Updated the Introduction, describing the general use of relay vs 2. Updated the Introduction, describing the general use of relay vs
the intended use-case of relaying DNSSEC key data. the intended use-case of relaying DNSSEC key data.
3. Restructuring the document to make it more inline with exisiting 3. Restructuring the document to make it more inline with existing
EPP extensions. EPP extensions.
Authors' Addresses A.7. draft-ietf-eppext-keyrelay-02
Miek Gieben 1. Updated the XML structure based on WG feedback
Google
Email: miek@google.com 2. Updated the wording
Marc Groeneweg Authors' Addresses
SIDN Labs
Rik Ribbers
SIDN
Meander 501 Meander 501
Arnhem 6825 MD Arnhem 6825 MD
NL NL
Email: marc.groeneweg@sidn.nl Email: rik.ribbers@sidn.nl
URI: https://www.sidn.nl/ URI: https://www.sidn.nl/
Rik Ribbers Marc Groeneweg
SIDN Labs SIDN
Meander 501 Meander 501
Arnhem 6825 MD Arnhem 6825 MD
NL NL
Email: rik.ribbers@sidn.nl Email: marc.groeneweg@sidn.nl
URI: https://www.sidn.nl/ URI: https://www.sidn.nl/
Miek Gieben
Email: miek@miek.nl
Antoin Verschuren Antoin Verschuren
Email: ietf@antoin.nl Email: ietf@antoin.nl
 End of changes. 87 change blocks. 
376 lines changed or deleted 382 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/