Network Working Group
eppext                                                         R. Gieben
Internet-Draft                                                    Google
Intended status: Standards Track                            M. Groeneweg
Expires: July 23, 2014                                        R. 12, 2015                                        H. Ribbers
                                                       A.L.J. Verschuren
                                                               SIDN Labs
                                                           A. Verschuren

                                                         January 19, 2014

       Key 8, 2015

        Relay Mapping Extension for the Extensible Provisioning Protocol
                     draft-ietf-eppext-keyrelay-00
                     draft-ietf-eppext-keyrelay-01

Abstract

   This document describes an a generic Extensible Provisioning Protocol
   (EPP) extension mapping for the purpose of relaying data between registrars.

   Furthermore, this document describes a specific implementation for
   relaying DNSSEC key material
   from one between DNS operator operators (by means of their
   respective registrars), to another, by using the administrative
   registration channel through the registrant, registrar and registry.
   The mapping introduces "<keyrelay>" as a new command in EPP.

   This command will help facilitate changing the DNS operator change of a
   domain DNS operator,
   while keeping the DNSSEC chain of trust intact.

   This I-D introduces a new generic command <relay> and an element
   <relayData>.  For the specific implementation of relaying DNSSEC key
   material it introduces an extension of the <relayData> with a
   <keyRelayData> element.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 23, 2014. 12, 2015.

Copyright Notice

   Copyright (c) 2014 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Conventions Used in This Document . .  Introduction  . . . . . . . . . . . .   2
   2.  Introduction . . . . . . . . . . . .   3
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   3
   3.
     1.2.  Relaying Key Material Data . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Rational
       1.2.1.  Rationale For a New Command . . . . . . . . . . . . .   4
       1.2.2.  Extending <relayData> per use case  . . . . . . . . .   4
   5.
     1.3.  Secure Transfer of DNSSEC Key Relay Interface Material  . . . . . . . . .   4
   2.  Object Attributes . . . . . . . . . . . .   4
     5.1.  Example . . . . . . . . . .   5
     2.1.  DNSSEC Key Relay Interface Material . . . . . . . . . . . . . . .   6
   6.  Server Reply . . . .   5
   3.  EPP Command Mapping . . . . . . . . . . . . . . . . . . . . .   6
   7.  Message Queue Interface
     3.1.  EPP Transient Commands  . . . . . . . . . . . . . . . . .   6
       3.1.1.  EPP <relay> Command . .   7
     7.1.  Message Queue Format . . . . . . . . . . . . . . .   6
     3.2.  EPP Query Commands  . . . . . . . . . . . . . . . . . . .   7
   8.  Formal Syntax
       3.2.1.  EPP <poll> command  . . . . . . . . . . . . . . . . .   7
   4.  Formal Syntax . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . .  10
     4.1.  Formal Syntax <relay> command and POLL response . . . . .  10
   10. Security Considerations
     4.2.  Formal Syntax <keyRelayData> data . . . . . . . . . . . .  11
   5.  IANA Considerations . . . . . . . . .  11
   11. Acknowledgements . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . .  11
   12. . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     12.1.  13
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     12.2.  13
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12  13
   Appendix A.  Changelog  . . . . . . . . . . . . . . . . . . . . .  12  13
     A.1.  draft-gieben-epp-keyrelay-00  . . . . . . . . . . . . . .  12  13
     A.2.  draft-gieben-epp-keyrelay-01  . . . . . . . . . . . . . .  12  13
     A.3.  draft-gieben-epp-keyrelay-02  . . . . . . . . . . . . . .  12  14
     A.4.  draft-gieben-epp-keyrelay-03  . . . . . . . . . . . . . .  12  14
     A.5.  draft-eppext-epp-keyrelay-00  draft-ietf-eppext-keyrelay-00 . . . . . . . . . . . . . .  13  14
     A.6.  draft-ietf-eppext-keyrelay-01 . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13  15

