Re: [DNSOP] Unknown DNS RDATA type presentation syntax vs. e.g. TXT records?

2020-02-10 Thread Mark Andrews
> On 11 Feb 2020, at 11:16, 神明達哉 wrote: > > At Sun, 9 Feb 2020 04:28:14 -0500, > Viktor Dukhovni wrote: > >> ---> An implementation MAY also choose to represent some RRs of known type >> ---> using the above generic representations for the type, class and/or >> ---> RDATA, which carries the

Re: [DNSOP] Unknown DNS RDATA type presentation syntax vs. e.g. TXT records?

2020-02-10 Thread 神明達哉
At Sun, 9 Feb 2020 04:28:14 -0500, Viktor Dukhovni wrote: > ---> An implementation MAY also choose to represent some RRs of known type > ---> using the above generic representations for the type, class and/or > ---> RDATA, which carries the benefit of making the resulting master file > ---

Re: [DNSOP] Unknown DNS RDATA type presentation syntax vs. e.g. TXT records?

2020-02-10 Thread Tony Finch
Viktor Dukhovni wrote: > > I was therefore surprised to find that BIND 9.14 refuses load zone files > with TXT records in the generic form, for example named-checkzone does > not accept: > > example.org.IN TXT \# 4 deadbeef The long version of Mark's message is that a TXT record consists

[DNSOP] Publication has been requested for draft-ietf-dnsop-7706bis-07

2020-02-10 Thread Suzanne Woolf via Datatracker
Suzanne Woolf has requested publication of draft-ietf-dnsop-7706bis-07 as Informational on behalf of the DNSOP working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-dnsop-7706bis/ ___ DNSOP mailing list DNSOP

Re: [DNSOP] Unknown DNS RDATA type presentation syntax vs. e.g. TXT records?

2020-02-10 Thread Viktor Dukhovni
> On Feb 9, 2020, at 4:55 AM, Mark Andrews wrote: > > Put a valid txt record in > > \# 5 04deadbeef Oops. :-( Never mind, thanks for the correction. Indeed not forgetting the length works. FWIW, I was just double-checking the presentation form of special characters in TXT records for a new c