--- 1/draft-ietf-regext-unhandled-namespaces-05.txt 2020-12-07 11:13:11.822170548 -0800 +++ 2/draft-ietf-regext-unhandled-namespaces-06.txt 2020-12-07 11:13:11.850170923 -0800 @@ -1,24 +1,24 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track M. Casanova -Expires: 19 May 2021 SWITCH - 15 November 2020 +Expires: 10 June 2021 SWITCH + 7 December 2020 Extensible Provisioning Protocol (EPP) Unhandled Namespaces - draft-ietf-regext-unhandled-namespaces-05 + draft-ietf-regext-unhandled-namespaces-06 Abstract The Extensible Provisioning Protocol (EPP), as defined in RFC 5730, - includes a method for the client and server tof determine the objects + 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 @@ -33,21 +33,21 @@ 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. + This Internet-Draft will expire on 10 June 2021. Copyright Notice Copyright (c) 2020 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 @@ -65,38 +65,39 @@ 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 + 8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 - 9.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 18 + 9.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 17 9.2. SWITCH Automated DNSSEC Provisioning Process . . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 - 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 + 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 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 A.4. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 20 A.5. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 20 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 . . . . . . . . . . . 21 + A.9. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 1. Introduction The Extensible Provisioning Protocol (EPP), as defined in [RFC5730], 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 @@ -154,35 +155,36 @@ An Unhandled Namespace is an XML namespace that is associated with a response extension that is not included in the client-specified EPP login services of [RFC5730]. The EPP login services consists of the set of XML namespace URIs included in the or elements of the [RFC5730] EPP command. The services supported by the server are included in the and elements of the [RFC5730] EPP , which should be a superset of the login services included in the EPP command. A server may have information associated with a specific namespace that it needs to return in the response to a client. The unhandled - namespaces problem exists when the server has information, that it - needs to return to the client, that is not supported by the client - based on the negotiated EPP command services. + namespaces problem exists when the server has information that it + needs to return to the client but the namespace of the information is + not supported by the client based on the negotiated EPP + command services. 3. Use of EPP for Unhandled Namespace Data In [RFC5730], the element is used to provide additional error diagnostic information, including the element that identifies the client-provided element that caused a server error - condition, and the element containing the human-readable + condition and the element containing the human-readable message that describes the reason for the error. This operational practice extends the use of the element for the purpose of returning unhandled namespace information in a successful response. - When a server has data to return to the client, that the client does + When a server has data to return to the client that the client does not support based on the login services, the server MAY return a successful response, with the data for each unsupported namespace moved into an [RFC5730] element. The unhandled namespace will not cause an error response, but the unhandled namespace data will instead be moved to an element, along with a reason why the unhandled namespace data could not be included in the appropriate location of the response. The element XML will not be processed by the XML processor. The element contains the following child elements: @@ -401,22 +403,22 @@ S: S: ns1.example.com S: ns2.example.com S: S: ns1.example.com S: ns2.example.com S: ClientX S: ClientY S: 1999-04-03T22:00:00.0Z S: ClientX - S: 2020-12-03T09:00:00.0Z - S: 2021-04-03T22:00:00.0Z + S: 1999-12-03T09:00:00.0Z + S: 2005-04-03T22:00:00.0Z S: 2000-04-08T09:00:00.0Z S: S: 2fooBAR S: S: S: S: S: ABC-12345 S: 54322-XYZ S: @@ -429,30 +431,30 @@ practice using the existing EPP protocol, where the client and the server can signal support for the operational practice using a namespace URI in the login and greeting extension services. The namespace URI "urn:ietf:params:xml:ns:epp:unhandled-namespaces-1.0" is used to signal support for the operational practice. The client includes the namespace URI in an element of the [RFC5730] Command. The server includes the namespace URI in an element of the [RFC5730] Greeting. A client that receives the namespace URI in the server's Greeting - extension services, can expect the following supported behavior by - the server: + extension services can expect the following supported behavior by the + server: 1. Support unhandled namespace object-level extensions and command- response extensions in EPP poll messages, per Section 6. 2. Support the option of unhandled namespace command-response extensions in general EPP responses, per Section 5. A server that receives the namespace URI in the client's - Command extension services, can expect the following supported + Command extension services can expect the following supported behavior by the client: 1. Support monitoring the EPP poll messages and general EPP responses for unhandled namespaces. 5. Usage with General EPP Responses The unhandled namespace approach defined in Section 3 MAY be used for a general EPP response to an EPP command. A general EPP response includes any non-poll message EPP response. The use of the unhandled @@ -469,22 +471,22 @@ returned when the server successfully executes an object-level EPP command extension. The server MAY return an unhandled object-level extension to the client as defined in Section 3.1. Returning domain name Redemption Grace Period (RGP) data, based on [RFC3915], provides an example of applying the unhandled namespace approach for a general EPP response. If the client does not include the "urn:ietf:params:xml:ns:rgp-1.0" namespace URI in the login services, and the domain response of a domain name does have RGP information, the server MAY exclude the element - from the EPP response or MAY include it under in the - element per Section 3.2. + from the EPP response or MAY include it under the element + per Section 3.2. [RFC5731] domain name response with the unhandled [RFC3915] element included under an element: S: S: S: S: S: Command completed successfully S: @@ -561,41 +563,39 @@ element: S: S: S: S: S: Command completed successfully; ack to dequeue S: S: S: S: update S: S: 2020-11-22T05:00:00.000Z S: 12345-XYZ S: URS Admin S: urs123 S: S: URS Lock S: S: S: S: urn:ietf:params:xml:ns:changePoll-1.0 not in login services S: S: S: - S: + S: S: 2020-11-22T05:00:00.000Z S: Registry initiated update of domain. S: S: S: S: change-poll.tld S: EXAMPLE1-REP S: S: @@ -664,70 +664,69 @@ S: urs123 S: S: URS Lock S: S: S: S: urn:ietf:params:xml:ns:changePoll-1.0 not in login services S: S: S: - S: + S: S: 2020-11-22T05:00:00.000Z S: Registry initiated update of domain. S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 7. Implementation Considerations There are implementation considerations for the client and the server to help address the risk of the client ignoring unhandled namespace information included in an EPP response that is needed to meet technical, policy, or legal requirements. 7.1. Client Implementation Considerations To reduce the likelihood of a client receiving unhandled namespace - information, the client should consider the following: + information, the client should consider implementing the following: + + 1. Ensure that the client presents the complete set of what it + supports when presenting its login services. If there are gaps + between the services supported by the client and the login + services included in the login command, the client may receive + unhandled namespace information that the client could have + supported. - 1. Ensure that the login services is accurate with what is supported - by the client. If there are gaps between the services supported - by the client and the login services included in the login - command, the client may receive unhandled namespace information - that the client could have supported. 2. Support all of the services included in the server greeting services that may be included in an EPP response, including the poll queue responses. The client should evaluate the gaps between the greeting services and the login services provided in the login command to identify extensions that need to be supported. 3. Proactively monitor for unhandled namespace information in the EPP responses, by looking for the inclusion of the element in successful responses, recording the unsupported namespace included in the element, and recording the unhandled namespace information included in the element - for later processing. The unhandled namespace can be implemented - by the client to ensure that information is processed fully in - future EPP responses. + for later processing. The unhandled namespace should be + implemented by the client to ensure that information is processed + fully in future EPP responses. 7.2. Server Implementation Considerations To assist the clients in recognizing unhandled namespaces, the server - should consider the following: + should consider implementing the following: 1. Monitor for returning unhandled namespace information to clients and report it to the clients out-of-band to EPP so the clients can add support for the unhandled namespaces. 2. Look for the unhandled namespace support in the login services when returning optional unhandled namespace information in General EPP Responses. 8. IANA Considerations @@ -965,20 +965,25 @@ returning unhandled namespace information. 2. Based on feedback from Thomas Corte, added a Implementation Considerations section to cover client and server implementation recommendations such as monitoring unhandled namespaces in the server to report to the clients out-of-band and monitoring for responses containing unhanded namespace information in the client to proactively add support for the unhandled namespaces. 3. Moved RFC 3735 and RFC 7451 to informative references to address down reference errors in idnits. +A.9. Change from REGEXT 05 to REGEXT 06 + + 1. Nit updates made based on the feedback provided by the Document + Shepherd, David Smith. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 United States of America Email: jgould@verisign.com URI: http://www.verisigninc.com