1.  Conventions Used  Introduction

   There are certain transactions in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", the lifecycle of a domain name,
   that require interaction between registrars but need registration
   data from the registry.  Since all registrars involved have a secure
   channel to the registry for maintaining the delegation, the registry
   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
      registrars through the existing authenticated EPP channel.  This
      protocol extension introduces a new EPP command called <relay>
      with an element <relayData>.

   o  An extension to the <relayData> element called <keyRelayData> that
      can be used for the relaying DNSSEC key material using the <relay>
      command.

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

   XML is case sensitive.  Unless stated otherwise, XML specifications
   and examples provided in this document MUST be interpreted in the
   character case presented in order to develop a conforming
   implementation.

   In examples, "C:" represents lines sent by a protocol client, and
   "S:" represents lines returned by a protocol server.  "////" is used
   to note element values that have been shortened to better fit page
   boundaries.  Indentation and
   white space in examples is provided only to illustrate element
   relationships and is not a mandatory feature of this protocol.

   XML is case sensitive.  Unless stated otherwise, XML specifications
   and examples provided in this document MUST be interpreted in the
   character case presented in order to develop a conforming
   implementation.

1.2.  Relaying Data

   The term "key material" denotes one or more DNSKEY resource records
   [RFC4034].

2.  Introduction

   Certain transactions for DNSSEC signed zones require an <relay> command uses the existing authenticated
   exchange of DNSSEC key material between DNS operators.  Often there
   is no direct secure EPP channel
   between the two or it is non-scalable.

   One of such transactions is changing registrar and the DNS operator for DNSSEC
   signed zones ([I-D.koch-dnsop-dnssec-operator-change].  We suggest
   DNS operators registry.  Registrars can use the administrative channel that is used to
   bootstrap the delegation to relay the key material for the zone.  In this document we define a protocol extension
   secure channel for use in EPP that
   helps relaying data to implement and automate this transaction.  This protocol
   extension introduces a new command called "<keyrelay>".

3.  Relaying Key Material other registrars.  The "<keyrelay>" command uses the existing authenticated EPP channel
   with the registry.  Registrars can securely talk to the registry and
   as such the registry can serve
   serves as a drop box for relaying key
   material an intermediary between them two registrars (see Figure 1).

            +-------------------+  DNSKEY  +--------------------+
            |losing DNS operator| <~~~~~~~ |gaining DNS operator|
            +-------------------+          +--------------------+
                             ^

                  +-------------+  relayData  +-------------+
                  | registrar X |~~~~~~~~~~~~>| registrar Y |
                  +-------------+             +-------------+
                         |              v
              +-----------------+          +---------+
              |current registrar|          |registrar|
              +-----------------+          +---------+                           ^
                         | EPP relay        EPP poll |
                         v                           | EPP keyrelay
                             |              V
                            +----------------+
                        +-----------------------------+
                        |           registry          |
                            +----------------+
                        +-----------------------------+

   Figure 1: The gaining and losing DNS operators should 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 Registry acting as a relay for the key material
                                 exchange. secure data exchange between
                                registrars.

   The "<keyrelay>" <relay> command uploads new key(s) data from a registrar X to the registry for a
   given domain.  This key material registry.
   The uploaded data is then relayed to pushed onto the current
   registrar's message queue.  This may be the same queue of registrar as
   Y by the one
   that submitted registry based on the "<keyrelay>" command in information within the situation where <relayData>
   element of the
   DNS operators change, but <relay> command and the registrar stays registration data maintained
   by the same.  There 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
   need relationship to registration data.  We have e-mail for that.

   If for some reason the registry to store the relayed key in cannot process the registry
   system, although <relay> command,
   an EPP error response MUST be returned.  If the registry MAY save does process
   the "<keyrelay>" message for
   administrative purposes.

   The registrar may upload multiple keys in one "<keyrelay>" message.

   There is no restriction on the type (for instance Key Signing Keys or
   Zone Signing Keys) of keys that can be put in the message.  It is up
   to the gaining DNS operator to select the keys that are needed in the
   losing operator's zone for the intended transaction to complete
   successfully.  It is up to the losing DNS operator to validate the
   correctness of the key material, and remove duplicate keys (Flags
   Field, Protocol Field, Algorithm Field and Public Key Field are
   equal) when identical keys are already in the zone.

   If for some reason the registry can not process the "<keyrelay>"
   command an EPP error response MUST be returned.  If the registry does
   process the "<keyrelay>" <relay> command it MUST put all uploaded keys elements of <relayData> on to the current registrar's
   message queue.

4.  Rational queue of registrar Y.

1.2.1.  Rationale For a New Command

   The existing commands in EPP all deal with data which either has an
   owner, or soon will have one (EPP create).  The "<keyrelay>"

   This new <relay> command
   is different, because can be best described as a "transient
   command" as it allows an upload only facilitates communication of key material which will
   never have an owner (in data between two
   registrars without changing the registry system).  All registration data at the "<keyrelay>" registry.
   No existing EPP command does is relay data in preparation can be (re)used for one this function.  This
   extension of the other
   existing EPP commands is in a process.  This way, existing commands
   don't need accordance to change, and backward compatibility for existing
   commands is guaranteed.  It allows [RFC3735].

1.2.2.  Extending <relayData> per use case

   One MUST extend the client <relayData> element per use case to be flexible in
   timing define the individual steps necessary
   data to complete a complex process
   like changing be relayed.  In the DNS operator extension, one MUST make provisions for a zone.  Creating a separate
   command also allows
   the command registry how to be used or extended 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
   transfer is one of the phases in the lifecycle of a domain name
   [I-D.koch-dnsop-dnssec-operator-change].

   DNS-operators need to relay exchange (through the gaining registrar) DNSSEC
   key
   or other material before the registration data for other future processes besides can be changed.

           +--------------------+  DNSKEY   +---------------------+
           |gaining DNS operator| ~~~~~~~~> | losing DNS operator
   changes.  This new category |
           +--------------------+           +---------------------+
                          |                   ^
                          |                   |
                          V                   |
           +--------------------+         +---------------------+
           |  gaining registrar |         | registrar of record |
           +--------------------+         +---------------------+
                          |                   ^
                EPP commands relay |                   | EPP poll
                          V                   |
                     +-----------------------------+
                     |           registry          |
                     +-----------------------------+

                Figure 2: Transfer of DNSSEC key material.

   As the <relay> command uses a secure channel, it can best be described as
   "communication command" used as it only facilitates communication of data 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 two EPP clients without changing any objects at the registry.

5.  Key Relay Interface
   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
   use case.

2.  Object Attributes

2.1.  DNSSEC Key Relay Interface uses Material

   To transfer DNSSEC key material with the <relay> command the generic
   <relayData> is extended with a "<keyrelay>" <keyRelayData> element that contains
   the data for relaying the key material.  It needs  See Section 1.2.2.

   This <keyRelayData> element REQUIRES a minimum of three elements: a domain name,
   the key(s) to upload, a token which indicates the request is
   authorized by the registrant, and an OPTIONAL expire element.

   Thus a "<keyrelay>" element MUST contain the following child
   elements:

   o  A "<name>" <name> element that which contains the domain name for which we
      upload the key.  The registry MUST relay the <keyRelayData> to the
      registrar of record of the provided domain name.

   o  A "<keyData>" element  One or more <keyData> elements that contains the DNSSEC key
      material as described in [RFC5910], Section 4.2.

   o  An "<authInfo>" <authInfo> element that contains an authorization token
      ([RFC5731], Section 3.2.4). 3.2.1).  This indicates that the registrar has
      authorization from the registrant to change the zone data, and a
      possible future transfer is authorized.  The registry MAY check if
      the "<authInfo>" <authInfo> data is correct and if it does, it MUST return an
      EPP error response if the authorization token is not correct.

   And MAY contain: an OPTIONAL <expiry> child element.

   o  An "<expiry>" <expiry> element that describes the expected lifetime 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 material
      from the zone.  This may be because the transaction that needed
      the insertion is either completed or has been abandoned if not
      completed before this expire time.  The <expiry> element MUST
      contain one of the following child elements:

      *  "<absolute/>":  <absolute/>: The policy is valid from the current date and time
         until it expires on the specified date and time.

      *  "<relative/>":  <relative/>: The policy is valid from the current date and time
         until the end of the specified duration.

