Re: [homenet] Dnsdir telechat review of draft-ietf-homenet-naming-architecture-dhc-options-21

2022-10-24 Thread Daniel Migault
Thanks for the response. Yours, Daniel On Mon, Oct 24, 2022 at 3:49 AM Miek Gieben wrote: > [ Quoting in "Re: [homenet] Dnsdir telechat > revie..." ] > >OLD: > >It is worth noticing that the Supported Transport field does not enable to > >specify a port and the used port is defined by standard.

Re: [homenet] Dnsdir telechat review of draft-ietf-homenet-naming-architecture-dhc-options-21

2022-10-24 Thread Miek Gieben
[ Quoting in "Re: [homenet] Dnsdir telechat revie..." ] OLD: It is worth noticing that the Supported Transport field does not enable to specify a port and the used port is defined by standard.    NEW: It is worth noticing that the Supported Transport field does not enable to specify a port and

Re: [homenet] Dnsdir telechat review of draft-ietf-homenet-naming-architecture-dhc-options-21

2022-10-18 Thread Daniel Migault
Hi, Thanks for the review. So the reason we do not consider DOH is that DoH 8484 has been defined for communications between a client and a resolver while in our case TLS is used between two authoritative servers. This document focuses on communication between DNS clients (such as operating

[homenet] Dnsdir telechat review of draft-ietf-homenet-naming-architecture-dhc-options-21

2022-10-14 Thread R. Gieben via Datatracker
Reviewer: R. Gieben Review result: Ready with Nits A straight forward document specifying dhcpv6 options, had little trouble reading it. Got a bit lost with acronyms though, i.e. forgetting what ORO is when nearing the end of the document. Any reason why DNS over HTTP (DoH, RFC 8484) isn't standa