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

Tom Herbert <tom@herbertland.com> Fri, 26 July 2024 15:41 UTC

Return-Path: <tom@herbertland.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 75F4CC1D6FCC for <v6ops@ietfa.amsl.com>; Fri, 26 Jul 2024 08:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, 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=herbertland.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 ahWVW3rvKlxu for <v6ops@ietfa.amsl.com>; Fri, 26 Jul 2024 08:41:19 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 9F87FC151086 for <v6ops@ietf.org>; Fri, 26 Jul 2024 08:41:19 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id 2adb3069b0e04-52efba36802so2412095e87.2 for <v6ops@ietf.org>; Fri, 26 Jul 2024 08:41:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1722008477; x=1722613277; 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=EaKAWV7mU0HStJ1Xcc3zd5PwE0fLNihGRdrhWfQmSpc=; b=WDTcYaIIWxFXTSvXXMd5OSm2V4x6Tv+l8jjTz4d+hMPHndaUZ/ZxIjM1b7Jx2KnGyy z9+bXJqat7Ur4vagnLMnGylj6xS7LlnSUnYEEeqEgZ7MzXXN+tXArhiSF8qpFbPj8b+r F30+Ffi+p8JNxeqQQncPyoA3HKW8yvoxCH0VGvF00AncBJVLT/XjghRzGXLA51VQv6iB 6NJm4hjtnnxuY0HxPb7P8Edqyx0it9Qmzv2memGLKCHaEc6WnJ/WZqVMn4tj6w6BItoc Lst6kVnj9Zj+Vq2IkxucznGb8v4XU5bZpnhZE9EchoI+rYLwZo5loApbeDmGVddR35LX jYiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722008477; x=1722613277; 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=EaKAWV7mU0HStJ1Xcc3zd5PwE0fLNihGRdrhWfQmSpc=; b=vJCPYLXPdJ19Nx21hDvxK7JkPeCPtxsKsApg/OgEqm3+kzgM/SGQBY67kV4suSMaVC 5D20H4QFDWzoTQ7q9rkGCzbWR/FMx8mwRVtGbxcYQ8GLMKYmKxjL1aBzArGrnRT1QK9h tnCbamqSVf1sTWhNeROk9h7ZBgUoYkMmmPhgrfyuARpBFU9iXGyWaj65FNlSuiyO224Z Wn+whmNEJMC5aEBUgPU8dZfKwV16eE1qMvm/Slc5SZxHZPk18+a7xftaYeaDUAv26wNr isOGsHKrlzbTeJSZr8nKO5EN6/9r5aYF4fnXY0/pcMNQg93+KX7tabWLZvk5X+nup/DR VCLA==
X-Forwarded-Encrypted: i=1; AJvYcCWcW1oyUtueNoFm+CFBkHigW8SNDR0g291x2KOcfd560Ers6YAQnhMGqhLnJ2Tz98UjTENJazIJpfKP1h09nQ==
X-Gm-Message-State: AOJu0YxyWlABt+q182E9hshkDalnBcDErjpTK2nQxoMee6mtXoO4H2of qiAsbjwViAuAYrM30PavPdJQ6Ftpl5afXHNQYUU9eUfuJVllTqqaP+uzTku2IzX2iHN6mtTQ7Og k7aopMaRCKsNyY9+6x9R8kr9AFWACzOYD5ZOc
X-Google-Smtp-Source: AGHT+IEN0pJOrojNYuz4LqN51qxmkEEYbzYZtL67eDjp3yuaqiPm2YN4HsoKKISa2R/9s1ZQNQ/P1g+rK/SNYlwlcsg=
X-Received: by 2002:a19:5f05:0:b0:52c:df77:6507 with SMTP id 2adb3069b0e04-5309b2bcbebmr109782e87.37.1722008477270; Fri, 26 Jul 2024 08:41:17 -0700 (PDT)
MIME-Version: 1.0
References: <172030377924.88100.13428146493407193705@dt-datatracker-5f88556585-j5r2h> <3ed7b6ba-0664-4e8d-aef3-56fab4e58390@gmail.com> <CACMsEX90SxxRQNCxEz6msJgF6JN3MkvLtYAHp7S+WZhKFY+2dw@mail.gmail.com> <CALx6S35=EuJ-P1pW3L-2SPXXfJKLfyKWb9=NLrcJQpc7Mc9tdA@mail.gmail.com> <ZqNPxZ2n_u1b0tOn@Space.Net>
In-Reply-To: <ZqNPxZ2n_u1b0tOn@Space.Net>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 26 Jul 2024 08:41:05 -0700
Message-ID: <CALx6S35cXaGZNr3BN_NtSfs-b75NHZfAYgd_exbL3=32+9zGvA@mail.gmail.com>
To: Gert Doering <gert@space.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: HJRQ3TUCY57PE4LXTTAP52BPBWSG2OX4
X-Message-ID-Hash: HJRQ3TUCY57PE4LXTTAP52BPBWSG2OX4
X-MailFrom: tom@herbertland.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: v6ops@ietf.org, draft-cc-v6ops-wlcg-flow-label-marking@ietf.org, v6ops-chairs@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: 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/4osbG8PpwoGdk_D_5ls0rFEF8Uk>
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>

On Fri, Jul 26, 2024 at 12:27 AM Gert Doering <gert@space.net> wrote:
>
> Hi
>
> On Thu, Jul 25, 2024 at 05:04:03PM -0700, Tom Herbert wrote:
> > Can you provide more information on this? Also, as "research" networks
> > it seems like there might be more latitude to be cutting edge and fix
> > problems with things like EH?
>
> Over here, "research" networks are more enterprise-style networks providing
> Internet connectivity to universities.
>
> There is no network research going on, many of them even lacking IPv6
> support (because, "enterprise").

Gert,

If it's an enterprise network then that would be closer to a limited
domain, so maybe the problems are addressable.

In any case, as this solution seems specific to a few enterprise
networks and I don't see any problem overloading the flow label in
this manner as people are certainly free to do whatever they want in
their network. There's no protocol change and I'm assuming that
IPV6_FLOWLABEL_MGR socket option is used to set the flow label (or
maybe a BPF program?) so there should be no kernel changes. On the
other hand, because it is specific to a network, I don't see the need
to publish this as an RFC. Using the flow label for this purpose is
inherently and perpetually limited so I believe wide adoption isn't
likely. If the intent is to push it as a general solution then I think
there will need to be a lot more discussion on the ramifications of
pushing a protocol with no scalability as opposed to using an existing
protocol that is scalable and designed for expressing this sort of
information (DestOpts). Maybe this could be published as an Individual
Contribution?

Tom
>
> Gert Doering
>         -- NetMaster
> --
> have you enabled IPv6 on something today...?
>
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Ingo Lalla,
>                                            Karin Schuler, Sebastian Cler
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279