IETF Logo Mail Archive

RE: Automatically connecting to stub networks...

Vasilenko Eduard <vasilenko.eduard@huawei.com> Thu, 03 December 2020 14:47 UTC

Return-Path: <vasilenko.eduard@huawei.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 D3E223A0C59 for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:47:31 -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, RCVD_IN_MSPIKE_H2=-0.001, 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 A067LRJVIfiR for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:47:30 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87A673A0C3A for <6man@ietf.org>; Thu, 3 Dec 2020 06:47:30 -0800 (PST)
Received: from fraeml706-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CmzBK4CF4z67Lgm for <6man@ietf.org>; Thu, 3 Dec 2020 22:44:25 +0800 (CST)
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Thu, 3 Dec 2020 15:47:26 +0100
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml703-chm.china.huawei.com (10.219.141.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 3 Dec 2020 17:47:26 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.2106.002; Thu, 3 Dec 2020 17:47:26 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: "otroan@employees.org" <otroan@employees.org>
CC: Ted Lemon <mellon@fugue.com>, 6MAN <6man@ietf.org>
Subject: RE: Automatically connecting to stub networks...
Thread-Topic: Automatically connecting to stub networks...
Thread-Index: AQHWVoMEIcqKzTjvV0WEUOTb/0Lf36nmAtVggAAc+wCAADOIgP//0TKAgAA0rrA=
Date: Thu, 03 Dec 2020 14:47:26 +0000
Message-ID: <2b6d6e3de97e4ffca174bbad739420d6@huawei.com>
References: <DA9CEF7E-44EA-44B0-AF07-2DAC4D29A59F@fugue.com> <59aeb842c7534e5ab24cde0426b5a4c9@huawei.com> <EBF0CBB1-4418-455B-A22A-05D97C704345@fugue.com> <a2482dd470524c9c80e6faddbca334e2@huawei.com> <93B4CC43-65AE-4BCB-A287-F9F42706997F@employees.org>
In-Reply-To: <93B4CC43-65AE-4BCB-A287-F9F42706997F@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.198.234]
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hpOv7yASOoZRf729rNzlqehkERE>
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:47:32 -0000

Hi Ole,
Strictly speaking yes:
After the job on 1st hop would be done
Additional source routing is needed between routing hops.

But here was the context of 1st hop. I did have the liberty to omit source routing discussion.
May be wrong.
Eduard
> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: 3 декабря 2020 г. 17:38
> To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
> Cc: Ted Lemon <mellon@fugue.com>; 6MAN <6man@ietf.org>
> Subject: Re: Automatically connecting to stub networks...
> 
> 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