[v6ops] Re: Fwd: The V6OPS WG has placed draft-cc-v6ops-wlcg-flow-label-marking in state "Call For Adoption By WG Issued"

Mark Smith <markzzzsmith@gmail.com> Tue, 13 August 2024 22:05 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5BDC14F6BE for <v6ops@ietfa.amsl.com>; Tue, 13 Aug 2024 15:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.149
X-Spam-Level:
X-Spam-Status: No, score=-1.149 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.455, 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=no 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 0mwY6TNPfmz6 for <v6ops@ietfa.amsl.com>; Tue, 13 Aug 2024 15:05:30 -0700 (PDT)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94971C14F6B7 for <v6ops@ietf.org>; Tue, 13 Aug 2024 15:05:30 -0700 (PDT)
Received: by mail-pj1-x102b.google.com with SMTP id 98e67ed59e1d1-2cb4c4de4cbso3958728a91.1 for <v6ops@ietf.org>; Tue, 13 Aug 2024 15:05:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723586729; x=1724191529; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=w+1e3nui8XGQ54rAIbJ12LjxokxrT3B8IdO54EZ4o98=; b=AbfwGgAaI/RweLQBMlA2XnMpljlZF3z3ZuK+phuqccv80LZspfnjw1z+U1MUosF1Iy W67NrOyG606R4+oX9eM4mj327FOVMvJDk1vsepHWDk8yMeMtVAoVSESeiQ3WleWNhHrB 9oiAvj4tdNylonmQ9penuAG8UbajvQfy9YsJd7vmdOa3EEknoEi3PbUzyUoZbwuv9WkJ Vzd+WGfYu3A7KouxYNaY5DFtWpneX9icXUz+a8buDpo2qHn0Oyt+zohTRjYJg5U+Eo6F FMbbfZy9SiGLH17FHJ1R4dJ2n5fYuwDjGlO6hfKHSKNuTblWJdlRQ+LFP1IFEk5LMzAY Gzbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723586729; x=1724191529; h=content-transfer-encoding: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=w+1e3nui8XGQ54rAIbJ12LjxokxrT3B8IdO54EZ4o98=; b=UKrjWN5gp/V/MbaVfvxgYgJ5Tt+ERXqv2aUGjld8z2V1/dcL+gLHqvyK6s174IBBh1 2W1S5WwPooCrO4fYjdgakmNzfLKArPGjVnQLNwtiUes8QIHj60uJSeGo3a8Vkp3EA0s7 Eyqj7gc4NaKBzbWtRphgzX+hu/icJtEUJ/7sWpnsUkGEgIubjUp7pSvcKDcw9RLQwumX 1Biwp5WfLSkIWSjABkbUT0YqTxL1EHDF22lXUQm/2wNgT5dMehKZ2vnsJWiOoszTFBtC V809wG8j6suxoVXFmHRskUKgBk3v05mbHsWRCIv50YgbdZpXv6knxF412KDBlpyPHXk+ CNTQ==
X-Forwarded-Encrypted: i=1; AJvYcCVIhq9Ctgkk5b6lqpcoXiMwtwmUSI0kBECdwF427Our7bHZ5QPR5P8nC4TvvP7CfwCmQn1sz+9IUgk9Zwmwdg==
X-Gm-Message-State: AOJu0YwWTNEk1Z01IyXDquJVD33YoM/aXAKeN3m8YDdoilIJhHEHwt1G TkAuAMNQgT1I0bdFQ1ImYg72qPy+EP3p3+KCG+g0e6/7HjtxGPIBN7KPtTsZmFa88+gxMJ3XxYl xoGBRsX5Xl4pqdxj4gfU+kQqxwtA=
X-Google-Smtp-Source: AGHT+IHI5EIi5RHNpCz7g2jc3YWbcbN02XLXtpQcgZPG2jF3QjEkRe0ic7YePw9I+mr/b1DhjJaSOMiXMYID0KJRGX0=
X-Received: by 2002:a17:90a:8d0f:b0:2cb:6419:5b53 with SMTP id 98e67ed59e1d1-2d3aaaa37admr1104342a91.24.1723586728943; Tue, 13 Aug 2024 15:05:28 -0700 (PDT)
MIME-Version: 1.0
References: <172030377924.88100.13428146493407193705@dt-datatracker-5f88556585-j5r2h> <CACMsEX_KFz57m67UEOxSqQRYU9dEq3yb_CHOqRdVJ5w_yiRwDg@mail.gmail.com> <CAN-Dau22o+3y5zqn69Q0XUuMoreBd509EHh6dExQzMwaz_7tpA@mail.gmail.com> <CACMsEX_dYL-bCmRohCRvJsE=yZfCSZCZtF-8E69tiahGBP47RQ@mail.gmail.com>
In-Reply-To: <CACMsEX_dYL-bCmRohCRvJsE=yZfCSZCZtF-8E69tiahGBP47RQ@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 14 Aug 2024 08:05:02 +1000
Message-ID: <CAO42Z2zh5EWE38mmgSa+m=4+wvkyOFGrDpPv7xiMiTqJgW3wxg@mail.gmail.com>
To: Nick Buraglio <buraglio@forwardingplane.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: QZZ2ZJMILOXXI4NHQV55UKXWIPMQ6NIJ
X-Message-ID-Hash: QZZ2ZJMILOXXI4NHQV55UKXWIPMQ6NIJ
X-MailFrom: markzzzsmith@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IPv6 Operations <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: Fwd: The V6OPS WG has placed draft-cc-v6ops-wlcg-flow-label-marking in state "Call For Adoption By WG Issued"
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mF5zI4khi9zLJz7Hx1QZ8IvTg2Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

