Re: [mpls] FW: I-D Action: draft-ietf-mpls-mna-requirements-10.txt

Greg Mirsky <gregimirsky@gmail.com> Thu, 08 February 2024 16:56 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0050C14F600 for <mpls@ietfa.amsl.com>; Thu, 8 Feb 2024 08:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o6bMNp298KJs for <mpls@ietfa.amsl.com>; Thu, 8 Feb 2024 08:56:24 -0800 (PST)
Received: from mail-yw1-x1135.google.com (mail-yw1-x1135.google.com [IPv6:2607:f8b0:4864:20::1135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5FA3C14F5FC for <mpls@ietf.org>; Thu, 8 Feb 2024 08:56:23 -0800 (PST)
Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-604ac794c01so658597b3.2 for <mpls@ietf.org>; Thu, 08 Feb 2024 08:56:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707411383; x=1708016183; 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=TUAP0WeE1muGLwqvgRKPubrPm9St8Rc7yIp1zhKkNJc=; b=Va0W0/J07tAFk2apuqsX5FnrvIUO9msXkwlFsbNbUC/qunD8jucqxlNA1s023g1asP bDh4mUPZ//7y4oZQRDKn3WqpGbgqwmbCgNjD24aeM4FVKXhLmBmAQWprbdLMymd472i4 24T0lgGaau7Vg3sFBQwpKymr3fy9CJXfnEdPu+yx5/L9F1cVYCXmjDUB2V6Ev9D5GN4Z kw2KC5YGAdFKDkGDp14Okrh946r6df7CnKRzWtgm40mxezs1MIDJdbgzswUHKudvUJf7 tM+qycMk3DDxrE8gBAIRCHTMC1lQsI8c4v9V3N6uhOSjbFktN/E6rHv5HFASuq3Lng3W 0KJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707411383; x=1708016183; 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=TUAP0WeE1muGLwqvgRKPubrPm9St8Rc7yIp1zhKkNJc=; b=u+3RVyC5jZYAfroaA8GTnHtHqq84nprMYVEnhZ+C6hcMFc9XrRr9bpi5ozkaiH2jbf mavv1c/mWyXF5PvdufT0Sd65BySZqX5hwga/MwDdpXyppj92AkqsNNlxsjDqCJEVrqWl +0DtcZI6Z9GMqzKzJtBkkID8D6kiCj8kLH85qRC1/l37cysk38vQXmct7c55co/T7DaR 3cskI5VJAo+DH2kWtr1trCTUrj3V4o/xWV6IH4et+yI2pAtOs2krQqI/09IB31jrHI7P 01mWqDH63HKUgHniSFqEGUHU3o0X+BD4fPi1dWVvOZH5r5pudu0WR8SLFroSvtERf2bR 2FoQ==
X-Gm-Message-State: AOJu0Yxhq0Hv/0vH3vWl0L2+GrqbwmUfO8wAis7okPBd6G6KeClb44oe IPRPhRcbNzCWAIpRwaTMD9nM+RtBuWNjB3BP2hJS0RVNblqo0ZJBBgGsjLiZgSrmVDAcKdKN/0s LBiQdQwisa/dVv2lh1NiwwKfJhX0=
X-Google-Smtp-Source: AGHT+IGghmBAAy41wh6hwxAdprd1nyx43EFIo8aFhQTKc3KHUlL1ISx2r+cMhTgD+gfCE/sXE6DHnW3GOSzmmCdorg0=
X-Received: by 2002:a25:44d7:0:b0:dc7:4903:ce3c with SMTP id r206-20020a2544d7000000b00dc74903ce3cmr17323yba.13.1707411382501; Thu, 08 Feb 2024 08:56:22 -0800 (PST)
MIME-Version: 1.0
References: <170731846141.46174.8015116885911002352@ietfa.amsl.com> <VI1PR0702MB3567798C9518DBC6CB95ADD8EB452@VI1PR0702MB3567.eurprd07.prod.outlook.com> <04c001da59e8$75498c50$5fdca4f0$@olddog.co.uk> <BY3PR13MB47873A422AB7DC413032842F9A452@BY3PR13MB4787.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB47873A422AB7DC413032842F9A452@BY3PR13MB4787.namprd13.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 08 Feb 2024 08:56:12 -0800
Message-ID: <CA+RyBmW0+R+FUoC0zh2piNzbX5YUzJD9PDmOUC=EVs+8-AALZA@mail.gmail.com>
To: Haoyu Song <haoyu.song@futurewei.com>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Dongjie (Jimmy)" <jie.dong@huawei.com>, "Matthew Bocci (Nokia" <matthew.bocci=40nokia.com@dmarc.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f0868f0610e1b0d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/jMqMCAtfxMK1rR5b30mPcLaeGSU>
Subject: Re: [mpls] FW: I-D Action: draft-ietf-mpls-mna-requirements-10.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2024 16:56:28 -0000

Hi Haoyu,
I feel that adding the "by default" clause confuses a reader. The
requirement as it is worded in the draft is clear and positions post-stack
AD as an optional solution if and when it is needed. Would you kindly
elaborate on your motivation to add the "by default" clause?

Regards,
Greg

On Wed, Feb 7, 2024 at 10:43 AM Haoyu Song <haoyu.song@futurewei.com> wrote:

> Dear all,
>
>
>
> I checked my original email and found some of them have been resolved.
>
>
>
> Now I understand the intention of the #7 better, and I suggested to add
> “by default” at the end of the first half of the sentence to make it
> clearer.
>
>
>
> 7.   A solution MUST NOT require an implementation to support post-
>
>         stack ancillary data (by default), unless the implementation
> chooses to
>
>         support a network action that uses post-stack ancillary data.
>
>
>
> The #20 remains the same, so my question stays. What are considered
> “existing MPLS data plane operations”. Is there a normative reference for
> this? Does this requirement exclude using any new operations that don’t
> exist today?
>
>
>
> Best regards,
>
> Haoyu
>
> *From:* Adrian Farrel <adrian@olddog.co.uk>
> *Sent:* Wednesday, February 7, 2024 9:10 AM
> *To:* 'Dongjie (Jimmy)' <jie.dong@huawei.com>; Haoyu Song <
> haoyu.song@futurewei.com>
> *Cc:* 'Matthew Bocci (Nokia' <matthew.bocci=40nokia.com@dmarc.ietf.org>;
> mpls@ietf.org
> *Subject:* RE: [mpls] FW: I-D Action:
> draft-ietf-mpls-mna-requirements-10.txt
>
>
>
> Thanks for this, Matthew.
>
>
>
> Jie and Haoyu, if you get a chance before the New Year holiday, it would
> be **really** helpful if you could let Matthew know whether you still
> have concerns resulting from your previous comments, or if Matthew has
> addressed them with changes to the current revision.
>
>
>
> If we are all good, then a 2nd WGLC can be run (with plenty of time for
> review and comments after New Year).
>
>
>
> Thanks,
> Adrian
>
>
>
> *From:* mpls <mpls-bounces@ietf.org> *On Behalf Of *Matthew Bocci (Nokia)
> *Sent:* 07 February 2024 15:14
> *To:* mpls@ietf.org
> *Subject:* [mpls] FW: I-D Action: draft-ietf-mpls-mna-requirements-10.txt
>
>
>
> All
>
>
>
> I have just posted an updated draft, hopefully addressing Tony’s comments
> below.
>
>
>
> There were some outstanding comments from Jie and Haoyu, but I think that
> these may have been addressed to some extent by some of the resolutions to
> the other comments. Please could you review the draft and let me know if
> you still have outstanding comments.
>
>
>
> Thanks
>
>
>
> Matthew
>
>
>
> *From: *mpls <mpls-bounces@ietf.org> on behalf of internet-drafts@ietf.org
> <internet-drafts@ietf.org>
> *Date: *Wednesday, 7 February 2024 at 15:07
> *To: *i-d-announce@ietf.org <i-d-announce@ietf.org>
> *Cc: *mpls@ietf.org <mpls@ietf.org>
> *Subject: *[mpls] I-D Action: draft-ietf-mpls-mna-requirements-10.txt
>
>
> CAUTION: This is an external email. Please be very careful when clicking
> links or opening attachments. See the URL nok.it/ext for additional
> information.
>
>
>
> Internet-Draft draft-ietf-mpls-mna-requirements-10.txt is now available.
> It is
> a work item of the Multiprotocol Label Switching (MPLS) WG of the IETF.
>
>    Title:   Requirements for Solutions that Support MPLS Network Actions
>    Authors: Matthew Bocci
>             Stewart Bryant
>             John Drake
>    Name:    draft-ietf-mpls-mna-requirements-10.txt
>    Pages:   11
>    Dates:   2024-02-07
>
> Abstract:
>
>    This document specifies requirements for the development of MPLS
>    network actions which affect the forwarding or other processing of
>    MPLS packets.  These requirements are informed by a number of
>    proposals for additions to the MPLS information in the labeled packet
>    to allow such actions to be performed, either by a transit or
>    terminating LSR (i.e. the LER).
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mpls-mna-requirements/
>
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-requirements-10
>
> A diff from the previous version is available at:
>
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-mpls-mna-requirements-10
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>