I would like to see some allowance of limited metadata about which node responded, or other information variance. If thats confined to comments in the outer protocol, it means the response inline cannot be used to debug specific problems with the node which responded.
We see this all the time in DNS: The lack of information about the service methods used to supply a response makes debug significantly harder. in-band introspection is useful. It isn't about the response, its about how the response came to be. -G On Thu, Aug 13, 2020 at 9:40 PM Gavin Brown <gavin.br...@centralnic.com> wrote: > > > On 12 Aug 2020, at 17:18, Marc Blanchet <marc.blanc...@viagenie.ca> wrote: > > > > well, already added text in the published draft yesterday. > > > > https://www.ietf.org/internet-drafts/draft-blanchet-regext-rfc7484bis-00.txt > > > > extract of my added text: > > « All RDAP endpoints referenced by the URLs in the array MUST return > > identical responses for the same RDAP query. » > > > > would that work? > > Looks good to me. > > G. > > -- > Gavin Brown > Head of Registry Services and Chief Innovation Officer > CentralNic Group plc (LSE:CNIC) > https://www.centralnic.com > > Tel: +44.7548243029 > > CentralNic Group plc is a company registered in England and Wales with > company number 8576358. Registered Offices: Saddlers House, Gutter Lane, > London EC2V 6AE. > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
