[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bmwg] RFC2544 26.5 System Recovery
IMO, it's 1), sender timestamp.
There's no receiver timestamp for a lost packet,
and no mention of a computed arrival time here.
others?
Al
At 11:30 AM 8/21/2009, Dave Fenstermacher wrote:
Content-class:
urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01CA2274.4B356605"
Hello,
Does the system recovery time include the latency time thru the device
under test? I am looking for clarification on the definition of Timestamp
B: 1) is this the sender timestamp inside the last packet that was lost,
or 2) is the time in which the packet was lost, i.e. expected to arrive
at the receiver (which means the receiver hardware timestamp)? If it is
1), then the system recovery time does not include the latency of the
DUT. If it is 2), then it does include the latency of the DUT. Also,
since the packet was lost, is this really the packet following the last
one that was lost?
Thank you,
Dave Fenstermacher
_______________________________________________
bmwg mailing list
bmwg at ietf.org
https://www.ietf.org/mailman/listinfo/bmwg