Re: [Int-area] What is in a name - draft-ietf-intarea-schc-ip-protocol-number

Luigi IANNONE <luigi.iannone@huawei.com> Thu, 06 April 2023 09:11 UTC

Return-Path: <luigi.iannone@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 DF024C13AE43 for <int-area@ietfa.amsl.com>; Thu, 6 Apr 2023 02:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i_KE83W0F_cu for <int-area@ietfa.amsl.com>; Thu, 6 Apr 2023 02:11:29 -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 0CA9BC151553 for <int-area@ietf.org>; Thu, 6 Apr 2023 02:11:29 -0700 (PDT)
Received: from lhrpeml100005.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4PsbHG1N1Pz6D9LD; Thu, 6 Apr 2023 17:07:22 +0800 (CST)
Received: from lhrpeml500002.china.huawei.com (7.191.160.78) by lhrpeml100005.china.huawei.com (7.191.160.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Thu, 6 Apr 2023 10:11:25 +0100
Received: from lhrpeml500002.china.huawei.com ([7.191.160.78]) by lhrpeml500002.china.huawei.com ([7.191.160.78]) with mapi id 15.01.2507.023; Thu, 6 Apr 2023 10:11:25 +0100
From: Luigi IANNONE <luigi.iannone@huawei.com>
To: Robert Moskowitz <rgm-ietf@htt-consult.com>, tom petch <ietfc@btconnect.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] What is in a name - draft-ietf-intarea-schc-ip-protocol-number
Thread-Index: AQHZZ7Eh6IuaPKSH/UeNL4pbOOMa5q8czE2AgAAkHoCAAQ7/oA==
Date: Thu, 06 Apr 2023 09:11:25 +0000
Message-ID: <641e931b1ebb4f708b7d43413772ba41@huawei.com>
References: <cfd8779b-1dbd-572d-8432-3b9769665712@htt-consult.com> <AM7PR07MB6248DAFD838C2C00ACB15A2EA0909@AM7PR07MB6248.eurprd07.prod.outlook.com> <8c6e4cc0-3dc8-de67-f921-a8b6d7374381@htt-consult.com>
In-Reply-To: <8c6e4cc0-3dc8-de67-f921-a8b6d7374381@htt-consult.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.206.215.36]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/eUoNo7aG5UF05GisnwY9_4JHbds>
Subject: Re: [Int-area] What is in a name - draft-ietf-intarea-schc-ip-protocol-number
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Internet Area WG 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: Thu, 06 Apr 2023 09:11:33 -0000

Hi,

[snip] 
> Thus the old draft name no longer reflects the new content.  There is a
> mechanism when you submit a draft to link it to a prior draft so the draft
> history is properly maintained (it does not support linking to multiple prior
> drafts or splitting an old draft into multiple, for that you have to ask for
> human help).
[LI] 
[LI] Actually linking to several previous drafts is feasible, here is an example: https://datatracker.ietf.org/doc/draft-iannone-ip-addressing-considerations/ 

For the naming, draft-ietf-intarea-schc-protocol-numbers-00  is just right.

Ciao

L.