IMHO: It is much better when name gives some additional information about the object. Like OAM=Operations, Administration, and Maintenance. When I saw initially iOAM, I believed that “i” was strictly for marketing: mimicking “i” in iPhone or iPad (Cargo cult). Actually, I still suspect that this is the case. Ed/ From: ipv6 [mailto:[email protected]] On Behalf Of Greg Mirsky Sent: Wednesday, December 13, 2023 6:13 AM To: 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]> Subject: [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) • iOAM - in-band OAM (RAW architecture) • oOAM - out-of-band OAM (RAW architecture) 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. 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 _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
