[Int-area] Introductions of 2 new drafts in Intarea wg

"Jiayihao (Network, 2012 Lab)" <jiayihao@huawei.com> Wed, 11 November 2020 17:36 UTC

Return-Path: <jiayihao@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 69B4B3A3149 for <int-area@ietfa.amsl.com>; Wed, 11 Nov 2020 09:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 818agRGetUtV for <int-area@ietfa.amsl.com>; Wed, 11 Nov 2020 09:36:05 -0800 (PST)
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 C2B063A21F4 for <int-area@ietf.org>; Wed, 11 Nov 2020 09:25:48 -0800 (PST)
Received: from fraeml701-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CWWmq1hD5z67H4Q for <int-area@ietf.org>; Thu, 12 Nov 2020 01:24:11 +0800 (CST)
Received: from dggemx704-chm.china.huawei.com (10.1.199.51) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 11 Nov 2020 18:25:46 +0100
Received: from dggemi759-chm.china.huawei.com (10.1.198.145) by dggemx704-chm.china.huawei.com (10.1.199.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1913.5; Thu, 12 Nov 2020 01:25:44 +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.1913.007; Thu, 12 Nov 2020 01:25:44 +0800
From: "Jiayihao (Network, 2012 Lab)" <jiayihao@huawei.com>
To: "int-area@ietf.org" <int-area@ietf.org>
CC: Sheng Jiang <jiangsheng@huawei.com>, "Yanshen (2012 NGIP)" <yanshen@huawei.com>, Dangjuanna <dangjuanna@huawei.com>, "Chenzhe (Z)" <chenzhe17@huawei.com>
Thread-Topic: Introductions of 2 new drafts in Intarea wg
Thread-Index: Ada4T9sJZA4NGY9GQp2Issc6yKJTrQ==
Date: Wed, 11 Nov 2020 17:25:44 +0000
Message-ID: <ce673442511b4a53bf400a5637aac5aa@huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.168.250]
Content-Type: multipart/alternative; boundary="_000_ce673442511b4a53bf400a5637aac5aahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/rJD7mHPNwwauVl-BzqcmBWnRmSU>
Subject: [Int-area] Introductions of 2 new drafts in Intarea wg
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: Wed, 11 Nov 2020 17:36:11 -0000

Dear All,

Last week I submitted 2 I-D on Intarea WG under the topic of a flexible IP address structure.
I'd like to share the key points of these 2 I-D before it could be discussed at IETF 109.

First, we see that increasingly networks expect a direct TCP/IP stack for its global reachability and facility. However, various scenarios naturally face challenges when adopting current IP protocol. As one example, satellite networks introduce routing oscillation due to topology dynamics, leading to low routing efficiency even though it is theoretically possible. The first I-D describe these well-recognized scenarios that prefer a "flexible" IP address structure. By "flexible" in this I-D, we mean that the IP address is constructed as multi-semantics and length variable.

Based on scenarios and the correlated requirements, the second draft describe an instance of a potential "flexible" IP address structure, i.e., FlexIP, and details the considerations behind the design. To still benefit from global reachability, FlexIP is expected to work only in limited domain (RFC8799) and be interoperable with IPv6. The main purpose of FlexIP design is to construct a flexible network address, and such address should be prospective enough to accommodate unforeseeable scenarios and futuristic requirements.

Attached below are 2 I-D that mentioned in this email.
I would be happy if you have any questions on this topic. Warmly welcome!

----------------

Draft 1: Scenarios for Flexible Address Structure
https://datatracker.ietf.org/doc/draft-jia-scenarios-flexible-address-structure/

Draft 2: Flexible IP: An Adaptable IP Address Structure
https://datatracker.ietf.org/doc/draft-jia-flex-ip-address-structure/


Thanks,
Yihao Jia.