Re: [v6ops] Thoughts about wider operational input

Toerless Eckert <tte@cs.fau.de> Tue, 22 March 2022 10:41 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 1A8573A0F00 for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 03:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, 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
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 FvZ2GYISG1Ur for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 03:41:25 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (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 59D233A0EF2 for <v6ops@ietf.org>; Tue, 22 Mar 2022 03:41:25 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id DAEF758C4B0; Tue, 22 Mar 2022 11:41:19 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4EE384EA9BA; Tue, 22 Mar 2022 11:41:19 +0100 (CET)
Date: Tue, 22 Mar 2022 11:41:19 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
Cc: v6ops@ietf.org
Message-ID: <Yjmnz+xszUhoEWSA@faui48e.informatik.uni-erlangen.de>
References: <52661a3d-75dc-111a-3f23-09b10d7cb8d4@gmail.com> <A72CDDDB-CDCE-4EAF-B95E-997C764DB2C4@gmail.com> <9175dc32-45c1-e948-c20a-3bcc958b77b9@gmail.com> <YjmJQMNgnJoSInUw@Space.Net> <D75EF08F-6A41-41B2-AFB2-649CBCC1D83E@consulintel.es> <CAPt1N1nRnYUFA=yyJHx6t52yqWbmcd2Tf1H8gQuCZBd3Q3VqJw@mail.gmail.com> <7F4AEB43-4B24-4A21-AE9D-3EB512B98C46@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <7F4AEB43-4B24-4A21-AE9D-3EB512B98C46@consulintel.es>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/K8nQaDq8UbF3jTwXKQu6oU0lXGk>
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 10:41:30 -0000

If i have a network i control, call it enterprise, IoT, home, whatever. And i want to
multi-home. And the host-stacks of my devices are all different and have problems with
the most advanced IPv6 features. Why would it not be a desirable feature for me as the
end-user to have an IPv6/IPv6 NAT on the router towards the 3 Internet connections to
which i multi-home ? Sure, we can probably list some downsides, but they need to be
weighted against the benefits for me as an end user. Not ?

Cheers
    Toerless

On Tue, Mar 22, 2022 at 10:34:22AM +0100, JORDI PALET MARTINEZ wrote:
> You’re right. Let’s say it in a different way, as may be my first email was not clear on this.
> 
>  
> I don’t think we want again to repeat the NAT problems, so NPT is not a valid solution for me.
> I think in the future almost every site could want to be multihomed, in some cases “n” links active, many other cases just as a backup.
> This means that renumbering is not (probably) a valid choice in any cases.
> Can we make PI work in such “huge scale” scenario?
> Can source-address forwarding work and solve all that, or we need that and/or something else.
>  
> 
> Only if we solve this, organizations could learn that NAT with IPv6 is not the solution, but something better that provides the same results, and no need to have “private” addresses, because the way NAT is offering a “different” addressing inside and outside is not NAT per-se, but statefull firewalling.
> 
>  
> 
> Regards,
> 
> Jordi
> 
> @jordipalet
> 
>  
> 
>  
> 
>  
> 
> El 22/3/22, 10:27, "v6ops en nombre de Ted Lemon" <v6ops-bounces@ietf.org en nombre de mellon@fugue.com> escribió:
> 
>  
> 
> Is it really hncp that we needed here?  I think the key tech we need is source-address-based forwarding, and babel i think has delivered that. Granted, getting that into soho routers is a problem. 
> 
>  
> 
> On Tue, Mar 22, 2022 at 10:11 JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
> 
> Maybe the terminology is not the most appropriate and we should talk about "organizations", because there are many types of networks that have the same problem and those are not enterprises (such as government sites, NGOs, etc.).
> 
> The problem is the same regardless of the "size" of the organization. The difference is that "today" most SMEs don't have that problem because they don't have PI, but it may turn the same when they realize that not being PI have renumbering issues if changing the ISP. Of course, again, if we talk about a "small" SME, then may not be an issue, they only have 40 or 50 devices to renumber (your mileage will vary), not easy but not "terrible".
> 
> On the rest of Gert comments, definitively I agree, and specially on our big mistake not working further on HNCP.
> 
> Regards,
> Jordi
> @jordipalet
> 
> 
> 
> El 22/3/22, 9:31, "v6ops en nombre de Gert Doering" <v6ops-bounces@ietf.org en nombre de gert@space.net> escribió:
> 
>     Hi,
> 
>     On Tue, Mar 22, 2022 at 11:42:12AM +1300, Brian E Carpenter wrote:
>     > I agree with Jordi that multihoming is a genuine impediment. What isn't generally realised is that it's a problem of scale when considering at least 10,000,000 enterprises, much more than it's a problem of IPv6 itself.
> 
>     What is "an enterprise"?
> 
>     My stance on this is that for "largely unmanaged SoHo networks" - which
>     could be called "small enterprise" - dual-enduser-ISP with dual-/48 or
>     NPT66 gets the job done in an easy and scalable way (HNCP would have
>     been great, but IETF politics killed it).
> 
>     "Enterprise that truly need their own independent fully managed network
>     with multiple ISP uplinks and fully routed independent address space"
>     are probably way less than 10 million...
> 
>     Half of them do not want Internet access anyway, just access to their
>     ALGs that will do the filtering and TLS inspection and everything, and
>     then out to the Internet as a new TCP session (= could be done with
>     DMZ islands of upstream-provider-allocated space just fine).
> 
> 
>     We need to work on our marketing regarding multihoming.  "What is it that
>     you get, what is the cost, which of the variants do you want, and why...?"
> 
>     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
> 
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org
>     https://www.ietf.org/mailman/listinfo/v6ops
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 
> _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops 
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 

> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops