Re: [dnsext] bitmap inference was Re: ... - NXDOMAIN for emptynon-terminals

[Edward Lewis <[e-mail]>]

At 19:14 +0100 3/29/11, George Barwood wrote:

>The standard ( http://tools.ietf.org/html/rfc4034#section-4.1.2 ) says
>    The Type Bit Maps field identifies the RRset types that exist at the
>    NSEC RR's owner name.

It doesn't say "MUST".  That's giving the semantic meaning of the 
field.  And it doesn't say "when" existence is tested.

>That's clear and unambiguous, I cannot see how you can read that any 
>other way.
>But I'm going to stop here and see if others have views on this.

The problem is determining a if there is a protocol violation.

If you get this:

t=0 (Q:fqdn.tld./IN/AAAA):
fqdn.tld.   3600 IN NSEC other.tld. priv_type
t=5 (Q:fqdn.tld./IN/A):
fqdn.tld.   3600 IN A 127.0.0.1

How can you tell if I generated the NSEC regardless of the A record 
or just before the A record was added to the zone?  In the latter 
case, if you asked for the A you don't get the would-be-new NSEC.


-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at [phone]

Me to infant son: "Waah! Waah! Is that all you can say?  Waah?"
Son: "Waah!"