Re: [EXTERNAL] Re: Limited Domains:

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 17 April 2021 01:59 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7963A0DF8 for <ipv6@ietfa.amsl.com>; Fri, 16 Apr 2021 18:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Rq4WlG2bp1lW for <ipv6@ietfa.amsl.com>; Fri, 16 Apr 2021 18:59:19 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 A45103A0DEB for <6man@ietf.org>; Fri, 16 Apr 2021 18:59:19 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id 10so10600362pfl.1 for <6man@ietf.org>; Fri, 16 Apr 2021 18:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=JfkUWOVfaj6LvRHGuwPAO8ujYPC8SlPbkhf+JnNOsIo=; b=dV3AZ9n5sURqamEDTeTkq/I3VaspJ9NQLKoBAkzRUDFyQossNPq+bJPIAprotVRo5c /ZA9PP+WgHakhFh8WKnXxKeLnyqvOms6vV+TKEXTiw3qWQ1DYhZqY3ct6zyJ8GSUUg3L vXQj9vMDPthXCGxM05Q1qzctsPQJFdu9xz8nSqPSZpzQn9gGBw9gzzZdqhOkTpWdJ3yM PyGPm2Wl7c8Pb/oRv9otjsVjWtVrETvSQpgtoCxm+kW7acY5UVb3sXSMUN0If/PQn3mV D5IVvYINFhyX/bFZR3ZZfwSjPRVoXu/vesWr96lAg6SA986uXJCU2Hk0eCoF+CBEW6k0 vs3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=JfkUWOVfaj6LvRHGuwPAO8ujYPC8SlPbkhf+JnNOsIo=; b=ZlCAqXPghI2kpKM4VXlhPeAvSI32atNLmKRiZw+8JI7Yixl0hoKSeGBoxtKgzkQ8HW ZgNsHkReJ2X/lHC8XyscbcMfrs8UlclUDRZRsvMDuuTNY4IGxfM2hTwYdayimhtSUwCR Dwhy1g09EspUfh442O1IhKI8PZmhq2MPTrrouDtbsbdYzkjVmTmSOUJJCoXTT6mE0+D5 Z/MfXyCtuq1H2klMHHW4vo7M+0blU/yMbwLHGe9IliuQN/q2+e23DnlO73gBDG7T+9vf 0R1kyl20yJ4uyfVGkbu9GEE9Tw7sKhQqNRXazab8i0xPSU7FK8g0qbV0UDgUGh/bPf// siQQ==
X-Gm-Message-State: AOAM530fYbO7I/DNQ/uqTtcRK4hClThk3ykTm86Bww7LwXocwS79sLct ewPgYNaFkcTB7FpBxEmdzQKIROiIW2GRyA==
X-Google-Smtp-Source: ABdhPJxX2t0P8Mhouc/cL1Dj2sKeaG2dwQ6ll7QIYvdvEhXK2oz+4lwmTOnDWUIYxEq7x/BNFTc4BQ==
X-Received: by 2002:a63:a47:: with SMTP id z7mr1586333pgk.350.1618624758288; Fri, 16 Apr 2021 18:59:18 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.131.14]) by smtp.gmail.com with ESMTPSA id t15sm5975475pgh.33.2021.04.16.18.59.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Apr 2021 18:59:17 -0700 (PDT)
Subject: Re: [EXTERNAL] Re: Limited Domains:
To: Robert Raszuk <robert@raszuk.net>
Cc: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, "6man@ietf.org" <6man@ietf.org>
References: <BL0PR05MB5316991D4124AD85BC69392AAE709@BL0PR05MB5316.namprd05.prod.outlook.com> <1697a0f8-b3cd-9f7d-d610-305b5305c9a1@gmail.com> <4077E736-0092-44C6-80D1-E094F468C00C@gmail.com> <12878114-5c26-86f9-89c3-bcfa10141684@gmail.com> <CALx6S35NBfVJmjqVwhNV3nui2avUOXn6ySMG3cxx2AvGkwr_Ow@mail.gmail.com> <08A6C3D2-A81C-413A-81B3-EFAAA9DBCCE5@cisco.com> <5b68beb6-a6f9-828b-5cca-9c5ec2bfbea7@foobar.org> <126B0A5E-B421-4B1F-AAEB-ABD48FFA4289@cisco.com> <CALx6S35yxqAqWJVhav-=+TB2ZyYttAFfsLNs6Btt+QUx__aQ1w@mail.gmail.com> <9b22cfe4-22eb-3977-2d25-79eb61370291@gmail.com> <17DC585D-3378-42BF-8CD0-67676BF0CFD3@gmail.com> <CAOj+MMG2wy-ag=O7vQO+GkoW+OcAr6CN38vsMU9X0bh=LhF2wA@mail.gmail.com> <57d84a666ee94eeea600377b862d2ed7@boeing.com> <CAOj+MMFAauP-XEVBxgMk1khKPeeS0k6d4P_+-GUc14XuCkunTQ@mail.gmail.com> <c05fb52b-78c9-a43f-d1fd-6c4b6477d5fe@gmail.com> <CAOj+MMFTPS0CDO1Z6S4pKLqDuNYPvqwCTYoToJCAXr0gjoB7uA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <8a366a28-8371-90b5-ab8d-a731b5d821b4@gmail.com>
Date: Sat, 17 Apr 2021 13:59:13 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAOj+MMFTPS0CDO1Z6S4pKLqDuNYPvqwCTYoToJCAXr0gjoB7uA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6OIhKU5XWNkRirZoll3-PApjFN4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Apr 2021 01:59:24 -0000

