draft-ietf-eppext-keyrelay-04.txt   draft-ietf-eppext-keyrelay-05.txt 
eppext H. Ribbers eppext HW. Ribbers
Internet-Draft M. Groeneweg Internet-Draft MW. Groeneweg
Intended status: Standards Track SIDN Intended status: Standards Track SIDN
Expires: December 31, 2015 R. Gieben Expires: February 1, 2016 R. Gieben
A. Verschuren ALJ. Verschuren
June 29, 2015 July 31, 2015
Key Relay Mapping for the Extensible Provisioning Protocol Key Relay Mapping for the Extensible Provisioning Protocol
draft-ietf-eppext-keyrelay-04 draft-ietf-eppext-keyrelay-05
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.
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 December 31, 2015. This Internet-Draft will expire on February 1, 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 2, line 32 skipping to change at page 2, line 32
3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 8 3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 8
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 12 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 12
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 12 5.2. XML Schema . . . . . . . . . . . . . . . . . . . . . . . 12
5.3. EPP Extension Registry . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 14
A.1. draft-gieben-epp-keyrelay-00 . . . . . . . . . . . . . . 14 A.1. draft-gieben-epp-keyrelay-00 . . . . . . . . . . . . . . 15
A.2. draft-gieben-epp-keyrelay-01 . . . . . . . . . . . . . . 14 A.2. draft-gieben-epp-keyrelay-01 . . . . . . . . . . . . . . 15
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 . . . . . . . . . . . . . . 15 A.6. draft-ietf-eppext-keyrelay-01 . . . . . . . . . . . . . . 15
A.7. draft-ietf-eppext-keyrelay-02 . . . . . . . . . . . . . . 15 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
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
There are certain transactions initiated by a DNS-operator, which There are certain transactions initiated by a DNS-operator, which
require an authenticated exchange of information between DNS- require an authenticated exchange of information between DNS-
operators. Often, there is no direct channel between these parties operators. Often, there is no direct channel between these parties
or it is non-scalable and insecure. or it is non-scalable and insecure.
One such transaction is the exchange of DNSSEC key material when One such transaction is the exchange of DNSSEC key material when
skipping to change at page 4, line 11 skipping to change at page 4, line 11
other (the ~ arrow in Figure 1) to exchange the DNSKEY, but often other (the ~ arrow in Figure 1) to exchange the DNSKEY, but often
there is no trusted path between the two. As both can securely there is no trusted path between the two. As both can securely
interact with the registry over the administrative channel through interact with the registry over the administrative channel through
the registrar, the registry can act as a relay for the key material the registrar, the registry can act as a relay for the key material
exchange. exchange.
The registry is merely used as a relay channel. Therefore it is up The registry is merely used as a relay channel. Therefore it is up
to the losing DNS-operator to complete the intended transaction. The to the losing DNS-operator to complete the intended transaction. The
registry SHOULD have certain policies in place that require the registry SHOULD have certain policies in place that require the
losing DNS operator to cooperate with this transaction, however this losing DNS operator to cooperate with this transaction, however this
is beyond this I-D. This I-D focusses on the EPP protocol syntax. is beyond this I-D. This I-D focuses on the EPP protocol syntax.
+--------------------+ 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 |
+--------------------+ +---------------------+ +--------------------+ +---------------------+
skipping to change at page 5, line 22 skipping to change at page 5, line 22
The <expiry> element MUST contain one of the following child The <expiry> element MUST contain one of the following child
elements: elements:
* <absolute>: The DNSSEC key material is valid from the current date and * <absolute>: The DNSSEC key material is valid from the current date and
time until it expires on the specified date and time. If a date time until it expires on the specified date and time. If a date
in the past is provided this MUST be interpreted as a revocation of a in the past is provided this MUST be interpreted as a revocation of a
previously send key relay object. previously send key relay object.
* <relative>: The DNSSEC key material is valid from the current date and * <relative>: The DNSSEC key material is valid from the current date and
time until the end of the specified duration. If a negative period is time until the end of the specified duration. If a period of zero is
provided this MUST be interpreted as a revocation of a previously send key provided this MUST be interpreted as a revocation of a previously send key
relay object. relay object.
3. EPP Command Mapping 3. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. The command in the EPP core protocol specification [RFC5730]. The command
mapping described here is specifically for use in this key relay mapping described here is specifically for use in this key relay
mapping. mapping.
skipping to change at page 12, line 37 skipping to change at page 12, line 37
<element name="absolute" type="dateTime" /> <element name="absolute" type="dateTime" />
<element name="relative" type="duration" /> <element name="relative" type="duration" />
</choice> </choice>
</complexType> </complexType>
</schema> </schema>
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace 5.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe a XML namespace conforming to a
conforming to a registry mechanism described in [RFC3688]. The registry mechanism described in [RFC3688]. The following URI
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
Registrant Contact: See the "Author's Address" section of this Registrant Contact: See the "Author's Address" section of this
document. document.
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry 5.2. XML Schema
This document uses URNs to describe a XML schema conforming to a
registry mechanism described in [RFC3688]. The following URI
assignment is requested of IANA:
URI: urn:ietf:params:xml:ns:keyrelay-1.0
XML: See the "Formal Syntax" section of this document.
5.3. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: details of the registration are as follows:
Name of Extension: "Key Relay Mapping for the Extensible Provisioning Name of Extension: "Key Relay Mapping for the Extensible Provisioning
Protocol" Protocol"
Document status: Standards Track Document status: Standards Track
skipping to change at page 13, line 49 skipping to change at page 14, line 13
registry specific policy. registry specific policy.
7. Acknowledgements 7. Acknowledgements
We like to thank the following individuals for their valuable input, We like to thank the following individuals for their valuable input,
review, constructive criticism in earlier revisions or support for review, constructive criticism in earlier revisions or support for
the concepts described in this document: the concepts described in this document:
Maarten Wullink, Marco Davids, Ed Lewis, James Mitchell, David Peal, Maarten Wullink, Marco Davids, Ed Lewis, James Mitchell, David Peal,
Patrik Faltstrom, Klaus Malorny, James Gould, Patrick Mevzek, Seth Patrik Faltstrom, Klaus Malorny, James Gould, Patrick Mevzek, Seth
Goldman, Maarten Bosteels, Ulrich Wisser and Kees Monshouwer. Goldman, Maarten Bosteels, Ulrich Wisser, Kees Monshouwer and Scott
Hollenbeck.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
skipping to change at page 16, line 28 skipping to change at page 16, line 40
do not support keyrelay transactions or DNSSEC as suggested by do not support keyrelay transactions or DNSSEC as suggested by
Kees Monshouwer. Kees Monshouwer.
3. Added additional text for supporting key revocation as suggested 3. Added additional text for supporting key revocation as suggested
by Kees Monshouwer by Kees Monshouwer
4. Updated some of the wording 4. Updated some of the wording
5. Fix the usage of multiple keys in a create message 5. Fix the usage of multiple keys in a create message
Authors' Addresses A.10. draft-ietf-eppext-keyrelay-05
1. Review comments after WG last call
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/
Marc Groeneweg Marc Groeneweg
 End of changes. 19 change blocks. 
21 lines changed or deleted 37 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/