> Section 2 says a serial number is:
>       A 32-bit monotonically increasing ordinal which wraps
>       from 2^32-1 to 0.  
> Section 5.10, it says:
>       An implementation which uses a fine granularity of time for the
>       Serial Number might never change the Cache Nonce.
> Which is correct? The latter is not a monotonically increasing ordinal.

both are.  and this is a problem because?

the nonce is not specified to be increasing or decreasing.  it is a
nonce, not a counter.

> Section 4 says:
>    When the cache updates its database, it sends a Notify message to
>    every currently connected router.
> Section 6.2 says:
>    The cache server SHOULD send a notify PDU with its current serial
>    number when the cache's serial changes
> The first is mandatory, the second is advisory; they should match.

there is no MUST in the *overview* in sec 4.  notify is not mandatory.

> In section 5.3, there seems to be an implicit "MUST flush all data",
> like the explicit one in section 5.10. It should probably be explicit
> here as well or, if not, the document should say why a router might
> not flush when getting data after a reset.

from the currently published version -12

5.3.  Reset Query

   Reset Query: The router tells the cache that it wants to receive the
   total active, current, non-withdrawn, database.  The cache responds
   with a Cache Response PDU (Section 5.4).

i see nothing about flushing anything.  restart session, please.

> 
> Section 5.10 says:
>       If, at
>       any time, either the router or the cache finds the value of the
>       nonces they hold disagree, they MUST completely drop the session
>       and the router MUST flush all data learned from that cache.
> Why does the session need to be dropped?

because it is not the same session.  e.g. serials are not commensurate.

> This could cause delay when re-authenticating.

if the nonce was off i sure would want to re-auth

> Section 6.1 says:
>    To limit the length of time a cache must keep the data necessary to
>    generate incremental updates, a router MUST send either a Serial
>    Query or a Reset Query no less frequently than once an hour.  This
>    also acts as a keep alive at the application layer.
> 
>    As the cache MAY not keep updates for more than one hour, the router
>    MUST have a polling interval of no greater than half an hour
> Which MUST is correct? Half an hour or an hour?

good catch

> (And why are these MUST-level at all? This could be simply be an
> operational decision.)

they may be under different authorities and be different code bases.

> In section 2, "Non-authoritative Cache" is defined but is then only
> used once, in section 3. Also in section 2, the definition of "cache"
> is not in fact a definition. Maybe get rid of these two from section
> 2, and pull the term "local cache" from section 3 here.

i wonder why i was differentiating.  have removed.  thanks.

> The repeated use of "rcynic" is confusing given that rcynic will
> probably have features added in the future. None of them is really
> needed in order to describe how this protocol functions.

it is used twice, and couched in words indicating it is an example
   software such as rcynic
   for example via rcynic

> A non-trivial editorial issue: the draft uses "commensurate" in many
> places that does not match any of the definitions I can find in my
> dictionaries. I *think* that the draft means "the same", but that is
> not clear.

no.  it means drawn from the same number space.  i.e. if the nonce
differs, the cache and the router mean very different things by serial
value 42.

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

Reply via email to