[OPS-AREA]foo-over-QUIC Operational Motivations & Challenges
[email protected] Thu, 2 Apr 2026 15:33:58 +0000
| Newsgroups | gmane.ietf.ops,gmane.ietf.opsawg,gmane.ietf.ippm |
|---|---|
| Message-ID | <PATP264MB676505917F8C7EACD83CED468851A@PATP264MB6765.FRAP264.PROD.OUTLOOK.COM> |
--===============6434604907646134993==
Content-Language: fr-FR
Content-Type: multipart/alternative;
boundary="_000_PATP264MB676505917F8C7EACD83CED468851APATP264MB6765FRAP_"
--_000_PATP264MB676505917F8C7EACD83CED468851APATP264MB6765FRAP_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
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 se=
veral technical arguments that motivate such extensions, however, porting p=
rotocols used within operator networks to support QUIC would have some impa=
cts on fault isolation, troubleshooting, etc. Because of the lack of the vi=
sibility on the transport headers, providing feature parity may be challeng=
ing without tools upgrade and also logistic (e.g., synchronize keys to deco=
de messages, etc.).
There is a need to (1) have a common understanding of the operational benef=
its, (2) understand the underlying challenges that can be inherited especia=
lly when the connection endpoints are not adjacent to each others, and (3) =
identify deployment incentives especially when there are alternate mechanis=
ms to achieve similar objectives (TLS, etc.), (4) identify whether there ar=
e specific missing QUIC features that would ease use in operators network ,=
and (5) explore whether there is common operational guidance that can info=
rm most of these extensions (and similar).
Per (cced) kindly accepted to coordinate and lead the discussion on this to=
pic. 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://githu=
b.com/IETF-OPS-AD/foo-over-QUIC-Operational-Considerations.
Thank you
Cheers,
Med
(*)
* draft-ietf-netconf-over-quic<https://datatracker.ietf.org/doc/draft-i=
etf-netconf-over-quic/>: NETCONF over QUIC
* draft-liu-grow-bmp-over-quic<https://datatracker.ietf.org/doc/draft-l=
iu-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/dra=
ft-llg-opsawg-ipfix-over-quic/>: IPFIX Protocol over QUIC
* draft-retana-idr-bgp-quic<https://datatracker.ietf.org/doc/draft-reta=
na-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/draf=
t-cel-nfsv4-rpc-over-quicv1/>: Remote Procedure Call over QUIC Version 1
* draft-ietf-regext-epp-quic<https://datatracker.ietf.org/doc/draft-iet=
f-regext-epp-quic/>: Extensible Provisioning Protocol (EPP) Transport over =
QUIC
___________________________________________________________________________=
_________________________________
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
--_000_PATP264MB676505917F8C7EACD83CED468851APATP264MB6765FRAP_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Courier New";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:67190494;
mso-list-template-ids:-152521118;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1529567494;
mso-list-template-ids:662843818;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang=3D"FR" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:bre=
ak-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
Hi all<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
<o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">Many proposals (*) are being promoted in several IETF WGs to=
port protocols widely used in operator networks to be transported over QUI=
C. 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, prov=
iding feature parity may be challenging
without tools upgrade and also logistic (e.g., synchronize keys to decode =
messages, etc.).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">There is a need to (1) have a common understanding of the op=
erational benefits, (2) understand the underlying challenges that can be in=
herited especially when the connection endpoints
are not adjacent to each others, and (3) identify deployment incentives es=
pecially 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 tha=
t can inform most of these extensions (and similar).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">Per (cced) kindly accepted to coordinate and lead the discus=
sion on this topic. Per will be presenting the outcome during IETF#126. Man=
y thanks Per!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">This is thus a call for inputs and feedback on this topic. F=
eel free to use this thread, get in touch with Per, or fill PRs/Issues using
</span><span style=3D"font-family:"Courier New""><a href=3D"https=
://github.com/IETF-OPS-AD/foo-over-QUIC-Operational-Considerations"><span l=
ang=3D"EN-US">https://github.com/IETF-OPS-AD/foo-over-QUIC-Operational-Cons=
iderations</span></a></span><span lang=3D"EN-US" style=3D"font-family:"=
;Courier New"">.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">Thank you<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
<o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
(*)<o:p></o:p></span></p>
<ul style=3D"margin-top:0cm" type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-list:l0 level1 lfo2"><span style=3D"fo=
nt-family:"Courier New""><a href=3D"https://datatracker.ietf.org/=
doc/draft-ietf-netconf-over-quic/"><span lang=3D"EN-US">draft-ietf-netconf-=
over-quic</span></a></span><span lang=3D"EN-US" style=3D"font-family:"=
Courier New"">:
NETCONF over QUIC<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"m=
so-list:l0 level1 lfo2"><span style=3D"font-family:"Courier New""=
><a href=3D"https://datatracker.ietf.org/doc/draft-liu-grow-bmp-over-quic/"=
><span lang=3D"EN-US">draft-liu-grow-bmp-over-quic</span></a></span><span l=
ang=3D"EN-US" style=3D"font-family:"Courier New"">:
Using BMP over QUIC connection<o:p></o:p></span></li><li class=3D"MsoNorma=
l" style=3D"mso-list:l0 level1 lfo2"><span style=3D"font-family:"Couri=
er New""><a href=3D"https://datatracker.ietf.org/doc/draft-liu-sidrops=
-rpki-rtr-over-quic/"><span lang=3D"EN-US">draft-liu-sidrops-rpki-rtr-over-=
quic</span></a></span><span lang=3D"EN-US" style=3D"font-family:"Couri=
er New"">:
RPKI to Router Protocol over QUIC<o:p></o:p></span></li><li class=3D"MsoNo=
rmal" style=3D"mso-list:l0 level1 lfo2"><span style=3D"font-family:"Co=
urier New""><a href=3D"https://datatracker.ietf.org/doc/draft-llg-opsa=
wg-ipfix-over-quic/"><span lang=3D"EN-US">draft-llg-opsawg-ipfix-over-quic<=
/span></a></span><span lang=3D"EN-US" style=3D"font-family:"Courier Ne=
w"">:
IPFIX Protocol over QUIC<o:p></o:p></span></li><li class=3D"MsoNormal" sty=
le=3D"mso-list:l0 level1 lfo2"><span style=3D"font-family:"Courier New=
""><a href=3D"https://datatracker.ietf.org/doc/draft-retana-idr-bgp-qu=
ic/"><span lang=3D"EN-US">draft-retana-idr-bgp-quic</span></a></span><span =
lang=3D"EN-US" style=3D"font-family:"Courier New"">:
BGP over QUIC<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-l=
ist:l0 level1 lfo2"><span style=3D"font-family:"Courier New""><a =
href=3D"https://datatracker.ietf.org/doc/draft-yl-radext-quic-transport/"><=
span lang=3D"EN-US">draft-yl-radext-quic-transport</span></a></span><span l=
ang=3D"EN-US" style=3D"font-family:"Courier New"">:
RADIUS over QUIC<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"ms=
o-list:l0 level1 lfo2"><span style=3D"font-family:"Courier New"">=
<a href=3D"https://datatracker.ietf.org/doc/draft-yang-pce-pcep-over-quic/"=
><span lang=3D"EN-US">draft-yang-pce-pcep-over-quic</span></a></span><span =
lang=3D"EN-US" style=3D"font-family:"Courier New"">:
PCEP over QUIC<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-=
list:l0 level1 lfo2"><span style=3D"font-family:"Courier New""><a=
href=3D"https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpc-over-quicv1/"=
><span lang=3D"EN-US">draft-cel-nfsv4-rpc-over-quicv1</span></a></span><spa=
n lang=3D"EN-US" style=3D"font-family:"Courier New"">:
Remote Procedure Call over QUIC Version 1<o:p></o:p></span></li><li class=
=3D"MsoNormal" style=3D"mso-list:l0 level1 lfo2"><span style=3D"font-family=
:"Courier New""><a href=3D"https://datatracker.ietf.org/doc/draft=
-ietf-regext-epp-quic/"><span lang=3D"EN-US">draft-ietf-regext-epp-quic</sp=
an></a></span><span lang=3D"EN-US" style=3D"font-family:"Courier New&q=
uot;">:
Extensible Provisioning Protocol (EPP) Transport over QUIC<o:p></o:p></spa=
n></li></ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
</div>
<pre>_________________<wbr>______________________________<wbr>_____________=
_________________<wbr>______________________________<wbr>_
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.</pre></body>
</html>
--_000_PATP264MB676505917F8C7EACD83CED468851APATP264MB6765FRAP_--
--===============6434604907646134993==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KT1BTLUFSRUEg
bWFpbGluZyBsaXN0IC0tIG9wcy1hcmVhQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4g
ZW1haWwgdG8gb3BzLWFyZWEtbGVhdmVAaWV0Zi5vcmcK
--===============6434604907646134993==--