Re: [L4s-discuss] Interop·Labs Low Latency Low Loss Scalable Throughput (L4S) February 26-March 1, 2024 - Registration open

[Greg White <[e-mail]>]

I think there is a good chance on GPS.  There are large windows with a clear view of the sky in the interop lab.  I will verify.

We primarily use pcaps, capturing traffic at both ends of the link in order to calculate and plot per-packet one way latency, ECN state changes, QP sanctioning events, packet drops precisely, so we've not needed clock synchronization, and this works for all application traffic types.   

-Greg



On 1/25/24, 2:39 PM, "rjmcmahon" <rjmcmahon=[e-mail] <mailto:[e-mail]>> wrote:


Any chance of having a GPS signal in the space? Or a PTP grandmaster and 
a low latency and low jitter switch for PTP multicast? This will allow 
for clock sync and enable iperf 2 one way delay (OWD) metrics which can 
provide insights as to what's going on.


Also, I'm now using rasperry pi 5's with GPS for iperf 2 development 
because they are inexpensive, have hardware PTP, have a realtime clock 
(RTC), have GPIO pulse per second, and outperform rpi 4's per a more 
than doubling of the core frequency. A challenge is that the rpi 5 
requires a later kernel and L4S code hasn't been ported to those 
versions yet. It would be good if L4S were available to this. Note: One 
can use an rpi 4b in the interim for L4S testing. 
https://www.l4sgear.com/ <https://www.l4sgear.com/>


Thanks,
Bob
> Hello!
> 
> CableLabs and Kyrio are hosting an Interop·Labs Low Latency Low Loss
> Scalable Throughput (L4S) Interoperability Event, beginning Monday,
> February 26, and ending Friday, March 1, 2024 at the CableLabs office
> in Louisville, Colorado.
> 
> The high-level objectives of the event are to enable application
> developers, operating system developers, transport protocol designers
> and network equipment manufacturers to perform interoperability and
> functional testing of their L4S implementations.
> 
> During the “Interop·Lab” event, if we can identify additional
> interoperability features that are supported by the participants, we
> will encourage and support further interoperability testing where
> applicable. It should be noted that complete feature development is
> not required in order to participate in the event; participants are
> encouraged to participate even with limited feature functionality and
> non-final solution platforms.
> 
> Participating organizations should plan to have at least one person
> attend on-site for the event. We plan to allow remote connection into
> the Interop Lab for additional persons to interact with their
> equipment. We will utilize a Slack channel to allow open discussion
> between the participants and support staff, as we work through the
> testing.
> 
> Test Process and Guidelines for Participation
> Click here for Interop·Labs Process & Guidelines [1]
> 
> All in-person participants and those desiring remote connectivity must
> register for the event:
> http://iplanprime.eventready.com/events/InteropL4SFeb2024 <http://iplanprime.eventready.com/events/InteropL4SFeb2024> [2]
> 
> Registration deadline: February 21, 2024
> 
> Any questions about registration: Renae Cox [e-mail] <mailto:[e-mail]>
> Any questions about event: Greg White [e-mail] <mailto:[e-mail]>
> 
> Thanks!
> 
> CableLabs/Kyrio team
> 
> 
> 
> Links:
> ------
> [1] 
> https://iplanprime.eventready.com/files/InteropL4SFeb2024/FEB%202024%20Guidelines%20Remote%20PHY%20Interop_.pdf <https://iplanprime.eventready.com/files/InteropL4SFeb2024/FEB%202024%20Guidelines%20Remote%20PHY%20Interop_.pdf>
> [2] http://iplanprime.eventready.com/events/InteropL4SFeb2024 <http://iplanprime.eventready.com/events/InteropL4SFeb2024>