Subject: [Dots] 128-255 key value range for telemetry attributes (was RE: I-D Action: draft-ietf-dots-telemetry-01.txt

From: <[email-masked]>
Date: Fri, 26 Jun 2020 12:47:59 +0000

Hi all, 

We discussed yesterday the proposal to use 128-255 as comprehension-optional range for telemetry attributes.  The issue was initially discussed below.  

If we hear no objection, we will update the draft to implement this proposal. If implemented, the telemetry draft will be updating RFC8782, which is fine. 

We do have new 117 attributes in the telemetry spec, but we are considering reducing that list in compliance with RFC7951 rules.  

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:[email-masked]] De la part de
> [email-masked]
> Envoyé : lundi 3 février 2020 10:37
> À : Jon Shallow ([email-masked]); [email-masked]
> Objet : Re: [Dots] I-D Action: draft-ietf-dots-telemetry-01.txt
> 
> Hi all,
> 
> FYI, a review from Jon is available at: https://github.com/boucadair/draft-
> dots-telemetry/raw/master/DOTS%20Telemetry%2001-rev%20Jon-res%20Med.docx
> 
> -02 will integrate almost all comments from  Jon. Please find below some
> points we would like to hear more from the working group:
> 
> (1) key value range for telemetry: Jon raised this point "These keys
> requires 3 bytes - and telemetry information is going to be difficult to
> fit into a packet.  I appreciate that comprehension-required
> Is for numbers less than 0x8000 - perhaps the comprehension-required range
> is reduced and also has a section higher up so the total of 0x8000 still
> stands so less bytes can be used here."
> 
>    +----------------------+-------+-------+------------+---------------+
>    | Parameter Name       | CBOR  | CBOR  | Change     | Specification |
>    |                      | Key   | Major | Controller | Document(s)   |
>    |                      | Value | Type  |            |               |
>    +----------------------+-------+-------+------------+---------------+
>    | ietf-dots-signal-cha | 32776 |   5   |    IESG    |   [RFCXXXX]   |
>    | nnel:telemetry       |       |       |            |               |
> 
> Med: This is a major one. We need to assess the gain, but it is possible in
> theory to update our assignment policies and reassign, e.g., 128-255 range
> to be comprehension-optional (specific for telemetry). This would mean that
> the telemetry spec will be tagged as updating the base signal channel spec.
> We need more discussion.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.