Return-Path: X-Original-To: detnet@mail2.ietf.org Delivered-To: detnet@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E450DC668854 for ; Sun, 8 Mar 2026 01:14:46 -0800 (PST) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=blanche-org.20230601.gappssmtp.com Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9DhrNAFCNSL for ; Sun, 8 Mar 2026 01:14:44 -0800 (PST) Received: from mail-oo1-xc36.google.com (mail-oo1-xc36.google.com [IPv6:2607:f8b0:4864:20::c36]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id DA8B0C66884D for ; Sun, 8 Mar 2026 01:14:44 -0800 (PST) Received: by mail-oo1-xc36.google.com with SMTP id 006d021491bc7-67bb19ac35aso89170eaf.1 for ; Sun, 08 Mar 2026 01:14:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1772961284; cv=none; d=google.com; s=arc-20240605; b=fcmpgqHVoeMf+92vha//7sy9RtJ3UJ0rEJdm6KmmNPhPPPBl7e877uojoOXgUVDMKE smMyrE2hXCHFzaiJzZ90DdrhLHmqT1cBjwd2L6MId0WsLi6K8+zrpW8oa2B3yxVr95bA bjNyGTsMkWhwZg2A+dKgTe6f1tzLgqlkFA/caVFzz2VUOFeIldnEluS4tNhW3Jmdwj9J eT4/KmWFmQbxOW5eGOVI37krOx0GRdR5vHX3mFUO0MH/9khry2MDBn0+87ISWsHwQuHf xM2TRXXBWL2POWSGiOqGzU6KmV8C1VjaLGBy5kDk/EbrimCnkN7dVaJr0lIfmCHw5Ghw kj/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=7zgBAUP5csBmAo4CKo8gWDfk73Wo4cU8sqKi7hPFTHM=; fh=Cg/N1bCzopSVi21KZmUK4GGMuQZViEE6KEmIiQCJSmg=; b=Crbx5FOqcuCPHXLGABzr6X53SDmlPK0cYd/cixwuimtSIw4re9LPmWnfJjyCeR7WSN 84HFjyUET1mI/2Lzow98v9ASIG7bbUlzedwUZEp8wHmHYqJJYHhU6GlhlMfQ68jf62wJ 6ql/5hbr9/1rxYHha0jS5VqMapR37pdqmCJUphl7uf8Hr0o+7aq35ji9x/eWzbGdE0GV kFHXYL5RAYlDvQh6JENhhr7ZoCSoEiy5UbB6EIzj9O9s7/BGoiQimCKlAL7iktTqFeTO GvDD30QvmW29+OTPpxYw7mWjYxVfLrczAjZ5CMW0FqFM2jFSsaDbmCXiL+Ur6oXEoWoB u0vw==; darn=ietf.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=blanche-org.20230601.gappssmtp.com; s=20230601; t=1772961284; x=1773566084; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7zgBAUP5csBmAo4CKo8gWDfk73Wo4cU8sqKi7hPFTHM=; b=BPqcyDVdvbHZSCJ8DpORxiT5ba0LNsVQ+zb4xGZSyJuMJjtx+U9tVzizrHbRH5SDky 7fo8nOQsbFq08Iqs6n6MDCg24iOIBrEnss40D29OJ+tHJ3OVr/bxIts+zXycIU4C7ATV Jwgc89qcbZKCWKSuclorqmy7eVCn1Cj06xirVdwzsMAVdhIDa5KCAkZeKghbVlLro1Qg yqDpwLy5icsO3InCCLVyRD4d4KoSnhpKA7biMOEBfK1a78ZhKBKoWY4TkzzUjKapHnq2 LSdvf2CB/L82QyKkkn2wzWfKLK3+quDAN0kt6c/nKsh3RPbox25jXuqn/HQ7UdsAp1yf pqMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772961284; x=1773566084; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=7zgBAUP5csBmAo4CKo8gWDfk73Wo4cU8sqKi7hPFTHM=; b=dd1nVi6gm87b8CF9WmZAEUeoqkogSES0TRmJt+Fxf9Jh6gYXJGZFqHvCTsAaElMYDw R02T6sErL9iURSyyHUBtStJZHlRH89gxNYmj8UZ+y9F9x/QKWi+crAwyV0AtZtBTbS2j hicIMiOS6h74vPk5/N5wgepp7hqr3iInQqFp1MfoqHYpuIqz6FzZMQuKn7GtCdydwGan UoUhYf+/AzFEQ12RcLPQfvmUNXse3ymI+mr++GRFyRD/W0PZP0f8peKY46ryeAHIWb5s 6TfWde18AUsipiu+fj3Mu6Cw3rdqrDq6Qhg4l8me/Tu+MIUQXhZeiZwejc4UUHRa2xfV lU2g== X-Forwarded-Encrypted: i=1; AJvYcCUH0MKTWe4EYboBR/pP0b6AlhAADHbfNBI8XL/i4yICHXoKj39MBKOpY4881sp+7DgFiHQG+4Y=@ietf.org X-Gm-Message-State: AOJu0YwHdNnHJn+1j3ZyqTZfbdFrzwvx4fxK4qWwZKh5WfTzN7nsHY11 dks68NtBBxexPNOT/M8wMfLqoTSBueeS6tPSkwFCHRWJv7lY6uFyegVvuvr8nDm3TQwaws++CaE kG8dOuUkeNLgNOlvrUnHz1n2f2g4tARklbf5f2n78qw== X-Gm-Gg: ATEYQzwrhMM9Y9/p1YlKm/70KIWX+/9YVrkpEH8Fm6GX612roESUH5nU3oF/SjlnjfT SxcicvUy51xkz99Fw10JfQhq/WW+1MbpPKtqEsvQWNV2g74LdNVOyu6pnQxlRMI/kZlGTIGIIKg b7FsaXn9UCk2god3pnS9flUjdHH6WaHnkjqwVueUClVARszQCYc1/efcV+8cxkIgvlmKBS19oYb FRmprzX3w7X1mOd5SDGpzJLsApgoQdbV3EtyouIr4x8loR741JCjaufBz6Q7k7m88ViPvc9Qrky zSsJgCFg09XUEfXBehXaO9pSWB7m8unKM1k= X-Received: by 2002:a05:6820:2017:b0:679:efb4:a3a7 with SMTP id 006d021491bc7-67b9bd1618bmr5214521eaf.43.1772961283808; Sun, 08 Mar 2026 01:14:43 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Mike Blanche Date: Sun, 8 Mar 2026 09:14:07 +0000 X-Gm-Features: AaiRm51PIyVTiOwPaMcvu0eGrFTtVBxNaM8e3OUnCM3wu1QI_hLtwmQW4fnUGVs Message-ID: To: Jinoo Joung Content-Type: multipart/alternative; boundary="00000000000085ae2b064c7fb73f" Message-ID-Hash: KITRVNBIZHBEHTRGKAM5AJYA7BFRSKDT X-Message-ID-Hash: KITRVNBIZHBEHTRGKAM5AJYA7BFRSKDT X-MailFrom: mike@blanche.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-detnet.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Janos Farkas , "detnet@ietf.org" , DetNet Chairs , Scott Mansfield X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BDetnet=5D_Re=3A_WG_adoption_poll=3A_joung-detnet-stateless-fair?= =?utf-8?q?-queuing-05?= List-Id: Discussions on Deterministic Networking BoF and Proposed WG Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --00000000000085ae2b064c7fb73f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Jinoo and authors, Thanks for the reply - comments inline: On Wed, 4 Mar 2026 at 02:06, Jinoo Joung wrote: > Hello Mike, for your careful consideration and comments. > > We will try our best to align this work with ITU-T standards. > Please see our answers in-line marked JJ. > > Best regards, > Jinoo (on behalf of authors) > > On Tue, Mar 3, 2026 at 9:00=E2=80=AFPM Mike Blanche wrote: > >> >> Hi Jinoo, authors, and the WG, >> >> Thank you Jinoo and the authors for updating this draft. >> >> I think the "meat" of what is new in the proposal is in 6.3.2.1 (IPv6 >> header format) and 6.3.2.2 (MPLS label format), and possibly 6.3.3, the >> admission procedure. >> > JJ: Right, and Section 7 (Approximate C-SCORE) too. > >> >> Most of the other content appears to summarize or restate what is in >> ITU-T Y.3129 and Y.3148, albeit with discrepancies. >> >> For example Section 4 appears to be a condensed version of section 6 of >> ITU-T Y.3129, although it still appears to include specifications alread= y >> defined in Y.3129, e.g. >> section 4 of this I-D: "Instead of deriving a new FT at each core node, >> we will specify a method of deriving the FT at downstream nodes by using >> the initial FT calculated at the entrance node." >> section 6 of Y.3129: "This Recommendation presents requirements and a >> framework for generation and update of FT..." >> > > JJ: To provide necessary context for the reader, this draft retains the > core principles of Y.3129. > Mike: I think it is fine to briefly restate the broad principles of the already standardised approach as an introduction, but the majority of the text in this I-D repeats or summarizes Y.3129, rather than referring to it. > Section 6.1 has five requirements but Y.3129 has nine. >> > > JJ: Right. But the context of the requirements remains identical. For > example, the first two requirements in Y.3129 states: > > R1: The entrance node of a flow is required to manage the flow state. > R2: The entrance node is required to determine initial FTs for packets > according to the flow state. > > These requirements are summarized as Requirement 1 below in the draft. > > Requirement 1: In the entrance node, it is REQUIRED to obtain the FTs wit= h > the following > equation. 0 denotes the entrance node of the flow under observation. > F0(p) =3D max{F0(p-1), A0(p)}+L(p)/r. > > Overall, the texts in Y.3129 are high-level, while those in the draft are > specific. > If you think the texts for the requirements should be identical, I will > gladly change them. > Mike: it is better to refer to Y.3129 than to copy it word for word. What happens if Y.3129 is updated or corrected? > The equations in section 6.2 include clock discrepancy adjustment which >> appears absent from the equivalent equations in section 8.2 of Y.3129. >> > > JJ: We will add the equation in the future version. > However, this version has been refined for brevity, retaining only the > critical elements necessary. > Mike: do you mean that Y.3129 will be updated to include the clock discrepancy adjustment? Or that this draft will be changed to match Y.3129? This I-D should be consistent with the already published standards. > The metadata proposal appears to conflict with the ITU Recommendations. >> The I-D suggests two pieces of metadata to be carried, Fh(p) and L/r. >> However Y.3129 and Y.3148 refers to three pieces of metadata, Fh(p), L a= nd >> r. >> > > JJ: What is required to fulfill the requirements and framework is the > metadata L/r. Making two (L and r) to one (L/r) can be seen as an > improvement. > However, if necessary we will specify both cases in the draft. > Mike: The ITU-T metadata standard specifies three pieces of metadata. This is the published standard. Having the I-D use (possibly) two pieces of metadata conflicts with the standard. If the approach in Y.3129 and Y.3148 is now considered inefficient, then these standards should be updated. (Although, I don't know where that leaves someone who has implemented a standards-compliant implementation of either of those Recommendations). > Section 6.3.4 is almost word-for-word identical to Y.3129 section 8.4, >> with the difference being the I-D suggests writing two pieces of metadat= a >> whereas Y.3129 suggests three. >> >> Section 6.3.5 similarly to Y.3129 section 8.5. >> >> Section 6.3.6 similarly to Y.3129 section 8.6. >> > > JJ: Right. These are the critical elements and the summarized texts. > Mike: They are word for word identical (apart from the discrepancies regarding the number of pieces of metadata carried). Why are we not referring to the existing standard? My overall issue is... imagine I'm trying to build a standards-compliant implementation. I am reading two ITU standards, and one IETF standard, but they differ, or are described differently. Which do I follow? Two ITU standards already explain the overall approach. The new work in this I-D should specify the IPv6 and MPLS formatting for the metadata defined in Y.3129 and Y.3148. Thanks, Mike > >> If I have misunderstood any of the above please let me know, it's >> entirely possible. >> >> We must ensure the work aligns with existing standards. If we refer to >> those standards we should not seek to recreate them in our drafts for ri= sk >> of introducing confusion. >> >> The abstract and introduction should also be updated to reflect what is >> "new" in this proposal. >> > > JJ: OK. We will update them as suggested. > > >> >> Thank you all for your continued efforts here. >> >> Mike >> >> >> >> >> On Fri, 27 Feb 2026 at 14:28, Janos Farkas > 40ericsson.com@dmarc.ietf.org> wrote: >> >>> Hi Jinoo, Authors, >>> >>> >>> >>> Thank you for the updates! >>> >>> >>> >>> Prior to publication as a WG document, we ask that you add a section >>> that describes the relationship of this work to the ITU-T work. >>> >>> >>> >>> Thank you, >>> >>> Lou and Janos >>> >>> >>> >>> >>> >>> *From:* Jinoo Joung >>> *Sent:* Friday, February 20, 2026 12:11 PM >>> *To:* Janos Farkas >>> *Cc:* Scott Mansfield = ; >>> detnet@ietf.org >>> *Subject:* Re: [Detnet] Re: WG adoption poll: >>> joung-detnet-stateless-fair-queuing-05 >>> >>> >>> >>> Hello Chairs, Scott, and WG, >>> >>> >>> >>> Please note that draft-joung-detnet-stateless-fair-queuing is revised >>> and uploaded as 07. >>> >>> In line with Scott's suggestions, the new version includes: >>> >>> 1) Abbreviations >>> >>> 2) New references including RFC8200, MPLS-related IETF drafts, and two >>> ITU-T Recommendations. >>> >>> 3) Minimized 6.1. Framework and other content that are duplicative with >>> ITU-T Recommendations. Only those that are essential to understand the >>> whole picture are left. >>> >>> 4) Elaborated 6.3.1 Metadata; 6.3.2. Header format; 6.3.3. Admission >>> control; 7. Approximate C-SCORE >>> >>> >>> >>> In 6.3.1 and 6.3.2, the methods for carrying metadata with IPv6 and MPL= S >>> MNA Sub-stack are described in detail. >>> >>> 6.3.3 delineates two distinct admission control methodologies, providin= g >>> for the selection of either procedure based on specific implementation >>> requirements. >>> >>> Section 7. Approximate C-SCORE specifies the nodal architecture and >>> algorithms to approximate C-SCORE with rotating strict priority schedul= ers. >>> >>> The E2E latency bound, in a complete math expression, is also given. >>> >>> This approximation serves to alleviate the sorting bottleneck intrinsic >>> to C-SCORE, >>> >>> bypassing the intensive priority queue operations while maintaining >>> near-optimal alignment with theoretical Finish Time objectives. >>> >>> >>> >>> Best regards, >>> >>> Jinoo (on behalf of authors) >>> >>> >>> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> >>> >>> >>> Internet-Draft draft-joung-detnet-stateless-fair-queuing-07.txt is now >>> available. It is a work item of the Deterministic Networking (DETNET) W= G >>> of >>> the IETF. >>> >>> Title: Latency Guarantee with Stateless Fair Queuing >>> Authors: Jinoo Joung >>> Jeong-dong Ryoo >>> Taesik Cheung >>> Yizhou Li >>> Peng Liu >>> Name: draft-joung-detnet-stateless-fair-queuing-07.txt >>> Pages: 23 >>> Dates: 2026-02-20 >>> >>> Abstract: >>> >>> This document specifies the framework and the operational procedure >>> for deterministic networking with a set of rate based work conservin= g >>> packet schedulers. The framework guarantees end-to-end (E2E) latenc= y >>> bounds to flows. The schedulers in core nodes do not need to >>> maintain flow states. Instead, the entrance node of a flow marks an >>> ideal service completion time according to a fluid model, called >>> Finish Time (FT), of a packet in the packet header. The subsequent >>> core nodes update the FT by adding the delay factor, which is a >>> function of the flow and the nodes. The packets in the queue of the >>> scheduler are served in the ascending order of FT. This mechanism i= s >>> called the stateless fair queuing. The result is that flows are >>> isolated from each other almost perfectly. The latency bound of a >>> flow depends only on the flow's intrinsic parameters such as the >>> maximum burst size and the service rate, except the link capacities >>> and the maximum packet length among other flows sharing each output >>> link with the flow. Furthermore, this document specifies an >>> approximation of stateless fair queuing implemented via a strict >>> priority (SP) scheduler. This approach maintains a guaranteed end- >>> to-end (E2E) latency bound. >>> >>> The IETF datatracker status page for this Internet-Draft is: >>> >>> https://datatracker.ietf.org/doc/draft-joung-detnet-stateless-fair-queu= ing/ >>> >>> There is also an HTMLized version available at: >>> >>> https://datatracker.ietf.org/doc/html/draft-joung-detnet-stateless-fair= -queuing-07 >>> >>> A diff from the previous version is available at: >>> >>> https://author-tools.ietf.org/iddiff?url2=3Ddraft-joung-detnet-stateles= s-fair-queuing-07 >>> >>> Internet-Drafts are also available by rsync at: >>> rsync.ietf.org::internet-drafts >>> >>> >>> >>> >>> >>> On Fri, Jan 23, 2026 at 10:52=E2=80=AFPM Janos Farkas >>> wrote: >>> >>> Hi, >>> >>> >>> >>> Scott, >>> >>> Thank you very mush for your guidelines! Much appreciated. >>> >>> >>> >>> Jinoo, >>> >>> Great to see agreement. >>> >>> Could you please revise the draft along the guidelines provided? Once >>> updated per the discussion below, we can publish it as a WG document. >>> >>> >>> >>> Thank you, >>> >>> Lou and Janos >>> >>> >>> >>> *From:* Jinoo Joung >>> *Sent:* Tuesday, January 20, 2026 4:23 PM >>> *To:* Scott Mansfield >>> *Cc:* detnet@ietf.org >>> *Subject:* [Detnet] Re: WG adoption poll: >>> joung-detnet-stateless-fair-queuing-05 >>> >>> >>> >>> Hello Scott, >>> >>> Thanks for your valuable suggestions. >>> I deeply appreciate your efforts to resolve this issue in a fair and >>> reasonable manner. >>> I agree with your proposed action. >>> >>> I have answered your guidelines in-line marked with JJ. Please take a >>> look. >>> >>> In short, there is a clear gap between the ITU-T work and the IETF >>> document. >>> While ITU-T work focuses on the requirements and framework, the IETF >>> document will elaborate on IP/MPLS specific information for deployment, >>> including header fields and formats, protocols for admission control an= d >>> time-difference compensation. >>> It will also include implementation details for approximating fair >>> queuing with a strict priority scheduler. >>> >>> Many thanks and best regards, >>> Jinoo >>> >>> >>> >>> On Tue, Jan 20, 2026 at 6:11=E2=80=AFAM Scott Mansfield >> 40ericsson.com@dmarc.ietf.org> wrote: >>> >>> Hi, >>> >>> >>> >>> Speaking as a liaison manager between the IETF and ITU-T, it is >>> important to note a few guidelines. Following this discussion, I obser= ve >>> there is concern that there is work being duplicated. In order to make= all >>> parties comfortable I would suggest the following: >>> >>> >>> >>> Potential Action: >>> >>> The process of =E2=80=9Cgap analysis=E2=80=9D is used a lot in the ITU-= T to ensure new >>> work items do not duplicate work already done by the industry recognize= d >>> center of competence. The reverse is true as well. I would want to se= e >>> the gap that the IETF is filling here and how it augments or modifies w= hat >>> the ITU-T has already done. If there are modifications to the ITU-T wo= rk >>> needed, I would like to see the authors plans to progress that work in = the >>> ITU-T. >>> >>> >>> >>> JJ: There is a clear gap, as I stated in the main text of this mail. Th= e >>> IETF draft will augment the ITU-T work. There is no need to modify the >>> ITU-T work. It serves as a solid foundation for the IETF draft. In my >>> opinion, the implementation specific issues in the IETF draft are not >>> appropriate for standardization in ITU-T. >>> >>> >>> >>> Guidelines To Note: >>> - It is appropriate for the IETF to take ITU-T work and augment it as >>> long as the augmentation is in the scope and mandate of IETF. Also, th= e >>> work should not fundamentally change (or be backwards incompatible). I= t is >>> imperative that the IETF document be clear what ITU-T work it is using = and >>> properly reference the work. >>> >>> >>> >>> JJ: I believe the IP/MPLS issues, protocols, and implementation >>> specifications are well within the scope of IETF. While the work procee= ds >>> in IETF, no changes will be introduced. The ITU-T works will be referen= ced >>> as well. >>> >>> >>> >>> - If there is anything being added in the IETF that requires a >>> fundamental change to the ITU-T work, that work needs to be >>> liaised/coordinated with the ITU-T. If what the IETF is doing is >>> explaining how to use the ITU-T work in the context of IETF (profiles e= tc.) >>> that is ok. >>> >>> >>> >>> JJ: Again, the ITU-T work won't be changed. The IETF draft will explain >>> how to use the fundamentals described in the ITU-T work. >>> >>> >>> >>> - If the IETF work is really changing the math, that should be >>> coordinated too. If the ITU-T work missed something, or is not appropr= iate >>> for the IETF use-case, again, coordination is needed. Since (at least) >>> some of the authors are the same in both groups, this is the best way t= o >>> gain consensus by ensuring the process of each group is followed. >>> >>> >>> >>> JJ: I definitely agree with you. >>> >>> >>> >>> I find coordination and cooperation is best handled when people work >>> together and have people that attend each organization and follow the >>> processes of the organization when progressing the documents. Liaison = can >>> be used, but they tend to be slow. The IETF DetNet mailing list is the >>> proper place to have this discussion especially if there are participan= ts >>> in this working group that need clarity to ensure work is not duplicate= d. >>> >>> >>> >>> Many thanks, >>> >>> -scott. >>> >>> >>> >>> >>> >>> >>> >>> [Detnet] Re: WG adoption poll: joung-detnet-stateless-fair-queuing-05 >>> >>> Jinoo Joung Fri, 02 January 2026 22:16 UTCShow heade= r >>> >>> >>> Hello Mike, it's great to hear from you. >>> >>> Thanks for the valuable feedback. >>> >>> It seems that your major concern is the discrepancy between the >>> standards. >>> >>> >>> >>> But I assure you that there is no conflict. >>> >>> Because ITU-T did not allow math equations in the Requirements section, >>> >>> I had to divide one equation into two or three sentences. >>> >>> That is why it seems the number of requirements are different. >>> >>> If you find any discrepancies, just let me know. >>> >>> >>> >>> Y.3148 also deals with considerations for metadata, but it still is at = an >>> >>> academic level. >>> >>> These two ITU-T standards are strictly based on the paper: >>> >>> https://ieeexplore.ieee.org/document/10261190 >>> >>> >>> >>> Best regards, >>> >>> Jinoo >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On Sat, Jan 3, 2026 at 4:09=E2=80=AFAM Mike Blanche >>> wrote: >>> >>> >>> >>> > >>> >>> > Hi Jinoo and all, >>> >>> > >>> >>> > Although the C-SCORE approach may be an appropriate solution within t= he >>> >>> > agreed taxonomy, I am still concerned about duplicating work already >>> done >>> >>> > elsewhere. >>> >>> > >>> >>> > What happens if the IETF draft diverges from the ITU Recommendation? >>> >>> > Y.3129 makes 9 "requirements", whereas the current draft has 5 >>> requirements >>> >>> > and 3 conditions. There is already one discrepancy between the two >>> >>> > documents in the description of the maths. This may lead to >>> inconsistent or >>> >>> > incompatible implementations depending on which document implementers >>> >>> > follow. >>> >>> > >>> >>> > I see the new draft (-06) focuses more on the necessary metadata. >>> This is >>> >>> > also already documented in ITU-T Y.3148, which covers metadata >>> creation and >>> >>> > updating procedures in depth. Again, how will it be ensured that this >>> draft >>> >>> > does not diverge from or conflict with the existing ITU Recommendatio= n? >>> >>> > >>> >>> > The latest draft still does not cite either ITU Recommendation Y.3129 >>> or >>> >>> > Y.3148. >>> >>> > >>> >>> > Thanks, >>> >>> > >>> >>> > Mike >>> >>> > >>> >>> > On Tue, 23 Dec 2025 at 00:08, Jinoo Joung wrote: >>> >>> > >>> >>> >> >>> >>> >> Hello Mike, thanks for the comment regarding the work in ITU-T. >>> >>> >> I understand your concern. >>> >>> >> >>> >>> >> Hello WG and Mike, >>> >>> >> >>> >>> >> The C-SCORE draft, as indicated in the version 6, will have the >>> following >>> >>> >> details in the future, once accepted as the WG draft. >>> >>> >> 1) MPLS and IP specific protocol details: This includes the header >>> >>> >> fields/formats, interactions between nodes and between control/data >>> planes. >>> >>> >> 2) Implementation issues regarding the priority queue, which is >>> currently >>> >>> >> required to sort the packets in FT orders: This includes an >>> approximation >>> >>> >> technique based on strict priority schedulers. >>> >>> >> >>> >>> >> Y.3129 is focused on the requirements and provides theoretical >>> >>> >> justifications but the C-SCORE draft targets on the solution. >>> >>> >> Some framework texts are covered in both. But they are necessary >>> >>> >> information for readers in order to understand the design principles >>> of the >>> >>> >> solution in the C-SCORE draft. >>> >>> >> >>> >>> >> C-SCORE is not a new invention. >>> >>> >> It is an outcome of the numerous researches conducted during late '9= 0 >>> ~ >>> >>> >> early '00s, which was the peak period of Internet research. >>> >>> >> There are more than hundreds of papers that are related to the fair >>> >>> >> queuing, after all. >>> >>> >> >>> >>> >> I believe it is worth being standardized by such virtues: >>> >>> >> 1) flow isolation capability, which protects from other flows' >>> >>> >> join/leave, bursts, or even malicious behaviours >>> >>> >> 2) scalability due to its stateless nature >>> >>> >> 3) flexibility from network asymmetry such as link capacity variatio= ns >>> >>> >> and uneven propagation delays >>> >>> >> 4) simple admission criteria, which allows incremental flow >>> acceptance, >>> >>> >> without modifying existing network setup >>> >>> >> 5) small average delay due to work conserving nature, >>> >>> >> just to mention a few. :-) >>> >>> >> >>> >>> >> Best regards, >>> >>> >> Jinoo (on behalf of authors) >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> On Fri, Dec 12, 2025 at 12:10=E2=80=AFAM Mike Blanche >>> >>> >> wrote: >>> >>> >> >>> >>> >>> >>> >>> >>> Hi all, >>> >>> >>> >>> >>> >>> This proposal appears very similar to ITU-T Recommendation Y.3129, >>> which >>> >>> >>> I believe was developed by some of the same authors. >>> >>> >>> >>> >>> >>> https://www.itu.int/rec/T-REC-Y.3129-202404-I/en >>> >>> >>> >>> >>> >>> The abstract text of the I-D is virtually identical to the summary = of >>> >>> >>> Y.3129. In addition, significant parts of the content are very >>> similar - >>> >>> >>> e.g. parts of section 6.3 of the draft are word-for-word the same a= s >>> parts >>> >>> >>> of section 8 of the ITU-T Recommendation. >>> >>> >>> >>> >>> >>> The ITU-T Recommendation is missing from the draft's References >>> section. >>> >>> >>> >>> >>> >>> I am unclear why we are considering duplicating work that appears t= o >>> be >>> >>> >>> already completed at the ITU. >>> >>> >>> >>> >>> >>> Best regards, >>> >>> >>> >>> >>> >>> Mike >>> >>> >>> >>> >>> >>> On Fri, 5 Dec 2025 at 15:49, Janos Farkas >> >>> >>> 40ericsson.com@dmarc.ietf.org> wrote: >>> >>> >>> >>> >>> >>>> Hi, >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> This email begins a 4-week adoption poll for: >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> https://datatracker.ietf.org/doc/draft-joung-detnet-stateless-fair-queu= ing/05/ >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> No IPR has been disclosed for this document. >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> Please voice your support or technical objections to adoption on t= he >>> >>> >>>> >>> >>> >>>> list by the end of the day (any time zone) January 2nd. >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> As a reminder this document is part of the larger set of adoption >>> calls >>> >>> >>>> >>> >>> >>>> of the documents discussed at IETF 124: >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> https://datatracker.ietf.org/doc/draft-joung-detnet-stateless-fair-queu= ing/05 >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> https://datatracker.ietf.org/doc/draft-peng-detnet-deadline-based-forwa= rding/18 >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> https://datatracker.ietf.org/doc/draft-peng-detnet-packet-timeslot-mech= anism/13 >>> >>> >>>> >>> >>> >>>> https://datatracker.ietf.org/doc/draft-eckert-detnet-tcqf/09 >>> >>> >>>> >>> >>> >>>> https://datatracker.ietf.org/doc/draft-eckert-detnet-glbf/06 >>> >>> >>>> >>> >>> >>>> >>> https://datatracker.ietf.org/doc/draft-ryoo-detnet-ontime-forwarding/04 >>> >>> >>>> >>> >>> >>>> https://datatracker.ietf.org/doc/draft-ryoo-detnet-nscore/02 >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> Thank you, >>> >>> >>>> >>> >>> >>>> J=C3=A1nos (as Co-chair) >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> _______________________________________________ >>> >>> >>>> detnet mailing list -- detnet@ietf.org >>> >>> >>>> To unsubscribe send an email to detnet-leave@ietf.org >>> >>> >>>> >>> >>> >>> _______________________________________________ >>> >>> >>> detnet mailing list -- detnet@ietf.org >>> >>> >>> To unsubscribe send an email to detnet-leave@ietf.org >>> >>> >>> >>> >>> >> >>> >>> - [Detnet] WG adoption poll: joung-detnet-stateless=E2=80=A6 >>> Janos >>> Farkas >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> Mike >>> Blanche >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> >>> song.xueyan2 >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> Jinoo >>> Joung >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> Yizhou >>> Li >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> >>> =EC=9C=A0=EC=97=B0=EC=B2=A0 >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> Jeong-dong >>> Ryoo >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> >>> xiong.quan >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> >>> =EC=A0=95=ED=83=9C=EC=8B=9D >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> Mike >>> Blanche >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> Jinoo >>> Joung >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> >>> liupengyjy@chinamobile.com >>> - [Detnet] Re: WG adoption poll: joung-detnet-state=E2=80=A6 >>> Xuesong >>> Geng >>> >>> >>> >>> _______________________________________________ >>> detnet mailing list -- detnet@ietf.org >>> To unsubscribe send an email to detnet-leave@ietf.org >>> >>> _______________________________________________ >>> detnet mailing list -- detnet@ietf.org >>> To unsubscribe send an email to detnet-leave@ietf.org >>> >> --00000000000085ae2b064c7fb73f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi J= inoo and authors,

Thanks for the reply - comments = inline:

On Wed, 4 Mar 2026 at 02:06, Jinoo Joung <jjoung@smu.ac.kr> wrote:
Hello Mike, for your careful consideration and comments.
We will try our best to align this work with ITU-T standards.= =C2=A0
Please see our answers in-line marked JJ.

Best regards,
Jinoo (on behalf of authors)
On Tue, = Mar 3, 2026 at 9:00=E2=80=AFPM Mike Blanche <mike-ietf@blanche.org> wrote:
=
Hi Jinoo, authors, and the WG,

Than= k you Jinoo and the authors for updating this draft.

I think the "meat" of what is new in the proposal is in 6.3.2.= 1 (IPv6 header format) and 6.3.2.2 (MPLS label format), and possibly 6.3.3,= the admission procedure.
=C2=A0JJ: Right, and= Section 7 (Approximate C-SCORE) too.

Most of the other co= ntent appears to summarize or restate what is in ITU-T Y.3129 and Y.3148, a= lbeit with discrepancies.

For example Section 4 ap= pears to be a condensed version of section 6 of ITU-T Y.3129, although it s= till appears to include specifications already defined in Y.3129, e.g.
section 4 of this I-D: "Instead of deriving a new FT at each cor= e node, we will specify a method of deriving the FT at downstream nodes by = using the initial FT calculated at the entrance node."
secti= on 6 of Y.3129: "This Recommendation presents requirements and a frame= work for generation and update of FT..."
=
JJ: To provide necessary context for the reader, this draft = retains the core principles of Y.3129.
<= br>
Mike: I think it is fine to briefly restate the broad princip= les of the already standardised approach as an introduction, but the majori= ty of the text in this I-D repeats or summarizes Y.3129, rather than referr= ing to it.
=C2=A0
Section 6.1 has five requi= rements but Y.3129 has nine.

JJ= : Right. But the context of the requirements remains identical. For example= , the first two requirements in Y.3129 states:=C2=A0

R1: The entrance node of a flow is required to manage t= he flow state.
R2: The entrance node is required to determine initial FT= s for packets according to the flow state.

These req= uirements are summarized as Requirement 1 below in the draft.
Requirement 1: In the entrance node, it is REQUIRED to obtain the FT= s with the following
equation. 0 denotes the entrance node of the flow u= nder observation.
F0(p) =3D max{F0(p-1), A0(p)}+L(p)/r.=C2=A0
=

Overall, the texts in Y.3129 are high-level, while thos= e in the draft are specific.=C2=A0
If you think the texts for the= requirements should be identical, I will gladly change them.

Mike: it is better to refer to Y.3129 = than to copy it word for word. What happens if Y.3129 is updated or correct= ed?
=C2=A0
The equations in section 6.2 incl= ude clock discrepancy adjustment which appears absent from the equivalent e= quations in section 8.2 of Y.3129.

<= div>JJ: We will add the equation in the future version.=C2=A0
How= ever, this version has been refined for brevity, retaining only the critica= l elements necessary.

Mik= e: do you mean that Y.3129 will be updated to include the clock discrepancy= adjustment? Or that this draft will be changed to match Y.3129? This I-D s= hould be consistent with the already published standards.
=C2=A0<= /div>
<= div dir=3D"ltr">
The metadata proposal appears to conflict with the ITU= Recommendations. The I-D suggests two pieces of metadata to be carried,=C2= =A0Fh(p) and L/r. However Y.3129 and Y.3148 refers to three pieces of metad= ata, Fh(p), L and r.

JJ: What i= s required to fulfill the requirements and framework is the metadata L/r. M= aking two (L and r) to one (L/r) can be seen as an improvement.=C2=A0
=
However, if necessary we will specify both cases in the draft.=C2=A0

Mike: The ITU-T metadata s= tandard specifies three pieces of metadata. This is the published standard.= Having the I-D use (possibly) two pieces of metadata conflicts with the st= andard. If the approach in Y.3129 and Y.3148 is now considered inefficient,= then these standards should be updated. (Although, I don't know where = that leaves someone who has implemented a standards-compliant implementatio= n of either of those Recommendations).
=C2=A0
Section 6.3.4 is almost word-for-word identical to Y.3129 section 8.4,= with the difference being the I-D suggests writing two pieces of metadata = whereas Y.3129 suggests three.

Section 6.3.5 simil= arly to Y.3129 section 8.5.

Section 6.3.6 similarly to = Y.3129 section 8.6.

JJ: Right. = These are the critical elements and the summarized texts.=C2=A0 =C2=A0

Mike: They are word for word = identical (apart from the discrepancies regarding the number of pieces of m= etadata carried). Why are we not referring to the existing standard?
<= div>


My overall issue is... ima= gine I'm trying to build a standards-compliant implementation. I am rea= ding two ITU standards, and one IETF standard, but they differ, or are desc= ribed differently. Which do I follow?=C2=A0

Two IT= U standards already explain the overall approach. The new work in this I-D = should specify the IPv6 and MPLS formatting for the metadata defined in Y.3= 129 and Y.3148.

Thanks,

M= ike


=C2=A0
<= br>
If I have misunderstood any of the above please let me know, = it's entirely possible.

We must ensure the wor= k aligns with existing standards. If we refer to those standards we should = not seek to recreate them in our drafts for risk of introducing confusion.<= /div>

The abstract and introduction should also be updat= ed to reflect what is "new" in this proposal.

JJ: OK. We will update them as suggested.
=C2=A0

Thank you all for your continued efforts here.

Mike




On Fri, 27 Feb 2026 at 14:28, Janos Farkas <Janos.Farkas=3D40ericsson.com@dma= rc.ietf.org> wrote:

Hi Jinoo, Authors,

=C2=A0

Thank you for the updates!

=C2=A0

Prior to publication as a WG document, we ask that you add a sect= ion that describes the relationship of this work to the ITU-T work.<= u>

=C2=A0

Thank you,

Lou and Janos

=C2=A0

=C2=A0

From: Jinoo Joung <jjoung@smu.ac.kr>
Sent: Friday, February 20, 2026 12:11 PM
To: Janos Farkas <Janos.Farkas@ericsson.com>
Cc: Scott Mansfield <scott.mansfield=3D40ericsson.com@dmarc.ietf.org&= gt;; detnet@ietf.org
Subject: Re: [Detnet] Re: WG adoption poll: joung-detnet-stateless-f= air-queuing-05

=C2=A0

Hello Chairs, Scott, and WG,

=C2=A0

Please note that=C2=A0draft-joung-detnet-stateless-f= air-queuing is revised and uploaded as 07.

In line with Scott's suggestions, the new versio= n includes:

1) Abbreviations

2) New references including RFC8200, MPLS-related IE= TF drafts, and two ITU-T Recommendations.