3.  EPP Command Mapping

3.1.  EPP Transient Commands

3.1.1.  EPP <relay> Command

   The current date EPP <relay> command is a generic EPP command used for relaying
   data between registrars.  It contains the data to be relayed and time are taken from the "<keyrelay>" service
      message's "<qDate>" element, see Section 7.1.
   client transaction identifier.  It has been designed to be extensible
   for usage in other use-cases.

   The <relay> command REQUIRES the following child elements:

   o  One or more <relayData> elements containing data to be relayed.

   o  An "<clTRID>" OPTIONAL <clTRID> (client transaction identifier) as described in element that
      MAY be used to uniquely identify the command to the registrar.
      See [RFC5730], Section 2.5.

5.1.

   Example Key Relay Interface

   The following is an example of the "<keyrelay>" command, where a key
   is uploaded with a relative expire date of one month and 13 days. <relay> command:

 C:<?xml version="1.0" encoding=:UTF-8" standalone="no"?>
 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 C:    xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
 C:    xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
 C:  xmlns:ext="urn:ietf:params:xml:ns:keyrelay-1.0">    xmlns:r="urn:ietf:params:xml:ns:relay-1.0">
 C:    <extension>
 C:    <ext:command>        <r:relay xmlns:r="urn:ietf:params:xml:ns:relay-1.0">
 C:            <r:relayData>
 C:      <ext:keyrelay>                    <k:keyRelayData
 C:        <ext:name>example.org</ext:name>                       xmlns:k="urn:ietf:params:xml:ns:keyrelay-1.0">
 C:        <ext:keyData>                       <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>cmlraXN0aGViZXN0</secDNS:pubKey>                            <secDNS:pubKey>
 C:                                cmlraXN0aGViZXN0</secDNS:pubKey>
 C:        </ext:keyData>                        </k:keyData>
 C:        <ext:authInfo>                        <k:authInfo>
 C:                            <domain:pw>JnSdBAZSxxzJ</domain:pw>
 C:        </ext:authInfo>                        </k:authInfo>
 C:        <ext:expiry>                        <k:expiry>
 C:           <ext:relative>P1M13D</ext:relative>                            <k:relative>P1M13D</k:relative>
 C:        </ext:expiry>                        </k:expiry>
 C:      </ext:keyrelay>                    </k:keyRelayData>
 C:      <ext:clTRID>ABC-12345</ext:clTRID>             </r:relayData>
 C:    </ext:command>            <r:clTRID>ABC-12345</r:clTRID>
 C:        </r:relay>
 C:    </extension>
 C:</epp>

