Re: [CDNi] Fwd: New Version Notification for draft-warshavsky-private-features-metadata-00.txt

[Guillaume Bichot <[e-mail]>]

Hi all,
Going in the same direction than Arnon, the MI.PrivateFeature is essential to segregate those configuration objects that are supposed to be “standard” from those that are private. Without such distinction there is no way to understand whether the unknown object is part of specific version possibly not supported or it is just a private feature we may ignore or deal specifically with it as suggested by Arnon. In other words, it facilitates the processing through disambiguation of standard / private configuration objects.
Guillaume Bichot

From: CDNi <[e-mail]> On Behalf Of Arnon Warshavsky
Sent: Thursday, March 28, 2024 7:11 PM
To: [e-mail]
Subject: Re: [CDNi] Fwd: New Version Notification for draft-warshavsky-private-features-metadata-00.txt


Hi all
I was unable to attend IETF119 and I would like to relate to a concern re this document that was brought up by Kevin Ma as for why do we need private features rather than just create genericMetadata objects as we wish.

When a dCDN is digesting a configuration coming from a uCDN (same configuration sent to several dCDNs),
every genericMetadata object can be handled in one of 3 ways:
1. digesting a known object registered either in SVTA schema or the dCDN own private schema (and maybe rejecting it if not properly set according to the schema)
2. rejecting an unknown object not appearing in any schema (e.g, a typo of MI.Sorce instead of MI.Source would be rejected)
3. skipping a private object of a different dCDN which is identified as such

The structure of the private features of having a vendor scope alongside the feature name,
is what enables 2 dCDN vendors define their own private features, and still maintain bullets 1,2 intact.

e.g assuming we have in Qwilt a feature called 'MI.PrivateFeature.Qwilt.RunPythonScript' that we will digest,
at the same time we will be able to skip 'MI.PrivateFeature.Lumen.RunLuaScript' appearing in the same configuration.

I hope this answers the question

thanks
/Arnon

Broadpeak, S.A. Registered offices at 3771 Boulevard des Alliés, 35510 Cesson-Sévigné, France
Trade Register: 524 473 063
This e-mail and its attachments contain confidential information from Broadpeak S.A. and/or its affiliates (Broadpeak), which is intended only for the person to whom it is addressed.
If you are not the intended recipient of this email, please notify immediately the sender by phone or email and delete it. Any use of the information contained herein in any way, including, but not limited to, total or partial disclosure, reproduction, or dissemination, by persons other than the intended recipient(s) is prohibited, unless expressly authorized by Broadpeak. Broadpeak, S.A. and its affiliates respect privacy laws, and is committed to the protection of personal data. Emails and/or attachments thereof exchanged between us may include your personal data which may be processed by Broadpeak and/or its affiliates according to applicable privacy laws & regulations.
In compliance with Regulation (EU) 2016/679 (GDPR) and applicable implementation in local legislations, you can exercise at any time your rights of access, rectification or erasure of your personal data, as well as your rights to restriction, portability or object to the processing.
For such purpose, or to know more about how Broadpeak processes your personal data, you may contact Broadpeak by email [e-mail].
Local authority : Commission Nationale Informatique et Libertés (CNIL): 3 Place de Fontenoy - TSA 80715 - 75334 PARIS CEDEX 07 or www.cnil.fr