3) Minimized 6.1. Framework and other content that a= re duplicative with ITU-T Recommendations. Only those that are essential=C2= =A0to understand the whole picture=C2=A0are left.

4) Elaborated 6.3.1 Metadata; 6.3.2. Header format; = 6.3.3. Admission control; 7. Approximate C-SCORE

=C2=A0

In 6.3.1 and 6.3.2, the methods for carrying metadat= a with IPv6 and MPLS MNA Sub-stack are described in detail.

6.3.3 delineates two distinct admission control meth= odologies, providing for the selection of either procedure based on specifi= c implementation requirements.

Section 7. Approximate C-SCORE specifies the nodal a= rchitecture and algorithms to approximate C-SCORE with rotating strict prio= rity schedulers.

The E2E latency bound, in a complete math expression= , is also given.

This approximation serves to alleviate the sorting b= ottleneck intrinsic to C-SCORE,=C2=A0

bypassing the intensive priority queue operations wh= ile maintaining near-optimal alignment with theoretical Finish Time objecti= ves.

=C2=A0

Best regards,

Jinoo (on behalf of authors)

=C2=A0

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=C2=A0

Internet-Draft draft-joung-detnet-stateless-fair-que= uing-07.txt is now
available. It is a work item of the Deterministic Networking (DETNET) WG of=
the IETF.

=C2=A0 =C2=A0Title:=C2=A0 =C2=A0Latency Guarantee with Stateless Fair Queui= ng
=C2=A0 =C2=A0Authors: Jinoo Joung
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Jeong-dong Ryoo
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Taesik Cheung
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Yizhou Li
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Peng Liu
=C2=A0 =C2=A0Name:=C2=A0 =C2=A0 draft-joung-detnet-stateless-fair-queuing-0= 7.txt
=C2=A0 =C2=A0Pages:=C2=A0 =C2=A023
=C2=A0 =C2=A0Dates:=C2=A0 =C2=A02026-02-20

Abstract:

=C2=A0 =C2=A0This document specifies the framework and the operational proc= edure
=C2=A0 =C2=A0for deterministic networking with a set of rate based work con= serving
=C2=A0 =C2=A0packet schedulers.=C2=A0 The framework guarantees end-to-end (= E2E) latency
=C2=A0 =C2=A0bounds to flows.=C2=A0 The schedulers in core nodes do not nee= d to
=C2=A0 =C2=A0maintain flow states.=C2=A0 Instead, the entrance node of a fl= ow marks an
=C2=A0 =C2=A0ideal service completion time according to a fluid model, call= ed
=C2=A0 =C2=A0Finish Time (FT), of a packet in the packet header.=C2=A0 The = subsequent
=C2=A0 =C2=A0core nodes update the FT by adding the delay factor, which is = a
=C2=A0 =C2=A0function of the flow and the nodes.=C2=A0 The packets in the q= ueue of the
=C2=A0 =C2=A0scheduler are served in the ascending order of FT.=C2=A0 This = mechanism is
=C2=A0 =C2=A0called the stateless fair queuing.=C2=A0 The result is that fl= ows are
=C2=A0 =C2=A0isolated from each other almost perfectly.=C2=A0 The latency b= ound of a
=C2=A0 =C2=A0flow depends only on the flow's intrinsic parameters such = as the
=C2=A0 =C2=A0maximum burst size and the service rate, except the link capac= ities
=C2=A0 =C2=A0and the maximum packet length among other flows sharing each o= utput
=C2=A0 =C2=A0link with the flow.=C2=A0 Furthermore, this document specifies= an
=C2=A0 =C2=A0approximation of stateless fair queuing implemented via a stri= ct
=C2=A0 =C2=A0priority (SP) scheduler.=C2=A0 This approach maintains a guara= nteed end-
=C2=A0 =C2=A0to-end (E2E) latency bound.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-joung= -detnet-stateless-fair-queuing/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html= /draft-joung-detnet-stateless-fair-queuing-07

A diff from the previous version is available at:
https://author-tools.ietf.org/i= ddiff?url2=3Ddraft-joung-detnet-stateless-fair-queuing-07

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

=C2=A0

=C2=A0

On Fri, Jan 23, 2026 at 10:52=E2=80=AFPM Janos Farkas <Janos.Farkas@ericsson.com= > wrote:

Hi,

=C2=A0

Scott,

Thank you very mush for your guidelines! Much appreciated.=

=C2=A0

Jinoo,

Great to see agreement.

Could you please revise the draft along the guidelines provided? = Once updated per the discussion below, we can publish it as a WG document.

=C2=A0

Thank you,

Lou and Janos

=C2=A0

From: Jinoo Joung <jjoung@smu.ac.kr>
Sent: Tuesday, January 20, 2026 4:23 PM
To: Scott Mansfield <scott.mansfield=3D40ericsson.com@dmarc.ietf.org&= gt;
Cc: detnet@ietf= .org
Subject: [Detnet] Re: WG adoption poll: joung-detnet-stateless-fair-= queuing-05

=C2=A0

Hello Scott,

Thanks for your valuable suggestions.
I deeply appreciate your efforts to resolve this issue in a fair and reason= able manner.
I agree with your proposed action.

I have answered your guidelines in-line marked with JJ. Please take a look.=

In short, there is a clear gap between the ITU-T work and the IETF document= .
While ITU-T work focuses on the requirements and framework, the IETF docume= nt will elaborate on IP/MPLS specific information for deployment, including= header fields and formats, protocols for admission control and time-differ= ence compensation.
It will also include implementation details for approximating fair queuing = with a strict priority scheduler.

Many thanks and best regards,
Jinoo

=C2=A0

On Tue, Jan 20, 2026 at 6:11=E2=80=AFAM Scott Mansfield <scott.mansfield= =3D40eri= csson.com@dmarc.ietf.org> wrote:

Hi,<= /u>

=C2=A0<= u>

Speaking as a liaison= manager between the IETF and ITU-T, it is important to note a few guidelin= es.=C2=A0 Following this discussion, I observe there is concern that there is work being duplicated.=C2=A0 In order to make all pa= rties comfortable I would suggest the following:

=C2=A0<= u>

Potential Action:

The process of =E2=80= =9Cgap analysis=E2=80=9D is used a lot in the ITU-T to ensure new work item= s do not duplicate work already done by the industry recognized center of competence.=C2=A0 The reverse is true as well.=C2=A0 I would want to se= e the gap that the IETF is filling here and how it augments or modifies wha= t the ITU-T has already done.=C2=A0 If there are modifications to the ITU-T= work needed, I would like to see the authors plans to progress that work in the ITU-T.

=C2=A0

JJ: There is a clear gap, as I stated in the main te= xt of this mail. The IETF draft will augment the ITU-T work. There is no ne= ed to modify the ITU-T work. It serves as a solid foundation for the IETF draft. In my opinion, the implementation specific = issues in the IETF draft are not appropriate for standardization in ITU-T.<= u>

=C2=A0

Guidelines To Note: - It is appropriate for the IETF to take ITU-T work and augment it as long = as the augmentation is in the scope and mandate of IETF.=C2=A0 Also, the wo= rk should not fundamentally change (or be backwards incompatible).=C2=A0 It= is imperative that the IETF document be clear what ITU-T work it is using and properly reference the work.=

=C2=A0

JJ: I believe the IP/MPLS issues, protocols, and imp= lementation specifications are well within the scope of IETF. While the wor= k proceeds in IETF, no changes will be introduced. The ITU-T works will be referenced as well.

=C2=A0

- If there is anythin= g being added in the IETF that requires a fundamental change to the ITU-T w= ork, that work needs to be liaised/coordinated with the ITU-T.=C2=A0 If what the IETF is doing is explaining how to use the IT= U-T work in the context of IETF (profiles etc.) that is ok.

=C2=A0

JJ: Again, the ITU-T work won't be changed. The = IETF draft will explain how to use the fundamentals described in the ITU-T = work.

=C2=A0

- If the IETF work is= really changing the math, that should be coordinated too.=C2=A0 If the ITU= -T work missed something, or is not appropriate for the IETF use-case, again, coordination is needed.=C2=A0 Since (at least) some = of the authors are the same in both groups, this is the best way to gain co= nsensus by ensuring the process of each group is followed.=

=C2=A0

JJ: I definitely agree with you.

=C2=A0

I find coordination a= nd cooperation is best handled when people work together and have people th= at attend each organization and follow the processes of the organization when progressing the documents.=C2=A0 Liaison can be u= sed, but they tend to be slow.=C2=A0 The IETF DetNet mailing list is the pr= oper place to have this discussion especially if there are participants in = this working group that need clarity to ensure work is not duplicated.

=C2=A0<= u>

Many thanks,

-scott.=

=C2=A0<= u>

=C2=A0<= u>

=C2=A0<= u>

[Detnet] Re: WG adopt= ion poll: joung-detnet-stateless-fair-queuing-05

Jinoo Joung <jjoung@smu.ac.kr>= =C2=A0Fri, 02 January 2026 22:16 UTCShow header

Hello Mike, it's = great to hear from you.

Thanks for the valuab= le feedback.

It seems that your ma= jor concern is the discrepancy between the standards.<= /p>

=C2=A0<= u>

But I assure you that= there is no conflict.

Because ITU-T did not= allow math equations in the Requirements section,

I had to divide one e= quation into two or three sentences.

That is why it seems = the number of requirements are different.

If you find any discr= epancies, just let me know.

=C2=A0<= u>

Y.3148 also deals wit= h considerations for metadata, but it still is at an

academic level.

These two ITU-T stand= ards are strictly based on the paper:

https://ieeexplore.i= eee.org/document/10261190

=C2=A0<= u>

Best regards,<= u>

Jinoo

=C2=A0<= u>

=C2=A0<= u>

=C2=A0<= u>

=C2=A0<= u>

On Sat, Jan 3, 2026 a= t 4:09= =E2=80=AFAM Mike Blanche <mike-ietf@b= lanche.org> wrote:

