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

Document Type Active Internet-Draft (regext WG)
Authors James Gould  , Martin Casanova 
Last updated 2020-11-15
Replaces draft-gould-casanova-regext-unhandled-namespaces
Stream IETF
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Consensus: Waiting for Write-Up (wg milestone: Jul 2020 - Submit for publicati... )
Document shepherd David Smith
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to David Smith <dsmith@verisign.com>
Network Working Group                                           J. Gould
Internet-Draft                                            VeriSign, Inc.
Intended status: Standards Track                             M. Casanova
Expires: 19 May 2021                                              SWITCH
                                                        15 November 2020

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

Abstract

   The Extensible Provisioning Protocol (EPP), as defined in RFC 5730,
   includes a method for the client and server tof 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.
   How should the server handle service data that needs to be returned
   in the response when the client does not support the required service
   namespace URI, which is referred to as an unhandled namespace?  An
   unhandled namespace is a significant issue for the processing of RFC
   5730 poll messages, since poll messages are inserted by the server
   prior to knowing the supported client services, and the client needs
   to be capable of processing all poll messages.  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 19 May 2021.

Copyright Notice

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

Gould & Casanova           Expires 19 May 2021                  [Page 1]
Internet-Draft             unhandledNamespaces             November 2020

   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
   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  . . . . . . . . . . . . . .  10
   6.  Usage with Poll Message EPP Responses . . . . . . . . . . . .  12
   7.  Implementation Considerations . . . . . . . . . . . . . . . .  15
     7.1.  Client Implementation Considerations  . . . . . . . . . .  15
     7.2.  Server Implementation Considerations  . . . . . . . . . .  16
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  XML Namespace . . . . . . . . . . . . . . . . . . . . . .  16
     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 . . . . . . . . . . . . . . . . . . .  18
   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  . . . . . . . . . . . . . . . . . .  20
     A.3.  Change from 02 to REGEXT 00 . . . . . . . . . . . . . . .  20
Show full document text