[OPS-AREA]Re: [OPSAWG]Technical Deep Dive (TDD) Chai rs: Call for Volunteers
Dan Voyer IETF <[email protected]> Wed, 8 Jul 2026 11:34:36 -0400
| Newsgroups | gmane.ietf.ops |
|---|---|
| Message-ID | <CA+nRKkqzCHE5Mtx3Q7ccDwU=MmjqjDWWzCrxmo7ARHi-O9Hx2A@mail.gmail.com> |
--===============3440533107299953345== Content-Type: multipart/alternative; boundary="000000000000651ee406561b3fe6" --000000000000651ee406561b3fe6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Mo/Andy, Are there any developments or updates on this ? Thanks, Dan On Wed, Jun 10, 2026 at 11:50=E2=80=AFAM Dan Voyer IETF <danvoyerwork@gmail= .com> wrote: > Hi Mo/Andy > > Hi Med, Andy, > > I would like to volunteer to join the TDD Chairs team. > > I believe I could bring a useful operator and routing/operations > perspective to the team. I have a strong ISP/operator background, includi= ng > many years working on IP/MPLS backbone architecture and operations, and I > remain very focused on how technologies are deployed, operated, automated= , > and explained in real networks. > > From an IETF perspective, I am active across the OPS and RTG areas, > including SRv6ops, OPSAWG/NMOP-related work, and topics around routing, > telemetry, YANG/gNMI, automation, network digital maps/knowledge graphs, > and operational observability. I would be happy to help identify timely > topics, engage potential presenters, and shape sessions that are > technically deep but also useful and accessible to operators. > > The areas I could best help cover are routing, SR/MPLS/SRv6, network > operations, telemetry/observability, automation, and operator deployment > experience. > > Dan > > On Tue, May 26, 2026 at 2:31=E2=80=AFAM <[email protected]> wr= ote: > >> Hi all, >> >> >> >> The Technical Deep Dive (TDD) is a venue for tutorials and presentations >> that provide insights into technologies which span multiple areas. TDD >> sessions are usually organized during IETF weeks, but other configuratio= ns >> may be considered. An overview of previous TDD sessions can be found at: >> https://datatracker.ietf.org/group/tdd/meetings/. >> >> >> >> In order to arrange for sessions covering various IETF areas and identif= y >> timely topics, we would like to have a team of TDD Chairs that will be >> responsible for the following: >> >> >> >> - Identify and suggest topics for future TDD sessions. >> - Approach and engage with presenters to cover specific topics. >> - Coordinate with presenters to build a session strawman. >> - Put in place a procedure to receive unsolicited talk requests. >> - Socialize TDD within the IETF and outside (RIPE, NANOG, etc.). >> >> >> >> If you are interested to join this team, please drop us an email. Please >> indicate the area(s) that you can cover. >> >> >> >> The team will be selected to ensure complementarity, diversity, and wide >> topics coverage. >> >> >> >> Cheers, >> >> Andy & Med >> >> ________________________________________________________________________= ____________________________________ >> Ce message et ses pieces jointes peuvent contenir des informations confi= dentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r= ecu 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 d= elete this message and its attachments. >> As emails may be altered, Orange is not liable for messages that have be= en modified, changed or falsified. >> Thank you. >> >> _______________________________________________ >> OPSAWG mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> > --000000000000651ee406561b3fe6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi Mo/Andy,<div><br></div><div>Are there any developments = or updates on this ?</div><div><br></div><div>Thanks,</div><div>Dan=C2=A0</= div></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"= ltr" class=3D"gmail_attr">On Wed, Jun 10, 2026 at 11:50=E2=80=AFAM Dan Voye= r IETF <<a href=3D"mailto:[email protected]">[email protected]= </a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:= 0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">= <div dir=3D"ltr">Hi Mo/Andy<div><br></div><div><p>Hi Med, Andy,</p><p>I wou= ld like to volunteer to join the TDD Chairs team.</p><p>I believe I could b= ring a useful operator and routing/operations perspective to the team. I ha= ve a strong ISP/operator background, including many years working on IP/MPL= S backbone architecture and operations, and I remain very focused on how te= chnologies are deployed, operated, automated, and explained in real network= s.</p><p>From an IETF perspective, I am active across the OPS and RTG areas= , including SRv6ops, OPSAWG/NMOP-related work, and topics around routing, t= elemetry, YANG/gNMI, automation, network digital maps/knowledge graphs, and= operational observability. I would be happy to help identify timely topics= , engage potential presenters, and shape sessions that are technically deep= but also useful and accessible to operators.</p><p>The areas I could best = help cover are routing, SR/MPLS/SRv6, network operations, telemetry/observa= bility, automation, and operator deployment experience.</p><p>Dan</p></div>= </div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">= On Tue, May 26, 2026 at 2:31=E2=80=AFAM <<a href=3D"mailto:mohamed.bouca= [email protected]" target=3D"_blank">[email protected]</a>> wro= te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px = 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div> <div lang=3D"FR"> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Hi all,<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">The Technical Deep Dive (TDD) is a venue for tutorials and p= resentations that provide insights into technologies which span multiple ar= eas. TDD sessions are usually organized during IETF weeks, but other configurations may be considered. An overview of previous= TDD sessions can be found at:=C2=A0</span><span style=3D"font-family:"= ;Courier New""><a href=3D"https://datatracker.ietf.org/group/tdd/meeti= ngs/" target=3D"_blank"><span lang=3D"EN-US">https://datatracker.ietf.org/g= roup/tdd/meetings/</span></a></span><span lang=3D"EN-US" style=3D"font-fami= ly:"Courier New"">.<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">In order to arrange for sessions covering various IETF areas= and identify timely topics, we would like to have a team of TDD Chairs tha= t will be responsible for the following:<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><u></u>=C2=A0<u></u></span></p> <ul style=3D"margin-top:0cm" type=3D"disc"> <li class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cou= rier New"">Identify and suggest topics for future TDD sessions.<u></u>= <u></u></span></li><li class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"fo= nt-family:"Courier New"">Approach and engage with presenters to c= over specific topics.<u></u><u></u></span></li><li class=3D"MsoNormal"><spa= n lang=3D"EN-US" style=3D"font-family:"Courier New"">Coordinate w= ith presenters to build a session strawman.<u></u><u></u></span></li><li cl= ass=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Courier N= ew"">Put in place a procedure to receive unsolicited talk requests.<u>= </u><u></u></span></li><li class=3D"MsoNormal"><span lang=3D"EN-US" style= =3D"font-family:"Courier New"">Socialize TDD within the IETF and = outside (RIPE, NANOG, etc.).<u></u><u></u></span></li></ul> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">If you are interested to join this team, please drop us an e= mail. Please indicate the area(s) that you can cover.<u></u><u></u></span><= /p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">The team will be selected to ensure complementarity, diversi= ty, and wide topics coverage.<u></u><u></u></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= <u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= Cheers,<u></u><u></u></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= Andy & Med<u></u><u></u></span></p> </div> <pre>______________________________________________________________________= ______________________________________ 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 message= s 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 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></div> _______________________________________________<br> OPSAWG mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]" ta= rget=3D"_blank">[email protected]</a><br> </div></blockquote></div> </blockquote></div> --000000000000651ee406561b3fe6-- --===============3440533107299953345== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KT1BTLUFSRUEg bWFpbGluZyBsaXN0IC0tIG9wcy1hcmVhQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4g ZW1haWwgdG8gb3BzLWFyZWEtbGVhdmVAaWV0Zi5vcmcK --===============3440533107299953345==--