[{"author": "J\u00e1nos Farkas", "text": "<p>Welcome to this DetNet session! Please join note taking: <a href=\"https://notes.ietf.org/notes-ietf-117-detnet?both\">https://notes.ietf.org/notes-ietf-117-detnet?both</a></p>", "time": "2023-07-26T20:01:48Z"}, {"author": "Antoine Fressancourt", "text": "<p>If we want to compare queueing mechanisms based on evaluation, either we need to have access to reference implementations for all the mechanisms or we need to have a common dataset (topology, set of flows) so we have the same ground for comparison</p>", "time": "2023-07-26T20:11:42Z"}, {"author": "J\u00e1nos Farkas", "text": "<p>Agree, many thanks to David!</p>", "time": "2023-07-26T20:14:11Z"}, {"author": "Antoine Fressancourt", "text": "<p>I agree the in depth presentations are really valuable</p>", "time": "2023-07-26T20:14:33Z"}, {"author": "David Black", "text": "<p>Also see the Detnet use case RFC - RFC 8578.  Some of those use cases need and/or benefit from the scalability extensions.</p>", "time": "2023-07-26T20:25:31Z"}, {"author": "J\u00e1nos Farkas", "text": "<p>Please note not jsut CQF but P802.1Qdv \u2013 Enhancements to CQF: <a href=\"https://1.ieee802.org/tsn/802-1qdv/\">https://1.ieee802.org/tsn/802-1qdv/</a></p>", "time": "2023-07-26T20:32:42Z"}, {"author": "J\u00e1nos Farkas", "text": "<p><a href=\"https://mailarchive.ietf.org/arch/msg/detnet/I0-73PaTi-aj9nX0UZ9bnoxys7A/\">https://mailarchive.ietf.org/arch/msg/detnet/I0-73PaTi-aj9nX0UZ9bnoxys7A/</a></p>", "time": "2023-07-26T20:33:06Z"}, {"author": "Yizhou Li", "text": "<p>Janos, thanks for pointing this out. The revision was made before the first text version of Qdv was available. Will try to add something in next revision. A quick comment to it is, current Qdv assumes point-to-point physical link between two nodes in order to maintain the cycle integrity. DetNet potentially allows more complex network structures and consequently holds some different assumptions. There can be subnetwork (TSN, MPLS TE, OTN) to provide underlying fwd and such a subnetwork can be but not necessarily must be a single point-to-point link.</p>", "time": "2023-07-26T20:44:28Z"}, {"author": "J\u00e1nos Farkas", "text": "<p>Cut-Through Forwarding is an ongoing project: P802.1DU <a href=\"https://1.ieee802.org/tsn/802-1du/\">https://1.ieee802.org/tsn/802-1du/</a>, not part of IEEE std 802.1Qbv-2015  Enhancements for Scheduled Traffic, aka TAS</p>", "time": "2023-07-26T20:54:25Z"}, {"author": "David Black", "text": "<p>P4 @ working meetings - Send Draft!</p>", "time": "2023-07-26T20:57:22Z"}, {"author": "J\u00e1nos Farkas", "text": "<p>An idea behind P802.1DC is to make TSN QoS mechanisms easily accessible to non-bridge devices, e.g., routers, see more at: <a href=\"https://1.ieee802.org/tsn/802-1dc/\">https://1.ieee802.org/tsn/802-1dc/</a>, e.g., the scope: IEEE Std 802.1Q specifies Quality of Service (QoS) features for bridges. These features are perfectly applicable to other devices, e.g. end stations, routers, or firewall appliances. In IEEE Std 802.1Q, the specifications of these features are scattered, and coupled tightly to the operation of a bridge. There is a need for simple reference points to these QoS specifications that are usable for non-bridge systems, and for managed objects for these features that are not specific to bridges.</p>", "time": "2023-07-26T21:30:34Z"}, {"author": "Antoine Fressancourt", "text": "<p>is it just me, or Toerless's voice is becoming robotic ?</p>", "time": "2023-07-26T21:32:40Z"}, {"author": "J\u00e1nos Farkas", "text": "<p>his voice is fine for me</p>", "time": "2023-07-26T21:32:58Z"}, {"author": "David Black", "text": "<p>Getting good audio fidelity remotely here - you might check MeetEcho's audio in rate.</p>", "time": "2023-07-26T21:33:41Z"}, {"author": "Antoine Fressancourt", "text": "<p>now getting better, must have been a QoS artefact on my side</p>", "time": "2023-07-26T21:33:43Z"}, {"author": "J\u00e1nos Farkas", "text": "<p>I wonder the interest in work from OT players like Siemens, Rockwell, etc.?</p>", "time": "2023-07-26T21:48:36Z"}, {"author": "Antoine Fressancourt", "text": "<p>I have no religion, and MPLS can make a good job in OT use cases</p>", "time": "2023-07-26T21:58:20Z"}, {"author": "Antoine Fressancourt", "text": "<p>or could, I have no proof at the end of the day</p>", "time": "2023-07-26T21:58:40Z"}, {"author": "Antoine Fressancourt", "text": "<p>In OT networking, I think resilience of the connections is necessary to have</p>", "time": "2023-07-26T22:00:20Z"}, {"author": "Antoine Fressancourt", "text": "<p>on top of deterministic aspects</p>", "time": "2023-07-26T22:00:36Z"}]