Re: [Anima] I-D Action: draft-yizhou-anima-l2-acp-based-ani-00.txt

Liyizhou <liyizhou@huawei.com> Thu, 28 October 2021 06:58 UTC

Return-Path: <liyizhou@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C71933A0ABE for <anima@ietfa.amsl.com>; Wed, 27 Oct 2021 23:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 S26vxnnXmi-W for <anima@ietfa.amsl.com>; Wed, 27 Oct 2021 23:58:16 -0700 (PDT)
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 CFEE43A0ABA for <anima@ietf.org>; Wed, 27 Oct 2021 23:58:15 -0700 (PDT)
Received: from fraeml743-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Hfx9B64Jvz6H6pX; Thu, 28 Oct 2021 14:53:34 +0800 (CST)
Received: from kwepeml100005.china.huawei.com (7.221.188.221) by fraeml743-chm.china.huawei.com (10.206.15.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Thu, 28 Oct 2021 08:58:12 +0200
Received: from kwepeml500003.china.huawei.com (7.221.188.182) by kwepeml100005.china.huawei.com (7.221.188.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Thu, 28 Oct 2021 14:58:10 +0800
Received: from kwepeml500003.china.huawei.com ([7.221.188.182]) by kwepeml500003.china.huawei.com ([7.221.188.182]) with mapi id 15.01.2308.015; Thu, 28 Oct 2021 14:58:10 +0800
From: Liyizhou <liyizhou@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Anima WG <anima@ietf.org>
Thread-Topic: [Anima] I-D Action: draft-yizhou-anima-l2-acp-based-ani-00.txt
Thread-Index: AQHXxL87hT/5hOAYtkuQqb43ioGX8avallyAgACc+ECACeZEgIACvTvg
Date: Thu, 28 Oct 2021 06:58:10 +0000
Message-ID: <0ab849833ec14a1494a89f1035e90a97@huawei.com>
References: <163463033712.25024.851885585891035829@ietfa.amsl.com> <7095c13c-1ad2-3b6e-25f2-657faa06fbaa@gmail.com> <b267b71a0ee04522a218620c57d126c6@huawei.com> <633.1635271761@localhost>
In-Reply-To: <633.1635271761@localhost>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.98.176]
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/anima/9o7P0uMJM0eJ72DzxRMiXEXOPwM>
Subject: Re: [Anima] I-D Action: draft-yizhou-anima-l2-acp-based-ani-00.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2021 06:58:21 -0000

Hi Michael,

Please see inlines with [yz]. Thanks.

Yizhou


-----Original Message-----
From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: Wednesday, October 27, 2021 2:09 AM
To: Anima WG <anima@ietf.org>
Subject: Re: [Anima] I-D Action: draft-yizhou-anima-l2-acp-based-ani-00.txt


Liyizhou <liyizhou@huawei.com> wrote:
    > A campus network may contain the different types of equipment, L2
    > switches,

unmanaged L2 switches?
Or managed L2 switches with L3 addresses for their control plane?

[yz] Right, also corrected in another email. It refers to something like "the interface cannot or is not configured to automatically get IP address without any external exchange."  

    > L3 routers, hybrid L2/L3 switches. To make things easy, it is
    > quite common that all the nodes are enrolled as layer 2 to form a layer
    > 2 topology.

Yes. It's a regular disaster when loops form and the STP turns off the wrong port, and then the network breaks.

[yz] Yes. We normally want to turn on STP on access ports and turn them off on trunk ports. Before getting plugged, it may not be so clear which ports will be used as trunk ports. So when turning off STP, there is a risk of loop though we basically trust network admin can do correct cabling.
The ambition is to form a L2 ACP without requiring STP and without requiring IP reachability first in the management plane. Too ambitious? 

    > Then a collection of the physical connection/topology would
    > be required to check to see if the cabling is correctly made.

SNMP/YANG collection of LLDP adjacency data would seem to be the correct process here.

[yz] It can be done in this way. But again, it requires IP reachability first. 

    > That is
    > to say, assuming using link-local unicast and multicast address to
    > reach each L2 port brings extra requirements to L2 devices as L2 ports
    > may never use those IP addresses for their real data plane forwarding.

That seems like the wrong way to do things.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide