Re: IEPG@IETF126: Call for presentations
Warren Kumari <[email protected]> Tue, 14 Jul 2026 11:20:50 -0500
| Newsgroups | gmane.ietf.iepg,gmane.ietf.general |
|---|---|
| Message-ID | <CAHw9_iKCgfnhkdYGsVE5-pNvDx_=i_OAsUKxHSGuG26C2dUGHQ@mail.gmail.com> |
--===============6625877063265795514== Content-Type: multipart/alternative; boundary="0000000000004443050656949733" --0000000000004443050656949733 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, Thanks to everyone who volunteered presentations -- we now have a (very) full agenda! But, please keep your ideas in mind for the next meeting! W On Tue, Jun 30, 2026 at 4:32=E2=80=AFAM, Jen Linkova <[email protected]> wr= ote: > Hi all, > > The IEPG is an informal gathering that meets on the Sunday prior to IETF > meetings. The intended theme of these meetings is essentially one of > operational relevance in some form or fashion. > > These presentations / discussions are generally around things like > problems discovered when deploying various protocols, interesting > operational issues or deployments, interesting measurement results, fun > things discovered while building networks, etc. It is much more > operationally focused than an IETF Working Group meeting, and is not a > place to just present your shiny new Internet Draft (that's HotRFC and > / or the relevant WG). > > So, things like: "If you have a chain of CNAME records, and one of them i= s > at the apex of a DNS zone, the 3 largest resolver implementations all do > different things. This allows you to fingerprint resolvers - here are som= e > results=E2=80=A6.", or "We implemented BGP Flowspec to allow fast respons= e to DDoS > events=E2=80=A6 and then we pushed out a rule which blocked access to the > controller. This is what happened after that=E2=80=A6" are all great IEPG > presentations. > > But "Here is my draft. It adds the Foo extension to the Bar protocol. The > format of the Foo extension looks like this=E2=80=A6. If a router using B= ar sees > this extension, it should increment the Baz counter. The YANG model for F= oo > looks like this=E2=80=A6 " is not =E2=80=94 that should be discussed in t= he Bar WG, or > HotRFC, or Dispatch, or similar=E2=80=A6 > > Previous presentations are here: http://www.iepg.org/ > > More info on the IEPG: RFC 1690 - https://tools.ietf.org/html/rfc1690 > > We will have remote participation through MeetEcho. > > If you have some sort of operationally relevant topic which you'd be > willing to present, please let the chairs ([email protected]) know. > > -- > Cheers, Jen Linkova > --0000000000004443050656949733 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <html><head></head><body><div> <div> <div>Hi all,</div><div><br></div><div>Thanks to everyone who volunt= eered presentations -- we now have a (very) full agenda!</div><div><br></di= v><div>But, please keep your ideas in mind for the next meeting!</div><div>= W</div> <div></div> <br> <div class=3D"gmail_signature"> =20 =20 </div> </div> <div class=3D"gmail_extra"> <br> <div class=3D"gmail_quote"> On Tue, Jun 30, 2026 at 4:32=E2=80=AFAM, Jen Linkova <<a href=3D"mailto:[email protected]" target=3D"_blank">furry13@= gmail.com</a>> wrote: <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0.8ex;border-= left:1px #ccc solid;padding-left:1ex"> <div><div><p>Hi all, </p><p> The IEPG is an informal gathering that meets on the Sunday prior to IETF meetings. The intended theme of these meetings is essentially one of operational relevance in some form or fashion. </p><p> These presentations / discussions are generally around things like problems discovered when deploying various protocols, interesting operational issues or deployments, interesting measurement results, fun things discovered while building networks, etc. It is much more operationally focused than an IETF Working Group meeting, and is not a place to just present your shiny new Internet Draft (that's HotRFC and <br> / or the relevant WG). </p><p> So, things like: "If you have a chain of CNAME records, and one of them is at the apex of a DNS zone, the 3 largest resolver implementations all do different things. This allows you to fingerprint resolvers - here are some results=E2=80=A6.", or "We = implemented BGP Flowspec to allow fast response to DDoS events=E2=80=A6 and then we pus= hed out a rule which blocked access to the controller. This is what happened after that=E2=80=A6" are all great IEPG presentations. </p><p> But "Here is my draft. It adds the Foo extension to the Bar protocol. The format of the Foo extension looks like this=E2=80=A6. If a router using Bar sees this extension, it should increment the Baz counter. The YANG model for Foo looks like this=E2=80=A6 " is not =E2=80=94 that should = be discussed in the Bar WG, or HotRFC, or Dispatch, or similar=E2=80=A6 </p><p> Previous presentations are here: <a href=3D"http://www.iepg.org/">http://ww= w.iepg.org/</a> </p><p> More info on the IEPG: RFC 1690 - <a href=3D"https://tools.ietf.org/html/rf= c1690">https://tools.ietf.org/html/rfc1690</a> </p><p> We will have remote participation through MeetEcho. </p><p> If you have some sort of operationally relevant topic which you'd be willing to present, please let the chairs (<a href=3D"mailto:iepg-chairs@ie= tf.org">[email protected]</a>) know. </p><p> --=20 <br> Cheers, Jen Linkova</p></div></div> </blockquote> </div> </div> </div></body></html> --0000000000004443050656949733-- --===============6625877063265795514== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Iepg mailing list Iepg-/1rEenAg/[email protected] https://lists.isc.org/mailman/listinfo/iepg --===============6625877063265795514==--