The WGLC for draft-ietf-regext-unhandled-namespaces ended on Friday, October 16th. The following are the changes included in draft-ietf-regext-unhandled-namespaces-04:
1. Changed from Best Current Practice (BCP) to Standards Track based on mailing list discussion. – This was agreed to ahead of the WGLC 2. Revised the dates in the examples to be more up-to-date. – The use of old dates was recognized while doing a final review of the draft by the document editors Please review and provide feedback on anything missed. Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 10/21/20, 10:11 AM, "regext on behalf of internet-dra...@ietf.org" <regext-boun...@ietf.org on behalf of internet-dra...@ietf.org> wrote: 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-04.txt Pages : 20 Date : 2020-10-21 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://secure-web.cisco.com/1Uo4ZL1LqMt0n4lILN7LZh4rEVbmOX1fbnBLpQgdlRyAXadRatHuEk5n0rtEvzqABkBXq3WoZdaWKOfiBDmfNbi4iGhd11ncvMjaMiaj0BVFMzVOsxjqsNW4KqITQX-oceNPZZ66yaDSWdwIBMAkQk06a-E7KClTXA51WQVETDEd2x6VBN5nc-FfgL6KkJzRjXWyk8j4y0No_0MKmMNQV0HRgT3QyYDG_HkQlrEgUqmbJTVwc_95ART0sQB6nIRLktQi6e3bm7pIZ5LobSULSSQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-unhandled-namespaces%2F There is also an HTML version available at: https://secure-web.cisco.com/17zFqzkELgDB1wyRS03J-ULqcrKQWfq_EW8jDO6EmwH_4C2AoEAvqQDcLnriyGvxvpA5oxnM2kLa7qSCB5JCZfJyt5CzKEZK589kbcRq2aUh5RQiasBQ4XG18eQIY4KYQ6lMMjGjyvQxL3iD0FM0uDmBasQsVBLrlsryfJebeQlzs-Edxc0lYscj4WwQ4JlOmVtm-XNUwczFefXBfgfd-LbBLceufk80Za9NgetgozyOLrZ6UOvjpJnn8iGJxE5QFHUSI32D6PUlQk3S15T9krMx2SHIM4ColjbAkmOyLP9s/https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-regext-unhandled-namespaces-04.html A diff from the previous version is available at: https://secure-web.cisco.com/1V-3pXnXlPyj2YgcDpha6flp9y-96gNV1ReR-QvTM4NYnOxpIlf1X3ougOooIsYgoggpyPnEzgj1-4SWXXS3KwaimO6JWUmsKki_dHl8AIlWBynlpUyJd_8TvM2zTsz8KvmvTF0EG4i1pFTHQbXYlEBEXxqG0pm3X6S9H4XLVKnYBx9Kb1qSNyjU8PDjcxrxmVYK2ICWTuNfkd45yOcl3wl06aph18e9npZbk4K_rSYRFGbqN64Lklw-hkJO1G7mBy30u2Qtj0EBUBnnjm-dfBXre3dr88xOm_CFAY7T4jeU/https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-regext-unhandled-namespaces-04 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/ _______________________________________________ regext mailing list regext@ietf.org https://secure-web.cisco.com/1cYbnDwqeJCyE6aIbizwM7NvsMBOYfQZWP2Lg0t3v-cLwgszQd7poDsDCK0EstrnmNUUkQaHkROzKqpzBdyAayQ8hB-gGvQtNKeXdB3G_lmipK3NaWFk45okw-ZjfzvwpQeg9bRdrXez5A4UVdewpI-NxOA4oxUS9Rv8AuURLt5t2l-kuDfJwBIuHBWpEul6O1qZFa8cQsWf3ZLBEEfL-dFHEgsy4cBei9S8Mfnt4T8ciDIsqpdN1MCELmEaXT4jLYEx6tD8QrHWaB1PGkPyELLX4p4hCisIGfCNfrLnclJ4/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext