Hi Greg, all, I personally prefer IOAM and OOAM.
I suggest that you edit rfc6291-bis (BCP 161) with a discussion on this specific point and a reco. Cheers, Med De : ipv6 <[email protected]> De la part de Greg Mirsky Envoyé : mercredi 13 décembre 2023 04:13 À : DetNet WG <[email protected]>; mpls <[email protected]>; 6man WG <[email protected]>; IETF IPPM WG <[email protected]>; opsawg <[email protected]>; Pascal Thubert <[email protected]>; Loa Andersson <[email protected]> Objet : [IPv6] IOAM, iOAM, and oOAM abbreviations Dear All, Loa and I have discussed these abbreviations to help us find a solution that avoids the confusion we found when we came across them. Firstly, what they stand for: * IOAM - In-situ OAM (RFC 9197<https://datatracker.ietf.org/doc/rfc9197/>) * iOAM - in-band OAM (RAW architecture<https://datatracker.ietf.org/doc/html/draft-ietf-raw-architecture-13>) * oOAM - out-of-band OAM (RAW architecture<https://datatracker.ietf.org/doc/html/draft-ietf-raw-architecture-13>) We discussed the issue with Pascal and came to slightly different abbreviations for the last two: * inb-OAM * oob-OAM We also discord these abbreviations with the RFC Editor. Resulting from that, RFC Editor agreed to add IOAM to the RFC Editor Abbreviation List<https://www.rfc-editor.org/materials/abbrev.expansion.txt>. The other two abbreviations cannot be added at this time. If that is needed, we can ask the RFC Editor to add them once the respective RFC is published. We are seeking your feedback on the following: * Do you see the benefit of introducing two new abbreviations for in-band OAM and out-of-band OAM? * Which set of abbreviations (iOAM/oOAM vs. inb-OAM/oob-OAM) do you prefer for being used in IETF? * Or would you propose another set of abbreviations? Regards, Loa and Greg ____________________________________________________________________________________________________________ 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
