Re: [v6ops] Thoughts about wider operational input

Nick Buraglio <buraglio@es.net> Mon, 21 March 2022 21:23 UTC

Return-Path: <buraglio@es.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 530D93A0EBD for <v6ops@ietfa.amsl.com>; Mon, 21 Mar 2022 14:23:40 -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, HTML_MESSAGE=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=es.net
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 WsCT5MiaEbkT for <v6ops@ietfa.amsl.com>; Mon, 21 Mar 2022 14:23:36 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 A47753A0D2A for <v6ops@ietf.org>; Mon, 21 Mar 2022 14:23:35 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id m3so14715713lfj.11 for <v6ops@ietf.org>; Mon, 21 Mar 2022 14:23:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=es.net; s=esnet-google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=2WJdKPENy7WtzNp/7DPGTvgBVHBObiCUv8PnP2gb+mM=; b=nHN88rdWYJHDTjUiB62t7Wj3ELGuTLnIykXrOpIAQFKHJLtmoTcUsPkzvNsuAr+5IU iQfrCM7IvXC2538OBOks6R1K5CdkQm0ZM7Txyr17fGdF6ZCrEO3hiCVGlcI2aicyGWPq ei7JKdA/Z8txzIQX4/DyrKXEJfvimtVYXfWGsuKCGsqgXO8bNePji7k10bBVyqGRZjq0 WMYJ72FdaqYyuXS8uEnny+udGmm2pI/rbS5BxBw19sVwtzYOPGZoVOQTqbfXqIL3YFUH plE6MFu0yY9YddiS4fSFAwx73+cEPLz1UfuXhfGqflD31vDkJ4sl+sfREBDc2k9N9Ze3 dvpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=2WJdKPENy7WtzNp/7DPGTvgBVHBObiCUv8PnP2gb+mM=; b=30w9C2mhmkdqCqJmeYpb9JK9ApAH/uICkjbLyxwqLp3Mr8DJdKEkAK5Tj5pVd59U7I 3lM1nfi/oU522H7ptU8vueVkkXOf1BjBYQi2VfzawZpdLiApLjS2ifxGrmD12IDRdUU1 leIutiFB+S67zf2AZjPrKJ6RpjccOzz2Kw6gXzBRjyNWY+0l5TQnI3oyn/l6/8v0Hjpl eQgX2RxUwYd/2mZsjiiC5VgpS+RO1SZ+bqtmj0Rv/RpeDanTaZB3sOtBG7uAfhMHRN+C NsRW3h5zcE1oLVbEJSKJrI04LCgiFmrbQdfRunJlHhlPlPhXRJYETYCUkFYo1kdkbXju jOYA==
X-Gm-Message-State: AOAM531LxWxeCVCBrPjKKvb3z6OOSZXxzLc50bOfCrmv72+EWu09yM4w iz8bm/rwBeFCqQjfVUfuy8sAmmv+qdd8zsqXNRMymOYlsM9nvEuB+cx0DrVp0mfQUfVn+rFSMFV LoSkWGxrQvH/ulmNvsb+dXAq07Y25hggQYWPI3VJcqncdqkV1EGw+fS1yezFENxJtCFfPFpvXRv cwemLC/Uk=
X-Google-Smtp-Source: ABdhPJxNQgdPOREU2zV+uB/bybSvVlYQwGazC791JzK7tRuKtcAfp1jfZZpcsra+vi/r/UHpsGlw1AnXjtFEz16kriU=
X-Received: by 2002:a05:6512:1148:b0:448:39c8:89d with SMTP id m8-20020a056512114800b0044839c8089dmr15583770lfg.644.1647897813271; Mon, 21 Mar 2022 14:23:33 -0700 (PDT)
MIME-Version: 1.0
References: <BE3310F7-692C-46E9-A75B-07C4C3C6476F@gmail.com>
In-Reply-To: <BE3310F7-692C-46E9-A75B-07C4C3C6476F@gmail.com>
Reply-To: buraglio@es.net
From: Nick Buraglio <buraglio@es.net>
Date: Mon, 21 Mar 2022 16:23:22 -0500
Message-ID: <CAM5+tA-9gH9GosUtKx8yhfHdAT=orPntw6m8q-bcWHWafz1AKg@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c9be1005dac11b41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7R4EkCUcX98NixqdlYNyklIDed0>
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: Mon, 21 Mar 2022 21:23:41 -0000

Enterprise input is difficult. Building interest is even harder for several
reasons, but the most prevalent reason I have seen is that there is a
severe lack of business case for deployment of IPv6 that enterprises can
see in short order. The key here is the timeframe. Most of even the largest
of enterprises are completely fine with - and even strongly advocate for -
private address space plus NAT, which many have conflated with a
security tool rather than a translation mechanism. Many larger enterprises
still rely on PA address space, IPv6 multihoming is significantly more
difficult for the same reasons that NAT is easy. Many of these
organizations do not have the expertise or the time to put IPv6 on the
radar until it is absolutely required by a business driver. These are
slowly coming, but they're slow. The slow rollout is adding to the
apprehension and laissez faire (at best) and outright refusal (at worst)
approach to consider IPv6.  De-mystifying the complex pieces are a huge
part of moving this forward. Making things approachable, easily consumable,
and friendly have been cornerstones to the experiences I have had
successfully deploying IPv6. To get enterprises interested it needs to be
worth their time in the short term and have wide and *emphatic* vendor
support across the enterprise platforms and for the protocol to be treated
as a first class citizen on those platforms, otherwise it is often viewed
as change for the sake of change. They need to be able to sample it and
model it in a way that is comfortable to them.
I don't believe that this is really a technology problem at its core.
Until we can make it work the same as what is believed to be "normal", it's
going to be a slog. When a vendor is asked if product X works without
legacy IP (or even supports IPv6) 95% need to say "well, yes, of course it
does" - or better yet, we should not need to ask. We don't need to ask if
things support IPv4, it's implied. The industry needs to be closer to that
mark.
Do I know how to get there? Not really. At this point I just yell as loud
as I can about IPv6 support everywhere I go and try to educate people the
best I can.

nb

On Mon, Mar 21, 2022 at 3:33 PM Fred Baker <fredbaker.ietf@gmail.com> wrote:

> I have thought some about the discussion we had in the V6ops meeting about
> increasing operational input. Several suggestions were made: add a separate
> meeting, segregate parts of the meeting, attend the IEPG, use an interim,
> and so on. One thought that I had was to schedule a meeting at RIPE in May.
>
> None of these address what seems to me to be a core problem: ISPs are
> deploying, but enterprise isn’t. How do we get enterprise on board?
>
> Sent using a machine that autocorrects in interesting ways...
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>