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

Greg Mirsky <gregimirsky@gmail.com> Tue, 18 June 2024 19:09 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 3E267C1D8779; Tue, 18 Jun 2024 12:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JuPfqba9vNcm; Tue, 18 Jun 2024 12:09:24 -0700 (PDT)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 99073C1D8769; Tue, 18 Jun 2024 12:09:24 -0700 (PDT)
Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-dff36345041so2802945276.3; Tue, 18 Jun 2024 12:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718737764; x=1719342564; 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=bzPW1xsCMfuf4I9uzpr4fFWB4cafmwanFmWGjQVlmIM=; b=fvkNWIA2RyDRYsYLSWapd+NTE6+R8LqdmVcsHGsFm/0oaO0+DkOjAhDr/RtAJiO6k5 iQlDm1nHzoSjw8gy5knLzeO0umW6vMAPocBuWs3xWDm8qcopQ6XMhoOd/Gh1GUqRByeo 7TGKM8iehdejhXBf+WnRbVTlSd+YxnhN4Nilh8/rE8hIgYfX62vFc9iZ2eG+9AGTAF59 2zWX9TEdj/khuM2a0beViB0xO45gZ6oNCEMtJCV/Vx2F1YpNPxhuQ0Q1D0IAwCZ0ClmC SiJskbzUCCSahiWqyH1yaQFfiA6uTEgbJAKLDGSs81kFkcs02oZ67UPKVH69N09in/Gy 3OUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718737764; x=1719342564; 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=bzPW1xsCMfuf4I9uzpr4fFWB4cafmwanFmWGjQVlmIM=; b=pk01O3yWjkpT+b5Nn6S7HUElaaitepGXSyy96mGHQWJVwTnU6S8AxzfxvzXGwsangl ixfmI0wzf7ZmlJLOoSpsxTFNVYGEIbhkGxt3ceNLKpnuDaxlTsN8/ZkEGVrKYupzohqV 47EagtaG96j6W5AAkpZYd3fsDFJs1pIU0W72xuIlx6PA/iSd+I/sJUdyXj+o+pJYoJvt G4NE5WS6NUAtKpVfLO2mtw3pn23wTbvRWDR69nJsGhOpwuoASkD9svQ59r8P5NxIuauy uAfjksvt6ry9A2d6WpfmxOWEW9b2MLmQpG2SZPhBDJi5OZWJjo/zKorxUHZyiwAE0RcF lJbg==
X-Forwarded-Encrypted: i=1; AJvYcCUeo9aKs7V/mtvxUNM3yb8bLEfKOF0U5gwNiJaBwIRV1ERG/bp+NZfx+99wK0U+vOQAC48EPtFg66s04fMwswpzIy13I0+i1T325R28299+D91SxaU/XJK6mZcnJ9cSBD6Yu7uHRVQ1E4j/wj9nkTw2qw22/wTZk7xCAY4DSnexO8G854cEu8dz
X-Gm-Message-State: AOJu0YybNJLYukfiCDam8Jk2xbiAb2wqDjCrUo4uCddNmsl8llCZlCvB V6AjLtlDaLMxp9In0DRS/UnvY+zt7JYdZFFGedHVDc1pwF2HdykGUgzEKPMRf6ejUuHcOVcn2jb hn8OJoBAVQ4yVlTZeNDb4GGBUQ1oIQWnI
X-Google-Smtp-Source: AGHT+IHR8XP+is/uwFBAzymYGwvVMUibOJwgaBLR7+IaIzmkh4Oe+1wVTAW0pF2JkLEURW31ham4LoKlm0QnbwzLRUU=
X-Received: by 2002:a25:aaa6:0:b0:df4:eb0b:8fc with SMTP id 3f1490d57ef6-e02be2102b5mr777753276.43.1718737763672; Tue, 18 Jun 2024 12:09:23 -0700 (PDT)
MIME-Version: 1.0
References: <DS0PR19MB65014515D511B396E79BA36FFCF82@DS0PR19MB6501.namprd19.prod.outlook.com> <DS0PR19MB6501D41C4A1E310C32D96FE4FCCE2@DS0PR19MB6501.namprd19.prod.outlook.com>
In-Reply-To: <DS0PR19MB6501D41C4A1E310C32D96FE4FCCE2@DS0PR19MB6501.namprd19.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 18 Jun 2024 12:09:12 -0700
Message-ID: <CA+RyBmU0wRL-zQGb_gbzprGjPQbG4fdxrbQ4J8aROF=0=T9vcg@mail.gmail.com>
To: Tarek Saad <tsaad.net@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ddabfe061b2ed13f"
Message-ID-Hash: T34E5IVXAUXO6HLTP3IQM7OCGCS3OMXT
X-Message-ID-Hash: T34E5IVXAUXO6HLTP3IQM7OCGCS3OMXT
X-MailFrom: gregimirsky@gmail.com
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/uBTkPmXssFcIj1Jm81FmXZ5OdvQ>
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>

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
>
>
>
> 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
>