At Thu, 24 Dec 2015 08:33:27 +0530,
Mukund Sivaraman <[email protected]> wrote:

> > I have a related clarification. What if the ADDRESS field has fewer
> > octets than than SOURCE PREFIX-LENGTH indicates? Should REFUSED or
> > FORMERR be returned in this case? The draft must clarify this if it's
> > requiring REFUSED.
>
> I also suggest describing implementation behavior with FAMILY=0 clearly
> in section 6 (option format). This is described all over the draft.

On re-reading the draft, I happen to have the same question that I've
not noticed in my previous phases of review.

> Example, section 7.2.1 (authoritative nameserver) says:
>
> >   The FAMILY, SOURCE PREFIX-LENGTH and ADDRESS in the response MUST
> >   match those in the query, unless the query specified only the SOURCE
> >   PREFIX-LENGTH for privacy (with FAMILY and ADDRESS set to 0).
>
> 1. It is not clear how SOURCE PREFIX-LENGTH makes sense by itself
> without knowing what FAMILY it is targetting. How can it be 0 with
> FAMILY=0?
>
> 2. I assume ADDRESS is missing here, not set to 0? Or are ADDRESS octets
> present to match SOURCE PREFIX-LENGTH and they are set to 0 bits?
> ADDRESS field should be undefined if FAMILY=0. It is better to clearly
> state all this under section 6 (option format).

+1 on these should be clarified.  It's also not clear what the
authoritative server should do if "only the SOURCE PREFIX-LENGTH"
should be specified (whatever it means).  The draft only suggests this
case is an exception by the word 'unless', but it's not clear to me
what the server should do instead in this case.

There's also at least one other phrase of 'ADDRESS set to 0':

   includes a non-zero ADDRESS, it MUST retry with FAMILY and ADDRESS
   set to 0.
(Section 7.1.3)

This should be also clarified as well as any other similar cases I
might be missing.

I also have one related question on Section 7.3:

   For a response to a query which specified only the
   SOURCE PREFIX-LENGTH for privacy masking, the FAMILY and ADDRESS
   fields should contain the appropriate non-zero information for
   caching.

On a re-read I just realized this sentence isn't clear enough to me.
Aside from what "specified only the SOURCE PREFIX-LENGTH" means,
precisely what does this mean? "the FAMILY and ADDRESS fields should
contain the appropriate non-zero information"

Does this mean the authoritative server should (somehow) have set the
FAMILY and ADDRESS to a non-zero value (see also about the other
question above on what the authoritative server should do)?  Or does
it mean the cached entry for such a response should be taken from the
source address of the very original query (i.e. the query that the
Intermediate Nameserver received)?  Or something else?

--
JINMEI, Tatuya

_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to