Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)
RFC 4310
Document | Type |
RFC - Proposed Standard
(December 2005; No errata)
Obsoleted by RFC 5910
Was draft-hollenbeck-epp-secdns (individual in ops area)
|
|
---|---|---|---|
Author | Scott Hollenbeck | ||
Last updated | 2013-03-02 | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4310 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | David Kessens | ||
Send notices to | sah@428cobrajet.net |
Network Working Group S. Hollenbeck Request for Comments: 4310 VeriSign, Inc. Category: Standards Track November 2005 Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of Domain Name System security extensions (DNSSEC) for domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of DNS security extensions. Table of Contents 1. Introduction ....................................................2 1.1. Conventions Used in This Document ..........................2 2. Object Attributes ...............................................3 2.1. Delegation Signer Information ..............................3 2.1.1. Public Key Information ..............................3 2.2. Booleans ...................................................3 2.3. Maximum Signature Lifetime Values ..........................4 3. EPP Command Mapping .............................................4 3.1. EPP Query Commands .........................................4 3.1.1. EPP <check> Command .................................4 3.1.2. EPP <info> Command ..................................4 3.1.3. EPP <transfer> Command ..............................8 3.2. EPP Transform Commands .....................................8 3.2.1. EPP <create> Command ................................8 3.2.2. EPP <delete> Command ...............................11 3.2.3. EPP <renew> Command ................................11 3.2.4. EPP <transfer> Command .............................11 Hollenbeck Standards Track [Page 1] RFC 4310 EPP DNS Security Extensions Mapping November 2005 3.2.5. EPP <update> Command ...............................11 4. Formal Syntax ..................................................15 5. Internationalization Considerations ............................18 6. IANA Considerations ............................................18 7. Security Considerations ........................................18 8. Acknowledgements ...............................................20 9. References .....................................................20 9.1. Normative References ......................................20 9.2. Informative References ....................................21 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) described in RFC 3730 [1]. This mapping, an extension of the domain name mapping described in RFC 3731 [2], is specified using the Extensible Markup Language (XML) 1.0 [3] and XML Schema notation ([4], [5]). The EPP core protocol specification [1] provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the mapping described in this document. Familiarity with the Domain Name System (DNS) described in RFC 1034 [11] and RFC 1035 [12] and with DNS security extensions described in RFC 4033 [13], RFC 4034 [6], and RFC 4035 [7] is required to understand the DNS security concepts described in this document. The EPP mapping described in this document specifies a mechanism for the provisioning and management of DNS security extensions in a shared central repository. Information exchanged via this mapping can be extracted from the repository and used to publish DNSSEC delegation signer (DS) resource records as described in RFC 4034 [6]. 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 [8]. 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 onlyShow full document text