Re: [Detnet] Comments on draft-bocci-mpls-miad-adi-requirements

Greg Mirsky <gregimirsky@gmail.com> Fri, 04 March 2022 00:15 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 BF5E33A0A82; Thu, 3 Mar 2022 16:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 dDBXJyI_0Tsk; Thu, 3 Mar 2022 16:15:45 -0800 (PST)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 85C123A0894; Thu, 3 Mar 2022 16:15:27 -0800 (PST)
Received: by mail-ed1-x52c.google.com with SMTP id p4so8742899edi.1; Thu, 03 Mar 2022 16:15:27 -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=hz4RT6Au4fVvtj2jP8a1jh6n6SnGUsEDqm43PAdz+K4=; b=e1ESw6pQQgf/odyw9lIRan/1rmYcpK0tl/uicywIOyCx/dcXSexs/CLsdkOoA6+G9I BZwn3gt9LkOIkuQg4w3RaskyeEQ0blt83uG2yjA6ovCEamsIL4d+lPxmA/VznViv8vUQ FigIHKHOkDnM84BeEEPRvyzVspcuCdnveYIKeBJagdc6Haa+kWnCXf7a3BFRDaa/Ow7s V6WwQo4VJIAI+wL0md0GCZKQ9IQXCd0IK0itZimjOmbFaU94ojnO4oxS8yJ/wBhXcSYq yqMI1FFRdPrao3YnfV7SA3kzZ5ZL8Yx4KDRJimOZQGEJpnP0ZUMlVhGWknEZ1BiMIJI2 FGVw==
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=hz4RT6Au4fVvtj2jP8a1jh6n6SnGUsEDqm43PAdz+K4=; b=0ZfHxovdfoSr4Tx72JA1ujUZLK5m40eBOmzvokg/THGX2hK8X7PiOxEj9sEkVRkf73 Uh/5YScSFGMPUqJisir1iXUAmZyNJfdzhOTPbF5ZDtyajtLxFY+Ylt4Gg6OClxippmVv 0Hv2TXgFbVB+k4NZxVG4XFE5mCh7qFDaREfdQRL5+p4tJYxH660liIW6YXrFzbgbvpw8 FbtOFhLCiEKMBKB5X/LCNmuO5FxRxgATh/Re/ryrTKZJeol98OHKTjFHVoscWmDozbKN 13HMNtX6auUshsXUmuQ2rDGOjPK3Z83iUomsmamDz6M6gzAP9YIKkD6zW/U2qOpMOaME Z7wA==
X-Gm-Message-State: AOAM533D8VVuD6xyyZAAr9a3ox1f3bW4ApErF3RN7yVx/9IgAcAVIH/U hd+xTt7uUItAuQBs35GkUahFVFRRelJ1fdaJOugsfje3oP8=
X-Google-Smtp-Source: ABdhPJxGsc3wLF+wMjYs2dk7SPcamFgDv2RdYVjtxEFgdAzF1yyEX/jkL6XCOSkb4NgAWEtr0ji+Dh8o+acoZBsh9Hk=
X-Received: by 2002:a05:6402:440d:b0:412:9e8a:5e51 with SMTP id y13-20020a056402440d00b004129e8a5e51mr37250118eda.362.1646352925414; Thu, 03 Mar 2022 16:15:25 -0800 (PST)
MIME-Version: 1.0
References: <CA+RyBmUkdm2dJ5+geme44C6i5bJyqWs_XiA4p_vKjuiniZrPew@mail.gmail.com> <VI1PR0701MB6991DE8DCAE47DEFDA462F52EB049@VI1PR0701MB6991.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB6991DE8DCAE47DEFDA462F52EB049@VI1PR0701MB6991.eurprd07.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 03 Mar 2022 16:15:14 -0800
Message-ID: <CA+RyBmWqBDemJ1pmfVzXNGLnvdTZkmhoKT8UX8XYiorxG8isqQ@mail.gmail.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>
Cc: "draft-bocci-mpls-miad-adi-requirements@ietf.org" <draft-bocci-mpls-miad-adi-requirements@ietf.org>, mpls <mpls@ietf.org>, spring <spring@ietf.org>, DetNet WG <detnet@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004b589a05d9596947"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/Z8EgYHZHY0U8Ig3FB8ixhY-qEfg>
Subject: Re: [Detnet] Comments on draft-bocci-mpls-miad-adi-requirements
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, 04 Mar 2022 00:15:57 -0000

Hi Matthew and Stewart,
thank you for your work addressing my comments; much appreciated. I have
several follow-up questions and comments to the new version of the draft,
mostly to the new Section 3.1.2
<https://datatracker.ietf.org/doc/html/draft-bocci-mpls-miad-adi-requirements#section-3.1.2>
:

   - I may suggest an editorial update to bullet 2

OLD TEXT:
   2.   A common mechanism for ancillary data MUST be defined so that a
        node receiving the ancillary data can determine whether to
        process, ignore or discard it.
NEW TEXT:
   2.   A common mechanism for ancillary data MUST be defined so that a
        node receiving the ancillary data can act according to the local
policies.

   - bullet 4 receives two notes:
      - I think it should be a requirement, not a recommendation
      - I think that an LSR must not be able to insert any ancillary data.
      Only ingress LER inserts data.
   - it would be good if bullet 6 can be split into two
   - RE: bullet 7, I don't think that MPLS is the appropriate layer to
   guarantee in-order delivery. Should that be left to an application?
   - it appears that bullet 8 is specific to the PSD case. If that is the
   case, should it refer to the BoS instead of "as close to the label stack as
   possible"?
   - I think that having a requirement for the use of a common ancillary
   data header will help the discussion.

Couple nits:

   - "an/or" -> "and/or"
   - s/lath/path/

Regards,
Greg

On Thu, Mar 3, 2022 at 3:58 AM Bocci, Matthew (Nokia - GB) <
matthew.bocci@nokia.com> wrote:

> Hi Greg
>
>
>
> Thank you for your detailed review and comments. We have tried to address
> these in the updated draft that we just posted.
>
>
>
> In answer to your question below about whether the ancillary data needs a
> common format, I agree that it at least needs a common header format.
>
>
>
> Regards
>
>
>
> Matthew
>
>
>
>
>
> *From: *Greg Mirsky <gregimirsky@gmail.com>
> *Date: *Tuesday, 15 February 2022 at 20:18
> *To: *draft-bocci-mpls-miad-adi-requirements@ietf.org <
> draft-bocci-mpls-miad-adi-requirements@ietf.org>
> *Cc: *mpls <mpls@ietf.org>, spring <spring@ietf.org>, DetNet WG <
> detnet@ietf.org>
> *Subject: *Comments on draft-bocci-mpls-miad-adi-requirements
>
> Hi Stewart and Matthew,
>
> thank you for organizing this document in a very clear and concise manner.
> I enjoyed reading it.
>
> Attached, please find a copy of the draft with my notes, comments, and
> suggestions. The most important, in my view, the question I have Should we
> add the requirement to have a common format for ancillary data defined?
>
>
>
> Looking forward to your feedback.
>
>
>
> Regards,
>
> Greg
>