IETF Logo Mail Archive

Re: Automatically connecting to stub networks...

Ted Lemon <mellon@fugue.com> Thu, 03 December 2020 14:40 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 4BB4D3A0CE3 for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:40:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Level:
X-Spam-Status: No, score=-1.885 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, 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 VXi0aQ9FaiWx for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:40:14 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 C5F613A0C3A for <6man@ietf.org>; Thu, 3 Dec 2020 06:40:13 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id f27so1448353qtv.6 for <6man@ietf.org>; Thu, 03 Dec 2020 06:40:13 -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=BnmR5MiTp/L3zhwq5jaPs8sUPmy2J173EhbV/ottVjc=; b=z7sTvgCUltNf98/SGsk8M8vovlkTnnKRXroNX8GxKOUA5LUBXW+rTD2xye5MF+TNFK 4PEPaVFMkx0BKuLmppgNkaj+uiQHsLJzWi/gSCr3qFHLSFOsZ2t5icfTh/+mp15kh7zP yuuBwzOt++ehFym3QBNcge/eulqswQP7rWjLAyhCjXEX6ScQye3knUTe4pXq67Kmzxx+ JZffkcLkuYcCZS1YH2hsqUmk+6gNQxkVWUwVEc3JbbBEBUfGAXQo8RFHqi6yiX+Ta6pu GHg3koDXFMW28udAanfGr+GqZEHrzCak6rRfVckCMrU0dqxx4FOO1QhA1/dkuOgAt5uq U5ow==
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=BnmR5MiTp/L3zhwq5jaPs8sUPmy2J173EhbV/ottVjc=; b=qy5JFpMKpgYSNuwdhhT69u33YAHg88FB3Yfuhi+p8zKh13znZmk3PeRfjeOcf0+RVa S4vE+YsA+7telfjpnwf4ysDs7EdSx23hYQsaGfj5nYFrfeBRV+5h7TqjyUZfR0Dk9K0B 44yDXOoz3dXpIiL1JELC3/z2oHetrIdISJLbPYc7qAi5LXWr69IJ9bAPQ1rnYBlHBM1B uzSV3R7pEeobYM6xYFk3zKC4Er88/56ndU6jVte53sPGiA5mzrWWQl7CUYlsCRpSoksA 6wDUVOoZ7oP154phCeOuDUOX9QfYHZVftqDZrMHWYseK+RZxWXgfTg6OvEpxyVtOs2cd Hwyg==
X-Gm-Message-State: AOAM533WGxPJ7D9hRtFszMn1rK1IB0sIqoXY+p4lr93F0ehErUtPrUId fFaPnJrjjE7cEVTMoX5ENEFE9jwWzS5NNy5A
X-Google-Smtp-Source: ABdhPJw0DLzLJuY6AppCcUjfodtQR+MSajqYg9ZHk1FGQ7FEddAY0z0qHysf8zZvbgVINEpzc5K0yg==
X-Received: by 2002:ac8:24a1:: with SMTP id s30mr3543707qts.89.1607006412762; Thu, 03 Dec 2020 06:40:12 -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 j19sm1536308qkk.119.2020.12.03.06.40.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Dec 2020 06:40:12 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-0FFA5B81-64DD-483B-977A-2E4538747586"
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:40:11 -0500
Message-Id: <6C299891-EB14-47BF-92EB-22264B0C1043@fugue.com>
References: <824E0042-44E7-4C56-8411-E917F9E22D05@fugue.com>
Cc: 6MAN <6man@ietf.org>
In-Reply-To: <824E0042-44E7-4C56-8411-E917F9E22D05@fugue.com>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
X-Mailer: iPhone Mail (18C62)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ISk4Pp-bvMqCm8VBiRt9uDYCBCM>
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:40:16 -0000

Oh, do you mean source address selection for hosts on the stub network?  That’sa good point. 

> On Dec 3, 2020, at 09:38, Ted Lemon <mellon@fugue.com> wrote:
> 
> 
> 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