Hi, Dne 13. 09. 22 v 18:21 Viktor Dukhovni napsal(a):
The "OPT-RR" is message metadata, and so should not be confused with other sorts of additional records. (TSIG would also fall into that bucket).
Thank you for this point. So we should invent a way how to convert OPT record into properties of the JSON-represented message structure.
However, RFC 8427 gives no hints at all, how to do it. So there is big chance that everyone will implement this differently, leading to non-interoperability.
Can we do something about it?
I should also note that in terms of presentation forms, the SVCB record is particularly challenging, since it also sports extensible options of arbitrary types, and requires both a generic presentation form (for not known options) and a type-specific form for known options.
It seems that SVCB will be standardized soon, which makes me think that we may inspire ourselves.
It might be possible to invent a presentation format for EDNS (despite it does not appear in zonefiles, it should be still useful for other purposes), which would use the same tricks as SVCB presentation format. What do you think?
Thanks, Libor _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
