Re: [Detnet] [spring] Comments on draft-saad-mpls-miad-usecases

Greg Mirsky <gregimirsky@gmail.com> Fri, 25 February 2022 17:54 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CE73A0F42; Fri, 25 Feb 2022 09:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bItqzZyYSl3R; Fri, 25 Feb 2022 09:54:41 -0800 (PST)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D8963A0EB7; Fri, 25 Feb 2022 09:54:41 -0800 (PST)
Received: by mail-ed1-x531.google.com with SMTP id q17so8478718edd.4; Fri, 25 Feb 2022 09:54:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jVZ2gvcuKw9lqZi51XxZIXyuNJ2tQ4C8+ODqucIq6WM=; b=kT4p9kteBkDUtoa7EmsROoDuKI6gRhRf9XKzQhVPmgDRFP7YHLfjtMHztFQBv5ugTl Eh8J+WwTSeVBNoNLWyj5nrI2eMjkdhcAWw41/wdUW4pk85PGcZBVJvuyq2I2sxFL4ErR 5J7ZHYTleAoJRg37MKwHA+F8QNWLClCB/bZnVuMjFof8CeKYHmKXSf7z36AT7FYnm92G FAluwv6sbbqrF+BrjAojpPoGFNQ7C7Wa+t2aHt2DN5UQ+/HKWIPcczXH5eGUp78iaV2b jv/JLlzr4Da3htkbmc56SwyMLQrr74AaNbauqkj8Dmpi3Ua2nW9AjWzGEozuiJL0uZRo JYqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jVZ2gvcuKw9lqZi51XxZIXyuNJ2tQ4C8+ODqucIq6WM=; b=erqrjhbicbQnjkeBu3yu0ClrZiGvYH+LRAtg1VdeHAiwmze2YCL5owpjq+Au4jhiYU SxIjPXgd3UxEiCVaD9EuRGxiXYmmIhV6ssPwMWkAAeb/OBoyCvPJI+0P4TQXMnvk7MRV zGMeC5mLz/R7qsMBGKipa4fNhEpxv2VTfPtQW9oTPZL6u7jrx2iRNhJUZuM3lQXlJ3Ed B159xKtPOm/KZxKXHUtyIpBim0dOOFzbnXl3PM3JOFiOGA1AZmBjlsPaJIiOJKSgsF4l yc2Dxg1W9j+TISqcnMKGgQUaSfq+1seNgbtgpkXRAzAuFxQX/ql9OZK9NS4S/+4xIGe2 mw4w==
X-Gm-Message-State: AOAM532sf78o6uqr5YQF9WgekLytrEpZmFq8txSBJRRsEhM9JwGOA4VS ot4ROCYFU1mmM4HHOr8R9jPFuYgLpn8eIFYrGm4=
X-Google-Smtp-Source: ABdhPJyywpPTx/gVeQK4PY6bePKrJZRi0a6qpw6+3/eFhnT4vM4HfbRnQRKY6JBYRJtFeLD7j5gc+aJX8hOKrbSWjnU=
X-Received: by 2002:a05:6402:51cb:b0:409:e99f:bc1c with SMTP id r11-20020a05640251cb00b00409e99fbc1cmr8321948edd.68.1645811679595; Fri, 25 Feb 2022 09:54:39 -0800 (PST)
MIME-Version: 1.0
References: <CA+RyBmX5=yagQ9FcNo1UKUzBavEa3L+c2mnbgVnqZvyszDOTSQ@mail.gmail.com> <DM5PR1901MB2150B2E45032A4DF5839AD14FC3D9@DM5PR1901MB2150.namprd19.prod.outlook.com> <CA+RyBmVUZnP--1C+W-Z3ewJc7q=Gm7DGGY2o5r2yTT6PgXWSXA@mail.gmail.com> <BY3PR13MB4787C8798BF17C923278B3009A3E9@BY3PR13MB4787.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB4787C8798BF17C923278B3009A3E9@BY3PR13MB4787.namprd13.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 25 Feb 2022 09:54:28 -0800
Message-ID: <CA+RyBmVwssUwe-BGbPvRENZjpVSy2XOg72kD1Bg208P_KuoXSQ@mail.gmail.com>
To: Haoyu Song <haoyu.song@futurewei.com>
Cc: Tarek Saad <tsaad.net@gmail.com>, mpls <mpls@ietf.org>, "pals@ietf.org" <pals@ietf.org>, DetNet WG <detnet@ietf.org>, spring <spring@ietf.org>, "draft-saad-mpls-miad-usecases@ietf.org" <draft-saad-mpls-miad-usecases@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000878f7205d8db6434"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/kkKecgSBxWiCxFWk0zbMfgGCXZk>
Subject: Re: [Detnet] [spring] Comments on draft-saad-mpls-miad-usecases
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2022 17:54:47 -0000

