[netconf] Re: WGLC for trace-ctx-extension-03

Jean Quilbeuf <jean.quilbeuf@huawei.com> Fri, 18 October 2024 14:02 UTC

Return-Path: <jean.quilbeuf@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FAD5C207962 for <netconf@ietfa.amsl.com>; Fri, 18 Oct 2024 07:02:40 -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_DNSWL_BLOCKED=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_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 8uF7IU-doDDZ for <netconf@ietfa.amsl.com>; Fri, 18 Oct 2024 07:02:36 -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 35087C1E0D77 for <netconf@ietf.org>; Fri, 18 Oct 2024 07:02:33 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4XVRG42sxjz6HJkv; Fri, 18 Oct 2024 22:01:48 +0800 (CST)
Received: from frapeml100001.china.huawei.com (unknown [7.182.85.63]) by mail.maildlp.com (Postfix) with ESMTPS id 745731403A0; Fri, 18 Oct 2024 22:02:31 +0800 (CST)
Received: from frapeml500001.china.huawei.com (7.182.85.94) by frapeml100001.china.huawei.com (7.182.85.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 18 Oct 2024 16:02:31 +0200
Received: from frapeml500001.china.huawei.com ([7.182.85.94]) by frapeml500001.china.huawei.com ([7.182.85.94]) with mapi id 15.01.2507.039; Fri, 18 Oct 2024 16:02:31 +0200
From: Jean Quilbeuf <jean.quilbeuf@huawei.com>
To: Kent Watsen <kent+ietf@watsen.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] WGLC for trace-ctx-extension-03
Thread-Index: AQHa6TVa06IV0LHFsEKnXD2WUq+HJLKM+bpQ
Date: Fri, 18 Oct 2024 14:02:31 +0000
Message-ID: <9e3917ebdad647ac82e76118a0433219@huawei.com>
References: <010001912fad646b-baf78304-4e64-4ff2-9554-a0dd3393ef1e-000000@email.amazonses.com>
In-Reply-To: <010001912fad646b-baf78304-4e64-4ff2-9554-a0dd3393ef1e-000000@email.amazonses.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.206.138.136]
Content-Type: multipart/alternative; boundary="_000_9e3917ebdad647ac82e76118a0433219huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: GLQB2HWLIDSADNBPHWMFQOATLFBGDUX3
X-Message-ID-Hash: GLQB2HWLIDSADNBPHWMFQOATLFBGDUX3
X-MailFrom: jean.quilbeuf@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] Re: WGLC for trace-ctx-extension-03
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/bqJ6baThggcBklK8Picshub9c-g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>

Hello,
I am a little late but I didn't see that call to be closed.

I think this document is ready. I would only suggest to say something in the Security Consideration such as

  "Traces of NETCONF operations may contain potentially sensitive information
   such as mapping client requests to actual configured devices and the internal
   hierarchy of orchestrators and controllers. The operators of the network should
   take the necessary steps to ensure that this information is not disclosed to
   unauthorized users, i.e. only the legitimate collectors can pull or push this data."

Great work.

Best,
Jean

From: Kent Watsen <kent+ietf@watsen.net>
Sent: Thursday, August 8, 2024 2:50 AM
To: netconf@ietf.org
Subject: [netconf] WGLC for trace-ctx-extension-03

This email begins a two-week WGLC on:

              NETCONF Extension to support Trace Context propagation
              https://datatracker.ietf.org/doc/html/draft-ietf-netconf-trace-ctx-extension-01

Please take time to review this draft and post comments by August 21.  Favorable comments are especially welcomed.

None of the authors or contributors have declared IPR:

              https://mailarchive.ietf.org/arch/msg/netconf/dJtouU8jYxfJ49fgYwW39E3nWZw/



Kent  // co-chair