IETF Logo Mail Archive

Re: [v6ops] Thoughts about wider operational input

Fred Baker <fredbaker.ietf@gmail.com> Tue, 29 March 2022 19:37 UTC

Return-Path: <fredbaker.ietf@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 189D83A1BDF for <v6ops@ietfa.amsl.com>; Tue, 29 Mar 2022 12:37:33 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYVJmvpYwRuN for <v6ops@ietfa.amsl.com>; Tue, 29 Mar 2022 12:37:28 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BA4F3A1BCE for <v6ops@ietf.org>; Tue, 29 Mar 2022 12:37:28 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id t2so16784335pfj.10 for <v6ops@ietf.org>; Tue, 29 Mar 2022 12:37:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LOkuJy3ZLgKpwCA/HmzLk3vpHcAAt29JlDK/MefUXxM=; b=am1JIilU4P6T/m6mdxSogGm67ybYVvG9NRP4Izn+oDEpyOoUoa06VSdvUlBUaOacf1 vYg4mCh1vdg3NUrlIG/ga14xbvL+b7Xy5yWd/MGbiG1YUTECk7+lAzR1QZnVqx3mETlb +TWCaeBvluSMED1a7HI3d0jYP6BLRjwtoBiBkP1R3ur1gReMSWyi6QI1Z9vyuTgmt75Z K3irdx3Fz9vHSUZBzgyvNFWfQ5GHl0hpAoH4yC8U2zwDhpbVQFwCuWprrH85Ha3bftG5 ekFpuwBUwQgIyU4GNxaqpDu87AWzhlS0xNktYrfNQu5otqXoOcENDnGwYJTpe8+DpItL DZCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LOkuJy3ZLgKpwCA/HmzLk3vpHcAAt29JlDK/MefUXxM=; b=rfCwSx5q7T8AqxKElzBmK9TYUtNJuJoLXMvG+OM3iu4tVD1TMoMxcY1znIgIvk3GXJ Daww42fk+gkPT+g7/Oko5NazQekGZ1fzNoQQuOQgtIYnDFpq1lQ650prj7OvbVAvKtjx YNYsquhTqi3M/inK67l/gcYRUZk9O7r0HrJ60cKtwVcDNvivKAXGj63EJMIBa9XjDg3b FE8pbhuNCz7kOuAhUJz+SqkasEjzyPps+0UEBiteKC3X3WlnxvxHnYF1ehd5RoJ1zfub Ad0pR0/bIDI/6ULk7QnBn4tWv1mXHlViNelZbav3Zbo519sYH9/Oo1K4Artn3qQ0M07S p/PA==
X-Gm-Message-State: AOAM533r1i5en/ncrff4E3BGM+X32V43tW9fZxqj8+OhREffoZ+UCPpz DEdunFLzdLsCH5aYVXIlcMT+fT4+SKY=
X-Google-Smtp-Source: ABdhPJwIfVCLZw+FDmulCfJtn6tvlM9Pp6RU97dFSCkjcZg/9n39372rP340e5QJlUFLKcxmpwRtlQ==
X-Received: by 2002:a63:8ac3:0:b0:398:9e2b:b85 with SMTP id y186-20020a638ac3000000b003989e2b0b85mr1090306pgd.32.1648582647215; Tue, 29 Mar 2022 12:37:27 -0700 (PDT)
Received: from smtpclient.apple ([2600:8801:d008:8c00:c937:4b4a:700f:a771]) by smtp.gmail.com with ESMTPSA id 21-20020a630115000000b00382a0895661sm16527545pgb.11.2022.03.29.12.37.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Mar 2022 12:37:26 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <bdd02e1bc8f5468ea4501f071a9e95a7@huawei.com>
Date: Tue, 29 Mar 2022 12:37:25 -0700
Cc: "Ackermann, Michael" <mackermann@bcbsm.com>, "Philipp S. Tiesel" <phils@in-panik.de>, IPv6 Ops WG <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <78A86A99-38C3-4494-B085-FFC224AFE1C4@gmail.com>
References: <BE3310F7-692C-46E9-A75B-07C4C3C6476F@gmail.com> <DM6PR14MB3178DB5E4F9560FFE0B13521D7179@DM6PR14MB3178.namprd14.prod.outlook.com> <29f35cbabc114386a1d00bf5c4054f6c@huawei.com> <DM6PR14MB3178A04B566F1D24571924F8D7199@DM6PR14MB3178.namprd14.prod.outlook.com> <1DA8D34D-3B77-4B6B-B49F-C4C200492624@in-panik.de> <36b1c1aa244f40afa05eb5e58cc62cdb@huawei.com> <DM6PR14MB3178AAF2A80CE63ED8A11C1DD71B9@DM6PR14MB3178.namprd14.prod.outlook.com> <CAM5+tA-zjL4hiL6uSTj3mUJYBAY==kuDUMynA=rCQTtmoSAmGA@mail.gmail.com> <bdd02e1bc8f5468ea4501f071a9e95a7@huawei.com>
To: Paolo Volpato <paolo.volpato=40huawei.com@dmarc.ietf.org>, "buraglio@es.net" <buraglio@es.net>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_g_5cK3c_pf1ViHCfvbROwvm2cw>
Subject: Re: [v6ops] Thoughts about wider operational input
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2022 19:37:41 -0000


> On Mar 29, 2022, at 7:51 AM, Paolo Volpato <paolo.volpato=40huawei.com@dmarc.ietf.org> wrote:
> 
> As Nick suggested, I also see a role for them to contribute in defining an evolution path to IPv6. I see this something that can be addressed in the IETF. 

I don't disagree with you in the least. That brings me back to my original question, however:

Can we get someone-that's-not-a-vendor-academic-or-ISP (using the word "enterprise" seems to be confusing) give a talk in v6ops in Philadelphia about what their proposed evolutionary target for IPv6 might be?

v2.23.0 | Report a Bug | By Email