Extensible Provisioning Protocol (EPP) Unhandled Namespaces
draft-ietf-regext-unhandled-namespaces-08

Document Type Active Internet-Draft (regext WG)
Authors James Gould  , Martin Casanova 
Last updated 2021-03-02 (latest revision 2021-02-19)
Replaces draft-gould-casanova-regext-unhandled-namespaces
Stream Internent Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jul 2020 - Submit for publicati... )
Document shepherd David Smith
Shepherd write-up Show (last changed 2021-01-22)
IESG IESG state RFC Ed Queue
Action Holders
(None)
Consensus Boilerplate Yes
Telechat date
Responsible AD Barry Leiba
Send notices to David Smith <dsmith@verisign.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
IANA expert review state Reviews assigned
RFC Editor RFC Editor state EDIT
Details
Network Working Group                                           J. Gould
Internet-Draft                                            VeriSign, Inc.
Intended status: Standards Track                             M. Casanova
Expires: 23 August 2021                                           SWITCH
                                                        19 February 2021

      Extensible Provisioning Protocol (EPP) Unhandled Namespaces
               draft-ietf-regext-unhandled-namespaces-08

Abstract

   The Extensible Provisioning Protocol (EPP), as defined in RFC 5730,
   includes a method for the client and server to determine the objects
   to be managed during a session and the object extensions to be used
   during a session.  The services are identified using namespace URIs,
   and an "unhandled namespace" is one that is associated with a service
   not supported by the client.  This document defines an operational
   practice that enables the server to return information associated
   with unhandled namespace URIs that is compliant with the negotiated
   services defined in RFC 5730.

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 https://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 23 August 2021.

Copyright Notice

   Copyright (c) 2021 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 (https://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

Gould & Casanova         Expires 23 August 2021                 [Page 1]
Internet-Draft             unhandledNamespaces             February 2021

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   3
   2.  Unhandled Namespaces  . . . . . . . . . . . . . . . . . . . .   4
   3.  Use of EPP <extValue> for Unhandled Namespace Data  . . . . .   4
     3.1.  Unhandled Object-Level Extension  . . . . . . . . . . . .   5
     3.2.  Unhandled Command-Response Extension  . . . . . . . . . .   7
   4.  Signaling Client and Server Support . . . . . . . . . . . . .  10
   5.  Usage with General EPP Responses  . . . . . . . . . . . . . .  11
   6.  Usage with Poll Message EPP Responses . . . . . . . . . . . .  13
   7.  Implementation Considerations . . . . . . . . . . . . . . . .  16
     7.1.  Client Implementation Considerations  . . . . . . . . . .  16
     7.2.  Server Implementation Considerations  . . . . . . . . . .  16
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  XML Namespace . . . . . . . . . . . . . . . . . . . . . .  17
     8.2.  EPP Extension Registry  . . . . . . . . . . . . . . . . .  17
   9.  Implementation Status . . . . . . . . . . . . . . . . . . . .  17
     9.1.  Verisign EPP SDK  . . . . . . . . . . . . . . . . . . . .  18
     9.2.  SWITCH Automated DNSSEC Provisioning Process  . . . . . .  18
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  19
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  19
     12.2.  Informative References . . . . . . . . . . . . . . . . .  20
   Appendix A.  Change History . . . . . . . . . . . . . . . . . . .  20
     A.1.  Change from 00 to 01  . . . . . . . . . . . . . . . . . .  20
     A.2.  Change from 01 to 02  . . . . . . . . . . . . . . . . . .  21
     A.3.  Change from 02 to REGEXT 00 . . . . . . . . . . . . . . .  21
     A.4.  Change from REGEXT 00 to REGEXT 01  . . . . . . . . . . .  21
     A.5.  Change from REGEXT 01 to REGEXT 02  . . . . . . . . . . .  21
     A.6.  Change from REGEXT 02 to REGEXT 03  . . . . . . . . . . .  21
     A.7.  Change from REGEXT 03 to REGEXT 04  . . . . . . . . . . .  21
     A.8.  Change from REGEXT 04 to REGEXT 05  . . . . . . . . . . .  22
Show full document text