Re: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest

Alexander Clemm <alex@futurewei.com> Mon, 28 November 2022 19:30 UTC

Return-Path: <alex@futurewei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B02FCC14E514 for <opsawg@ietfa.amsl.com>; Mon, 28 Nov 2022 11:30:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
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 K7TDo_EHWsS3 for <opsawg@ietfa.amsl.com>; Mon, 28 Nov 2022 11:30:45 -0800 (PST)
Received: from NAM04-MW2-obe.outbound.protection.outlook.com (mail-mw2nam04on2072b.outbound.protection.outlook.com [IPv6:2a01:111:f400:7e8c::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77C02C14F6EC for <opsawg@ietf.org>; Mon, 28 Nov 2022 11:30:45 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kbeLU/DK+U9C4jGYqt5Le8LbOiR/MYFndLyJzdIGnWxhbf1DNlC3esTvhgNCUQu0uSID4DwD75JNpimYcj9x/k1iNVE+CUrkaYmOcmRwipWKsV520lmuUIv8JCt+5B8h5F+DXsaFnQgpu0BUiFIOyIw8I93Fq4HyCDwhShrI1WvJeuNoxrPikSCt1ll3bCUv9arlrjgy/RGVVQJMl9PcsjpkHJy+okC+SkkAOuyDAnGJgLd56lzZXzNszNMzlluMpXQz9U3Z1B562AbE/f8NshrRlpXAKfLIvo73CeO4Rdz/4FuN9sLxfRkWibfQeaH3AerJUpeIx2OOXEUp3+pefQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=5DcGdwf4KRVamuQS9xiVk6HWkxsgmzKZ0RGcsIBOtdE=; b=TA1ZeGz8S5BteQbOSJeCAqU8wNLSorZo7OP5Z7+0S/ZgutViD8YoKHhv7YSgwcjM1wYuQfAA5GFDMl55CUtRG46NzQKxb8NothUbnREvc0S5H8LQzT9b5meaPoxXcPacnRwNwlS8l8UbRGL2ELtbZSdMtisP43UAHfqmMNAdk5gZX5KJIdkq08CXY1o8HzR0R1ZOB8WIZhFrXlra9+4yfyMFkP82YQDL1VU9zVkn2CCkcxzxPlVWHUh9b/LPnQlszz6C8OhvnsdNiPF9q+zIU2CaxA643aVDL8hWmemWDvBNTadUzO35k77V4aXYUMXMIOMH8i7vzfvXpPEslN83Zg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5DcGdwf4KRVamuQS9xiVk6HWkxsgmzKZ0RGcsIBOtdE=; b=Fyep/ymndHKxZupIBYMOQGlP8bpLQuwFU0eM6jyIx9VdBb0wIHkSdbNKWguNfUdYX0xN3+siGM9qCBN6wsywYD39vg5wo+w1rTHNFXyF6WllH6C6dB6e7mf3Iev5CN759Zw55N6xM+aJJYE+dpt7MTIjChKdVH35ccKD6w8+5yY=
Received: from SN4PR13MB5374.namprd13.prod.outlook.com (2603:10b6:806:20d::8) by CO6PR13MB5275.namprd13.prod.outlook.com (2603:10b6:303:146::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5857.23; Mon, 28 Nov 2022 19:30:32 +0000
Received: from SN4PR13MB5374.namprd13.prod.outlook.com ([fe80::a2cc:8680:86ad:f718]) by SN4PR13MB5374.namprd13.prod.outlook.com ([fe80::a2cc:8680:86ad:f718%5]) with mapi id 15.20.5857.023; Mon, 28 Nov 2022 19:30:31 +0000
From: Alexander Clemm <alex@futurewei.com>
To: IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <ignacio.dominguezmartinez@telefonica.com>, Tianran Zhou <zhoutianran@huawei.com>, opsawg <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest
Thread-Index: AQHY/ajsiz2DGtqqo0KvtYYplbPCnK5JrKpggAHk8yWACIUvgIAApCfg
Date: Mon, 28 Nov 2022 19:30:31 +0000
Message-ID: <SN4PR13MB5374947E74BDA7D6D63DACF6DB139@SN4PR13MB5374.namprd13.prod.outlook.com>
References: <5DE33697-1939-4CB5-95C6-C41128B8E035@telefonica.com> <SN4PR13MB5374058A70B3D44A71432B97DB0A9@SN4PR13MB5374.namprd13.prod.outlook.com> <d0e0419f68ea4ffeb99e257163d96b8c@huawei.com> <6C121102-752A-4E69-90DA-BB1BD255DC94@telefonica.com>
In-Reply-To: <6C121102-752A-4E69-90DA-BB1BD255DC94@telefonica.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=futurewei.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SN4PR13MB5374:EE_|CO6PR13MB5275:EE_
x-ms-office365-filtering-correlation-id: be90fc91-d787-480b-9721-08dad1770353
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: JYiKaOCGnaP74Z8iOCQGEIRi85GZpv06S4dB4Cdce9ubh5lZt4Y0C8Iyt9YbCuoyzkWyjDLyIn5SGJpM/qgHQ/84c43vjCuebUOIO/TwbCEp8IICiX1GpRisRMdxcDEiM3pW7IizGLXxwA8Hiz/G8wzcL9z0v+VjI8Q2h8iQXf9qC/wpBwvco4WHlhEEDVAKVNOzxcX8c8wjSBp1SpYsqTyytXxGKas5s2dpPtGce7NFseEydsTPEqOKfom9bVd7bBWaRn8HDgNJJbr73Ja1xfZEAd2/20aQ7jB3LkCB7lGAuI1/Dmj5g1ALJF5qhzadft0YUvOaBqE0ySQbY3LwUDChBsleytpumukRNBiFKVFeB4djJF722OrH1SRjBTjIkzMndopuf7/vGJ1FvvBx9/WYr1AJb9opq8mDL/8cP87ynvJrtc1+W6BbbH2WsgGMHoXbeoWuV6kNAtUUHAIbE52ImuSuW0zxAxlfk4+rZ6vMxSlAVo4opbSYuXYLc5ALyl+SRTZawzdS9XdbP0eY+QBnFaxPDtLGuTQMTQUQg1+oc23nlwD9rFQUGM+Pylz4Df1OlqX3YRZeXV5S9+dY3Yo3OPo36V+PY48J5FRu8VHN9PnePWrUjK4FJ7XX5aAuJdQQrvomI3R0TNjUYgaUm/7vd6/fYWRRg5gXu4upL4YwAt10iQSoWbOndb4IqkhzLrAtG7V9gCWVfLVboLSnxeV1oRMH5SNOc+WuCiXiV6w=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SN4PR13MB5374.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230022)(4636009)(376002)(136003)(346002)(396003)(366004)(39840400004)(451199015)(2906002)(4001150100001)(30864003)(66899015)(296002)(186003)(5660300002)(76116006)(41300700001)(66556008)(64756008)(66446008)(66946007)(66476007)(110136005)(33656002)(71200400001)(8676002)(52536014)(8936002)(7696005)(86362001)(26005)(478600001)(966005)(9686003)(6506007)(53546011)(316002)(38100700002)(66574015)(55016003)(83380400001)(166002)(122000001)(38070700005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: pv+iy/Q4lBpNHjnMZ0lf6M5x3Jg9kAzRUhtViUVVh7ElT8wWQU1M6Z++RR7JLe0oYWEXTn7QcJNMqYTGhruCSJAXocV5WmZCIbVSMsNOx2Q8UCTv/HOL4nMwLfv44jj72v+ej1kC5kaPZ1Flm82nwgCl/wwhHWUmp4lDlki2FgoDMfOivbZsmtru3qtzt852oDqiWBFyk3CgaAQYEpXLRInKCHBqNKe5PvEbzw3A6gZsPYJSmFZPfSDdEkHM3sGw1AymUAxJFTW50x8GHVzuNL9WcSoetb2aZpzjVEmdqGchAGxsaLdSmfEa4XMmG4f2DkHulKmaUzxEPX+2haKA6avIw2M/d7dw+Nz7051UHKIfDzBXHo5r1fH/XahfGumAzRHlVtvHyFnm7HlSG+LRMxB7l/VS08VDkrHMUED/V9ytzq5OgOMx0mYmd5LXfEyS9FWaHLJSHQpjdNyQRC4pgD/4D7fpUxU25QpVouGKE3IPqEaxSnMNF+UdXgMP+Y243uYJFzppXQzM3ex3jQ1Bf7Xss5r8b8PuPZIhfBAvi+5AwHM20J1ESF1HQAtJk6TTyiubsTlODpX+tIUi/R/IgrR+DJ0c+SBH7RVfGL4StPwwB3ImGtF5fVesbo/MJ+p0gsseF6ARc1efIwRMTGXRsl/PT0mV46yPM62hZ2TrRB5skNE/RaubWNKbF6U4xXQtCevYgsB7ylt+CRytEYFjHJwS8IUGMMi3OUEe2CwKe8nM30uyKlBfH1PQpEtRok5T4KNC7p5fgM2eJgdsgvyX5kRXx5SOwH6oNDxIaMtUgHbZe/CDBfyysqv+H20s9IZJsHxxX46dhquMj+4/4qcvcf3nANkDhxIENV7TJ79Kae7Pq3Gx28XZS39xpZgQ0gNWop2xhtZHfBk+3I7mu5mzf/AlDZQsn6KfItBR83e6vZGVLTt43q4vGZt7OwCEzleWAV4jANjrjJdDg6M46Nw9bo/1KKYiQ3XB+ucGUelmPFGtTp4YWAkU24B7NXrDrLmN62EroV9MGCa93kCSENBLqtoBfntyxj0Q6eSmxaTSMN8g157n4NTBl0up3hrSlpwcHPpVrh4GI82nX9nCLXlNWE59AuzVTavxG5504GqpeKfAOPJNTlnqy+juYTW/Z44/DPmEjZ8zZwzTns+jVBermQOZvkFO+lFMu0U6c9BTaGhE66ejyQml0QZYTzv/94WvZ/02jRIKrLEc6+Pi0/Dw1RivjDo4JrUn9XJQqL8qRFCwluulJpGVtCzlhVkdYQwwNElKchbIcAalqOOvBYgH+IX4XkM3B3zG98+K1B8eJLgMupG9Lvr5XV3g6i3s28QMQz+DppD/7iTTnxLp92KlQ/vVTgb9utK6zWJ6Snb5ZYALqlMjZzXPnNUzsY9afInOlLaDVsbt7TMu8yRyc/TcttIDkXw/tQhneTHOocXf+zjI0vUro3f3D3JwS2QAZZ5Fikw22scZhN/FtNCXYwW92RzjwuoiqeKkZvKDgF+3mvOCuS260bEDBFtYEgNfbn45A94/exhKarCpXfAPH0T6/j5TtX6ZY59iieXcwXCand8LB19ZhmvDOYZkvQcqOkTd
Content-Type: multipart/alternative; boundary="_000_SN4PR13MB5374947E74BDA7D6D63DACF6DB139SN4PR13MB5374namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SN4PR13MB5374.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: be90fc91-d787-480b-9721-08dad1770353
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2022 19:30:31.2984 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3CDsuuTAgtZXJvYg/1Fgs3nz7crBJZYH8yQTI90yd0jBcvLvZKfJ/D+BuyHReaWOeavVYlqV/B15l4NFgbI8Gg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO6PR13MB5275
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/jG1MnwA2NT9wf7BE_C5xfM8ykrE>
Subject: Re: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Nov 2022 19:30:49 -0000

I find this response confusing.  To me this reads that if a non-IETF telemetry feature is used, the data manifest would in fact be up to the implementation i.e. proprietary.  However, it would seem to me that to be useful, the information in the data manifest would need to be standardized, even it is supposed to describe proprietary and/or non-IETF telemetry mechanisms.  So, if gNMI is supposed to be covered, it should spell out specifically how.  Of course, whether it makes sense trying to managing non-IETF mechanisms (which have their own mechanisms) via an IETF standard may be another question; I agree with Tianran here.

Either way, I think at a minimum further clarification in the draft is needed.

--- Alex

From: IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <ignacio.dominguezmartinez@telefonica.com>
Sent: Monday, November 28, 2022 12:09 AM
To: Tianran Zhou <zhoutianran@huawei.com>; Alexander Clemm <alex@futurewei.com>; opsawg <opsawg@ietf.org>
Subject: Re: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest

Hi Tianran,

I understand your point. In the beginning, the MDT collector would provide the Data Collection Manifest as this component knows about the MDT subscription details depending on the type of protocol (e.g., gNMI, YANG Push). But ideally, the network platform would implement the manifest so subscription information can also be streamed directly from the platform, regardless of which MDT protocol is used. This is explained in the draft as follows:

      It is expected that the Data Manifest is streamed directly from the
   network equipment, along with the telemetry feature.  If a platform
   streaming telemetry does not support yet the YANG modules from the
   Data Manifest specified in this document, the collector could
   populate the Data Manifest from available information from the
   platform.  However, this option requires efforts on the collector
   side, as the information gathered in the Data Manifest proposed in
   this document could be scattered among various standard and vendor-
   specific YANG modules [RFC8199], that depend on the platform.

Hope this answered your question.

Many thanks!

Best regards,
Nacho.


From: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>
Date: Wednesday, 23 November 2022 at 00:02
To: Alexander Clemm <alex@futurewei.com<mailto:alex@futurewei.com>>, IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <ignacio.dominguezmartinez@telefonica.com<mailto:ignacio.dominguezmartinez@telefonica.com>>, opsawg <opsawg@ietf.org<mailto:opsawg@ietf.org>>
Subject: RE: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest

Hi Nacho,

I am not sure if I really understand this argument.
There are different lines, like Yang push, gnmi, private implementations. If they cannot follow IETF subscription, i.e., Yang push, how could they follow an IETF manifest? I mean they will use their own way to indicate the collection information.
I mean I think we should only consider Yang push here.

Best,
Tianran
________________________________

Sent from WeLink
发件人: Alexander Clemm<alex@futurewei.com<mailto:alex@futurewei.com>>
收件人: IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA<ignacio.dominguezmartinez@telefonica.com<mailto:ignacio.dominguezmartinez@telefonica.com>>;Tianran Zhou<zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>;opsawg<opsawg@ietf.org<mailto:opsawg@ietf.org>>
主题: RE: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest
时间: 2022-11-22 02:09:12

Thank you for clarifying.  Yes, I think it will be good to make this more explicit to the draft (and perhaps hint also to at the alternative option of subscribing to the subscription configuration if it were only YANG-Push (as opposed to other mechanisms) that was being used, to more clearly differentiate the delta provided by this draft).
Best
--- Alex

From: IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <ignacio.dominguezmartinez@telefonica.com<mailto:ignacio.dominguezmartinez@telefonica.com>>
Sent: Monday, November 21, 2022 4:58 AM
To: Alexander Clemm <alex@futurewei.com<mailto:alex@futurewei.com>>; Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>; opsawg@ietf.org<mailto:opsawg@ietf.org>
Subject: Re: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest

Hi Alex,

The purpose of the Data Collection Manifest is to cover all possible MDT mechanisms, not only YANG Push. There are other mechanisms like gNMI, which rely on subscriptions based on YANG path, for which we need the context of the subscription (e.g., on-change, suppress-redundancy). Additionally, vendors like Cisco or Huawei also implement other MDT mechanisms based on YANG Path.

For more details, you can follow an internal discussion he had on github: https://github.com/JeanQuilbeufHuawei/draft-collected-data-manifest/pull/30<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJeanQuilbeufHuawei%2Fdraft-collected-data-manifest%2Fpull%2F30&data=05%7C01%7Calex%40futurewei.com%7C250b9213f5ba48d4a49308dad117d2f5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638052197539444125%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Et6LdF8I2OPWWt9oCCFzLSJKM6dsK5V9peLWjjumjNs%3D&reserved=0>

In any case, I agree that we can better clarify this aspect in the draft.

Many thanks for your feedback!

Best regards,
Nacho.

From: OPSAWG <opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org>> on behalf of Alexander Clemm <alex@futurewei.com<mailto:alex@futurewei.com>>
Date: Friday, 18 November 2022 at 17:39
To: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>, "opsawg@ietf.org<mailto:opsawg@ietf.org>" <opsawg@ietf.org<mailto:opsawg@ietf.org>>
Subject: Re: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest

So, saving the invocation of one command to establish the “meta-subscription”, that’s all this is for?  And for this we are asking implementors to create what is in effect redundant instrumentation?  This seems a lot of effort for a small saving.

As a thought, even in that case, would you even need a redundant YANG-data model, or would it make sense to instead augment the existing model with an additional parameter instead “provide manifest info”, which adds implicitly a subscription to the subscription info to the subscription itself?  Such an alternative could be accomplished by augmenting such a parameter into the existing model, and save the need to create YANG data instrumentation that is basically redundant, hence reduce the complexity of implementations.

--- Alex

From: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>
Sent: Thursday, November 17, 2022 10:49 PM
To: Alexander Clemm <alex@futurewei.com<mailto:alex@futurewei.com>>; opsawg@ietf.org<mailto:opsawg@ietf.org>
Subject: RE: Manifest need? Re: draft-claise-opsawg-collected-data-manifest

Hi Alex,

I think this is a very good discussion. I raised this question before in the mailing list.
I think there may be some benefits:
1. The meta data can always go with the telemetry data, without explicit subscription. This facilitates the close loop automation.
2. Another subscription to the subscription information may make the management complex, since we put all the subscriptions in one list.

Best,
Tianran

发件人: OPSAWG [mailto:opsawg-bounces@ietf.org] 代表 Alexander Clemm
发送时间: 2022年11月18日 7:40
收件人: opsawg@ietf.org<mailto:opsawg@ietf.org>
主题: [OPSAWG] Manifest need? Re: draft-claise-opsawg-collected-data-manifest

Hello draft-claise-opsawg-collected-data-manifest coauthors,

I just wanted to follow up on my comment at the microphone in London regarding draft-claise-opsawg-collected-data-manifest.

Clearly, there is a need to preserve context to be able to correctly interpret data after it has been collected.  That being said, as currently stated, the draft appears to overspecify some of those things, defining some YANG data that IMHO is not actually needed as the same can already be accomplished.  This concerns the specifics about the subscription itself.

RFC 8641 includes a YANG model that reflects for each subscription how it is configured (whether configured directly or established by RPC), including the selection filter, the update trigger, the period and anchor time (in case of periodic subscription), dampening periods and excluded changes (in case of on-change subscription), etc. The corresponding YANG data can be itself be subscribed to, or retrieved on demand, just like any other kind of YANG data.

I am therefore not quite sure what the proposed manifest would provide that couldn't be accomplished already.  The suggestion to retain the subscription data along with the subscribed data makes a lot of sense but would appear to be a practice that will be up to the management application to implement, with the mechanism already provided.  (This could of course be included as a description of a recommended practice in the draft.)  Or is there something else that is missing?

If there is indeed a delta that cannot be otherwise accomplished, my suggestion would be to add text to the draft that clearly describes the possibility of subscribing to subscription configuration data, then explaining the functional delta that your draft covers in addition to that.

Thanks
--- Alex

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição