Re-, Thanks, Rob. Will make the change.
Cheers, Med > -----Message d'origine----- > De : Rob Wilton (rwilton) <[email protected]> > Envoyé : vendredi 29 avril 2022 11:13 > À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; > [email protected] > Cc : [email protected] > Objet : RE: OFFLIST TR: New Version Notification for draft-ietf- > opsawg-l2nm-13.txt > > Hi Med, > > I think that this should be a normative reference, but I don’t > think that should be a problem. > > Regards, > Rob > > > > -----Original Message----- > > From: [email protected] > > <[email protected]> > > Sent: 29 April 2022 07:34 > > To: Rob Wilton (rwilton) <[email protected]>; > [email protected] > > Cc: [email protected] > > Subject: RE: OFFLIST TR: New Version Notification for > > draft-ietf-opsawg- l2nm-13.txt > > > > Hi Rob, Adrian, > > > > As you may note in -14, the following reference: > > > > [IEEE802.1Qcp-2018] > > IEEE, "IEEE Standard for Local and metropolitan > area > > networks--Bridges and Bridged Networks--Amendment > 30: YANG > > Data Model", September 2018, > > <https://ieeexplore.ieee.org/document/8467507>. > > > > is listed as informative. The rationale was to align with what > i2rs > > did (they discussed this specific point in the context of RFC > 8944). > > > > Please advise if you think that we should change that. Thanks. > > > > Cheers, > > Med > > > > > -----Message d'origine----- > > > De : BOUCADAIR Mohamed INNOV/NET > > > Envoyé : jeudi 28 avril 2022 16:53 > > > À : 'Rob Wilton (rwilton)' <[email protected]> Cc : > [email protected] > > > Objet : RE: OFFLIST TR: New Version Notification for draft- > ietf- > > > opsawg-l2nm-13.txt > > > > > > Re-, > > > > > > Please see inline. > > > > > > Cheers, > > > Med > > > > > > > -----Message d'origine----- > > > > De : Rob Wilton (rwilton) <[email protected]> Envoyé : jeudi > 28 > > > avril > > > > 2022 16:23 À : BOUCADAIR Mohamed INNOV/NET > > > > <[email protected]> Cc : [email protected] Objet : > RE: > > > > OFFLIST TR: New Version Notification for draft-ietf- > > > > opsawg-l2nm-13.txt > > > > > > > > Hi Med, > > > > > > > > Just one further tweak under QinQ: > > > > > > > > leaf translate { > > > > type empty; > > > > description > > > > "Translate one or two outer > > > tags. > > > > PCP > > > > bits are preserved."; > > > > } > > > > > > > > Do you need to change this to: > > > > > > > > leaf translate { > > > > type uint8 { > > > > range "1|2"; > > > > } > > > > description > > > > "Translate one or two outer > > > tags. > > > > PCP > > > > bits are preserved."; > > > > } > > > > > > > > To indicate whether it is one or two outer tags that are > being > > > > translated? > > > > > > > > > > [Med] The presence of tag-1/type and/are tag-2/type is > redundant > > > with indicating it in the range. No? > > > > > > > E.g., trans-1-2 would be translate 1 with both tag-1/tag-1- > type > > > and > > > > tag-2/tag-2-type pushed tags. Trans-2-2 would be translate > 2 > > > > + tag-1/tag-1-type and tag-2/tag-2-type. Trans-2-1 would be > > > > translate 2 + tag-1/tag-1-type. > > > > > > > > Perhaps in the descriptions for tag-1/tag-2 indicate that > tag-1- > > > type > > > > etc must be specified (or maybe add must statements to > enforce > > > this)? > > > > Alternatively could add defaults so that tag-1- type > defaults to > > > > S-VLAN and tag-2-type defaults to C-VLAN? > > > > > > > _________________________________________________________________________________________________________________________ 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