Hi,

I don't support adoption for a number of reasons.

Firstly, and the main reason, v6ops working group adoption means the
document becomes a product of the WG, rather than just the authors.

As this ID is documenting violations of IETF Standard Track RFC 6437,
it becoming a v6ops WG document means that the v6ops WG is tacitly
endorsing RFC 6437 violation, even if published as Informational.

It becoming a WG document also suggests there is further work to be
done on it by the WG, not just the authors. What further work on this
ID is there the v6ops WG to do?

If the IETF is the best place to publish it, why can't it be published
as an Independent Submission, avoiding v6ops tacit endorsement and any
WG publication overheads.

Why can't it be published as an academic paper outside of the IETF,
further avoiding the IETF RFC publication costs?

Regards,
Mark.

On Wed, 14 Aug 2024 at 04:27, Nick Buraglio
<buraglio@forwardingplane.net> wrote:
>
>
> This call for adoption is wrapping up. If anyone else would like to comment, please read the draft and provide feedback by tomorrow.
> Below is the current state:
>
> | [draft-cc-v6ops-wlcg-flow-label-marking](https://datatracker.ietf.org/doc/draft-cc-v6ops-wlcg-flow-label-marking/) |             | Adoption Called 05-Aug-2024                        | Adoption Ending 19-August-2024 |
> | ------------------------------------------------------------------------------------------------------------------ | ----------- | -------------------------------------------------- | ------------------------------ |
> | Support                                                                                                            | Opposed     | Comments                                           | Comments Addressed             |
> | Brian Carpenter                                                                                                    |             | discussion of deviations from RFC 6437 is helpful. |                                |
> | Tim Winters                                                                                                        |             |                                                    |                                |
> | Nick Buraglio                                                                                                      |             |                                                    |                                |
> |                                                                                                                    | Tom Herbert | Feels is too specific                              | Yes                            |
> | David Farmer                                                                                                       |             |                                                    |
>
>
> I believe Tom had his concerns addressed but I never saw explicit support after.
> If anyone else would like to comment, please read the draft and provide feedback by tomorrow.
>
> nb
>
>
> On Mon, Aug 5, 2024 at 2:13 PM David Farmer <farmer@umn.edu> wrote:
>>
>>
>> I support adoption.
>>
>> On Mon, Aug 5, 2024 at 13:35 Nick Buraglio <buraglio@forwardingplane.net> wrote:
>>>
>>> All,
>>> We'd like to wrap this adoption call up. As of now we don't have a lot
>>> of input, but it is mostly positive. Please read and comment.  Current
>>> state:
>>>
>>> ### draft-cc-v6ops-wlcg-flow-label-marking
>>> #### Adoption Called 06-July-2024
>>> * Support - Comments - Comments Addressed
>>> Brian Carpenter - discussion of deviations from RFC 6437 is helpful.
>>> Tim Winters
>>> Nick Buraglio
>>>
>>>  * Opposed - Comments - Comments Addressed
>>> Tom Herbert - Feels is too specific - no
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
>>> Date: Sat, Jul 6, 2024 at 5:09 PM
>>> Subject: The V6OPS WG has placed
>>> draft-cc-v6ops-wlcg-flow-label-marking in state "Call For Adoption By
>>> WG Issued"
>>> To: <draft-cc-v6ops-wlcg-flow-label-marking@ietf.org>,
>>> <v6ops-chairs@ietf.org>, <v6ops@ietf.org>
>>>
>>>
>>>
>>> The V6OPS WG has placed draft-cc-v6ops-wlcg-flow-label-marking in state
>>> Call For Adoption By WG Issued (entered by Nick Buraglio)
>>>
>>> The document is available at
>>> https://datatracker.ietf.org/doc/draft-cc-v6ops-wlcg-flow-label-marking/
>>>
>>> _______________________________________________
>>> v6ops mailing list -- v6ops@ietf.org
>>> To unsubscribe send an email to v6ops-leave@ietf.org
>
> _______________________________________________
> v6ops mailing list -- v6ops@ietf.org
> To unsubscribe send an email to v6ops-leave@ietf.org