Re: [IPv6] Can We Turn the Global Network into a Firewall Protecting All End Users?

Jared Mauch <jared@puck.nether.net> Wed, 24 April 2024 20:26 UTC

Return-Path: <jared@puck.nether.net>
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 62756C14F61A; Wed, 24 Apr 2024 13:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.994
X-Spam-Level:
X-Spam-Status: No, score=-1.994 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=puck.nether.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6vgU1jvIXr7; Wed, 24 Apr 2024 13:26:36 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAB64C14F5FB; Wed, 24 Apr 2024 13:26:35 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2602:fe55:64:0:718e:2b7a:fa3d:bba3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jared) by puck.nether.net (Postfix) with ESMTPSA id 7B4B554008D; Wed, 24 Apr 2024 16:26:05 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 puck.nether.net 7B4B554008D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=puck.nether.net; s=default; t=1713990365; bh=OLsz82k1Ng9pOHm7pTPa+TYIlGfa6yPrvE25A6FCXbo=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=eRUBpOONxMduWu2MD0Q6o+eN91LYKugHCu0ZsS7pQAbCsXSwVEnNiqQpZj3dYg40V ozGBX/sNHH2sW7o46yVdjfoU9J9QqVEq3rttzPCTxLbtdfVJgN+nHoNzsL1Xb+5x4Q zueraXfnizHQ1t3GH6iW+EFDjpOODIrj3sQdKgGIT2cgYkwgcbFVhxfFP6OobO56aR LXU2PfgfYGrIJ/fEsMyh4l00/n7leq1LtHmNpNVIXoqudXqOsGPhcZu7XwXmzYKLrD SHaQjMPA/ydLg2Hz7MDp4RJ9mAT9DskmUQm8GikLgxMPu5zyhnYNXeBH8v1qH5VSEz Wz08xCceMhY7g==
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAMkkUf1brxg1DhPiv-93PtN1pOyGsGhLopGbxTW6jgz+c92wTA@mail.gmail.com>
Date: Wed, 24 Apr 2024 16:26:21 -0400
Cc: Mark Andrews <marka@isc.org>, 6man <ipv6@ietf.org>, 6lo@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <23BC33A7-5BF5-4F14-B29A-D5FBCC587DD2@puck.nether.net>
References: <CAMkkUf3UqjJbuBQwvaOAsV=4VwPYBCUTBNLfUB2ZF4gAv4CHnQ@mail.gmail.com> <D4424AFD-CE28-46C8-808E-A41979973DA4@isc.org> <CAMkkUf1brxg1DhPiv-93PtN1pOyGsGhLopGbxTW6jgz+c92wTA@mail.gmail.com>
To: Hubert W <hubert.wisniewski@gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/q1COPOCNfUlEo1hZi1mXkkcet5A>
Subject: Re: [IPv6] Can We Turn the Global Network into a Firewall Protecting All End Users?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 24 Apr 2024 20:26:40 -0000

I had thought of doing something where the device could send a profile to the router/DHCP server that says “here’s the ports, dns names, etc.. that I will be using”.

This would then permit only those related bits to flow.

- Jared

> On Apr 24, 2024, at 4:23 PM, Hubert W <hubert.wisniewski@gmail.com> wrote:
> 
> 
> 
> On Wed, Apr 24, 2024, 07:46 Mark Andrews <marka@isc.org> wrote:
> 
> 
> > On 23 Apr 2024, at 16:51, Hubert W <hubert.wisniewski@gmail.com> wrote:
> > 
> > Dear WG,
> > 
> > 
> > I woke up with one idea and I would like to challenge it. 
> > In IPv6, every device receives a routable address. To protect endpoints effectively, we require firewalls to filter unwanted traffic. 
> 
> Apart from packet volume this is a false assertion.  No device should require a firewall.
> 
> > But what if we could stop such traffic at the source? Could this approach convince more people toward adopting IPv6?
> > 
> > According to RFC 7381: “In a /48 assignment, typical for a site, there are then still 65,535 /64 blocks.” and “All user access networks should be a /64.”
> 
> /64 is typical not required.
> 
> > Can we use then bit 63 to convey a message: “I don’t want any incoming traffic initiated towards me!!!”? Of course a response would be accepted.
> > 
> > We could divide the /64 allocations into two groups: one for servers, and these accept incoming traffic (bit 63 = 0):
> > 
> > for example 2001:0db8:0000:0000::/64
> > 
> > And the second group: endpoints, these never accept incoming traffic (bit 63 = 1):
> > 
> > for example 2001:0db8:0000:0001::/64
> > 
> > We only need all systems to understand the message. If a router or firewall sees such a packet, then drops it. 
> > Every TCP packet with flag SYN, where destination address (IPv6) has bit 63 equal 1, must be dropped.
> 
> All the world is not TCP.  Additionally for TCP the filtering device would need to track state and that implies symmetric routing.
> 
> > Would it be theoretically possible?
> 
> No.
> 
> > Best regards
> > 
> > Hubert Wisniewski
> > 
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
> I think there would be no issue with asymmetric traffic if we only check SYN flag, but I understand that is not a good idea. Thank you for your opinion. 
> 
> Hubert Wisniewski 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------