Gavin, I guess it comes down to the definition of backwards compatibility. I view this as an XML schema bug that doesn't match the intention of the specification. A client will not be expecting an error in this case, but will be expecting a success, which is addressed by fixing the bug in the XML schema. Changing the XML namespace can certainly be done, but I don't believe it's necessary for fixing a schema bug.
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 1/27/26, 8:22 AM, "Gavin Brown" <[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, > On 26 Jan 2026, at 1:14 pm, Gould, James <[email protected] > <mailto:[email protected]>> wrote: > > I agree that the report is correct, and I confirmed the issue and the fix in > our EPP SDK. I'm not sure whether changing of the namespace URI is necessary > here since the fix is backward compatible and meets the intent of the > extension. Existing implementations of the namespace URI will not be impacted > by replacing the XML schema with the corrected version. I don't think this is the case. If client and server each implement different versions, then each could receive an EPP XML instance from the other that it would consider invalid. The only way for client and server to know which version the other implements is via the namespace URIs in the <extURI> elements in the <greeting>. Therefore a new URI is necessary, I think. G. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://secure-web.cisco.com/16wMakdjXcMzzBrW1x2c6pGyCRnnyo60FuyMc9E2CgS1nqTm9ugQXm-RAf7zs63e5IoJm6v0g6F6hPmbIhE5wK9A-tGoHiNatptwMDLL1QTsh6SUSCH1m7r3NMH5oVIPoJW0BXVKoS2Mc2ij5af2M0uUn-2nTuR3HrNGYRR09jvf6w2eXmiirRzE4b7md-fcSO2zSmgolDiPGIpmyoYZoxihCcoaynZcJAdEy3lEJCAKfr0FJp_7Oan-p5Aj-qlfoXR-JAkuksGVs0L165rZ0wFmYQI-jerZefaYw6bkkCOs/https%3A%2F%2Fwww.icann.org <https://secure-web.cisco.com/16wMakdjXcMzzBrW1x2c6pGyCRnnyo60FuyMc9E2CgS1nqTm9ugQXm-RAf7zs63e5IoJm6v0g6F6hPmbIhE5wK9A-tGoHiNatptwMDLL1QTsh6SUSCH1m7r3NMH5oVIPoJW0BXVKoS2Mc2ij5af2M0uUn-2nTuR3HrNGYRR09jvf6w2eXmiirRzE4b7md-fcSO2zSmgolDiPGIpmyoYZoxihCcoaynZcJAdEy3lEJCAKfr0FJp_7Oan-p5Aj-qlfoXR-JAkuksGVs0L165rZ0wFmYQI-jerZefaYw6bkkCOs/https%3A%2F%2Fwww.icann.org> _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
