Re: [v6ops] Thoughts about wider operational input

"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Tue, 22 March 2022 01:22 UTC

Return-Path: <bzeeb-lists@lists.zabbadoz.net>
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 414CF3A1C8A for <v6ops@ietfa.amsl.com>; Mon, 21 Mar 2022 18:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 cwHZVLmbvYCP for <v6ops@ietfa.amsl.com>; Mon, 21 Mar 2022 18:22:07 -0700 (PDT)
Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 323763A1C87 for <v6ops@ietf.org>; Mon, 21 Mar 2022 18:22:06 -0700 (PDT)
Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id E72E38D4A17A; Tue, 22 Mar 2022 01:22:03 +0000 (UTC)
Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 2F86BE707C8; Tue, 22 Mar 2022 01:22:03 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sbone.de
Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id l_4K26W2SNh8; Tue, 22 Mar 2022 01:22:01 +0000 (UTC)
Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:d416:3e38:a9ce:db88]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id B512FE707BA; Tue, 22 Mar 2022 01:22:01 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, v6ops@ietf.org
Date: Tue, 22 Mar 2022 01:22:01 +0000
X-Mailer: MailMate (2.0BETAr6151)
Message-ID: <39D4AD57-836E-4B01-BC59-46B68F588786@lists.zabbadoz.net>
In-Reply-To: <26C8710D-BB40-4DBD-98A2-20BC3767D732@gmail.com>
References: <52661a3d-75dc-111a-3f23-09b10d7cb8d4@gmail.com> <A72CDDDB-CDCE-4EAF-B95E-997C764DB2C4@gmail.com> <9175dc32-45c1-e948-c20a-3bcc958b77b9@gmail.com> <26C8710D-BB40-4DBD-98A2-20BC3767D732@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LanMh65ySynL8_I1P9MNzHFB-Uo>
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, 22 Mar 2022 01:22:10 -0000

On 22 Mar 2022, at 1:01, Bob Hinden wrote:

> I should probably know better to respond to this thread, but 
> apparently not :-)

dito… and I don’t know what triggered this thread as .. as 
not-onsite and Fred wasn’t exactly saying.. Anyway…

> In my view, and I think I am agreeing with Nick said, it’s not a 
> technical problem that would be fixed by a technical feature.   IPv4 
> works for most enterprises today and they don’t see a need (aka 
> business case) to do anything different.   The Enterprises who are 
> thinking about moving to IPv6 are very large enterprises who can’t 
> live within the limits of private IPv4 space.

But remember that these XXL-enterprises are also seeking solutions and 
using ways often not feasible or applicable for the common SMLB.


> I suspect these are the ones we should be talking to.

I suspect the answer is more like “wait until they start speaking to 
you”; well, why should they?  IETF is on no radar for most of them ..  
so rather you have to go and “listen when and where they speak” 
because they do.

0.1ct/bz