Re: [Anima] ipv4-only network

"Michael H. Behringer" <michael.h.behringer@gmail.com> Thu, 05 August 2021 11:29 UTC

Return-Path: <michael.h.behringer@gmail.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 750363A0C6F for <anima@ietfa.amsl.com>; Thu, 5 Aug 2021 04:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 GDPOj1_2Tdpr for <anima@ietfa.amsl.com>; Thu, 5 Aug 2021 04:29:10 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 015B73A0C67 for <anima@ietf.org>; Thu, 5 Aug 2021 04:29:09 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id z4so6064160wrv.11 for <anima@ietf.org>; Thu, 05 Aug 2021 04:29:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=sKJMjstm//12nVNtyMdLfnzdrAi101/V2Cy6eZucqSo=; b=bCii3P0YURJVmdSuhidvByKMbw2w/COZbCNqQEIPSxj384OsiP/5BeixWQZlxG+3e/ s6gSCWfFNZqax72AlxaZILicre8lbR8kY1M+Wcdbzxv95ZOvFw2yjX6SjauRzBTQe9TV G6LWY8vTGwLINdVUmJAN5KF17yT0mCMopTovh37Xv5TapUd+Na8HmKKymo3Vi6DzTL7/ BTLOTBs9rWSyUQCEcx4kBILI2NNqKez9k+2+2RjnBwqoJFsvr3E4FrxKsfGhHLtTPzBu htPWfe9+ROdbBiQPaYu8P5VYzzPQ+pfb0lFTSev/NvDekrVF2Y8uEBiVTCj4+VCR4E/c OO3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=sKJMjstm//12nVNtyMdLfnzdrAi101/V2Cy6eZucqSo=; b=JL6VJ6FcL0c+GFYcxx90z8g8RYcp+I9WBzPylTDT5nwpY78qWjr/n5ZqjK52pYXwXc Tikxut34u1+UoO1VNlXhvSu9HAAKPeWgqAkhj7Lh91DXBZVKS5AjEPR7v0anKUHYHTf7 C5TrwDjg9HdHHEtsWR2xXw6E2uUB8Ak1D2tIAcKsako1r3tMxSLNRfRIC3pHn4f3ZngE Igf7DbUYJalzkRzjrBZ4Q831bV2Oj0z8jzGRe2mHcY4IIY+4Xz22o0Yn9+s0U8yRhkZR ojNafs+sxP82Aud7uL8DbTQwzvibPvad4G80fBCQIdET83dzBvP+LqsTSt5SIYyeO8lM FgAA==
X-Gm-Message-State: AOAM532gfYCUJB/vMmOcTXoeL1ekWyWxxr3Zdw3nwgPckJXMqnovA6MG bF3pULiMHh7t7rNnACxIDPhCjqv5jmo=
X-Google-Smtp-Source: ABdhPJwWJBzVs9892YVzC3I6xEETSR/pY+PSWJwwN6r9v6pOPV+/WbSWunQzmrJjCmfraHFtABnIHQ==
X-Received: by 2002:adf:d20e:: with SMTP id j14mr4481730wrh.177.1628162947267; Thu, 05 Aug 2021 04:29:07 -0700 (PDT)
Received: from ?IPv6:2a01:cb1d:111:eb00:ccd4:c2fb:c955:1cf9? ([2a01:cb1d:111:eb00:ccd4:c2fb:c955:1cf9]) by smtp.gmail.com with ESMTPSA id x12sm6039012wrt.35.2021.08.05.04.29.06 for <anima@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 05 Aug 2021 04:29:06 -0700 (PDT)
From: "Michael H. Behringer" <michael.h.behringer@gmail.com>
X-Google-Original-From: "Michael H. Behringer" <Michael.H.Behringer@gmail.com>
To: anima@ietf.org
References: <24e8e37e34a34bcf9201e7f7a7478794@huawei.com> <CANMZLAZTMUYwVwuv-WoTwAWFne0cWF8QC+4pFWnbkGc3wWp5YA@mail.gmail.com>
Message-ID: <7eb89c6c-b72b-27a1-6b9d-11d0f2dfbf0d@gmail.com>
Date: Thu, 05 Aug 2021 13:29:06 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CANMZLAZTMUYwVwuv-WoTwAWFne0cWF8QC+4pFWnbkGc3wWp5YA@mail.gmail.com>
Content-Type: text/html; charset="utf-8"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/IH2FH3mZ-BHyhPBfUko8KIE-OdE>
Subject: Re: [Anima] ipv4-only network
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, 05 Aug 2021 11:29:15 -0000

To add to that, we had a short but quite intensive debate about whether we need an IPv4 ACP, a few years back, after this document was proposed:

https://datatracker.ietf.org/doc/html/draft-du-anima-ipv4-acp" rel="nofollow">https://datatracker.ietf.org/doc/html/draft-du-anima-ipv4-acp

We came to the conclusion that it makes no sense to propose an IPv4 ACP; the ACP is an entirely new concept, so there was the opinion that there is no need for backwards compatibility with IPv4.

Michael

On 05/08/2021 12:08, Brian Carpenter wrote:
We don't require any IPv6 enablement by the NOC. All we require is standard dual stack on all autonomic devices, which creates link-local addresses. Everything else in the ACP is automatic. Why waste any effort on an IPv4 version? (The operator can do whatever they want in the data plane, of course.)

Regards,
    Brian Carpenter
    (via tiny screen & keyboard)

On Thu, 5 Aug 2021, 20:01 Liyizhou, <liyizhou@huawei.com> wrote:

Hi,

 

RFC8994 explained the main reasons that ACP is based on IPv6 addressing are simplicity and scale.

I wonder if there was/is any interest in defining and deploying ACP in IPv4-only network without requiring IPv6 enablement.

For example, as ULA and link-local address schemes are not available in ipv4 networks, whether and how to establish the ACP channel? (RFC3927 defines IPv4 link-local address config, but it is not a full functional substitute of ipv6 link-local address in ipv4 world in my understanding.)

 

There might be discussions and thoughts in this aspect in earlier days in the community. I would be very appreciated if anyone can point them out.

 

Thank you,

Yizhou

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima" rel="noreferrer noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/anima

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima" rel="nofollow">https://www.ietf.org/mailman/listinfo/anima