IETF Logo Mail Archive

Re: [Snac] draft-ietf-snac-simple-01 review comments

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 24 July 2023 19:16 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 7FF89C151B12 for <snac@ietfa.amsl.com>; Mon, 24 Jul 2023 12:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=sandelman.ca
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 FXMDAmGP_OzU for <snac@ietfa.amsl.com>; Mon, 24 Jul 2023 12:16:01 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 69134C151B03 for <snac@ietf.org>; Mon, 24 Jul 2023 12:16:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9AAA838990; Mon, 24 Jul 2023 15:15:59 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id RnEYAedD5cPW; Mon, 24 Jul 2023 15:15:59 -0400 (EDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:40a:34ff:fe10:f571]) by tuna.sandelman.ca (Postfix) with ESMTP id 9A1033898F; Mon, 24 Jul 2023 15:15:58 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1690226158; bh=dLA4o5ylN4CcqVHYQvsjqzgC33OMH3kjYIH6wF5xHdM=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=Ai7fApNqBijWbRWPad8SIrcjIJ76AVMf5fV3b6Joo89yZn1TsWaxMCK5IwY1D+ct4 NW9knIpAlgvYK27v9kpQXisZFMatvDggSDIw0/Kdd0IqVeEPs+W4JBXRAfj2SV2+wf DaKoa13rePSe7y3lLC09j5QlHpFEqZkBi3P61kEEGevSvLUY2UBTEuABsvb4pAUcud zrrblYbXKpAfQmwmWZRfzsRTyUTKOBRGGEthe3Us/td3tGXF5UzDBO0P1kWQ8o7N93 bJOnHsaodXryq4Vtn8z80NKR/JEV9mjhhF1MgDf2K6EmFDZtrXcc+wEPQFHrjuigFb mufosNRSOGN4A==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 81AA390; Mon, 24 Jul 2023 15:15:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
cc: "Darren Dukes (ddukes)" <ddukes=40cisco.com@dmarc.ietf.org>, "snac@ietf.org" <snac@ietf.org>
In-Reply-To: <CAPt1N1nNXrCK_E9DgH9NyjMEu4_ROAcWS3iO6-oPF7LVkrLFyQ@mail.gmail.com>
References: <BL1PR11MB5366C82D3ECC50F851E4EC9DC87F9@BL1PR11MB5366.namprd11.prod.outlook.com> <19968.1684504919@localhost> <CAPt1N1kMOsSj_NYDF=Kigjm51GMZ7YzVVdxiwkva4vABmv1dOw@mail.gmail.com> <CAPt1N1nNXrCK_E9DgH9NyjMEu4_ROAcWS3iO6-oPF7LVkrLFyQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 24 Jul 2023 15:15:58 -0400
Message-ID: <27390.1690226158@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/kZoKaOGjhtkFnaAIKv5d4L0SxZY>
Subject: Re: [Snac] draft-ietf-snac-simple-01 review comments
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: Mon, 24 Jul 2023 19:16:05 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > This would not work for WiFi networks, but possibly we could use the
    > SSID for this case? Maybe there's not enough randomness in it, but

That seems okay for me, if you put it through some PRF.

    > since it only has to be unique to the AIL, and can't be routed, perhaps
    > that's okay. Is there any other equivalent thing we could do? I'm
    > highly inclined to just get rid of the "try to remember old prefixes"
    > text, because our experience is that this approach failed pretty often,
    > resulting in reachability problems that took significant time to
    > resolve.

So, the stub network gets renumbered after a mains failure?
(How many thunder storms you get this July?  We got 3-4/week it seems)
Some battery powered devices will survive and have the old prefixes.

I'm just not keen on this.

Does the problem go away if the home router does PD?


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email