Hi Haoyu,
in RFC 8596 I don't find anything that would require any modification to
the existing MPLS architecture. I would agree that SFC NSH using MPLS to
connect SFP components might benefit from the new enhancements to the MPLS,
but so would any other client that uses the MPLS network. Do you think that
the use case document should list them all?

Regards,
Greg

On Fri, Feb 25, 2022 at 9:42 AM Haoyu Song <haoyu.song@futurewei.com> wrote:

>
>    - in my earlier comments, I've noted that the informational RFC 8596
>    appears not posing any requirements for enhancements in the MPLS data
>    plane. If I am missing something, please let me know.
>
> Hi Greg,
>
>
>
> The RFC is mentioned because it shows that SFC NSH has been considered to
> be supported in MPLS as well, so it’s a legitimate use case like the others
> in the draft. When we need to support multiple such use cases at the same
> time, we need a generic mechanism to support them, so the use-case draft
> serves as a motivation for our work in the ODT.
>
> Hopefully this answers your question. Thanks,
>
> Haoyu
>
>
>
> *From:* Greg Mirsky <gregimirsky@gmail.com>
> *Sent:* Thursday, February 24, 2022 5:09 PM
> *To:* Tarek Saad <tsaad.net@gmail.com>
> *Cc:* mpls <mpls@ietf.org>; pals@ietf.org; DetNet WG <detnet@ietf.org>;
> spring <spring@ietf.org>; draft-saad-mpls-miad-usecases@ietf.org
> *Subject:* Re: [spring] Comments on draft-saad-mpls-miad-usecases
>
>
>
> Hi Tarek,
>
> thank you for your thoughtful consideration of my comments. I've reviewed
> the diff and got several follow-up notes:
>
>    - the new text in the Introduction section explains the ISD as being
>    encoded as labels:
>
> within the label stack, e.g., encoded as labels, referred to as In
>
>                  Stack Data (ISD), and
>
> I think s/as labels/into label stack elements/ makes the text a bit more
> accurate. What do you think?
>
>
>    - in my earlier comments, I've noted that the informational RFC 8596
>    appears not posing any requirements for enhancements in the MPLS data
>    plane. If I am missing something, please let me know.
>    - I might have missed it earlier. The TSN is the term used for a very
>    specific technology developed at IEEE to support, for example, URLLC
>    services. The DetNet WG defines the methodology in support of these
>    services using IETF technologies - MPLS and IP. I think it would be
>    appropriate if an IETF document refers to Deterministic Networking, not
>    TSN. What is your opinion?
>
> Regards,
>
> Greg
>
>
>
>
>
> On Thu, Feb 24, 2022 at 5:52 AM Tarek Saad <tsaad.net@gmail.com> wrote:
>
> Hi Greg,
>
>
>
> Thanks for your comments. I’ve addressed several of your comments. The
> latest diffs (revision to be uploaded soon) can be found at:
>
>
> https://tools.ietf.org//rfcdiff?url1=https://www.ietf.org/archive/id/draft-saad-mpls-miad-usecases-00.txt&url2=https://raw.githubusercontent.com/tsaad-dev/drafts/master/miad-usecases/draft-dt-mpls-miad-usecases.txt
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Frfcdiff%3Furl1%3Dhttps%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-saad-mpls-miad-usecases-00.txt%26url2%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Ftsaad-dev%2Fdrafts%2Fmaster%2Fmiad-usecases%2Fdraft-dt-mpls-miad-usecases.txt&data=04%7C01%7Chaoyu.song%40futurewei.com%7Ca25ba0813707413b445108d9f7fb7dac%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637813481798472749%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=5ZAFo77LGZeJuVzSIgVan4snl%2FC%2FaMEpdKS62AY%2BxB8%3D&reserved=0>
>
>
>
> Regards,
>
> Tarek (for co-authors)
>
>
>
> *From: *spring <spring-bounces@ietf.org> on behalf of Greg Mirsky <
> gregimirsky@gmail.com>
> *Date: *Friday, February 18, 2022 at 4:15 PM
> *To: *draft-saad-mpls-miad-usecases@ietf.org <
> draft-saad-mpls-miad-usecases@ietf.org>, mpls <mpls@ietf.org>,
> pals@ietf.org <pals@ietf.org>, DetNet WG <detnet@ietf.org>, spring <
> spring@ietf.org>
> *Subject: *[spring] Comments on draft-saad-mpls-miad-usecases
>
> Dear Authors,
>
> thank you for your work putting this document together. It helps to
> analyze essential use cases in the scope of the work at the Open DT.
> Attached, please find a copy of the draft with my notes and some
> editorial suggestions. I hope you'll find some of them helpful.
>
> I am looking forward to your feedback and questions.
>
>
>
> Regards,
>
> Greg
>
>