Hello ops, I too support the adoption of draft-boucadair-opsawg-rfc7125-update. The new text proposed in Section 3 is crystal clear to me and addresses the motivation exposed in section 1.
Cheers, Christian. Orange Restricted De : OPSAWG <opsawg-boun...@ietf.org> De la part de thomas.g...@swisscom.com Envoyé : samedi 21 janvier 2023 16:21 À : jclarke=40cisco....@dmarc.ietf.org; opsawg@ietf.org Objet : Re: [OPSAWG] CALL FOR ADOPTION: An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element Dear opsawg, I support the adoption and think draft-boucla-opsawg-ipfix-fixes should follow the adoption call next as well. Both are very valuable to keep the IPFIX registry up to date. I agree with the author that IE6 tcpControlBits should mirror the TCP header flags registry (https://www.iana.org/assignments/tcp-parameters/tcp-parameters.xhtml#tcp-header-flags). With this update network operators understand when packets are being observed with bit 7 set which application in the network should be upgraded to reflect the change being introduced with RFC 8311. I suggest in the introduction to take the angle of correct observability vs. TCP protocol interoperability to describe the motivation. Best wishes Thomas From: OPSAWG <opsawg-boun...@ietf.org<mailto:opsawg-boun...@ietf.org>> On Behalf Of Joe Clarke (jclarke) Sent: Tuesday, January 17, 2023 5:25 PM To: opsawg@ietf.org<mailto:opsawg@ietf.org> Subject: [OPSAWG] CALL FOR ADOPTION: An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element Happy new year, all. One of the AIs that slipped through the cracks coming out of 115 was a call for adoption for draft-boucadair-opsawg-rfc7125-update. One of the asks of Med at 115 was to look at what else might need to be done from an IE registry standpoint. He replied on-list to that a while ago: "Yes, I had a discussion with Benoît during the IETF meeting to see how to handle this. We agreed to proceed with at least two documents: * draft-boucadair-opsawg-rfc7125-update to update the TCP IPFIX RFC. * Edit a second draft to "clean" other entries in registry. This document is intended to include only simple fixes and which do not require updating existing RFCs. The candidate list of these proposed fixes can be seen at https://boucadair.github.io/simple-ipfix-fixes/draft-boucla-opsawg-ipfix-fixes.html<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fboucadair.github.io%2Fsimple-ipfix-fixes%2Fdraft-boucla-opsawg-ipfix-fixes.html&data=05%7C01%7CThomas.Graf%40swisscom.com%7C0fc3378bcd7d4776e9db08daf8a75b0b%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C638095694937996003%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2JKQwErsxzygLiYeWWPZFuy2eQ8GueAAnzlzM%2FV85pQ%3D&reserved=0>. New IEs, if needed, will be moved to a separate document. simple-ipfix-fixes may or may not be published as an RFC." So, let this serve as a two-week call for adoption for the existing draft-boucadair-opsawg-rfc7125-update document. Please reply on-list with your comments, support, or dissent by January 31, 2023. Thanks. Joe _________________________________________________________________________________________________________________________ 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
