Hi Paul, Do you still think there is an issue with the design? Thanks.
Cheers, Med De : BOUCADAIR Mohamed INNOV/NET Envoyé : mardi 23 janvier 2024 14:56 À : 'Aitken, Paul' <[email protected]>; Joe Clarke (jclarke) <[email protected]>; [email protected] Cc : [email protected] Objet : octetArray/hextetArray/32tetArray RE: Re: [IPFIX] WG LC: IPFIX documents Hi Paul, (restricted the distribution lists to OPSAWG and IPFIX) The octetArray type is especially confusing as these are really hextetArrays. [Med] Not sure we need a new data type here as octeArray is defined as follows: The octetArray data type has no encoding rules; it represents a raw array of zero or more octets, with the interpretation of the octets defined in the Information Element definition. The draft proposes the encoding not of octets, but of 16-bit values. Therefore it's not an "array of zero or more octets" but rather, an "array of zero or more hextets". [Med] I was assuming that «interpretation of the octets defined in the Information Element definition" in the excerpt is not restrictive and leave it to the definition of the IE to determine how to interpret the octets (including when grouping them into 16 bits, 32 bits, etc.). Given that interpreting the data requires anyway digesting the structure in the definition not only the abstract data type, I thought that we don't need to define new types for specific octet- blocks, but I may be mistaken. ____________________________________________________________________________________________________________ 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.
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
