Re: IEPG@IETF126: Call for presentations

[Warren Kumari <[e-mail]>]

Hi all,

We do still have free agenda time, so please let us know if you'd like to
present something of interest to IEPG…

W


On Tue, Jun 30, 2026 at 4:32 AM, Jen Linkova <[e-mail]> wrote:

> 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 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….", or "We implemented BGP Flowspec to allow fast response to DDoS
> events… and then we pushed out a rule which blocked access to the
> controller. This is what happened after that…" 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…. If a router using Bar sees
> this extension, it should increment the Baz counter. The YANG model for Foo
> looks like this… " is not — that should be discussed in the Bar WG, or
> HotRFC, or Dispatch, or similar…
>
> 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 ([e-mail]) know.
>
> --
> Cheers, Jen Linkova
>