Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

340K
active users

mastodon.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-nightly.2025-04-15

#ietf

6 posts4 participants0 posts today
Public
Hippo 🍉

The EU is mandating messaging apps be compatible with each other, but the current plan is looking less like #federation and more like "register your chat app with Meta, send them all your data, and link with their prescribed APIs that they may decide to change any day"

At the risk of preaching to the converted, here's @guusdk advocating for *real* interoperability between messaging apps, using an existing, battle-tested, #IETF-backed standard: #XMPP! :xmpp:

discourse.igniterealtime.org/t

Ignite Realtime Community Forums · It’s time for real interoperability. Let’s make it happen!When I explain to others what I do for a living, I often ask why it is that we are not surprised that one can use a Gmail account to send an email to someone who uses an Outlook account, yet many people fully accept that you can’t send a message to someone using WhatsApp from a Telegram account. We’re not surprised that we can use our phone to set up a call with someone who uses a different brand of phone (or is subscribed to a different provider), yet, for instant messaging, we find ourselves i...
Public *
Max Resing

Just wanted to share some thoughts on #RFC9715 - an #RFC that defines standards on reducing the #DNS issue of IP fragmentation over #UDP. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the #Internet. A great leap forward to (hopefully) reduce the reflection/amplification #DDoS potential of DNS.

Just today I learned that #Google will configure their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to #TCP.

#ipv4#ipv6#ietf
Public
Paul Wouters

Google Alloydb Omni on any cloud with Aiven - something
I worked on for my $dayjob (yes I do more than just #ietf work 😜) linkedin.com/posts/oskarisaare

www.linkedin.comManaged Google AlloyDB Omni service | Aiven | Oskari SaarenmaaWe are incredibly honored to be named Google Cloud 2025 Partner of the Year for Databases! This award is a testament to the exceptional collaboration between Aiven and Google Cloud, and we extend our sincere gratitude to the entire Google Cloud team for this recognition. Together, we’ve achieved some great milestones, most notably the GA announcement of Aiven for AlloyDB Omni at #GoogleCloudNEXT. By combining Google Cloud's powerful AlloyDB Omni, with Aiven's expertise in managed services, we're empowering developers to: - Deploy AlloyDB Omni across all major clouds (AWS, Azure, Google Cloud) - Leverage Aiven's robust PostgreSQL extensions seamlessly - Maintain enterprise-grade security and compliance with ease - Benefit from a reliable 99.99% uptime SLA This joint offering simplifies database management, allowing developers to focus on building innovative, AI-driven applications with the full power of PostgreSQL, regardless of their cloud environment. We're excited to continue this journey with Google Cloud, and deliver transformative database solutions to our customers. Discover the power of Aiven for AlloyDB Omni and start your 30-day free trial. #GoogleCloudNEXT #Aiven #AlloyDBOmni #PostgreSQL #AI #GoogleCloudPartners #MultiCloud Andi Gutmans Barry Morris Gurmeet G. Elena Zykova John Kennedy Mike von Speyr Conor Forde Jeff Mery https://lnkd.in/eWXVahqK
Public
Fabrizio T.

The Internet isn't value-neutral, and neither is the #IETF. We want the Internet to be useful for communities that share our commitment to openness and fairness. We embrace technical concepts such as decentralized control, edge-user empowerment and sharing of resources, because those concepts resonate with the core values of the IETF community. These concepts have little to do with the technology that's possible, and much to do with the technology that we choose to create.
-- RFC 3935, Oct 2004

Continued thread
Public
Xamanismo Coletivo

#DigitalSovereignity needs #StructuralPower

"Who enforces digital standards such as those that come from the #IETF or the #W3C?
In a few cases, it is state power (e.g. accessibility in some jurisdictions) but that's rare. In some other cases, it's market discipline… But most of the important areas of the #digitalsphere have stopped being open, competitive markets over a decade ago so that the market no longer has a credible disciplining function to enforce #standards. What matters is who has the #structuralpower to deploy the standards they want to see and avoid those they dislike."
@robin

berjon.com/digital-sovereignty

Robin BerjonDigital SovereigntyDigital sovereignty has a bad reputation. In internet governance circles, sovereignty is considered awkward enough to be referred to by as the "s-word." It is often associated with misguided attempts at returning to the era of national champions, like building a French search engine or a European Google, or worse with the eternal boogeyman that is the "splinternet." It doesn't have to be this way!
Continued thread
Public *
T_X

@ffhl @videolan die technische Hintergrund der neuen Streams:
Statt #IPv6 / UDP / #RTP / #Opus. Ist es jetzt: IPv6 / UDP / #MPEG2TS / RTP / Opus.
Es ist also noch ein gaaanz toller (Sarkasmus), proprietärer, unnötiger Protokollheader dazwischen gekommen, der nur das Paket aufbläht. VLC v3 kann aber noch nicht das #IETF #RFC standardisierte, native RTP-Opus, das kann erst der nightly/v4.
Sobald VLC endlich mal releasen sollte, schmeiß ich das MPEG-TS auch ganz schnell wieder weg.

#multicast
Public
Tim Hergert

Was really looking forward to an April 1 IETF RFC this year - but it appears i will be disappointed this year.

Instead - I guess I'll have to share some of my favorites from years past

RFC 3514 "The Security Flag in the IPv4 Header"
datatracker.ietf.org/doc/html/

RFC 1149 "A Standard for the Transmission of IP Datagrams on Avian Carriers"

datatracker.ietf.org/doc/html/

IETF DatatrackerRFC 3514: The Security Flag in the IPv4 HeaderFirewalls, packet filters, intrusion detection systems, and the like often have difficulty distinguishing between packets that have malicious intent and those that are merely unusual. We define a security flag in the IPv4 header as a means of distinguishing the two cases. This memo provides information for the Internet community.
#IETF#RFC#AprilFools
Public
Brett Sheffield (he/him)

#IETF RFC 9777 was released last month, replacing RFC 3810 for #Multicast Listener Discovery ( #MLD2 ).

Reviewing this, aside from a bunch of textual clarifications and fixes, the only real technical change to speak of was an adjustment to the Multicast Address Listening Interval (MALI).

I've patched #libmld and #librecast with the new timer value and the change will be included in the next release.

datatracker.ietf.org/doc/html/

Logo of the IETF
IETF DatatrackerRFC 9777: Multicast Listener Discovery Version 2 (MLDv2) for IPv6This document specifies the Multicast Listener Discovery version 2 (MLDv2) protocol. MLD is used by an IPv6 router to discover the presence of multicast listeners on directly attached links and to discover which multicast addresses are of interest to those neighboring nodes. MLDv2 is designed to be interoperable with MLDv1. MLDv2 adds the ability for a node to report interest in listening to packets with a particular multicast address only from specific source addresses or from all sources except for specific source addresses. This document updates RFC 2710 and obsoletes RFC 3810.
Public *
jbz

🚫 Boycott IETF 127

｢ The IETF Administration LLC has decided to continue to hold meetings in the US, in spite of significant threats to the safety of the community in traveling there. As an Internet community we strive to include everyone. Holding a meeting in the US is incompatible with our values. We call on the IETF community to refuse to travel to the 127th IETF meeting, to be held in San Francisco ｣

boycott-ietf127.org/

boycott-ietf127.orgBoycott IETF 127
More from Q ✨
#IETF#humanrights#uspol
ExploreLive feeds
About