6.  Server Reply

   Example "<keyrelay>" response:

   S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
   S:  <response>
   S:    <result code="1000">
   S:       <msg>Command completed successfully</msg>
   S:    </result>
   S:    <trID>
   S:       <clTRID>ABC-12345</clTRID>
   S:       <svTRID>54321-ZYX</svTRID>
   S:    </trID>
   S:  </response>
   S:</epp>

   As stated an

3.2.  EPP error response MUST be returned if a "<keyrelay>"
   command can Query Commands

   This EPP extension does not be processed for any reason.

7.  Message Queue Interface

   The message queue interface uses the interface as defined in
   [RFC5730], Section 2.6.  All elements that are present in change any command other than the
   "<keyrelay>" EPP message are put on
   <poll> command response.

3.2.1.  EPP <poll> command

   This extension adds elements to the message queue response to a <poll> command with
   the "op" attribute set to "req".  Specifically, a <panData> element
   is added to the <resData> section of the current
   registrar for service message, containing
   the domain in following elements:

   o  A REQUIRED <relayData> element that contains the "<name>" element. relayed data.

   o  A "<keyrelay>" message MUST be delivered to REQUIRED <paDate> element that contains the current registrar's
   message queue, even if date and time of the current registrar has indicated that it
   does not support "<keyrelay">.

