This... seems very interesting

#Bluesky is "...standardizing parts of #ATProtocol in an effort to establish long-term governance for the protocol."

"to establish long-term governance for the protocol"

Here: https://docs.bsky.app/blog/taking-at-to-ietf

Also see at #Github:

"Add patent pledge link to README (# 4246)"

"Bluesky Social PBC has committed to a software patent non-aggression pledge. For details see [the original announcement] (https://bsky.social/about/blog/10-01-2025-patent-pledge)."

Here: https://github.com/bluesky-social/atproto/commit/d239f0bcf5e7ed391c8ced32e13aaa4c1324a757

All that said, not sure exactly what it *means* long-term, but it is... interesting

#AT #IETF #Patents

#IETF Pecha-Kucha (funny talk) of Barbara Jantzen at the last meeting, about #DNSSEC. Next time you have a DNSSEC issue, watch the video. https://www.youtube.com/watch?v=7mQ5x7Jpj4I

(For my French-speaking followers: good level of englsh required.)

In july 2025, there was the #IETF meeting, the 123th, in Madrid. Before the meeting, there was the now traditional hackathon. I worked on the future protocol #RPP (RESTful Provisioning Protocol), which may be the successor of #EPP. https://www.bortzmeyer.org/hackathon-ietf-123.html

#IETF123

Technische Maßnahmen gegen den Ansturm der KI-Crawler

KI-Unternehmen schicken massenhaft neue Crawler los. Wie diese geregelt werden können, beschäftigt auch die IETF.

https://www.heise.de/news/Technische-Massnahmen-gegen-den-Ansturm-der-KI-Crawler-10497930.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#IETF#Internet#IT#KünstlicheIntelligenz #news

In the transcript of an #IETF meeting, "I dislike that intensely" became "I did like this intensely".

The speaker at #IETF is francophone and adds many "Alors" and "Voilà" in his talk in english :-)

Cool set of tools linked to today in a presentation in the #IETF#HAPPYWG session:

https://www.happy-eyeballs.net/

It allows you to characterize the Happy Eyeballs behavior of a client, such as to see how much of a delay in DNS resolution or TCP connection response triggers a failback from IPv6 to IPv4.

See more details in Dave Plonka's talk:

https://datatracker.ietf.org/meeting/123/materials/slides-123-happy-hackathon-maprg-happy-eyeballs-and-ipv6-test-pod-open-testing-00

#HappyEyeballs#IPv6#IETF123

Cool set of tools linked to today in a presentation in the #IETF#HAPPYWG session:

https://www.happy-eyeballs.net/

It allows you to characterize the Happy Eyeballs behavior of a client, such as to see how much of a delay in DNS resolution or TCP connection response triggers a failback from IPv6 to IPv4.

See more details in Dave Plonka's talk:

https://datatracker.ietf.org/meeting/123/materials/slides-123-happy-hackathon-maprg-happy-eyeballs-and-ipv6-test-pod-open-testing-00

#HappyEyeballs#IPv6#IETF123

Heard at #IETF: "paywall standards [ISO was mentioned as an example] are a security problem [because implementors will not be able to work on the real standard]"

Many people on the #IETF wifi networks in Madrid are running into problems using @signalapp. My hypothesis is that the large number of users in a small number of IPv6 /64s is triggering some rate-limiting. Does #Signal have the ability to apply reputation and rate-limits on a /128 basis for specific /64s? (Clearly future IETFs should use /64-per-host as @abhayakara pointed out on the mailing list.)

Seen on a slide at #IETF
"from all over the world (mostly Europe)"

#smallWorld

In Memoriam: Dave Täht @mtaht - Jason Livingood at @ietf 123 Plenary 🖤

Very much appreciated!

Watch it here:
https://youtu.be/5Ju82sykvhM?si=uUGvYQ3W0W8MsXPJ

#IETF123#IETF #bufferbloat#RFC8290#FQ_CoDel#sch_CAKE #LibreQoS#QoE#OpenSource #latency #jitter#Linux#BandwidthIsALIE

Technische Maßnahmen gegen den Ansturm der KI-Crawler

KI-Unternehmen schicken massenhaft neue Crawler los. Wie diese geregelt werden können, beschäftigt auch die IETF.

https://www.heise.de/news/Technische-Massnahmen-gegen-den-Ansturm-der-KI-Crawler-10497930.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#IETF#Internet#IT#KünstlicheIntelligenz #news

In Memoriam: Dave Täht @mtaht - Jason Livingood at @ietf 123 Plenary 🖤

Very much appreciated!

Watch it here:
https://youtu.be/5Ju82sykvhM?si=uUGvYQ3W0W8MsXPJ

#IETF123#IETF #bufferbloat#RFC8290#FQ_CoDel#sch_CAKE #LibreQoS#QoE#OpenSource #latency #jitter#Linux#BandwidthIsALIE

Many people on the #IETF wifi networks in Madrid are running into problems using @signalapp. My hypothesis is that the large number of users in a small number of IPv6 /64s is triggering some rate-limiting. Does #Signal have the ability to apply reputation and rate-limits on a /128 basis for specific /64s? (Clearly future IETFs should use /64-per-host as @abhayakara pointed out on the mailing list.)

Now, the #IETF itself: impact of crawlers on the many IETF Web services. The IETF data must be public, so blocking is not an option in most cases.

20 Mbytes (on 277 by month) are sent to bots. (AI crawlers are a minority of these bots.)

#IETF123

Heard in the #IETF meeting: "milestones are aspirations"

so it wasn't bad enough that google pops up all over the show with their signin dialog on the top right, so the #IETF follows suit with their form of bullshit?

I'm neither an attendee nor have I an account there.

https://datatracker.ietf.org/doc/html/rfc1034

Ayant entendu le terme anglophone de "centa-thread" à l'#IETF, je propose de parler d'« hectofil » pour un fil de discussion sur une liste de discussion, qui a dépassé cent messages.

In the chat of the Meetecho tool at an #IETF meeting: "I don't have a time machine, unfortunately, as evident by the lack of pterosaurs pets attending IETF"