On Tue, 24 Jan 2023 at 19:28, Tim Wicinski <[email protected]> wrote:
>8
> One thing which concerns me is the updating of RFC8914. RFC8914 has only been
> out a short while, and we're just starting to see deployment out in the world.
It does seem distasteful to pile structured data into a field which
RFC8914 declares to be explanatory text.
The basic idea behind this draft is a good one which could also be
useful in other contexts.
I hope that the authors of RFC8914 might be persuaded to produce an
RFC8914-bis allowing JSON structured data to appear in the EXTRA-TEXT
field. The wire-format remains the same, the structured case being
distinguished by the appearance of a "{" or "[" as the leading
character. The EXTRA-TEXT field should perhaps be renamed EXTRA-INFO
to reflect its more general content.
A quick and dirty modification to perl Net::DNS then produces the following:
;; { "EDNS-VERSION": 0,
;; "FLAGS": "0000",
;; "RCODE": 0,
;; "UDPSIZE": 0,
;; "OPTIONS": [
;; { "EXTENDED-ERROR": { "EXTRA-TEXT": { "c": [ "tel:+358-555-1234567",
;; "sips:[email protected]",
;; "https://ticket.example.com?d=example.org&t=1650560748"; ],
;; "j": "malware present for 23 days", "o":
"example.net Filtering Service", "s": 1
;; }, "INFO-CODE": 123 } } ]
;; }
--Dick
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
