Re: [Dime] Issue#32 status

Ulrich,

Would you agree to the following to replace the first two statements:

Sequence number is of type Unsigned64.

When generated, a new sequence number must be greater than the sequence
number contained in the active overload report to which it applies
(including over reboot of that node).  Note: this allows sequence
numbers to start at 1 for any occurrence of overload at a reporting
node.  This, I think, allows us to ignore wraparound issues as
wraparound will never happen.  Unless we are worried about a server
staying in overload for billions of years (assuming reports with a ten
minute validity period refreshed every five minutes).

The other two statements are good.

Steve

On 2/19/14 9:33 AM, Wiehe, Ulrich (NSN - DE/Munich) wrote:
> #32: Sequence-Number Time-Stamp values within OC-OLR
>  
> I understand that we agreed the following principles:
>  
> Sequence-Number is of type Time, however the value need not correspond
> to the point in time of generation.
>  
> When generated, a new sequence number must be  greater than any
> sequence number previously generated by the same node (including over
> a reboot of that node)
>  
> When received, a sequence number is used to detect
> outdates/replays/freshness.
>  
> Sequence numbers of expired OLRs MUST NOT be remembered by reacting nodes.
>  
>  
> I did not understand the requirement for globally uniqueness as
> introduced by Jouni.
> Can Jouni please explain.
>  
> Ulrich
>  
>  
>  
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime