Re: I-D ACTION:draft-van-beijnum-shim6-reach-detect-00.txt

[Brian E Carpenter <brc@zurich.ibm.com>]

> 1. The base timing unit for this mechanism is named ShimKeepT.
>    Until a negotiation mechanism to negotiate different values for
>    ShimKeepT becomes available, a value of 10 seconds MUST be
>    used.

Having just seen claims that IPv6 will increase battery lifetime because
it avoids NAT keepalives, this "until" bothers me a bit.

Is it essential that the two ends agree on the value of ShimKeepT?

Couldn't we devise an algorithm for progressively increasing it, or for
tuning it according to the rate of data packets? Presumably a session that
generates one packet every five minutes would not be damaged by a much
larger ShimKeepT.

> When a host suspects that there is a failure for a context, it gathers
> the set of possible source addresses and the set of possible destination
> addresses.

"Suspect" can't form part of an algorithm. Can you define what this means
algorithmically? Does it mean "When full reachability exploration is started"?

   Brian