Hi all, Forwarding now that the call for adoption for bmp-over-quic is closed, fwiw.
If you have any relevant item for consideration like the one raised by Claudio, feel free to get in touch with Per. Cheers, Med De : [email protected] <[email protected]> Envoyé : jeudi 2 avril 2026 17:34 À : [email protected]; Operations and Management Area Working Group Discussion List <[email protected]>; Nmop <[email protected]>; IETF IPPM WG ([email protected]) <[email protected]> Cc : Per Andersson <[email protected]> Objet : [NMOP] foo-over-QUIC Operational Motivations & Challenges Hi all Many proposals (*) are being promoted in several IETF WGs to port protocols widely used in operator networks to be transported over QUIC. There are several technical arguments that motivate such extensions, however, porting protocols used within operator networks to support QUIC would have some impacts on fault isolation, troubleshooting, etc. Because of the lack of the visibility on the transport headers, providing feature parity may be challenging without tools upgrade and also logistic (e.g., synchronize keys to decode messages, etc.). There is a need to (1) have a common understanding of the operational benefits, (2) understand the underlying challenges that can be inherited especially when the connection endpoints are not adjacent to each others, and (3) identify deployment incentives especially when there are alternate mechanisms to achieve similar objectives (TLS, etc.), (4) identify whether there are specific missing QUIC features that would ease use in operators network , and (5) explore whether there is common operational guidance that can inform most of these extensions (and similar). Per (cced) kindly accepted to coordinate and lead the discussion on this topic. Per will be presenting the outcome during IETF#126. Many thanks Per! This is thus a call for inputs and feedback on this topic. Feel free to use this thread, get in touch with Per, or fill PRs/Issues using https://github.com/IETF-OPS-AD/foo-over-QUIC-Operational-Considerations. Thank you Cheers, Med (*) * draft-ietf-netconf-over-quic<https://datatracker.ietf.org/doc/draft-ietf-netconf-over-quic/>: NETCONF over QUIC * draft-liu-grow-bmp-over-quic<https://datatracker.ietf.org/doc/draft-liu-grow-bmp-over-quic/>: Using BMP over QUIC connection * draft-liu-sidrops-rpki-rtr-over-quic<https://datatracker.ietf.org/doc/draft-liu-sidrops-rpki-rtr-over-quic/>: RPKI to Router Protocol over QUIC * draft-llg-opsawg-ipfix-over-quic<https://datatracker.ietf.org/doc/draft-llg-opsawg-ipfix-over-quic/>: IPFIX Protocol over QUIC * draft-retana-idr-bgp-quic<https://datatracker.ietf.org/doc/draft-retana-idr-bgp-quic/>: BGP over QUIC * draft-yl-radext-quic-transport<https://datatracker.ietf.org/doc/draft-yl-radext-quic-transport/>: RADIUS over QUIC * draft-yang-pce-pcep-over-quic<https://datatracker.ietf.org/doc/draft-yang-pce-pcep-over-quic/>: PCEP over QUIC * draft-cel-nfsv4-rpc-over-quicv1<https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpc-over-quicv1/>: Remote Procedure Call over QUIC Version 1 * draft-ietf-regext-epp-quic<https://datatracker.ietf.org/doc/draft-ietf-regext-epp-quic/>: Extensible Provisioning Protocol (EPP) Transport over QUIC ____________________________________________________________________________________________________________ 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. ____________________________________________________________________________________________________________ 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.
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
