IETF Logo Mail Archive

Re: Automatically connecting to stub networks...

otroan@employees.org Thu, 03 December 2020 14:38 UTC

Return-Path: <otroan@employees.org>
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 215153A0D89 for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 coeQAWx2TazR for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:38:18 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D31E83A0D99 for <6man@ietf.org>; Thu, 3 Dec 2020 06:38:18 -0800 (PST)
Received: from astfgl.hanazo.no (77.16.50.176.tmi.telenormobil.no [77.16.50.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 60F134E11A45; Thu, 3 Dec 2020 14:38:17 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id B82F246C3DF6; Thu, 3 Dec 2020 15:38:13 +0100 (CET)
From: otroan@employees.org
Message-Id: <93B4CC43-65AE-4BCB-A287-F9F42706997F@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_06C0E3FC-B962-4816-A47A-66878E52558B"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
Subject: Re: Automatically connecting to stub networks...
Date: Thu, 03 Dec 2020 15:38:13 +0100
In-Reply-To: <a2482dd470524c9c80e6faddbca334e2@huawei.com>
Cc: Ted Lemon <mellon@fugue.com>, 6MAN <6man@ietf.org>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
References: <DA9CEF7E-44EA-44B0-AF07-2DAC4D29A59F@fugue.com> <59aeb842c7534e5ab24cde0426b5a4c9@huawei.com> <EBF0CBB1-4418-455B-A22A-05D97C704345@fugue.com> <a2482dd470524c9c80e6faddbca334e2@huawei.com>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8SatgWVTTQ8LmECLs8KZTqoPEoI>
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:38:27 -0000

Vasilenko,

> You do discuss how RFC 4191 would help.
> This RFC is not needed at all if source address chosen 1st
> Because after source address selection it is trivial to decide about next hop
> Without any tweaking of routing tables on the host.
> 
> Hence, You stick to the current mode of host operation: next hop is decided 1st.
> 
> I agree with RFC 8028 that it should be changed.
> RFC 8028 is the only comprehensive solution now for the general MHMP case.

No, unfortunately not. That only solves the problem when a host is directly connected to the exit routers.
You need SADR in addition. See RFC8043 and its references.

Best regards,
Ole

v2.23.0 | Report a Bug | By Email