7.1.  Message Queue Format

   This is an example "<keyrelay>" service message.  Note
      submitted <relay> command.

   o  A REQUIRED <reID> element that contains the
   optional clTRID in this message is identifier of the clTRID value from
      registrar that requested the command data relay.

   o  A REQUIRED <acID> element that polls contains the message queue.  It is not identifier of the clTRID value used in
      registrar that SHOULD act upon the
   EPP "<keyrelay>" command. data relay.

   Example <poll> response:

 S:<?xml version="1.0" encoding=:UTF-8" standalone="no"?>
 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 S:    xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
 S:  xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
   S:  xmlns:keyrelay="urn:ietf:params:xml:ns:keyrelay-1.0">    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>Key Relay            <msg>Relay action completed successfully.</msg>
 S:        </msgQ>
 S:        <resData>
 S:        <keyrelay:response>            <r:panData xmlns:r="urn:ietf:params:xml:ns:relay-1.0">
 S:           <keyrelay:panData>                <r:relayData>
 S:              <keyrelay:name paResult="true">example.org                    <k:keyRelayData
 S:              </keyrelay:name>                       xmlns:k="urn:ietf:params:xml:ns:keyrelay-1.0">
 S:              <keyrelay:paDate>1999-04-04T22:01:00.0Z                       <k:name>example.org</k:name>
 S:              </keyrelay:paDate>
   S:              <keyrelay:keyData>                       <k:keyData>
 S:                            <secDNS:flags>256</secDNS:flags>
 S:                            <secDNS:protocol>3</secDNS:protocol>
 S:                            <secDNS:alg>8</secDNS:alg>
 S:                 <secDNS:pubKey>cmlraXN0aGViZXN0</secDNS:pubKey>                            <secDNS:pubKey>
 S:                                cmlraXN0aGViZXN0</secDNS:pubKey>
 S:              </keyrelay:keyData>                        </k:keyData>
 S:              <keyrelay:authInfo>                        <k:authInfo>
 S:                            <domain:pw>JnSdBAZSxxzJ</domain:pw>
 S:              </keyrelay:authInfo>                        </k:authInfo>
 S:              <keyrelay:expiry>                        <k:expiry>
 S:                 <keyrelay:relative>P24D</keyrelay:relative>                            <k:relative>P1M13D</k:relative>
 S:              </keyrelay:expiry>                        </k:expiry>
 S:              <keyrelay:reID>ClientX</keyrelay:reID>                    </k:keyRelayData>
 S:              <keyrelay:acID>ClientY</keyrelay:acID>                </r:relayData>
 S:           </keyrelay:panData>                <r:paDate>1999-04-04T22:01:00.0Z</r:paDate>
 S:        </keyrelay:response>                <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>

8.

4.  Formal Syntax

   An EPP object mapping is specified in XML Schema notation.  The
   formal syntax presented here is a complete schema representation of
   the object mapping suitable for automated validation of EPP XML
   instances.

   "<keyrelay>"

4.1.  Formal Syntax <relay> command schema: and POLL response

   <?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:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" 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: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 domain name protocol
               extension schema for relaying key material. data.
           </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="command" type="keyrelay:commandType" name="relay" type="r:relayDataType" />
       <element name="response" type="keyrelay:responseType" />

      <complexType name="responseType">
         <sequence>
            <element name="panData"
                     type="keyrelay:panKeyRelayDataType"/>
         </sequence>
      </complexType> type="r:relayPanDataType" />

       <complexType name="commandType"> name="relayDataType">
           <sequence>
               <element name="keyrelay"
                     type="keyrelay:keyRelayType" name="relayData" type="epp:extAnyType" />
               <element name="clTRID" type="epp:trIDStringType"
                     minOccurs="0"/>
                   minOccurs="0" />
           </sequence>
       </complexType>

       <complexType name="keyRelayExpiryType">
         <choice> name="relayPanDataType">
           <sequence>
               <element name="absolute" name="relayData" type="epp:extAnyType" />
               <element name="paDate" type="dateTime" />
               <element name="relative" type="duration" name="reID" type="eppcom:clIDType" />
         </choice>
               <element name="acID" type="eppcom:clIDType" />
           </sequence>
       </complexType>
   </schema>

