[Int-area] Follow-up on Internet addressing presentation at IETF111 int-area meeting

Dirk Trossen <dirk.trossen@huawei.com> Mon, 02 August 2021 08:17 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4793A12EC for <int-area@ietfa.amsl.com>; Mon, 2 Aug 2021 01:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 VNQyWLJ_8JIb for <int-area@ietfa.amsl.com>; Mon, 2 Aug 2021 01:17:34 -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 8BC013A12DC for <int-area@ietf.org>; Mon, 2 Aug 2021 01:17:34 -0700 (PDT)
Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GdW825lnRz6F86Q for <int-area@ietf.org>; Mon, 2 Aug 2021 16:17:22 +0800 (CST)
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by fraeml703-chm.china.huawei.com (10.206.15.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 2 Aug 2021 10:17:30 +0200
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 2 Aug 2021 09:17:30 +0100
Received: from lhreml701-chm.china.huawei.com ([10.201.68.196]) by lhreml701-chm.china.huawei.com ([10.201.68.196]) with mapi id 15.01.2176.012; Mon, 2 Aug 2021 09:17:29 +0100
From: Dirk Trossen <dirk.trossen@huawei.com>
To: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Follow-up on Internet addressing presentation at IETF111 int-area meeting
Thread-Index: AdeHdrf0TumK8wXfRLOQ3Yo3+glhjg==
Date: Mon, 02 Aug 2021 08:17:29 +0000
Message-ID: <d1e8fdb2f359484183451c2b72bb1a84@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.8.170]
Content-Type: multipart/alternative; boundary="_000_d1e8fdb2f359484183451c2b72bb1a84huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/nOgWwezGGwCXU_6RFcQFMeZ4ewg>
Subject: [Int-area] Follow-up on Internet addressing presentation at IETF111 int-area meeting
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 08:17:39 -0000

Dear all,

As a follow-up from the int-area meeting on 31st of July, we would like to solicit comments and feedback on the Internet addressing problem statement and gap analysis drafts (https://datatracker.ietf.org/doc/draft-jia-intarea-scenarios-problems-addressing/ and https://datatracker.ietf.org/doc/draft-jia-intarea-internet-addressing-gap-analysis/, respectively).

For this, let me restate the key questions we asked at the end of the presentation during the meeting:

1) Have the extensions shown that gaps to addressing have been identified by the Internet community?
2) Are the identified issues worth thinking of different approaches to solving the identified gaps?

Additionally, are there contributors to this discussion who would want to work with us to push the discussion and associated material further?

Any views on those questions are welcome.

Best regards,
Dirk (on behalf of the co-authors)