[regext] I-D Action: draft-ietf-regext-unhandled-namespaces-00.txt

internet-drafts@ietf.org Fri, 14 February 2020 21:49 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 77BE9120013; Fri, 14 Feb 2020 13:49:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.117.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: regext@ietf.org
Message-ID: <158171694441.16207.5341182498471832316@ietfa.amsl.com>
Date: Fri, 14 Feb 2020 13:49:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/0uknjUTWMi46GxcsXNDKDTSGDwk>
Subject: [regext] I-D Action: draft-ietf-regext-unhandled-namespaces-00.txt
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2020 21:49:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Registration Protocols Extensions WG of the IETF.

        Title           : Extensible Provisioning Protocol (EPP) Unhandled Namespaces
        Authors         : James Gould
                          Martin Casanova
	Filename        : draft-ietf-regext-unhandled-namespaces-00.txt
	Pages           : 18
	Date            : 2020-02-14

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.
   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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-unhandled-namespaces/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-regext-unhandled-namespaces-00
https://datatracker.ietf.org/doc/html/draft-ietf-regext-unhandled-namespaces-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/