4.2.  Formal Syntax <keyRelayData> data

   <?xml version="1.0" encoding="UTF-8"?>
       <schema targetNamespace="urn:ietf:params:xml:ns:keyrelay-1.0"
       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>
           <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"
           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="k:keyRelayDataType" />

       <complexType name="keyRelayType"> name="keyRelayDataType">
           <sequence>
               <element name="name" type="eppcom:labelType" />
               <element name="keyData" type="secDNS:keyDataType"
                   minOccurs="1"
                   maxOccurs="unbounded" />
               <element name="authInfo" type="domain:authInfoType" />
               <element name="expiry"
               type="keyrelay:keyRelayExpiryType" type="k:keyRelayExpiryType"
                   minOccurs="0" />
           </sequence>
       </complexType>
       <complexType name="panKeyRelayDataType">
         <sequence>
            <element name="name" type="domain:paNameType" />
            <element name="paDate" type="dateTime" />
            <element name="keyData" type="secDNS:keyDataType"
                     minOccurs="1" maxOccurs="unbounded" />
            <element name="authInfo" type="domain:authInfoType" /> name="keyRelayExpiryType">
           <choice>
               <element name="expiry"
               type="keyrelay:keyRelayExpiryType" minOccurs="0" name="absolute" type="dateTime" />
               <element name="reID" type="eppcom:clIDType"/>
            <element name="acID" type="eppcom:clIDType"/>
         </sequence> name="relative" type="duration" />
           </choice>
       </complexType>
   </schema>

9.

5.  IANA Considerations

   This document uses URNs to describe XML namespaces and XML schemas
   conforming to a registry mechanism described in RFC 3688 RFC3688 [RFC3688].

   Two

   Four URI assignments must be completed by the IANA.

   Registration request for the extension namespace: namespaces:

   URI: urn:ietf:params:xml:ns:keyrelay-1.0
   URI: urn:ietf:params:xml:ns:relay-1.0

   Registrant Contact: IESG

   XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the extension XML schema: schemas:

   URI: urn:ietf:params:xml:schema:keyrelay-1.0
   URI: urn:ietf:params:xml:schema:relay-1.0

   Registrant Contact: IESG

   XML: See the "Formal Syntax" section of this document.

10.

6.  Security Considerations

   The "<keyrelay>" EPP extension does not allow for

   A registry MUST NOT perform any object
   transformations. transformation on registration data
   under registry management when processing a <relay> command.

   Any registrar can use this mechanism to put key material data on the message queue
   of another registrar, thus mounting allowing for the potential of a denial of
   service attack.  However this can, and should SHOULD be detected by the
   registry.  A
   correct "<ext:authInfo>" element can be used as an indication that
   putting the key material on the losing registrar's message queue is
   authorized by the registrant of that registrar.  A registry MAY set a server policy which limits or rejects "<keyrelay>"
   <relay> messages if it detects the mechanism is being abused.

   Communication between

   For the <keyRelayData> data a registrar and registry is mostly done over
   EPP, but communication between DNS operators, registrants or
   registrars often is not.  If EPP is not correct <authInfo> element SHOULD be
   used between these entities,
   relaying as an indication that putting the key between a DNS operator and registrar should be
   adequately authenticated for material on the complete relay channel to remain
   secure.  It's out
   registrar's message queue is authorized by the _registrant_ of scope for that
   domain name.  This draft does not specify how this document <authInfo> is
   provided to describe the registrar.  This depends on how the DNS operator is
   authorised to
   authenticate with other methods than EPP.

