Re: [Snac] Relax the requirement on a single 'root' ULA prefix generated by stub router?
Erik Auerswald <auerswal@unix-ag.uni-kl.de> Thu, 10 August 2023 11:17 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 CAC85C151098 for <snac@ietfa.amsl.com>; Thu, 10 Aug 2023 04:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 xA2eQUb1AEn3 for <snac@ietfa.amsl.com>; Thu, 10 Aug 2023 04:17:23 -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 9866EC151092 for <snac@ietf.org>; Thu, 10 Aug 2023 04:17:23 -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 37ABHRKr095330 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 Aug 2023 13:17:27 +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 37ABHK8H016803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 Aug 2023 13:17:20 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 37ABHJeJ016799; Thu, 10 Aug 2023 13:17:19 +0200
Date: Thu, 10 Aug 2023 13:17:19 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
Cc: "snac@ietf.org" <snac@ietf.org>
Message-ID: <20230810111719.GA13659@unix-ag.uni-kl.de>
References: <DU0P190MB1978F18F16051B3ECEE03159FD12A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DU0P190MB1978F18F16051B3ECEE03159FD12A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/Z5i_uzRxps1Hnt3qIN221tisA9E>
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: Thu, 10 Aug 2023 11:17:28 -0000
Hi, On Wed, Aug 09, 2023 at 11:06:23AM +0000, Esko Dijk wrote: > One issue found during implementation is that snac-simple-02 requires > a single ULA prefix as a 'root' to derive further ULA prefixes from > for the stub network and the AIL. > But in practice it may be desirable to use 2 ULA prefixes for these > respective cases. The proposal is to relax the requirement to allow > such use. > > Issue is created here: > https://github.com/ietf-wg-snac/draft-ietf-snac-simple/issues/31 Using a single ULA prefix may allow to implement the example procedure from [RFC 6724 section 10.6.][1], specifically the following part: | Since ULAs are defined to have a /48 site prefix, an implementation | might choose to add such a row automatically on a machine with a ULA. [1]: https://www.rfc-editor.org/rfc/rfc6724#section-10.6 My impression was that ULA generation in SNAC was intended for local IPv6 connectivity inside a site. I might be worth it to provide compatibility with existing specifications that cater to ULA use for IPv6 connectivity inside a site. Best regards, Erik P.S. I do not know of any implementation of RFC 6724 section 10.6.
- [Snac] Relax the requirement on a single 'root' U… Esko Dijk
- Re: [Snac] Relax the requirement on a single 'roo… Erik Auerswald
- Re: [Snac] Relax the requirement on a single 'roo… Erik Auerswald
- Re: [Snac] Relax the requirement on a single 'roo… Esko Dijk
- Re: [Snac] Relax the requirement on a single 'roo… Erik Auerswald
- Re: [Snac] Relax the requirement on a single 'roo… Erik Auerswald
- Re: [Snac] Relax the requirement on a single 'roo… Michael Richardson