Re: [Snac] Host Requirements for SNAC Use?
Erik Auerswald <auerswal@unix-ag.uni-kl.de> Sat, 26 August 2023 13:30 UTC
Return-Path: <auerswal@unix-ag.uni-kl.de>
X-Original-To: snac@ietfa.amsl.com
Delivered-To: snac@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C477C14CE54 for <snac@ietfa.amsl.com>; Sat, 26 Aug 2023 06:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 wJfZg5oHlmJo for <snac@ietfa.amsl.com>; Sat, 26 Aug 2023 06:30:41 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (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 4032CC14CE2E for <snac@ietf.org>; Sat, 26 Aug 2023 06:30:40 -0700 (PDT)
Received: from sushi.unix-ag.uni-kl.de (sushi.unix-ag.uni-kl.de [IPv6:2001:638:208:ef34:0:ff:fe00:65]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 37QDUkaq023615 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 26 Aug 2023 15:30:46 +0200
Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 37QDUcYE012695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 26 Aug 2023 15:30:38 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 37QDUc3l012694; Sat, 26 Aug 2023 15:30:38 +0200
Date: Sat, 26 Aug 2023 15:30:38 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
Cc: SNAC List <snac@ietf.org>
Message-ID: <20230826133038.GA10862@unix-ag.uni-kl.de>
References: <20230820182355.GA4872@unix-ag.uni-kl.de> <DU0P190MB1978ACB9522FD82E21D33619FD1DA@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <20230825145816.GB26200@unix-ag.uni-kl.de> <DU0P190MB1978FACC9B1BBDF7C036029EFDE3A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <20230825174224.GA2700@unix-ag.uni-kl.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20230825174224.GA2700@unix-ag.uni-kl.de>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/2ZR1_wjeaJHY1wtuRsCyDW-7pdY>
Subject: Re: [Snac] Host Requirements for SNAC Use?
X-BeenThere: snac@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Mailing list for discussing problems relating to the automatic connection of stub networks to existing infrastructure networks. " <snac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/snac>, <mailto:snac-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/snac/>
List-Post: <mailto:snac@ietf.org>
List-Help: <mailto:snac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/snac>, <mailto:snac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Aug 2023 13:30:42 -0000
Hi, On Fri, Aug 25, 2023 at 07:42:24PM +0200, Erik Auerswald wrote: > On Fri, Aug 25, 2023 at 03:33:17PM +0000, Esko Dijk wrote: > > [...] > > By the way, is there any potential issue that the stub-router-provided > > ULA prefix would somehow interfere with IPv4 connectivity? I'm assuming > > here that IPv4 provides a default route (e.g. via the home router/ISP) > > while the stub router does not provide a default route. > > That was the case in the past, but RFC 6724 introduced a "label" for ULA > that is distinct from GUA. Since matching labels are preferred, the match > between two IPv4 addresses (one label for IPv4) is preferred over the > mismatched labels of GUA and ULA. There is another possible failure case, > when a remote ULA is received via DNS although the traffic would have to > go via Internet. This case is solved in RFC 6724 by specifying a lower > "precedence" for ULA than for IPv4. (Not all hosts implement the latter > part, e.g., GNU/Linux has a higher preference for ULA than for IPv4.) The combination of Router Lifetime = 0 with an on-link ULA prefix with a lifetime > 0 might do the trick here, i.e., an RFC 4191 type A or B host might ignore the stub router and thus might treat all IPv6 destination addresses outside of that subnet as unusable. A type C host should use the stub router to reach the stub network. Best regards, Erik
- [Snac] Host Requirements for SNAC Use? Erik Auerswald
- Re: [Snac] Host Requirements for SNAC Use? Esko Dijk
- Re: [Snac] Host Requirements for SNAC Use? Erik Auerswald
- Re: [Snac] Host Requirements for SNAC Use? Esko Dijk
- Re: [Snac] Host Requirements for SNAC Use? Erik Auerswald
- Re: [Snac] Host Requirements for SNAC Use? Erik Auerswald