Re: [DNSOP] [core] [dns-privacy] WGA call for draft-lenders-dns-over-coap

2022-08-15 Thread Carsten Bormann
On 15. Aug 2022, at 17:11, Ted Lemon wrote: > > This is a good question. I think we’d want to understand what the actual use > case is for DNS-over-CoAP before proceeding with this, The main use case is systems that already implement CoAP and do not want to add machinery for some protocols tha

Re: [DNSOP] [core] [dns-privacy] WGA call for draft-lenders-dns-over-coap

2022-08-15 Thread Carsten Bormann
On 15. Aug 2022, at 19:41, Ted Lemon wrote: > >> On Aug 15, 2022, at 1:34 PM, Carsten Bormann wrote: >> >> On 15. Aug 2022, at 17:11, Ted Lemon wrote: >>> >>> This is a good question. I think we’d want to understand what the actual >>> use

Re: [DNSOP] [core] WGA call for draft-lenders-dns-over-coap

2022-09-20 Thread Carsten Bormann
I think we are falling into the restatement antipattern. This antipattern happens when documents restate mandates from their references, invariably creating confusion if this is just a restatement or actually new normative text that replaces or updates text from the dependency. Don’t do that. Examp

Re: [DNSOP] [core] Next steps: draft-ietf-core-dns-over-coap

2023-07-07 Thread Carsten Bormann
On 2023-07-07, at 09:26, Esko Dijk wrote: > > In the last interim meeting presentation “security” was a key driver for this > draft. Which is a very good one; compared to non-secured DNS as the > alternative. > > Firmware size and code complexity/BOM are also relevant if this protocol can >

[DNSOP] Fwd: WG Adoption Call for draft-lenders-core-coap-dtls-svcb

2024-07-29 Thread Carsten Bormann
Resending as there appears to be a mail forwarding problem. > > Forwarded Message > Subject: WG Adoption Call for draft-lenders-core-coap-dtls-svcb > Date: Mon, 29 Jul 2024 11:59:31 +0200 > From: Marco Tiloca > To: c...@ietf.org

[DNSOP] Re: [Last-Call] Opsdir last call review of draft-ietf-dnsop-generalized-notify-05

2025-02-07 Thread Carsten Bormann
On 2025-02-07, at 18:28, John R. Levine wrote: > > I think we usually remove the implementation status section when an I-D turns > into an RFC. Yes, and that practice has consensus as a Best Current Practice (BCP 205): https://www.rfc-editor.org/rfc/rfc7942 It may be worth to read this BCP and