IETF Logo Mail Archive

Re: [v6ops] Thoughts about wider operational input

Gert Doering <gert@space.net> Wed, 23 March 2022 05:57 UTC

Return-Path: <gert@space.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 5F0B23A0598 for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 22:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, 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=space.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 k01TCZNrOgNn for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 22:57:36 -0700 (PDT)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A9453A0490 for <v6ops@ietf.org>; Tue, 22 Mar 2022 22:57:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1648015057; x=1679551057; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=YbjNDVgxSc4X5gnxkNv4D5rrR6KzLVm7R03UNVcTU+Y=; b=V/zkXWWWkpYFdHERTTj2Z+8O7yX0IzLFvLCz3x7miwbXFx4PgDobp7tM 1ih5Lmm9WA4Ua2EQNG7YrMvU/VjlXbGGos4gXDhdzdRtFO68HP9O32xou JqchyzYRUI6hXQwaNfIDVCbDv2m4InnJMtwJw0hiFtmnk5dIFamj4OIeu npqUUVrAAoZwoChX/6n5saMkcIxKJ2NkihIuKrdJjypTNLbl1uIa1DS00 O/N7z6F6m1V4sICX3EL00VJnoQ8ZRrXwR6dEHEd8z1J10BqfZaEz6RZSl gAF79MvYFor6Kvo7+e/DhjNhrFMqdNmhz+/Bt3lC7TN8lYmFYsjolYlUJ w==;
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Mar 2022 06:57:33 +0100
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id D0B7E43758 for <v6ops@ietf.org>; Wed, 23 Mar 2022 06:57:32 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id C2D5E40CA3; Wed, 23 Mar 2022 06:57:32 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id BF9B41174FD; Wed, 23 Mar 2022 06:57:32 +0100 (CET)
Date: Wed, 23 Mar 2022 06:57:32 +0100
From: Gert Doering <gert@space.net>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Chongfeng Xie <xiechf@chinatelecom.cn>, IPv6 Ops WG <v6ops@ietf.org>
Message-ID: <Yjq2zKNQuDXJMUkp@Space.Net>
References: <BE3310F7-692C-46E9-A75B-07C4C3C6476F@gmail.com> <AD2EE5F7-150B-40ED-8542-872256326579@chinatelecom.cn> <CABNhwV1_1m_NqdKymKggjOqgQvzkLGCN9qN5NnmV2m_kZnkBLw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABNhwV1_1m_NqdKymKggjOqgQvzkLGCN9qN5NnmV2m_kZnkBLw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6RTOL49fBDcgZNioNU_TgP6NTko>
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: Wed, 23 Mar 2022 05:57:42 -0000

Hi,

On Tue, Mar 22, 2022 at 10:40:25PM -0400, Gyan Mishra wrote:
> How do you justify if everything works fine and if it???s not broken why fix
> it mantra.  That goes for even companies in the IT business.

Real Enterprise Networks are never "everything works fine", but usually
a horrible mess of internal NAT44, sometimes multiple layers.

I've been told by one enterprise customer that it sometimes takes them
2 weeks to troubleshoot "host A cannot reach host B" problems, because
of "nobody knows which addresses host A and host B should have, in network 
parts X, Y and Z, so it needs 5 different teams to debug this".

What is still missing is the understanding "the mess of grown bandaid-NAT
goes away with IPv6".

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

v2.23.0 | Report a Bug | By Email