On Mon, 24 Jun 2024, Joe Abley wrote:
It seems like it would be nice to be able to implement future new RRTypes like WALLET
simply by adding an RRType to an array of RRTypes that are all implemented the same way,
rather than writing new parsers for every one of them. It would also make applican
It appears that Joe Abley said:
>(c) write some guidance for future applications of the form "basically TXT but
>with a different RRTYPE" to make things as cookie-cutter as
>possible for implementers, and add a question to the application template of
>the form "explain why you can't just use th
I recall a long-ago problem involving SIP DNS resource records related to
confusion over escaped values. I believe it was the NAPTR resource record.
The problem presented to me involved two RFC documents, but related to NAPTR
and both “published” as RFCs (not Internet Drafts).
The conflict bet
On 23 Jun 2024, at 04:58, Mark Andrews wrote:
> Turning off escape processing prevents turning off multi line processing.
https://www.iana.org/assignments/dns-parameters/WALLET/wallet-completed-template
Our expert review guidelines are explicitly lenient so I suppose I'm not
surprised this wa
I was meaning to send a more meaningful message.
WALLET has the following paragraph that should have prevented it being approved
because multi-line continuation can be anywhere in a record and there is no way
actually write a zone file parser and also do the requested behaviour.
"None of the char
