IETF Logo Mail Archive

Re: Automatically connecting to stub networks...

Ted Lemon <mellon@fugue.com> Thu, 03 December 2020 14:38 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 CE8103A0E60 for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, NO_DNS_FOR_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 iSwQ9FRZdTfC for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:38:47 -0800 (PST)
Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 D98413A0D79 for <6man@ietf.org>; Thu, 3 Dec 2020 06:38:46 -0800 (PST)
Received: by mail-qv1-xf32.google.com with SMTP id g19so1014923qvy.2 for <6man@ietf.org>; Thu, 03 Dec 2020 06:38:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=pKsYem8HIzXfmlrMTjfNQK2S0qyyjsRMk0dGkWBhaKI=; b=aA1mxKRDVXomyV36jnArfcfZamytvjAFVBwwI9/6rl7KIDF5P4ongAiyr/81f/H0u7 SZffOwm4KnaPIUCMw6bqo6hX4OjUjG7DQiXen1UlQWC5foxP8wVK8ypyCEt4lsdgYomS QduIn6/T8+yBGGgMsGzKjx8M1JxeSIjxzWPGgBOVh8Zh2D6hS1Qhnbz++hVjOcVwRB1W t/Qx+e1nohI8zGy4tWLrSh04yN6tHH0pDjLj46iO4uv4mzGpsCzGuUC99lQ9/NlB1ub5 hXmyBLgSSWOEwidTNunXZq3tjKE/Qf9smkIlCY1C1jpmTHSyew/M/lEKPPVTy9LG1/vn Tohw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=pKsYem8HIzXfmlrMTjfNQK2S0qyyjsRMk0dGkWBhaKI=; b=NS8vm4ecVpdIKTp77vuM72CTZQe9Rg9r51lP//18lqUZRwuLnT6Si7lbqijwXZVbnD qNLy4rTo6biZ+Df4NSlo5GiWeG+Pwpk2N9u520xlEbkecse14NN4d3X2IBf0OeEwOwBK PztDGIfeieXWUh6G9r9T2V8YXiLf4e0Eu8PsOjVtRQsWnmX8emxyL3kPz0u9Q0pYpoM1 8Sqykm6i9TVtEukqbP96/R7X5KU4XpylieRYqyDgPPYt2kD/2TFZ/42ZZ5Gj0eyZnOvy hyMeoafnxt3ebQXkw6HojR5YsvzMJT4WspDdS0BFb0TvULlLY/B/apgmAuECfGkURw5p TjwQ==
X-Gm-Message-State: AOAM533kjAh59YPDZiallCeD7fP+nBGHY2qtQXc+Z/HRQqPS9I1BZMUF iXfq6GliMXRXp+OMsipIR5Q+hI6D5ny7slaH
X-Google-Smtp-Source: ABdhPJx7uNRuKVU+VE4pQU0O/1yQQ6OeftYu9goxg25NdqY3NBPJprYbfmc5xH59tvzKy7D6QYxxlg==
X-Received: by 2002:a0c:e50a:: with SMTP id l10mr3359598qvm.55.1607006325889; Thu, 03 Dec 2020 06:38:45 -0800 (PST)
Received: from [192.168.4.114] (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id 17sm1365435qtb.17.2020.12.03.06.38.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Dec 2020 06:38:45 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-2E85E102-0919-4662-A839-8CA50D2809B8"
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Automatically connecting to stub networks...
Date: Thu, 03 Dec 2020 09:38:44 -0500
Message-Id: <824E0042-44E7-4C56-8411-E917F9E22D05@fugue.com>
References: <a2482dd470524c9c80e6faddbca334e2@huawei.com>
Cc: 6MAN <6man@ietf.org>
In-Reply-To: <a2482dd470524c9c80e6faddbca334e2@huawei.com>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
X-Mailer: iPhone Mail (18C62)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nuwdQuB5e3zb30EiHc0_eizuUjw>
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:56 -0000

Eduard, you still haven’t actually describe the problem you think you see. Can you explain why source address selection matters in this case and what specifically could go wrong?

> On Dec 3, 2020, at 09:31, Vasilenko Eduard <vasilenko.eduard@huawei.com> wrote:
> 
> 
> 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.
>  
> Ed/
> From: Ted Lemon [mailto:mellon@fugue.com] 
> Sent: 3 декабря 2020 г. 17:21
> To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
> Cc: 6MAN <6man@ietf.org>
> Subject: Re: Automatically connecting to stub networks...
>  
> On Dec 3, 2020, at 5:01 AM, Vasilenko Eduard <vasilenko.eduard@huawei.com> wrote:
> It is the very principal question what should happen 1st on the host: next hop or source address choice?
>  
> Can you explain why you think there’s a conflict here? I’m not seeing it.
>  
>

v2.23.0 | Report a Bug | By Email