Re: [Snac] Relax the requirement on a single 'root' ULA prefix generated by stub router?

Erik Auerswald <auerswal@unix-ag.uni-kl.de> Fri, 25 August 2023 13:08 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 62F62C15199D for <snac@ietfa.amsl.com>; Fri, 25 Aug 2023 06:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 tAmuJSb71gIE for <snac@ietfa.amsl.com>; Fri, 25 Aug 2023 06:08:07 -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 B6C6CC15199A for <snac@ietf.org>; Fri, 25 Aug 2023 06:08:07 -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 37PD8Dg6029703 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 25 Aug 2023 15:08:13 +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 37PD85WW000473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 25 Aug 2023 15:08:05 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 37PD852g000471; Fri, 25 Aug 2023 15:08:05 +0200
Date: Fri, 25 Aug 2023 15:08:05 +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: <20230825130805.GA26200@unix-ag.uni-kl.de>
References: <DU0P190MB1978F18F16051B3ECEE03159FD12A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <20230810111719.GA13659@unix-ag.uni-kl.de> <20230816092035.GA11872@unix-ag.uni-kl.de> <DU0P190MB197890A2C768BDB86C0632D5FD1DA@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DU0P190MB197890A2C768BDB86C0632D5FD1DA@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/kpYL7SdEn3IjiWx-HQLnrvoSU_o>
Subject: Re: [Snac] Relax the requirement on a single 'root' ULA prefix generated by stub router?
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: Fri, 25 Aug 2023 13:08:13 -0000

Hi,

On Thu, Aug 24, 2023 at 11:49:12AM +0000, Esko Dijk wrote:
> 
> Thanks for the summary of points.
> 
> > A host implementing the RFC 6724 section 10.6 procedure would detect
> >    the stub router's 48-bit ULA prefix on the AIL as local.  
> 
> If there are say N stub routers, each with own stub network, there
> would be N different ULA prefixes.
> [...]
> We assume also that the case of one auto-assigned ULA prefix and one
> GUA prefix on the AIL is not applicable, since the stub router only
> assigns the ULA prefix if there's nothing else already assigned.

The current draft seems to rely exclusively on RFC 4191 type C hosts by
advertising stub prefixes as off link on the AIL.

Always using a single ULA prefix per stub network, combined with
advertising a subnet from this ULA prefix on the AIL as on-link, could
be an additional method to also support RFC 4191 type A/B hosts that
implement RFC 6724 section 5 rule 5.5.  Such a host would use a ULA from
the stub network's prefix as source address, and would use a stub router
connected to that sepcific stub network.

The RFC 6724 section 10.6 procedure is not even required for this to work.

An explicit requirement for hosts to implement the behavior of RFC 4191
type C to work with SNAC would IMHO improve the draft.

Best regards,
Erik