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

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 18 November 2021 17:29 UTC

Return-Path: <mcr@sandelman.ca>
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 B0B573A0826 for <anima@ietfa.amsl.com>; Thu, 18 Nov 2021 09:29:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 GAgS716vP815 for <anima@ietfa.amsl.com>; Thu, 18 Nov 2021 09:29:19 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9EBF3A0824 for <anima@ietf.org>; Thu, 18 Nov 2021 09:29:19 -0800 (PST)
Received: from dooku.sandelman.ca (cpe788a207f397a-cmbc4dfb96bb50.sdns.net.rogers.com [174.116.121.43]) by relay.sandelman.ca (Postfix) with ESMTPS id 383FC1F456; Thu, 18 Nov 2021 17:29:17 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id AD2561A0558; Thu, 18 Nov 2021 12:29:14 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Liyizhou <liyizhou@huawei.com>, Anima WG <anima@ietf.org>
In-reply-to: <08dfbe37ed2c4b1a94d5be81cb4b8623@huawei.com>
References: <163463033712.25024.851885585891035829@ietfa.amsl.com> <7095c13c-1ad2-3b6e-25f2-657faa06fbaa@gmail.com> <32375.1635271594@localhost> <08dfbe37ed2c4b1a94d5be81cb4b8623@huawei.com>
Comments: In-reply-to Liyizhou <liyizhou@huawei.com> message dated "Thu, 28 Oct 2021 03:59:06 -0000."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 18 Nov 2021 12:29:14 -0500
Message-ID: <172188.1637256554@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/fDkrZxGYjfL6sHElJKoYF7WSRXo>
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, 18 Nov 2021 17:29:25 -0000

Liyizhou <liyizhou@huawei.com> wrote:
    > Thank you for your careful reading. It takes me some time to have some
    > more thinking on the draft.

    > You are right that most devices have management interface with L3
    > capability.

    > The difficulty we met was when IPv4 is in use the management interface
    > needs to get to DHCP server first to get its IP. DHCP is a BUM traffic.
    > RFC3927 defined a self-configured IPv4 address, but AFAIK it is
    > implemented in some host OS but not on network nodes.  The expected
    > L2ACP in my mind has the function of L2 loop-free reachability before
    > the management interface of the nodes obtains IP via DHCP.

I feel that we've been over this many times... it's even in RFC8994, and
Brian has written a lot about this.
It seems that you are stuck on the 40 year old IPv4 model of doing layer-2 tricks.

    > I understand an IPv6 link-local address can be used for ACP even when
    > the data plane is IPv4. I tried to talk to some engineers/admins if
    > they would like to use it in such a way. Some think it is ok.

Clearly there is a lot of reluctance, and there is really no words I can add
to change that.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-