Re: Automatically connecting to stub networks...

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 03 December 2020 18:25 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 6877B3A0B62 for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 10:25:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNhBoRRaRJSj for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 10:25:22 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43AED3A0B36 for <6man@ietf.org>; Thu, 3 Dec 2020 10:25:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1695D389CD; Thu, 3 Dec 2020 13:27:12 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id OA3Ifuoths_m; Thu, 3 Dec 2020 13:27:06 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 10131389CC; Thu, 3 Dec 2020 13:27:06 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1E38D1FB; Thu, 3 Dec 2020 13:25:13 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>, 6MAN <6man@ietf.org>
Subject: Re: Automatically connecting to stub networks...
In-Reply-To: <5143DC1F-321C-4FCD-9B56-372E492D4CDD@fugue.com>
References: <DA9CEF7E-44EA-44B0-AF07-2DAC4D29A59F@fugue.com> <59aeb842c7534e5ab24cde0426b5a4c9@huawei.com> <22203.1607003159@localhost> <5143DC1F-321C-4FCD-9B56-372E492D4CDD@fugue.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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: Thu, 03 Dec 2020 13:25:13 -0500
Message-ID: <30146.1607019913@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zJ0gSssTK7-kIAaNoNYYa-lCyRA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Dec 2020 18:25:24 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > On Dec 3, 2020, at 8:45 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    >> I don't understand how RFC7078 helps, given that a postulate of the
    >> stub-network is that the home/enterprise DHCPv6-server is not capable of
    >> being aware of the stub-network.

    > In order to get a prefix to advertise on the stub network, DHCPv6-PD
    > would work. Of course, no host on the stub network is ever going to do
    > DHCPv6-PD, or if they do they’ll fail, but the draft does in that sense
    > rely on DHCPv6-PD for the globally addressable prefix use case.

I'm assuming that it's the gateway that does DHCPv6-PD.
If that works, then we are done.
We don't necessarily need the ULA or the NAT64 at that point.
(Although, the delegated prefix might not be a GUA.)

It's when it does not work that I think your draft comes into play.
One is essentially bring IPv6 to a LAN where there might not any.
I think that's okay.
{I also think that the thing bring that ULA to the LAN should be a DHCPv6-PD
server as well: there could be another gateway that needs IPv6}

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