Re: Fwd: New Version Notification for draft-wouters-edns-tcp-chain-query-01.txt (fwd)

Paul Wouters <[email protected]> wrote:
>
> But when you are hammering all imaginary zone cuts, and you really
> needed .ca, that seems overly aggressive to me.

Even though in the majority of cases you'll only make a couple of
redundant queries?

I thought we weren't trying to save bandwidth :-)

> > > > I think the Last Known Query Name needs to be the First Unknown Query
> > > > Name.
> > >
> > > I was avoiding that because the client does not know what it doesn't
> > > know. There might not be zone cuts on every dot. Which is why I opted
> > > for it to convey that it did know.
> >
> > If the client is querying for www.example.com and it knows com, and it
> > knows it doesn't know example.com, it should put example.com in the
> > option. It doesn't matter if that is a zone cut or not.
>
> What if it does know example.com, just not www.example.com. It puts in
> www.example.com?

Right, since www.example.com might be a zone cut. And if it knows
www.example.com there is no need for the option.

> And what is "knowing" with regard to RRtype?

Not my choice of word! And we're concerned with the ability to validate
any RRset at a name, which is independent of the RRtype.

> It might not "know" something because it does not exist.

It will either know nothing since it has nothing in the cache or know it
has a negative cache entry or know it has a cached proof of insecurity.

Tony.
-- 
f.anthony.n.finch  <[email protected]>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.
_______________________________________________
dnsext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsext