[Detnet] Re: IETF 122 Slot Requests

CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> Wed, 05 March 2025 06:10 UTC

Return-Path: <cjbc@it.uc3m.es>
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 89990790207 for <detnet@mail2.ietf.org>; Tue, 4 Mar 2025 22:10:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=it.uc3m.es
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 ngEsgTfD14vH for <detnet@mail2.ietf.org>; Tue, 4 Mar 2025 22:10:09 -0800 (PST)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 F26C27901CC for <detnet@ietf.org>; Tue, 4 Mar 2025 22:10:08 -0800 (PST)
Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-54954fa61c8so5220158e87.1 for <detnet@ietf.org>; Tue, 04 Mar 2025 22:10:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it.uc3m.es; s=google; t=1741155007; x=1741759807; 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=DNcwBoctKYmMLXxV9cAr9fmOgjQkV5024lFc07TUmxc=; b=p40RBSkqt9oATD7rSOExzbwIAU/EYl9gA8ZM3oB39/YYJDbXfSWvs0kXc5qI0ESow4 XpS5Uv9M5rKxyBbYT4G0jsBP9WF5soIynUOMM6Je1pWkm6yepu5veTor1r4k/Zd6yupz CXfOO//WF5ZPgHXGJJmkiLdAuiTBCtjii7AxvtMr8EBqdoAgMnjv8FTNtDJKxoPQGRMp Xi1Fm1FawJg2iE2WnOGgPZHydYBp/6FU67GtMLdwgy9CfMu4gA7kh6i/V9doOmzSVxV5 xnIyOhooaS51vvArV6GspRT/ENJVbav+8OBThN2cLxURXmDsg4Pm9KjSACJX6UZgcwzR ibpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741155007; x=1741759807; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DNcwBoctKYmMLXxV9cAr9fmOgjQkV5024lFc07TUmxc=; b=JYBb3/WbV5l7k1/l+5Oad7ENb1tpMLzp1JMtyjRYTFufCBWE5ysbtI+CKzMOLmnsCz EnAA1PxPf7zBqjbczwC90zR7yZwboX6xmBdIZch9tmrf/wnVGywPxc9wA1m9xkiTZKrU ZJ5YBq7bdBg+CnAbRvzAUB5OrwSjAJqyqQ6yRe3YO6OqazIy8DLvmYM9sYMb1Z2izoZl YhAKU6PEDr5PAQcuEt1Vr1Z4xMkLexe2m7OJILPRuX9nQTIv6wCeDxZXj9gyxzzV0qEc HxJPXHL9vmxNTtyKKMnTsTyPU+XsRlSu0sXQqcXAsQGkfRcBUS936bxQbQNTK15DPdQw Cjdw==
X-Forwarded-Encrypted: i=1; AJvYcCUao42idimjsGcGOFfhe9ya3HazsG/m/lqgdPfAU9pxdZs41L79gn2kI4wub7q4oyHrA8pFhF8=@ietf.org
X-Gm-Message-State: AOJu0Yz7ovl3z+56ddIEQO7U4SIbIw5RgQh3ZIrMWGc8MV/ZYbiSiAIx EhiAth0RI9wmHZbXswecmRqmY2NNsItUN1IeND8wXwa/uOA39VFKRiaQcwpmf10+7bLfPqUp0ny Cj3MfKCFfpCeZXz2+FgMHV48O/Cx01QNU3/7ULg==
X-Gm-Gg: ASbGncsIeeIjUVLbd2vdmbCwA2aBN2tTcG4/823vCCwCFrlvT1wL1xqghl6jG5B9J8z Dbc+Z3L2c2E35HOKAmPSqOoq0bjYQ7IoVOfPOPVYU1wdFvTAzZcr1vt/YcGXjd3+KgQlufyZY7N KGq2Lbv610wQb1nBoJQ9O4oboLgdpBw4pcnm6mgLlns/3yvfn9UhT0fkYs6Kmn
X-Google-Smtp-Source: AGHT+IFpmGZTllG+Fnl2+vqNMqIQhaUo0UF2gDrJAUaeQyHMD1/1BEjmV4+YM2UrPOwOgvYPkVY87vkd/zBCVa5XOdQ=
X-Received: by 2002:a05:6512:3190:b0:549:7c64:3bc0 with SMTP id 2adb3069b0e04-5497d35028emr472383e87.29.1741155005561; Tue, 04 Mar 2025 22:10:05 -0800 (PST)
MIME-Version: 1.0
References: <159373570027.29538.11387984048129033777@ietfa.amsl.com> <a245f635-8eab-4c81-8536-302d42aa1787@labn.net> <SJ0PR14MB4792E3B68FD54B9E7FB180E3C3F82@SJ0PR14MB4792.namprd14.prod.outlook.com> <CALypLp9bmy1HT+UYt7Pjc9F2rgiL3_OwCk6qDdHmMiyC+dNWyQ@mail.gmail.com> <PAWPR07MB10010C830D26401BC3B9400B6F2CC2@PAWPR07MB10010.eurprd07.prod.outlook.com> <CALypLp8+eegC0Ja-dAuB3zdU09CzEWOsqmXMWP5tG_DEOAY5tQ@mail.gmail.com> <SJ0PR14MB479253291DDF9D0AC1110526C3CE2@SJ0PR14MB4792.namprd14.prod.outlook.com>
In-Reply-To: <SJ0PR14MB479253291DDF9D0AC1110526C3CE2@SJ0PR14MB4792.namprd14.prod.outlook.com>
From: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Date: Wed, 05 Mar 2025 07:09:54 +0100
X-Gm-Features: AQ5f1Jr-cYmDJSX3o1v50lNNlSJj3uzFxfUKztDZQ8nbdXYV-T7im_Y717st5So
Message-ID: <CALypLp_ZthgMC=eDrfRrYVm=5KeKksJ4DnVHgBe4JcuUoCv_=A@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary="0000000000009b210b062f923dec"
Message-ID-Hash: GZEWY6PUGWUN6PAZ2TAPIZZWNPQ6RKOX
X-Message-ID-Hash: GZEWY6PUGWUN6PAZ2TAPIZZWNPQ6RKOX
X-MailFrom: cjbc@it.uc3m.es
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 <Janos.Farkas@ericsson.com>, DetNet WG <detnet@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Detnet] Re: IETF 122 Slot Requests
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/TE3aXwY9BQRCVDNK49IsD0txiZk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Owner: <mailto:detnet-owner@ietf.org>
List-Post: <mailto:detnet@ietf.org>
List-Subscribe: <mailto:detnet-join@ietf.org>
List-Unsubscribe: <mailto:detnet-leave@ietf.org>

Thanks Lou for the feedback.

I agree with your proposed way forward. I’ll start working on that
direction and present some ideas during the meeting. My idea would be to
start working on the definitions of a multi-domain detnet, and then start
working on the PCE-based detnet controller framework (there I don’t have
yet a clear idea on how to do it, one could be definitely the one you
propose).

Thanks,

Carlos

Sent from a mobile device, please excuse any brevity or typing errors.


On Sun, 2 Mar 2025 at 22:00, Lou Berger <lberger@labn.net> wrote:

> Carlos,
>
> As I read your document, it really builds on the controller plane
> framework by introducing the concept of multiple cooperating controller
> plane instances, where each instance is scoped by pce controllers that
> interoperate and use radio sub Network technologies.
>
> I personally see this is interesting work. This said, I think this work
> requires some foundation to build on. One of these foundations is certainly
> the definition of a multi-domain Detnet control. Another is a framework for
> q pce-based detnet controller. Whether this work is done in a single
> document or multiple isn't so important to me, but I do think foundational
> work/definitions need to be done before jumping all the way to multi-domain
> raw.
>
> If I were taking on this work, I probably would approach it by authoring a
> single document, perhaps titled something along the lines of "PCE-based
> DetNet controller plane framework". With that document fully defining the
> framework for single control domain -first generally and then with raw
> considerations. From there I would move on to multi domain, again first
> generally and then raw considerations.
>
> We can certainly gauge general interest in the topic at the coming
> meeting, but I don't think you need anyone's agreement to work the topic
> and contribute an individual draft on the whole topic.
>
> I do think the foundational topics need to be covered before the working
> group can focus on, i.e., adopt, work that is specific to pce control of a
> multi-domain raw network.
>
> Thank you for contributing the work and I look forward to the conversation
> on this topic.
>
> Lou
> ------------------------------
>
> On March 1, 2025 3:01:20 AM CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
> wrote:
>
>> Hi Janos,
>>
>> Thanks a lot. Regarding your comment, that I fully agree with, I already
>> added in the past content in that directions after you and Lou's feedback
>> in one meeting. While the name of the draft has not changed, it now
>> includes content for RAW-RAW and RAW-DetNet multi-domain. Next step would
>> be probably to have DetNet-DetNet as the main scenario and RAW-RAW,
>> RAW-DetNet documented in annexes. I also need to update terminology used,
>> according to the latest discussions. I'm not sure if I'll be able to do all
>> these changes in time for IETF 122, but definitely those are in my roadmap.
>>
>> To me, what matters the most is to see if there is consensus in the WG to
>> work in this type of problem. It'd be great if we can work on this topic.
>>
>> Thanks!
>>
>> Carlos
>>
>>
>> On Fri, Feb 28, 2025 at 6:03 PM Janos Farkas <Janos.Farkas@ericsson.com>
>> wrote:
>>
>>> Hi Carlos,
>>>
>>>
>>>
>>> Sure, we’ll put you on the agenda.
>>>
>>>
>>>
>>> Honestly, as I mentioned earlier related to multi-domain, I’d be happier
>>> to see draft-bernardos-detnet-multidomain.
>>>
>>>
>>>
>>> What I mean is that RAW is integral part of DetNet, which is nicely
>>> reflected in the RAW architecture draft.
>>>
>>> More in detail, it would be very good to have a generic DetNet
>>> multi-domain draft. Wireless aspects could be part of such generic DetNet
>>> draft, e.g., whether it is multi-domain because of multiple technology
>>> domains, e.g., wireless.
>>>
>>>
>>>
>>> I know, it is not much time before IETF 122, but, any rough draft on
>>> generic DetNet multi-domain would be appreciated as a kick-off.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Janos
>>>
>>>
>>>
>>> *From:* CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
>>> *Sent:* Wednesday, February 26, 2025 10:02 AM
>>> *To:* Lou Berger <lberger@labn.net>
>>> *Cc:* DetNet WG <detnet@ietf.org>; DetNet Chairs <detnet-chairs@ietf.org
>>> >
>>> *Subject:* Re: [Detnet] IETF 122 Slot Requests
>>>
>>>
>>>
>>> Dear Lou, Janos, WG.
>>>
>>>
>>>
>>> I'd like to request a slot to present an update
>>> of draft-bernardos-detnet-raw-multidomain that we are preparing. We'd like
>>> to get feedback from the WG, as we want to request a call for adoption
>>> during the meeting, if the chairs agree of course (this is in line with
>>> previous discussions in past meetings, but I prefer to check if you are
>>> fine with it).
>>>
>>>
>>>
>>> Thanks!
>>>
>>>
>>>
>>> Carlos
>>>
>>>
>>>
>>> On Sun, Feb 16, 2025 at 9:25 PM Lou Berger <lberger@labn.net> wrote:
>>>
>>> WG,
>>>
>>> The draft agenda for IETF122 has been posted -
>>> https://datatracker.ietf.org/meeting/122/agenda
>>>
>>> We are scheduled to meet:
>>> https://datatracker.ietf.org/meeting/122/agenda?filters=detnet
>>>
>>> Session: Monday, March 17, 2025 09:30 - 11:30 (Bangkok) Monday Session I
>>>
>>> Calendar: https://datatracker.ietf.org/meeting/122/sessions/detnet.ics
>>>
>>> This will be an in-person/hybrid meeting.  As usual, we will focus on
>>> updates, summarizing open issues, and new topics.
>>>
>>> Please send slot requests to detnet-chairs@ietf.org before the end of
>>> the day March 2nd (any TZ).  Please include draft names(s), datatracker
>>> URL, presenter, desired slot length.  Also, please let us know if you think
>>> the topic would be better covered in a Virtual Interim to be held at a
>>> future date.
>>>
>>> Thank you!
>>>
>>> Lou and Janos
>>>
>>> Important dates:
>>>    https://datatracker.ietf.org/meeting/122/important-dates/
>>>
>>> 2025-02-19 Wednesday Cut-off date for requests to reschedule Working
>>> Group or BOF meetings UTC 23:59.
>>>
>>> 2025-02-21 Friday Final agenda to be published.
>>>
>>> 2025-03-03 Monday Early registration and payment cut-off at UTC 23:59.
>>>
>>> 2025-03-03 Monday Internet-Draft submission cut-off (for all
>>> Internet-Drafts, including -00) by UTC 23:59. Upload using the I-D
>>> Submission Tool <https://datatracker.ietf.org/submit/>.
>>>
>>> 2025-03-05 Wednesday Draft Working Group agendas due by UTC 23:59.
>>>
>>> 2025-03-10 Monday Revised Working Group agendas due by UTC 23:59.
>>>
>>> 2025-03-10 Monday Registration cancellation cut-off at UTC 23:59.
>>>
>>>
>>>
>>> _______________________________________________
>>> detnet mailing list -- detnet@ietf.org
>>> To unsubscribe send an email to detnet-leave@ietf.org
>>>
>>>