#ietf

14 posts · Last used 16d

Back to Timeline
Lorenzo Miniero @lminiero@fosstodon.org · Jul 29, 2026
At the latest #IETF in Vienna, we decided to run a peculiar experiment... stream the #MoQ sessions using #MoQ itself! All using our existing #WebRTC infrastructure as the source for the media. If you want to learn more, this blog post is a detailed overview on how we made that happen. Feedback (and boosts) welcome! https://www.meetecho.com/blog/moq-ietf126/
2
0
2
Erik Nygren :verified: @nygren@hachyderm.io · Jul 28, 2026
Following some discussions during #IETF last week (in the hallway and on various mailing lists), the awesome #IPvFoo extension now shows in Mozilla #FireFox if connections used H1, H2, or H3, not just IPv4-vs-IPv6! This is helpful for seeing how that angle of Happy Eyeballs works. (It would work in the Chrome version as well but the interface for getting at this info is broken and always returns H1.) Note that if the connection starts with H2 but then switches to H3 for later objects on the hostname (eg, if you have an Alt-Svc record) then it will show H3 rather than H2. https://addons.mozilla.org/en-US/firefox/addon/ipvfoo/ #QUIC #HTTP2 #HTTP3 #IPv6 #HappyEyeballs
17
3
12
LibreQoS @LibreQoS@fosstodon.org · Jul 25, 2026
1
1
1
Kushal Das :python: :tor: 🇸🇪 @kushal@toots.dgplug.org · Jul 25, 2026
I attended my first ever #IETF.
2
1
0
heise online @heiseonline@social.heise.de · Jul 24, 2026
IETF: Warnung vor Nebenwirkungen eines Social-Media-Verbots für Jugendliche Auf dem IETF-Treffen in Wien warnten Entwickler vor den Risiken von Altersverifikationssystemen. Diese könnten Sicherheit und Vertraulichkeit im Netz gefährden. https://www.heise.de/news/IETF-Warnung-vor-Nebenwirkungen-eines-Social-Media-Verbots-fuer-Jugendliche-11376975.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon #Datenschutz #DigitalServicesAct #IETF #Internet #Jugendschutz #Netzpolitik #Security #news
0
0
1
Heather @sphcow@mas.to · Jul 23, 2026
I have been in a few of the many, many conversations this week at #IETF regarding if and how to built new Internet protocols for AI agents, and I have so many questions. So many, but maybe also just one. Are we ultimately moving towards building a separate internet (lowercase on purpose) just for AI? Is that what all these discussions lead to? FWIW, I think that’s probably a terrible idea. I don’t think I’ve heard anything that suggests the problems we’re attempting to solve are specific to agentic AI. AI, as always, makes things go faster (and so scale is a legit problem) but the discovery problems, the identification problems, the authentication and authorization problems… they aren’t precisely new. There are more of them, and there are questions as to whether agents have any right to privacy, but do we need entirely new protocols to account for that? hmmmmmm.
8
3
3
Heather @sphcow@mas.to · Jul 20, 2026
With over 100 active Internet Drafts on various topics around AI, a third of the available side meetings, and nearly half of the HotRFC lightning talks at #IETF 126, I’m feeling more than a little overwhelmed with all the heat and so very little light.
14
0
2
Erik Nygren :verified: @nygren@hachyderm.io · Jul 20, 2026
Topic of #IETF conversation in #HAPPYWG and elsewhere is when and for how long it is acceptable to ignore #DNS TTLs (as long as the client validates the server cert still matches): https://datatracker.ietf.org/doc/html/draft-gakiwate-dnsop-optimistic-dns-00 It is already generating many good hallway conversations. The tension is between performance ("if we ignore TTLs and use minutes/hours/days old A/AAAA records things connection establishment is faster") and operational correctness and safety. Clients have been implementing this for years, but more want to do so. Operationally this has the potential to be quite surprising, making it much harder for operators to drain traffic from servers by taking them out of the DNS, whether to reuse IPs for other purposes, for maintenance, for DNS load balancing, or when switching providers. As much as we might like it to, just because a server returns a valid cert is not an reason to assume that it is intended to be in service. (Not that naming or cache invalidation are hard problems in Computer Science or anything.)
3
2
1
Olaf Kolkman @olaf@social.secret-wg.org · Jul 19, 2026
Running into an old friend at #IETF. Time for some friendly social conversation, so I engage and 'Sorry, my CPU is at 100%' is the reply. I smile and understand.
0
0
0
Martin Hoffmann @partim@social.tchncs.de · Jul 17, 2026
Travel Day! Today should have been a simple journey to Vienna for #IETF, but things keep going off the rails. Engineering works in Germany complicate things, but I found a nice, quick trip. Except that engineering works in the Netherlands made that impossible. A little reshuffle salvaged most of it. But now I see that DB moved ICE 211 to run five minutes earlier (not sure when that happened), so our connection in Mannheim is down to two minutes. To make that definitely not work, they also moved ICE 225 to a different platform. We can still change in Stuttgart, Ulm, or Augsburg, but that means our reservations will be void and I suspect 211, which goes to Graz, will be busy. With a bit of luck, ICE 225 will have so much delay by Mannheim that none of this matters, anyway.
8
1
0
Jeffrey Haas @Jhaas@infosec.exchange · Jul 12, 2026
The #ietf126 agenda for the IDR working group that standardizes BGP has been posted. It's going to be a busy week! #ietf
0
0
0
Wish the sun to stand still 🌞 @tasket@infosec.exchange · Jul 04, 2026
RE: https://mas.to/@nemo/116864001224955528 NSA involved in "off the rails" warrant-less mass surveillance. This (and the fact that their chain of command was purged by the Trump regime) should be factored into the debate around the IETF relying on the NSA's input. If your position is that a simple RFC is "not a big deal" then IDK why you're making a big deal out of people like @djb@mastodon.cr.yp.to being against it. #FISA #crypto #ietf #tls #pqc #privacy #surveillance
1
0
1
ClaudioM @claudiom@bsd.network · Apr 20, 2026
#IPv8?! We're still trying to get everyone to agree to move over to #IPv6!! :flan_despair::flan_XD:#ietf #InternetProtocol https://www.ietf.org/archive/id/draft-thain-ipv8-00.html
0
3
0

You've seen all posts