[Dime] [dime] #32: Sequence-Number Time-Stamp values within OC-OLR

["dime issue tracker" <[e-mail]>]

#32: Sequence-Number Time-Stamp values within OC-OLR

 The -01 draft says in clause 4.4:
    From the functionality point of view, the OC-Sequence-Number AVP MUST
    be used as a non-volatile increasing counter between two overload
    control endpoints (neglecting the fact that the contents of the AVP
    is a 64-bit NTP timestamp [RFC5905]).  The sequence number is only
    required to be unique between two overload control endpoints.
    Sequence numbers are treated in uni-directional manner, i.e. two
    sequence numbers on each direction between two endpoints are not
    related or correlated.

    When generating sequence numbers, the new sequence number MUST be
    greater than any sequence number previously seen between two
    endpoints within a time window that tolerates the wraparound of the
    NTP timestamp (i.e. approximately 68 years).


 With this mechanism it is difficult to get back to sync once you are out
 of sync (for whatever reason).
 It is proposed to mandate that the Sequence Number is a real 64-bit NTP
 timestamp (RFC5905) indicating the point in time when the OLR was created,
 and to mandate that  OLRs with a time stamp higher than time of reception
 must be ignored by the reacting node.

-- 
--------------------------------------+--------------------------
 Reporter:  [e-mail]  |      Owner:  Ulrich Wiehe
     Type:  defect                    |     Status:  new
 Priority:  major                     |  Milestone:
Component:  draft-docdt-dime-ovli     |    Version:
 Severity:  Active WG Document        |   Keywords:
--------------------------------------+--------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/32>
dime <http://tools.ietf.org/wg/dime/>