11.  Acknowledgements

   We like to thank perform DNS changes on behalf of the following individuals for their valuable input,
   review, constructive criticism in earlier revisions or support for registrant through
   the concepts described registrar on record.  This authorisation is not covered in this document:

   Maarten Wullink, Marco Davids, Ed Lewis, James Mitchell, David Peal,
   Patrik Faltstrom, Klaus Malorny, James Gould, Patrick Mevzek and Seth
   Goldman.

12.
   I-D.

7.  References

12.1.

7.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              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)",
              STD 69, RFC 5730, August 2009.

   [RFC5731]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Domain Name Mapping", STD 69, RFC 5731, August 2009.

   [RFC5910]  Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
              Security Extensions Mapping for the Extensible
              Provisioning Protocol (EPP)", RFC 5910, May 2010.

12.2.

7.2.  Informative References

   [I-D.koch-dnsop-dnssec-operator-change]
              Koch, P., Sanz, M., and A. Verschuren, "Changing DNS
              Operators for DNSSEC signed Zones", draft-koch-dnsop-
              dnssec-operator-change-05
              dnssec-operator-change-06 (work in progress), July 2013.

   [RFC5731] February
              2014.

   [RFC3735]  Hollenbeck, S., "Extensible "Guidelines for Extending the Extensible
              Provisioning Protocol (EPP)
              Domain Name Mapping", STD 69, (EPP)", RFC 5731, August 2009. 3735, March 2004.

Appendix A.  Changelog

   [This section should be removed by the RFC editor before publishing]

A.1.  draft-gieben-epp-keyrelay-00

   1.  Initial document.

A.2.  draft-gieben-epp-keyrelay-01

   1.  Style and grammar changes;

   2.  Added an expire element as per suggestion by Klaus Malorny;
   3.  Make the authInfo element mandatory and make the registry check
       it as per feedback by Klaus Malorny and James Gould.

A.3.  draft-gieben-epp-keyrelay-02

   1.  Added element to identify the relaying EPP client as suggested by
       Klaus Malorny;

   2.  Corrected XML for missing and excess clTRID as noted by Patrick
       Mevzek;

   3.  Added clarifications for the examples based on feedback by
       Patrick Mevzeck;

   4.  Reviewed the consistency of using DNS operator versus registrar
       after review comments by Patrick Faltstrom and Ed Lewis.

A.4.  draft-gieben-epp-keyrelay-03

   1.  Style and grammar changes

   2.  Corrected acknowledgement section

   3.  Corrected XML for Expire element to not be mandatory but only
       occur once.

A.5.  draft-eppext-epp-keyrelay-00  draft-ietf-eppext-keyrelay-00

   1.  Added feedback from Seth Goldman and put him in the
       acknowledgement section.

   2.  IDnits formatting ajustments

A.6.  draft-ietf-eppext-keyrelay-01

   1.  Introducing the <relay> command, and thus seperating the data and
       the command.

   2.  Updated the Introduction, describing the general use of relay vs
       the intended use-case of relaying DNSSEC key data.

   3.  Restructuring the document to make it more inline with exisiting
       EPP extensions.

Authors' Addresses

   R. (Miek)

   Miek Gieben
   Google

   Email: miek@google.com

   M.

   Marc Groeneweg
   SIDN Labs
   Meander 501
   Arnhem  6825 MD
   NL

   Email: marc.groeneweg@sidn.nl
   URI:   https://www.sidn.nl/

   Rik Ribbers
   SIDN Labs
   Meander 501
   Arnhem  6825 MD
   NL

   Email: rik.ribbers@sidn.nl
   URI:   https://www.sidn.nl/

   Antoin Verschuren
   SIDN Labs
   Meander 501
   Arnhem  6825 MD
   NL

   Email: antoin.verschuren@sidn.nl
   URI:   https://www.sidn.nl/ ietf@antoin.nl