Internet addressing: Problem statement and Gap analysis

Jiayihao <jiayihao@huawei.com> Fri, 16 July 2021 12:01 UTC

Return-Path: <jiayihao@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 21A543A33E2 for <ipv6@ietfa.amsl.com>; Fri, 16 Jul 2021 05:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 Apwv-8_ZH_Rv for <ipv6@ietfa.amsl.com>; Fri, 16 Jul 2021 05:01:51 -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 674853A33E3 for <ipv6@ietf.org>; Fri, 16 Jul 2021 05:01:51 -0700 (PDT)
Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GR8gt3XV6z6H7fd for <ipv6@ietf.org>; Fri, 16 Jul 2021 19:50:34 +0800 (CST)
Received: from dggemi761-chm.china.huawei.com (10.1.198.147) 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; Fri, 16 Jul 2021 14:01:48 +0200
Received: from dggemi759-chm.china.huawei.com (10.1.198.145) by dggemi761-chm.china.huawei.com (10.1.198.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 16 Jul 2021 20:01:47 +0800
Received: from dggemi759-chm.china.huawei.com ([10.1.198.145]) by dggemi759-chm.china.huawei.com ([10.1.198.145]) with mapi id 15.01.2176.012; Fri, 16 Jul 2021 20:01:47 +0800
From: Jiayihao <jiayihao@huawei.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Internet addressing: Problem statement and Gap analysis
Thread-Topic: Internet addressing: Problem statement and Gap analysis
Thread-Index: Add6OVL1ZxoKCG1fSb2qQjWIzsCQ+gAALWYg
Date: Fri, 16 Jul 2021 12:01:47 +0000
Message-ID: <b9c070ccba0f47d9b5b4cf8b663bc47b@huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.233.142]
Content-Type: multipart/alternative; boundary="_000_b9c070ccba0f47d9b5b4cf8b663bc47bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/l9txI255R_Bbr5CozhJ_ZSlQ_dA>
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: Fri, 16 Jul 2021 12:01:56 -0000

Dear all,



We have submitted two companion I-Ds on issues regarding Internet addressing, continuing the discussion on Internet addressing started at IETF110.



The first draft (https://datatracker.ietf.org/doc/draft-jia-intarea-scenarios-problems-addressing/) provides an update on various communication scenarios and issues identified in those scenarios regarding addressing. Those issues lead ultimately to outlining a problem statement for a discussion to re-think the approach to extensions to Internet addressing.



The second draft (https://datatracker.ietf.org/doc/draft-jia-intarea-internet-addressing-gap-analysis/) builds on this problem statement by providing an analysis of extensions to identified key properties of Internet addressing. Those extensions are presented along various methodologies for realizing them and examples that have done so, while their existence is being seen as evidence for the existence of gaps to the original Internet addressing albeit filling those gaps through a plethora of point extensions rather than a coherent architectural approach. It is this point extension approach that has led to a number of issues, such as complexity, fragility, among others, that the draft outlines.



We believe that the intended goal of re-thinking Internet addressing may be of interest to this community and we would therefore invite you to not only review those drafts but provide your comments and feedback - please do so on the current 'home' for this discussion, the int-area mailing list of the IETF.



Best regards,

Yihao Jia (on behalf of all authors)