On Fri, 3 May 2024 13:11:38 +0000 Gavin Brown <gavin.br...@icann.org> wrote:
> Hi Maarten, Hello Gavin, > > On 25 Apr 2024, at 13:10, Maarten Wullink > > <maarten.wullink=40sidn...@dmarc.ietf.org> wrote: [cut] > > We added a new XML schema in our last version to better align the > > EPP XML to the RESTful style, if this is a blocking issue, then we > > can remove the new XML schema in the next version and go back to > > using the XML schema from RFC 5730. > > Thanks for providing this context, it's helpful to understand what > the objectives are. > > As I understand it, the rationale is to move some protocol elements > from the XML to elsewhere in the HTTP message so that these can be > used to control routing, caching, load balancing, etc. > > *Copying* these elements would achieve the same effect, and altering > the XML schema just to avoid duplication throws the baby out of the > bathwater. I would strongly recommend that the schemas from RFCs > 5730-5733 remain unchanged. If the elements would be copied, I would like to see a text that states that the values that are put in the HTTP message MUST be the same as the ones in the xml data. And also what to do if they are not the same. I know a client who doesn't do that is not compliant with the standard, but that would not stop people from doing it ;-( -- Stefan Ubbink DNS & Systems Engineer Present: Mon, Tue, Wed, Fri SIDN | Meander 501 | 6825 MD | ARNHEM | The Netherlands T +31 (0)26 352 55 00 https://www.sidn.nl
pgpqajSxDX3vw.pgp
Description: OpenPGP digital signature
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
