Re-,
What about adding the following under "Operational Considerations":
NEW:
Implementations of tcpSharedOptionExID16 and tcpSharedOptionExID32 IEs are
assumed to be provided with a list of valid Experiment IDs {{IANA-TCP-EXIDs}}.
How that list is maintained is implementation-specific. Absent that list, an
implementation can't autonomously determine whether an ExID is present and, if
so, whether it is 2- or 4-byte length.
Cheers,
Med
> -----Message d'origine-----
> De : Wesley Eddy <w...@mti-systems.com>
> Envoyé : mercredi 17 janvier 2024 14:25
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>;
> tsv-...@ietf.org
> Cc : draft-ietf-opsawg-ipfix-tcpo-v6eh....@ietf.org;
> opsawg@ietf.org
> Objet : Re: Tsvart early review of draft-ietf-opsawg-ipfix-tcpo-
> v6eh-05
>
> On 1/17/2024 3:34 AM, mohamed.boucad...@orange.com wrote:
> > [Med] This can be part of regular code updates. Please note
> that this
> > is not unusual in ipfix (see for example ipv4Options, natevent,
> etc.
> > in
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fwww.iana.org%2Fassignments%2Fipfix%2Fipfix.xhtml&data=05%7C02%7C
> mohamed.boucadair%40orange.com%7C69fc748e4be24a2aa56808dc175fb703
> %7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638410947053802590%
> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eZcICzC8rw%2BLDau
> B82e4BxG2PkB5X3LRQO%2BDCUmGQyU%3D&reserved=0 which depend on an
> IANA registry).
>
> Ok; do you think the document should explain this in a sentence
> or two for implementers?
>
> If they are not all familiar with details of how ExIDs are used,
> then it seems like a stretch to assume they'll all understand
> that products need to be designed to periodically update ExID
> definitions.
____________________________________________________________________________________________________________
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
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