=C2=A0<= u>

>=C2=A0<= /u>

> Hi Jinoo and all= ,

>=C2=A0<= /u>

> Although the C-S= CORE approach may be an appropriate solution within the

> agreed taxonomy,= I am still concerned about duplicating work already done<= /u>

> elsewhere.

>=C2=A0<= /u>

> What happens if = the IETF draft diverges from the ITU Recommendation?

> Y.3129 makes 9 &= quot;requirements", whereas the current draft has 5 requirements

> and 3 conditions= . There is already one discrepancy between the two

> documents in the= description of the maths. This may lead to inconsistent or

> incompatible imp= lementations depending on which document implementers<= /p>

> follow.

>=C2=A0<= /u>

> I see the new dr= aft=C2=A0 (-06) focuses more on the necessary metadata. This is

> also already doc= umented in ITU-T Y.3148, which covers metadata creation and

> updating procedu= res in depth. Again, how will it be ensured that this draft

> does not diverge= from or conflict with the existing ITU Recommendation?

>=C2=A0<= /u>

> The latest draft= still does not cite either ITU Recommendation Y.3129 or

> Y.3148.

>=C2=A0<= /u>

> Thanks,

>=C2=A0<= /u>

> Mike

>=C2=A0<= /u>

> On Tue, 23 Dec 2= 025 at 00:08, Jinoo Joung <jjoung@smu.ac.kr> wrote:

>=C2=A0<= /u>

>>=C2=A0=

>> Hello Mike, = thanks for the comment regarding the work in ITU-T.

>> I understand= your concern.

>>=C2=A0=

>> Hello WG and= Mike,

>>=C2=A0=

>> The C-SCORE = draft, as indicated in the version 6, will have the following=

>> details in t= he future, once accepted as the WG draft.

>> 1) MPLS and = IP specific protocol details: This includes the header=

>> fields/forma= ts, interactions between nodes and between control/data planes.

>> 2) Implement= ation issues regarding the priority queue, which is currently=

>> required to = sort the packets in FT orders: This includes an approximation=

>> technique ba= sed on strict priority schedulers.

>>=C2=A0=

>> Y.3129 is fo= cused on the requirements and provides theoretical

>> justificatio= ns but the C-SCORE draft targets on the solution.

>> Some framewo= rk texts are covered in both. But they are necessary

>> information = for readers in order to understand the design principles of the

>> solution in = the C-SCORE draft.

>>=C2=A0=

>> C-SCORE is n= ot a new invention.

>> It is an out= come of the numerous researches conducted during late '90 ~

>> early '0= 0s, which was the peak period of Internet research.

>> There are mo= re than hundreds of papers that are related to the fair

>> queuing, aft= er all.

>>=C2=A0=

>> I believe it= is worth being standardized by such virtues:

>> 1) flow isol= ation capability, which protects from other flows'=

>> join/leave, = bursts, or even malicious behaviours

>> 2) scalabili= ty due to its stateless nature

>> 3) flexibili= ty from network asymmetry such as link capacity variations=

>> and uneven p= ropagation delays

>> 4) simple ad= mission criteria, which allows incremental flow acceptance,

>> without modi= fying existing network setup

>> 5) small ave= rage delay due to work conserving nature,

>> just to ment= ion a few. :-)

>>=C2=A0=

>> Best regards= ,

>> Jinoo (on be= half of authors)

>>=C2=A0=

>>=C2=A0=

>>=C2=A0=

>> On Fri, Dec = 12, 2025 at 12:10=E2=80=AFAM Mike Blanche <mik= e-ietf@blanche.org>

>> wrote:

>>=C2=A0=

>>>=C2=A0

>>> Hi all,<= /span>

>>>=C2=A0

>>> This pro= posal appears very similar to ITU-T Recommendation Y.3129, which<= /u>

>>> I believ= e was developed by some of the same authors.

>>>=C2=A0

>>> https://www.itu.int/rec/T-REC-Y.3129-202404-I/en

>>>=C2=A0

>>> The abst= ract text of the I-D is virtually identical to the summary of=

>>> Y.3129. = In addition, significant parts of the content are very similar -<= /u>

>>> e.g. par= ts of section 6.3 of the draft are word-for-word the same as parts

>>> of secti= on 8 of the ITU-T Recommendation.

>>>=C2=A0

>>> The ITU-= T Recommendation is missing from the draft's References section.=

>>>=C2=A0

>>> I am unc= lear why we are considering duplicating work that appears to be

>>> already = completed at the ITU.

>>>=C2=A0

>>> Best reg= ards,

>>>=C2=A0

>>> Mike

>>>=C2=A0

>>> On Fri, = 5 Dec 2025 at 15:49, Janos Farkas <Janos.Farkas=3D<= /p>

>>> 40ericss= on.com@dmarc.ietf.org> wrote:

>>>=C2=A0

>>>> Hi,<= /span>

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>> This= email begins a 4-week adoption poll for:

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-joung-detnet-stateless-fair-queuing/= 05/

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>> No I= PR has been disclosed for this document.

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>> Plea= se voice your support or technical objections to adoption on the<= /u>

>>>>=C2= =A0

>>>> list= by the end of the day (any time zone) January 2nd.

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>> As a= reminder this document is part of the larger set of adoption calls<= u>

>>>>=C2= =A0

>>>> of t= he documents discussed at IETF 124:

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-joung-detnet-stateless-fair-queuing/= 05

>>>>=C2= =A0

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-peng-detnet-deadline-based-forwardin= g/18

>>>>=C2= =A0

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-peng-detnet-packet-timeslot-mechanis= m/13

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-eckert-detnet-tcqf/09<= /u>

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-eckert-detnet-glbf/06<= /u>

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-ryoo-detnet-ontime-forwarding/04=

>>>>=C2= =A0

>>>> https://datatracker.ietf.org/doc/draft-ryoo-detnet-nscore/02<= /u>

>>>>=C2= =A0

>>>>=C2= =A0

>>>>=C2= =A0

>>>> Than= k you,

>>>>=C2= =A0

>>>> J=C3= =A1nos (as Co-chair)

>>>>=C2= =A0

>>>>=C2= =A0

>>>> ____= ___________________________________________

>>>> detn= et mailing list -- detnet@ietf.org

>>>> To u= nsubscribe send an email to detnet-leave@iet= f.org

>>>>=C2= =A0

>>> ________= _______________________________________

>>> detnet m= ailing list -- detnet@ietf.org

>>> To unsub= scribe send an email to detnet-leave@iet= f.org

>>>=C2=A0

>>=C2=A0=

=C2=A0<= u>

_______________________________________________
detnet mailing list -- detnet@ietf.org
To unsubscribe send an email to detnet-leave@ietf.org

_______________________________________________
detnet mailing list -- detnet@ietf.org
To unsubscribe send an email to detnet-leave@ietf.org
--00000000000085ae2b064c7fb73f--