#IETF

🫧 socialcoding..smallcircles@social.coop
2026-02-23

@eyeinthesky @cwebber @evan @deadsuperhero

There are a couple of really great #IETF documents on protocol design and maintenance. You often see me mentioning protocol decay, which is only a paragraph in the splendid #RFC9413 Maintaining Robust Protocols.

The next section for instance is on detrimental ecosystem effects if you are either too stricly enforcing standards or are too laissez faire about them.

rfc-editor.org/rfc/rfc9413.html

#SocialWeb #ActivityPub

सिर्फ春sirfharu@en.osm.town
2026-02-21

THERE'S AN IETF RFC ABOUT MEANING OF MUST, SHOULD, MAY, ETC WTF!?

datatracker.ietf.org/doc/html/

#RFC #IETF

Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2026-02-20

Intéressante information à l'#IETF : un outil de mise en œuvre d'un brouillon de #RFC a été écrit par un #LLM qui a lu le brouillon. L'idée est que si une IA comprend correctement la spécification, les humains devraient y arriver.

Michael Richardsonmcr314@todon.nl
2026-02-19

@sam good job. As an #ietf veteran let.me know if I can help. Not sure where new #ogg stuff would go since the codec WG closed, but in many ways, CELLAR is the successor.

Sam Whitedsam@social.coop
2026-02-19

I did a bad thing… samwhited.codeberg.page/oggste

TL;DR this is the initial outline of an Internet Draft (I-D) for stem files using an open and non-patent-encumbered format. Currently it probably does not match the code in the same repo for generating them (codeberg.org/SamWhited/oggstem/) as I'm still experimenting with the layout of the files. This I-D has not been submitted to the IETF (at some point I'll move it to their data tracker). Feedback welcome.

#IETF #DJing #Stems

2026-02-17

That minipgp6-based SOP binary interoperates nicely with all other RFC 9580 implementations I've tested, including with PQC algorithms.

And the entire binary literally fits on a 💾

🥳

As I anticipated, RFC 9580 *really shines* ✨ in implementations that leave out all of the legacy parts.

The #OpenPGP WG at the #IETF specified an excellent modernization, with the "v6" formats. RFC 9580 perfectly balances full backward compatibility with *massive* forward-looking simplifications.

2026-02-16

I'd be happy to take this to IETF or contribute to a JSON Schema for nesbitt.io/2026/02/08/sandwich. #ietf #json

🫧 socialcoding..smallcircles@social.coop
2026-02-13

Hello @evan and @bifurcation .. a question.

For inclusion of #ActivityPub information resources on the delightful-fediverse-development curated list there is this (now expired) #IETF draft exploring #MIMI / #MLS versus AP. I find this draft to be well-written and informative, and thus the draft possibly a candidate for inclusion for people as additional background reading to the #SocialCG work on MLS. Unless there are so many changes since the creation of the draft that it may raise confusion, and should not be included. What is your opinion here?

ietf-wg-mimi.github.io/mimi-ar

2026-02-13

Routinator, our RPKI validation software, now sees more than 1000 Autonomous System Provider Authorization (ASPA) objects in the wild. These are published by operators to detect and prevent BGP route leaks.

ASPAs can be created in the hosted RPKI services of the RIPE NCC and ARIN, as well as our open-source RPKI Certification Authority software, Krill.

Open-source routing projects such as BIRD, OpenBGPD and FRRouting already offer support for ASPA, while major commercial vendor support is expected later this year.

#OpenSource #OpenStandards #IETF #RPKI #BGP #RoutingSecurity

A screenshot of the Routinator summary output.
Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2026-02-11

"have I finally attained pure dinosaur status by not hopping on the LLM bandwagon?"

#IETF

Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2026-02-11

La formule dans la nouvelle politique de contrôle des participants de l'#IETF : « The IETF community will treat people with kindness and grace, but not endless patience. »

[Il y a eu quelques trolls grâtinés.]

Judah Hansenjudahhansen
2026-02-10

The IETF (@ietf) has made a remarkable amount of great April Fools satire of their own technical documents. They're definitely worth the read: en.wikipedia.org/wiki/April_Fo.

Waitzman   Experimental   [Page 1]
===
RFC 2549   IP over Avian Carriers with QoS   1 April 1999

   Weighted fair queueing (WFQ) MAY be implemented using scales, as
   shown:

ASCII art of a scale. On the left is a box in two segments, both containing the text "10g." On the right is a crudely drawn ASCII art of a bird facing right. There are two consecutive periods beneath the bird on the scale, representing something that is eluded to with the text beneath:

   Carriers in the queue too long may leave log entries, as shown on the
   scale.
TechGlimmertechglimmer
2026-02-10

Good bot or bad bot? is becoming one of the biggest questions on the modern web.

Web Bot Auth is a new cryptographic standard that lets AI agents prove who they are, so sites can trust verified automation and block malicious scrapers.

In my latest TechGlimmer piece, I unpack how it works, why Cloudflare, AWS, and Fingerprint are adopting it, and what it means for creators and businesses.

techglimmer.io/what-is-web-bot

2026-02-10
@2something@transfem.social
Maybe upgrade to the #IETF chat standard #xmpp then. 😇
@babe@glitterkitten.co.uk
TheDoctorTheDoctor512
2026-02-07

Eine kleine Optimierung, große Wirkung: Geänderte CNAME-Reihenfolge legte 1.1.1.1 teilweise lahm. Der Vorfall zeigt, wie fragil -Implementierungen sind – nun soll ein -Draft für Klarheit sorgen.

Marcel SIneM(S)USsimsus@social.tchncs.de
2026-02-06

heise+ | Streit um Post-Quantum-TLS: Ist die #IETF-Standardisierung leicht zu kapern? | c't Magazin heise.de/hintergrund/Streit-um #heiseplus

Daniel Gultschdaniel@gultsch.social
2026-02-04

I understand that the endless social media debates about which messaging client is best are obnoxious. That’s why we need to finally adopt a common standard so everyone can choose between Cheogram, Conversations, and Yaxim, or Dino and Gajim, without having to convince everyone else to use the same one.

#Jabber #XMPP #IETF #RFC

2026-02-02

Only started to read into this "new" , informational #IETF #RFC, called "#Multicast Lessons Learned from Decades of Deployment Experience", but it's already a super interesting read:
datatracker.ietf.org/doc/draft

Kevin Karhan :verified:kkarhan@infosec.space
2026-02-02

Addendum: I was wrong.
Thanks for correcting me everyone!

@hisold WTF?

WHO AT #IETF decided to allow this #Enshittification???

#JavaScript is malware and #JS does not belong into any #RFC!!!

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst