I was rethinking my initial concerns, and needed to talk it out with others. After going back over it with folks smarter than myself, it's more obvious to me that when the need for escaping inputs will be more of an exception.
My concern is focused not so much on implementers (sorry) but the operators and engineers who will be the ones inserting these records into zone files. I do however want to have the presentation format examples be full DNS records, and not just RDATA. In the followinbg section in on failure cases, DNS records are used: example.com. SVCB 1 foo.example.com. mandatory The test vectors should be the same. tim On Fri, May 7, 2021 at 9:19 AM Dick Franks <rwfra...@gmail.com> wrote: > On Fri, 7 May 2021 at 11:21, Pieter Lexis <pieter.le...@powerdns.com> > wrote: > > > >8 > > > > I can see how this might be confusing to those writing zone contents and > > would support a solution that either prohibits comma's in SVCParam list > > values or a different value separator that is not allowed to be embedded > > in values. > > Tim W. pointed out earlier in this thread that "those writing zone > contents" are the majority stakeholders and rarely familiar with the > finer points of DNS. > If we are inflicting confusion on these people by departing from > standard and well-understood character escapes for no other reason > than the convenience of developers, then we have our priorities > seriously wrong. > > > --Dick >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
