Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Hi folks, On 3/22/21 5:29 PM, Willem Toorop wrote: > [...] > Would be good to have that in a test vector ;). Hence the inclusion of the unsorted keys vector :). > Excellent! How SHOULD it enforce? By failing to load or by fixing. This is all implementation specific of course :). For PowerDNS

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Op 22-03-2021 om 15:50 schreef Ben Schwartz: > On Mon, Mar 22, 2021 at 5:41 AM Willem Toorop > wrote: > > But what about the keys in the "mandatory" SvcParam? Should they be > sorted automatically? Or should the parser produce an error if they are > not

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

> On 22 Mar 2021, at 20:41, Willem Toorop wrote: > > Op 19-03-2021 om 18:03 schreef Pieter Lexis: >> Hi Willem, >> >> On 3/19/21 11:47 AM, Willem Toorop wrote: >>> That'd be nice! >> >> PR is here [1]. >> >>> Do you also have tests for peculiar/corner and failure cases? >> >> I'm a little

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Op 19-03-2021 om 18:03 schreef Pieter Lexis: > Hi Willem, > > On 3/19/21 11:47 AM, Willem Toorop wrote: >> That'd be nice! > > PR is here [1]. > >> Do you also have tests for peculiar/corner and failure cases? > > I'm a little bit unsure what you men with this :). Well, I am wondering how

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

On Fri, 19 Mar 2021 at 10:15, Willem Toorop wrote: >8 > > > The Net::DNS perl library does have parsing and printing of SVCB and > HTTPS based on draft-ietf-dnsop-svcb-https-01 since version 1.26 > (released on August 6, 2020). @Dick, what is your position on this? Change of name only affects

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

On Fri, 2021-03-19 at 10:42 -0400, Ben Schwartz wrote: > Does anyone have an example of test vector presentation that they like? > Perhaps it should be structured as a pair of zone files representing the same > zone, one in SVCB format and one in RFC 3597. tl;dr: +1 to that I recently

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Hi Willem, On 3/19/21 11:47 AM, Willem Toorop wrote: > That'd be nice! PR is here [1]. > Do you also have tests for peculiar/corner and failure cases? I'm a little bit unsure what you men with this :). The code is here[2]. I've also opened a PR updating our parser for the draft-03 changes for

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Op 19-03-2021 om 11:19 schreef Pieter Lexis: > Hi Willem, Ben, > > On 3/19/21 11:14 AM, Willem Toorop wrote: >> Also, it would have been nice to have some test-vectors of RR's in >> presentation format and wire format (in hexdump) in an appendix in the >> document, to assist in the creation of

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Hi Willem, Ben, On 3/19/21 11:14 AM, Willem Toorop wrote: > Also, it would have been nice to have some test-vectors of RR's in > presentation format and wire format (in hexdump) in an appendix in the > document, to assist in the creation of interoperable implementations. > Maybe this can still be

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

[ Quoting in "Re: [DNSOP] I-D Action: draft-ietf-..." ] No version of NSD, Unbound, ldns and getdns with SVCB and HTTPS support has been released yet, so no problem for us to change the name of SvcParamKey 5 to ech for us there, but ... The Net::DNS perl library does have parsing and printing

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

No version of NSD, Unbound, ldns and getdns with SVCB and HTTPS support has been released yet, so no problem for us to change the name of SvcParamKey 5 to ech for us there, but ... The Net::DNS perl library does have parsing and printing of SVCB and HTTPS based on draft-ietf-dnsop-svcb-https-01

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Hi, On 3/18/21 6:42 PM, Tommy Pauly wrote: > Personally, I’d prefer to see the name change, and not burn a codepoint, > as long as we’re not breaking any zone files. Agree. > I think the question is: does anyone have a zone that has actually > deployed the echconfig parameter? I see many

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

FYI in Knot DNS, the implementation is at exactly the same state: an existing merge request. For us, it's technically no issue if the presentation/wire format changes during next few weeks. I'm saying nothing about ideological consequences of such approach. /Libor Dne 19. 03. 21 v 0:05 Mark

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

> On 19 Mar 2021, at 04:42, Tommy Pauly > wrote: > > > >> On Mar 17, 2021, at 6:04 PM, Ben Schwartz >> wrote: >> >> Release notes for this revision: >> * Simplify the IANA instructions (pure First Come First Served) >> * Recommend against publishing chains of >8 aliases >>

Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

> On Mar 17, 2021, at 6:04 PM, Ben Schwartz > wrote: > > Release notes for this revision: > * Simplify the IANA instructions (pure First Come First Served) > * Recommend against publishing chains of >8 aliases > * Clarify requirements for using SVCB with a transport proxy

[DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : Service binding and parameter specification via the DNS (DNS SVCB and HTTPS RRs) Authors :