IETF Logo Mail Archive

RE: Automatically connecting to stub networks...

Vasilenko Eduard <vasilenko.eduard@huawei.com> Thu, 03 December 2020 14:17 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 C33F63A0A3E for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:17:00 -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 V2Ll1CUs0cuk for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 06:16:58 -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 A56493A09A8 for <6man@ietf.org>; Thu, 3 Dec 2020 06:16:58 -0800 (PST)
Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CmyW763gLz67Kx0; Thu, 3 Dec 2020 22:13:55 +0800 (CST)
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by fraeml707-chm.china.huawei.com (10.206.15.35) 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 15:16:57 +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:16:56 +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:16:56 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
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/0Lf36nmAtVggAATHYCAADsYYA==
Date: Thu, 03 Dec 2020 14:16:56 +0000
Message-ID: <c0fe4ddd864c4036a851678d32b504aa@huawei.com>
References: <DA9CEF7E-44EA-44B0-AF07-2DAC4D29A59F@fugue.com> <59aeb842c7534e5ab24cde0426b5a4c9@huawei.com> <22203.1607003159@localhost>
In-Reply-To: <22203.1607003159@localhost>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xXkmWPXyxNQA5UjDQ7VGWayGG5A>
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:17:01 -0000

Hi Michael,
You do not understand, because you have deleted explanation.
If I would read what is left below - I would not understand too.
Ed/
> -----Original Message-----
> From: Michael Richardson [mailto:mcr+ietf@sandelman.ca]
> Sent: 3 декабря 2020 г. 16:46
> 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 Eduard <vasilenko.eduard@huawei.com> wrote:
>     > Hi All,
>     > This draft contradicts to RFC 8028. If IETF would approve both then
>     > overall progress would be “nowhere”.
> 
> I don't understand.
> It seems to entirely depend upon RFC8028, leverage it.
> 
>     > Alternative general approach is explained in RFC 7157: synchronous
>     > download of the same policy into SASA (by RFC 7078) and next hop
>     > selection (by RFC 4191), then current priority for next hop selection
>     > could be preserved.
> 
> I don't understand how RFC7078 helps, given that a postulate of the stub-
> network is that the home/enterprise DHCPv6-server is not capable of being
> aware of the stub-network.
> 
> If it could, then we could do DHCPv6-PD.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email