draft-ietf-eppext-keyrelay-07.txt   draft-ietf-eppext-keyrelay-08.txt 
eppext HW. Ribbers eppext HW. Ribbers
Internet-Draft MW. Groeneweg Internet-Draft MW. Groeneweg
Intended status: Standards Track SIDN Intended status: Standards Track SIDN
Expires: February 25, 2016 R. Gieben Expires: March 5, 2016 R. Gieben
ALJ. Verschuren ALJ. Verschuren
August 24, 2015 September 02, 2015
Key Relay Mapping for the Extensible Provisioning Protocol Key Relay Mapping for the Extensible Provisioning Protocol
draft-ietf-eppext-keyrelay-07 draft-ietf-eppext-keyrelay-08
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 February 25, 2016. This Internet-Draft will expire on March 5, 2016.
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
skipping to change at page 3, line 4 skipping to change at page 3, line 4
A.3. draft-gieben-epp-keyrelay-02 . . . . . . . . . . . . . . 15 A.3. draft-gieben-epp-keyrelay-02 . . . . . . . . . . . . . . 15
A.4. draft-gieben-epp-keyrelay-03 . . . . . . . . . . . . . . 15 A.4. draft-gieben-epp-keyrelay-03 . . . . . . . . . . . . . . 15
A.5. draft-ietf-eppext-keyrelay-00 . . . . . . . . . . . . . . 15 A.5. draft-ietf-eppext-keyrelay-00 . . . . . . . . . . . . . . 15
A.6. draft-ietf-eppext-keyrelay-01 . . . . . . . . . . . . . . 16 A.6. draft-ietf-eppext-keyrelay-01 . . . . . . . . . . . . . . 16
A.7. draft-ietf-eppext-keyrelay-02 . . . . . . . . . . . . . . 16 A.7. draft-ietf-eppext-keyrelay-02 . . . . . . . . . . . . . . 16
A.8. draft-ietf-eppext-keyrelay-03 . . . . . . . . . . . . . . 16 A.8. draft-ietf-eppext-keyrelay-03 . . . . . . . . . . . . . . 16
A.9. draft-ietf-eppext-keyrelay-04 . . . . . . . . . . . . . . 16 A.9. draft-ietf-eppext-keyrelay-04 . . . . . . . . . . . . . . 16
A.10. draft-ietf-eppext-keyrelay-05 . . . . . . . . . . . . . . 16 A.10. draft-ietf-eppext-keyrelay-05 . . . . . . . . . . . . . . 16
A.11. draft-ietf-eppext-keyrelay-06 . . . . . . . . . . . . . . 17 A.11. draft-ietf-eppext-keyrelay-06 . . . . . . . . . . . . . . 17
A.12. draft-ietf-eppext-keyrelay-07 . . . . . . . . . . . . . . 17 A.12. draft-ietf-eppext-keyrelay-07 . . . . . . . . . . . . . . 17
A.13. draft-ietf-eppext-keyrelay-08 . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
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 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 is identified command MUST contain a <keyrelay:create> element that is identified
by the keyrelay namespace. The <keyrelay:create> element contains by the keyrelay namespace. The <keyrelay:create> element contains
the following child elements: the 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 <authInfo> element that contains authorization
information associated with the domain object ([RFC5731],
Section 3.2.1).
o One or more REQUIRED <keyrelay:keyRelayData> element containing o One or more REQUIRED <keyrelay:keyRelayData> element containing
data to be relayed, as defined in Section 2.1 data to be relayed, as defined in Section 2.1
Example <create> commands: Example <create> commands:
Note that in the provided example the second <keyrelay:keyRelayData> Note that in the provided example the second <keyrelay:keyRelayData>
element had a negative period and thus represents the revocation of a element has a period of zero and thus represents the revocation of a
previouly send key relay object (see Section 2.1.1). previouly send key relay object (see Section 2.1.1).
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>
C: <create> C: <create>
C: <keyrelay:create> C: <keyrelay:create>
skipping to change at page 9, line 36 skipping to change at page 9, line 36
C: </keyrelay:expiry> C: </keyrelay:expiry>
C: </keyrelay:keyRelayData> C: </keyrelay:keyRelayData>
C: <keyrelay:keyRelayData> C: <keyrelay:keyRelayData>
C: <keyrelay:keyData> C: <keyrelay:keyData>
C: <s:flags>256</s:flags> C: <s:flags>256</s:flags>
C: <s:protocol>3</s:protocol> C: <s:protocol>3</s:protocol>
C: <s:alg>8</s:alg> C: <s:alg>8</s:alg>
C: <s:pubKey>bWFyY2lzdGhlYmVzdA==</s:pubKey> C: <s:pubKey>bWFyY2lzdGhlYmVzdA==</s:pubKey>
C: </keyrelay:keyData> C: </keyrelay:keyData>
C: <keyrelay:expiry> C: <keyrelay:expiry>
C: <keyrelay:relative>-P1D</keyrelay:relative> C: <keyrelay:relative>P0D</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>ABC-12345</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.
skipping to change at page 11, line 19 skipping to change at page 11, line 19
response. response.
3.2.5. EPP <update> Command 3.2.5. EPP <update> Command
Update semantics do not apply to key relay objects, so there is no Update semantics do not apply to key relay objects, so there is no
mapping defined for the EPP <update> command and the EPP <update> mapping defined for the EPP <update> command and the EPP <update>
response. response.
4. Formal Syntax 4. Formal Syntax
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:keyrelay-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:keyrelay-1.0"
xmlns:keyrelay="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:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> 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" <annotation>
schemaLocation="epp-1.0.xsd" /> <documentation>
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" Extensible Provisioning Protocol v1.0 protocol
schemaLocation="eppcom-1.0.xsd" /> extension schema for relaying DNSSEC key material.
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1" </documentation>
schemaLocation="secdns-1.1.xsd" /> </annotation>
<import namespace="urn:ietf:params:xml:ns:domain-1.0"
schemaLocation="domain-1.0.xsd" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType" /> <import namespace="urn:ietf:params:xml:ns:epp-1.0"
<element name="infData" type="keyrelay:infDataType" /> schemaLocation="epp-1.0.xsd" />
<element name="create" type="keyrelay:createType" /> <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" />
<complexType name="createType"> <element name="keyRelayData" type="keyrelay:keyRelayDataType" />
<sequence> <element name="infData" type="keyrelay:infDataType" />
<element name="name" type="eppcom:labelType" /> <element name="create" type="keyrelay:createType" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType" />
</sequence> <complexType name="createType">
</complexType> <sequence>
<element name="name" type="eppcom:labelType" />
<element name="authInfo" type="domain:authInfoType" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="infDataType"> <complexType name="infDataType">
<sequence> <sequence>
<element name="name" type="eppcom:labelType" /> <element name="name" type="eppcom:labelType" />
<element name="authInfo" type="domain:authInfoType" /> <element name="authInfo" type="domain:authInfoType" />
<element name="keyRelayData" type="keyrelay:keyRelayDataType" <element name="keyRelayData" type="keyrelay:keyRelayDataType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<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" /> <element name="keyData" type="secDNS:keyDataType" />
<element name="expiry" type="keyrelay:keyRelayExpiryType" <element name="expiry" type="keyrelay:keyRelayExpiryType"
minOccurs="0" /> minOccurs="0" />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="keyRelayExpiryType">
<choice> <complexType name="keyRelayExpiryType">
<element name="absolute" type="dateTime" /> <choice>
<element name="relative" type="duration" /> <element name="absolute" type="dateTime" />
</choice> <element name="relative" type="duration" />
</complexType> </choice>
</schema> </complexType>
</schema>
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace 5.1. XML Namespace
This document uses URNs to describe a XML namespace conforming to a This document uses URNs to describe a XML namespace conforming to a
registry mechanism described in [RFC3688]. The following URI registry mechanism described in [RFC3688]. The following URI
assignment is requested of IANA: assignment is requested of IANA:
URI: urn:ietf:params:xml:ns:keyrelay-1.0 URI: urn:ietf:params:xml:ns:keyrelay-1.0
skipping to change at page 17, line 13 skipping to change at page 17, line 13
1. Review comments after WG last call 1. Review comments after WG last call
A.11. draft-ietf-eppext-keyrelay-06 A.11. draft-ietf-eppext-keyrelay-06
1. Review comments by Ulrich Wisser during IESG writeup 1. Review comments by Ulrich Wisser during IESG writeup
A.12. draft-ietf-eppext-keyrelay-07 A.12. draft-ietf-eppext-keyrelay-07
1. fixed changelog 1. fixed changelog
A.13. draft-ietf-eppext-keyrelay-08
1. fixed issue with authinfo
2. fixed issue with relative period in example xml
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. 16 change blocks. 
64 lines changed or deleted 76 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/