[mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-fwk

Loa Andersson <loa@pi.nu> Wed, 19 June 2024 07:32 UTC

Return-Path: <loa@pi.nu>
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 4C80DC16A128; Wed, 19 Jun 2024 00:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 LVHv0svPb6E9; Wed, 19 Jun 2024 00:32:20 -0700 (PDT)
Received: from srv.pi.nu (srv.pi.nu [46.246.39.30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 5CBCDC15108B; Wed, 19 Jun 2024 00:32:16 -0700 (PDT)
Message-ID: <67196bb4-2061-4d9b-af19-9c1d0e45e29a@pi.nu>
Date: Wed, 19 Jun 2024 09:32:14 +0200
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>, Tarek Saad <tsaad.net@gmail.com>
References: <DS0PR19MB65014515D511B396E79BA36FFCF82@DS0PR19MB6501.namprd19.prod.outlook.com> <DS0PR19MB6501D41C4A1E310C32D96FE4FCCE2@DS0PR19MB6501.namprd19.prod.outlook.com> <CA+RyBmU0wRL-zQGb_gbzprGjPQbG4fdxrbQ4J8aROF=0=T9vcg@mail.gmail.com>
Content-Language: sv, en-GB
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <CA+RyBmU0wRL-zQGb_gbzprGjPQbG4fdxrbQ4J8aROF=0=T9vcg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: 55KNAUU6AIFRXVOHL64KEUAVD65SUBED
X-Message-ID-Hash: 55KNAUU6AIFRXVOHL64KEUAVD65SUBED
X-MailFrom: loa@pi.nu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-mna-fwk@ietf.org" <draft-ietf-mpls-mna-fwk@ietf.org>, MPLS Working Chairs <mpls-chairs@ietf.org>, "draft-ietf-mpls-mna-hdr@ietf.org" <draft-ietf-mpls-mna-hdr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-fwk
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Qoz_vo78w2Y1IJUt9mwbzxmojbs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

Tarek,

First, it is not the tradition (or at least not required) in the MPLS WG 
that the author respond to the WGLC, but since other co-authors has 
responded. I support progressing the draft.

To Greg's comment on using RFC XXXX, I'm not in favour of this. Best 
would be to use the correct title, and alternatively use 
[I-D.ietf-mpls.mna-requirements]. Using a link will cause a nits-tool 
error and also inform us when the RFC number is available. We or the RFC 
Editor may change.

/Loa

Den 2024-06-18 kl. 21:09, skrev Greg Mirsky:
> Hi, Tarek et al.,
> I read the current version of the draft and found it concise. I 
> support progressing this document to the publication. I have a minor 
> question. As I understand it, in the last paragraph of Abstract, 
> draft-ietf-mpls-mna-requirements 
> <https://datatracker.ietf.org/doc/draft-ietf-mpls-mna-requirements/> is 
> referenced by the title:
>    Some of these
>    actions are defined in existing MPLS specifications, while others
>    require extensions to existing specifications to meet the
>    requirements found in "Requirements for MPLS Network Actions".
> But the full title of the MNA requirements draft is slightly 
> different, "Requirements for Solutions that Support MPLS Network 
> Actions (MNA)". To avoid a possible confusion and misreference, and 
> since both documents are progressing closely, perhaps the reference 
> could use RFC XXXX format with a note to RFC Editor pointing to 
> yet-to-be-assigned RFC number of MNA Requirements draft.
>
> Regards,
> Greg
>
> On Tue, Jun 18, 2024 at 7:53 AM Tarek Saad <tsaad.net@gmail.com> wrote:
>
>     Dear WG,
>
>     This email starts a two-week Working Group last call for
>     draft-ietf-mpls-mna-fwk.
>
>     Please indicate your support or concern for this draft. If you are
>     opposed to the progression of the draft to RFC, please articulate
>     your concern. If you support it, please indicate that you have
>     read the latest version, and it is ready for publication
>
>     in your opinion. As always, review comments and nits are most
>     welcome. Please send your comments to the mpls WG mailing list
>     (mpls@ietf.org)
>
>     If necessary, comments may be sent unidirectional to the WG chairs.
>
>     Note, currently there are 2 IPR disclosures against this document
>     at
>     https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-mpls-mna-fwk
>     <https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-mpls-mna-fwk>
>
>     This poll runs until July 5. 2024.
>
>     Thank you,
>
>     Tarek (for the MPLS WG co-chairs)
>
>     _______________________________________________
>     mpls mailing list -- mpls@ietf.org
>     To unsubscribe send an email to mpls-leave@ietf.org
>
>
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org

-- 
Loa Andersson
Senior MPLS Expert
Bronze Dragon Consulting
loa@pi.nu
loa.pi.nu.@gmail.com