> On 26 Oct 2022, at 11:05, Eduardo Duarte
> wrote:
>
> Hi all,
>
> I'm not active in the WG but some one point out this draft during last week
> DNS-OARC meeting and I have a question for the Authors.
> So from my understanding after reading the Draft all the reporting is done
> over
Hi all,
I'm not active in the WG but some one point out this draft during last
week DNS-OARC meeting and I have a question for the Authors.
So from my understanding after reading the Draft all the reporting is
done over DNS itself. Did the Authors think of adding other reporting
mechanisms
Hello Ben,
Thanks for the feedback! We will account for that in the next version of
the DoC draft (-02) ASAP.
Some discussion regarding the ALPN ID (3) already started here:
https://github.com/core-wg/draft-dns-over-coap/issues/22, something
similar for OSCORE might also be required.
Best
Dne 26. 10. 22 v 19:02 Klaus Frank napsal(a):
I don't quite understand what the controversial part with this is, but
why not just copy RFC7686 (onion special use domain name) for .ALT?
Please don't.
RFC7686 requires that all DNS software, both recursive and
authoritative, treats .onion in
The IESG has approved the following document:
- 'DNS Security Extensions (DNSSEC)'
(draft-ietf-dnsop-dnssec-bcp-06.txt) as Best Current Practice
This document is the product of the Domain Name System Operations Working
Group.
The IESG contact persons are Warren Kumari and Robert Wilton.
A URL
I don't quite understand what the controversial part with this is, but
why not just copy RFC7686 (onion special use domain name) for .ALT?
It's an established precedence and also doesn't look like a bad idea to
just register the TLD with NXDOMAIN on the "normal" root dns servers?
>
John Levine wrote on 2022-10-25 14:30:
> ...
... Considering the vast amount of junk traffic that the roots
get now, it's hard to imagine that .alt would add enough to care about.
we don't and can't know that. in any case we should first do no harm.
the DNS is capable of signaling that a
Hi Roy,
Thank you for the explanation. Hopefully there will software that does
the translation to other reporting tools soon after the Draft is accepted.
eduardo_sign
Best regards,
Aviso de Confidencialidade/Disclaimer:
Este e-mail foi escrito de acordo com o novo acordo ortográfico.
Esta
On Oct 26, 2022, at 10:02 AM, Klaus Frank wrote:
>
> I don't quite understand what the controversial part with this is, but why
> not just copy RFC7686 (onion special use domain name) for .ALT?
>
> It's an established precedence and also doesn't look like a bad idea to just
> register the TLD
It appears that Paul Hoffman said:
>It is completely clear that, seven years later, many resolvers don't follow
>that SHOULD NOT rule. In fact, at at least one root server,
>.onion queries appear more often than many gTLDs and ccTLDs.
>
>The question is thus, is the value of adding that special
You're right. Someone should update that standards document to reflect
the real world standard.
Because after all if everyone does it it's still a standard even though
we currently don't have the RFC reflect "the actual standard".
However having an update to the RFC exactly with these points
11 matches
Mail list logo