On 17-Apr-21 12:30, Robert Raszuk wrote:
> Hi Brian,
>  
> 
>     On that argument the SPRING WG should never have been chartered and the 6MAN WG should never have approved RFC8754. Also, we should never have defined diffserv in 1998. And NAT, of course, would be excluded by definition, and RFC1918 from 1996 would need to be obsoleted.
> 
> 
> I beg to differ in the perspective on this. 

Not so much. I was simply trying to underline that the IETF has been actively defining limited domain solutions for many years, while claiming to define Internet-wide protocols.
 
> I would rather see 6man understanding the reality, understanding that hardware engineering and innovation there have moved on and that protecting original father's of IPv6 fixed size header wall garden does not make sense any more. 
> 
> Yet we still see orthodox protection over technically obsolete dogmas. 

I also see people from the hardware side of the router and firewall world asking for less flexible header design. There's quite a tussle going on here.
 
> As we see in parallel there is equally interesting discussion on use of the last 64 bits of IPv6 address happening. This is pretty interesting considering that even most conservative folks agree that IPv6 address should be assigned to the interfaces. So I define a logical interface which is an anchor to internal switching vector and different processing function. 
> 
> Last RFC1918 just talks about address allocation - not sure how is this related to any of this discussion ... you mean that the notion that private addresses are not routable globally is the key point here ? 

I should probably have pointed the finger at RFC1597 (Address Allocation for Private Internets). But yes, that was an explicit enabler for limited domains within which you could do whatever private protocol you wanted, between a subset of hosts, in 1994.

> I thought the concern is with router's processing capabilities not with where such processing is subject to happen.

Routing is only one aspect. Limited domains exist for all kinds of reasons. Like it or not (and some people don't like it), the current architecture of the Internet includes thousands (probably millions) of limited domains.

> 
> Best,
> R.
> 
> PS. Btw FWIW my interest and former activity in 6man list on SR topics where not so much motivated in that I like SR. Much more I oppose hardcore resistance to protect something which technology wise is all pretty much obsoleted. 
> 
> And I fully understand why this is going on like this - to make sure new features do not break existing IPv6 world ... it is just that protecting something which technically is already addressed and keeping innovation gated is IMO not the best strategy for networking. 

Yes. That's exactly why I worked on RFC8799. 

    Brian