IETF Logo Mail Archive

Re: Automatically connecting to stub networks...

Ted Lemon <mellon@fugue.com> Thu, 03 December 2020 14:27 UTC

Return-Path: <mellon@fugue.com>
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 AD6113A1109 for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level:
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NO_DNS_FOR_FROM=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 mdRhs4W0a1VG for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:27:18 -0800 (PST)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D447E3A0DF9 for <6man@ietf.org>; Thu, 3 Dec 2020 06:26:53 -0800 (PST)
Received: by mail-qk1-x731.google.com with SMTP id q22so2178597qkq.6 for <6man@ietf.org>; Thu, 03 Dec 2020 06:26:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Qcen/hc+cMixNgUhZreBeuNmiXgBR7kgfPh7mOWtFlk=; b=XblJENz74X6jLJobo1qgMbJi//GzTm5FAlGOeMk0HPZ9ST9b1Z59/6PWVoFCJbh8R3 DZfo2XgHHRlVz0h78heoMMD9cgbccwTy0RBt9g8OYnX7NKh5+02qAPPF6iz1uEoxoyhO VOaKSZosx4qgps94Fp2divHHmTM7sxu768Fa8H1N8S/ePtsHFgs6inB2gYMhpzaEUXxu Q7xRj3twTOr/VUKLEAzK644WFvN4TO9EPhCEiSktq53m4oZa5UCI2WO1PBX5NRiH8e5L 7C7MTdkEKJoVM01VEEy32059A7HyAY2HFCcExbWVX2irOz/6bXH7cjZuyETYtFy/QKSm 3VkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Qcen/hc+cMixNgUhZreBeuNmiXgBR7kgfPh7mOWtFlk=; b=SKvobSzOpuL+OdRTu6LqMx4PY4Cs4boeI4p3W2h70KRqfAiq6lLyZMjmIIZFx07JJ+ Q52qXvBIqPXthN8EDUGJG7K7jXsAqCEs5h9t6H9t/D/W1vXRcUCUsQuufxCDUFegE0HB gtZ2sFKqqTtxPwp0Kp+XZ3/qYZ4Cj2/thAn+0GJPrChtqBv2R0cXxa+cN1UO4qKAJjjQ tyVdYlZdmgY5mWOnBPEKPraH0jF/9xA8xCwFYl7ItDbDY8091aq+YHUAECJ2Sd/P6ChC fJTQdqvLAM/HlA/8zZOfI+SoP0YuWBz0Yt8KVtog7A92dX8G7bn4iUOdP8MFvQ8VsbsX 6iEw==
X-Gm-Message-State: AOAM531n88xoOP9VuQ2C4dv9txpOasJejz1+b+c6FZrqX+aZc+2WWg9D zDF7EWljEMyXiJq6l+d21pexVQ==
X-Google-Smtp-Source: ABdhPJwmQXIeBzWssfRhfMNboWzZrBkO3IDJv7pXQHGcFrsyy+HFIyfIG4CoMPMS3niT/E5MjDXWcA==
X-Received: by 2002:a05:620a:16cd:: with SMTP id a13mr2984120qkn.11.1607005612185; Thu, 03 Dec 2020 06:26:52 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id c68sm1511552qkb.17.2020.12.03.06.26.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Dec 2020 06:26:51 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <B85D498A-2B34-4636-8BDA-A23352CD34CC@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C011C66F-0717-4CA4-9151-558A9F5FAEFD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Subject: Re: Automatically connecting to stub networks...
Date: Thu, 03 Dec 2020 09:26:50 -0500
In-Reply-To: <a72f29b6c7dd4429a299087e93ebbd2a@huawei.com>
Cc: 6MAN <6man@ietf.org>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
References: <DA9CEF7E-44EA-44B0-AF07-2DAC4D29A59F@fugue.com> <a72f29b6c7dd4429a299087e93ebbd2a@huawei.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ofIrZbsyR0LJd7dL5foCM1_m96w>
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 14:27:23 -0000

On Dec 3, 2020, at 5:15 AM, Vasilenko Eduard <vasilenko.eduard@huawei.com> wrote:
> I believe that it is very big question should it be L2 or L3 solution for stub router?

An L2 solution simply isn’t possible when the media in question have such different characteristics. E.g., there’s no way to do this with 6lowpan.  The closest you can easily get is proxy ARP, which is discussed in the document. This is particularly problematic if you have multiple ingresses to the stub network. Implementation becomes complex. Doing it at L3 is much simpler. My goal here is to come up with simple solutions, not interesting problems. :)

In any case, an L2 solution is simply a different solution. It’s not a stub network. If you can make it work for you, great, but if you can’t, that’s when a stub network solution may be a better choice.

v2.23.0 | Report a Bug | By Email