Michael, We'll agree to disagree on this. I don't believe inclusion of an XML schema and a candidate set of XML examples is too high of a bar for working group adoption of an EPP extension when an XML schema is needed. As changes occur in the draft, the XML schema and XML examples can be updated. The latest practice is to use point versioning (e.g., start with of the XML namespace " urn:ietf:params:xml:ns:epp:variants-0.1" and bump the version with each material change to the interface, with a final bump to "urn:ietf:params:xml:ns:epp:variants-1.0" once it passes WGLC) to enable draft implementations with namespace isolation and signaling via the EPP <greeting> and the EPP <login>.
Thanks, -- JG James Gould Fellow Engineer [email protected] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 5/23/26, 4:22 AM, "Michael Bauland" <[email protected] <mailto:[email protected]>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Jim, Am 18.05.2026 um 22:16 schrieb Gould, James: > Arnt, > > The EPP extension draft should be in a mature enough state to request > for adoption in step #3, which includes an initial XML schema and a set > of XML examples. It’s unclear what draft-galvin-regext-epp-variants is > proposing to do without proposing an XML schema and having sample XML > for each of the supported commands. Some items can be TBD and worked > out based on working group discussion and the XML schema and XML > examples can drastically change. I believe inclusion of an XML schema > and a set of XML examples as a minimum bar for EPP extension drafts that > require an XML schema. My recommendation is to add them to provide a > clearer picture of what is being proposed. we're currently in the process of adding some further examples (two are already part of the currently published version). While we agree that the final version will have a full set of examples and the schema definition of the EPP extension, we would prefer not having this complete data available at this stage. What we are suggesting and how this should be done is already described in the text for the different commands and responses. However, we expect that there might be some changes and/or additions depending on how we are going to deal with other existing related extensions. Best regards, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: [email protected] <mailto:[email protected]> Software Development E-mail: [email protected] <mailto:[email protected]> Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp Certified according DIN ISO/IEC 27001:2017 _______________________________________________ regext mailing list -- [email protected] <mailto:[email protected]> To unsubscribe send an email to [email protected] <mailto:[email protected]> _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
