Re: [spring] PEDF / PIFO / ... (was: Re: [Detnet] new draft on segment routing approach to TSN)

2021-03-08 Thread Yaakov Stein
Toerless I describe PEDF in the ID. It is a twist on the combination of strict priority and EDF. Basically there can be multiple time sensitive flows with different priorities and non-sensitive traffic as well. With PEDF one first looks at the TS structure with the highest priority, however, on

Re: [spring] [Srcomp] New drafts from SRCOMP design team

2021-03-08 Thread Rishabh Parekh
Ron, SRv6 Replication SID does not need to follow IPv6 multicast address format since it is an IPv6 unicast address like any other SRv6 SID. -Rishabh On Tue, Mar 2, 2021 at 9:09 AM Ron Bonica wrote: > Rishabh, > > > > Is Section 2 of the SR replication segment draft compliant with Section > 2.7

[spring] PEDF / PIFO / ... (was: Re: [Detnet] new draft on segment routing approach to TSN)

2021-03-08 Thread Toerless Eckert
> Yaakov wrote: > I've heard of PIFO (Push In First out) but not PIPO. Is this a typo or > something new? > I agree that there are mechanisms that are optimized for hardware, but I have > come up with a very nice hardware implementation for PEDF and prefer to find > hardware implementations for

Re: [spring] new draft on segment routing approach to TSN

2021-03-08 Thread Liubingyang (Bryan)
Some advantages. If you use budget instead of deadline, you don't need accurate time sync. If you use budget, the time budget encoded in packet require fewer bits than using absolute time. The tightness is related to whether and how many flows can be admitted. It is related to network resource

Re: [spring] new draft on segment routing approach to TSN

2021-03-08 Thread Yaakov Stein
Bryan The local deadlines are specified in absolute time - not deltas. So there is no need to add the time saved - it is already there! As I previously replied, the accuracy of the time sync depends on the tightness of the budget. It has nothing to do with the encoding. Y(J)S From: Liubingyang

Re: [spring] new draft on segment routing approach to TSN

2021-03-08 Thread Liubingyang (Bryan)
Hi Yaakov, Great work. One suggestion. If we divide the end-to-end delay budget to per-hop budgets, and carry them in SR header, we can mimic using the end-to-end absolute deadline. One thing we need to do is, when the actual time used in a hop is less than the budget of this hop, you can add t

Re: [spring] WG Last Call draft-ietf-spring-nsh-sr

2021-03-08 Thread Huzhibo
Hi, I have read the draft and support the publication. Thanks, Zhibo From: spring [mailto:spring-boun...@ietf.org] On Behalf Of bruno.decra...@orange.com Sent: Friday, March 5, 2021 1:45 AM To: spring@ietf.org Cc: draft-ietf-spring-nsh...@ietf.org Subject: Re: [spring] WG Last Call draft-ietf-s

Re: [spring] new draft on segment routing approach to TSN

2021-03-08 Thread Yaakov Stein
Bala'zs, The IEEE definition of TSN mentions determinism, but defines it not as constant delay as in a TDM service, but rather as to provide deterministic services through IEEE 802 networks, i.e., guaranteed packet transport with bounded latency, low packet delay variation, and low packet loss.

Re: [spring] new draft on segment routing approach to TSN

2021-03-08 Thread Balázs Varga A
Hi Yaakov, Thanks for the clarifications, that helps a lot to position correctly your draft. As You have wrote: "Determinism is not the main goal of this draft" what was not clear from the text. I may be somewhat mis-leaded by the name You have used for the concept. TSN is widely used in IEEE as

Re: [spring] WG Last Call draft-ietf-spring-nsh-sr

2021-03-08 Thread Zhuangshunwan
Hi, I have read the draft and support the publication. Thanks, Shunwan From: spring [mailto:spring-boun...@ietf.org] On Behalf Of bruno.decra...@orange.com Sent: Wednesday, February 10, 2021 2:31 AM To: spring@ietf.org Cc: draft-ietf-spring-nsh...@ietf.org Subject: [spring] WG Last Call draft