[Idr] Let's polish the draft draft-ietf-idr-5g-edge-service-metadata to be a RFC candidate
Cheng Li <c.l@huawei.com> Fri, 21 June 2024 20:16 UTC
Return-Path: <c.l@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F25FBC14F696; Fri, 21 Jun 2024 13:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 KPIR7oqW9DUK; Fri, 21 Jun 2024 13:16:15 -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 EC6E4C14F694; Fri, 21 Jun 2024 13:16:14 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4W5TBS3P9Hz6K66G; Sat, 22 Jun 2024 04:15:44 +0800 (CST)
Received: from lhrpeml100001.china.huawei.com (unknown [7.191.160.183]) by mail.maildlp.com (Postfix) with ESMTPS id ED7C11400D7; Sat, 22 Jun 2024 04:16:11 +0800 (CST)
Received: from dggpemf100009.china.huawei.com (7.185.36.128) by lhrpeml100001.china.huawei.com (7.191.160.183) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 21 Jun 2024 21:16:10 +0100
Received: from dggpemf500009.china.huawei.com (7.185.36.50) by dggpemf100009.china.huawei.com (7.185.36.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Sat, 22 Jun 2024 04:16:08 +0800
Received: from dggpemf500009.china.huawei.com ([7.185.36.50]) by dggpemf500009.china.huawei.com ([7.185.36.50]) with mapi id 15.02.1544.011; Sat, 22 Jun 2024 04:16:08 +0800
From: Cheng Li <c.l@huawei.com>
To: "draft-ietf-idr-5g-edge-service-metadata@ietf.org" <draft-ietf-idr-5g-edge-service-metadata@ietf.org>
Thread-Topic: Let's polish the draft draft-ietf-idr-5g-edge-service-metadata to be a RFC candidate
Thread-Index: AdrEF63fyoD3Oph/SsC8kI9QzyDopw==
Date: Fri, 21 Jun 2024 20:16:08 +0000
Message-ID: <481b14075bdf41cdb062627d978e3267@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.70.229]
Content-Type: multipart/alternative; boundary="_000_481b14075bdf41cdb062627d978e3267huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: W2SMIHLM6VKJDG4XLNWSWYY2FSGNN64H
X-Message-ID-Hash: W2SMIHLM6VKJDG4XLNWSWYY2FSGNN64H
X-MailFrom: c.l@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "idr@ietf.org" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Let's polish the draft draft-ietf-idr-5g-edge-service-metadata to be a RFC candidate
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/9a944hCyKZi_86z0kbERSRESV2I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>
Hi Linda, Two more comments from my side. Please see l https://github.com/ietf-wg-idr/draft-ietf-idr-5g-edge-service-metadata-14/issues/25 l https://github.com/ietf-wg-idr/draft-ietf-idr-5g-edge-service-metadata-14/issues/26 Basically, we need to add the descriptions of all the fields in TLVs, including Length field, reserved field, and flag, in order. Also, need to add text to handle the cases that if something wrong occur, like error handling. A good example is https://datatracker.ietf.org/doc/html/draft-ietf-idr-segment-routing-te-policy-26. You know, we are implementing this document, and this will be published as a standard track RFC, so let's make a deep review of the draft, modifying the text, adding content to make it as a candidate of a RFC. Thanks. Let me know, if you need any help. Respect, Cheng