Hi, Based on an action item from IETF-102, Martin Casanova and I created the BCP draft-gould-casanova-regext-unhandled-namespaces to describe an approach for EPP unhandled namespaces. Please review and provide feedback. We would like to have an agenda item (10 minutes) at the IETF-103 REGEXT WG meeting to introduce and discuss the draft.
Thanks, — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 10/1/18, 10:20 AM, "internet-dra...@ietf.org" <internet-dra...@ietf.org> wrote: A new version of I-D, draft-gould-casanova-regext-unhandled-namespaces-00.txt has been successfully submitted by James Gould and posted to the IETF repository. Name: draft-gould-casanova-regext-unhandled-namespaces Revision: 00 Title: Extensible Provisioning Protocol (EPP) Unhandled Namespaces Document date: 2018-10-01 Group: Individual Submission Pages: 18 URL: https://www.ietf.org/internet-drafts/draft-gould-casanova-regext-unhandled-namespaces-00.txt Status: https://datatracker.ietf.org/doc/draft-gould-casanova-regext-unhandled-namespaces/ Htmlized: https://tools.ietf.org/html/draft-gould-casanova-regext-unhandled-namespaces-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-gould-casanova-regext-unhandled-namespaces 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. 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. The IETF Secretariat _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
