I find the latest alt-tld draft to be inconsistent when it first
says “[alt names] should not be looked up in a DNS context” and
"DNS stub and recursive resolvers do not need to look them up in
the DNS context” but then later "Caching DNS servers will treat
[alt names] just as they would any other
> On 11 Nov 2022, at 09:48, Wessels, Duane
> wrote:
>
> I find the latest alt-tld draft to be inconsistent when it first
> says “[alt names] should not be looked up in a DNS context” and
> "DNS stub and recursive resolvers do not need to look them up in
> the DNS context” but then later "Cachin
Dne 11. 11. 22 v 10:48 Wessels, Duane napsal(a):
5. Authoritative DNS Servers: Authoritative servers MUST respond to
queries for .alt names with NXDOMAIN.
I don't like to repeat myself, but I still consider this requirement
proposal inproper and I disagree with it.
The reasons
All
Thanks everyone for attending (and apologies for my bad audio from multiple
devices it seems). Thanks also to Paul Hofman for taking minutes.
I merged my notes and added some Chairs Actions (still being discussed),
and uploaded them:
https://datatracker.ietf.org/meeting/115/materials/minute
On Nov 11, 2022, at 9:48 AM, Wessels, Duane
wrote:
>
> I find the latest alt-tld draft to be inconsistent when it first
> says “[alt names] should not be looked up in a DNS context” and
> "DNS stub and recursive resolvers do not need to look them up in
> the DNS context” but then later "Caching
Hello.
It's not a major thing in your design, but I see a risk that DNSKEYs at
non-apex might have trouble validating, so at some point I'd expect your
proposal to choose a different approach (e.g. allocate a new identical
RR type) or at least confirm that it won't be a major problem.
--Vlad
Mark Andrews wrote on 2022-11-11 02:26:
...
4. Caching DNS Servers: Caching servers MUST [or SHOULD] NOT
attempt to resolve .alt names in the global DNS root. They
MAY respond to queries for such names with NXDOMAIN [or
REFUSED?].
Caching servers MUST NOT
