Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Administered by:

Server stats:

255
active users

en.osm.town: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#ietf

13 posts9 participants0 posts today
Public
Stéphane Bortzmeyer

Les protocoles Internet plutôt applicatifs transportent souvent du texte qui sera montré aux utilisateurices (HTTP est l'exemple typique).
Les protocoles Internet plutôt d'infrastructure (BGP, DNS, NTP) ne transportent typiquement jamais de texte destiné aux utilisateurices. (Je vous laisse chercher une ou deux exceptions.)
Faut-il changer cela ? (Grosse discussion à l'#IETF.)

Replied in thread
Public
Kevin Karhan :verified:

@jens I think it's really sad for an organization like #IETF to still cling to in-person meetings.

  • I'd be more understanding it they were like EuroNCAP or OSHA, NTSB or other orgs that have to deal with physical safety and may include testing as part of their meetings with certified professionals assessing everything to quickly allow decisions.

I mean none of the folks at IETF's meetings are "#TechIlliterates" and it's not as if group videocalling and screensharing is something absurdly expensive nor that these meetings require actual privacy as per sensitivity of their nature.

  • Aslo with the current regime in place the USA is a "can't enter" for more people than ever before, as neither ESTA nor a Visa guarantees one is being let in.
Public
ulrike

Internet Standards Almanac: Who’s really shaping the internet? Our new tool helps answers three key questions:

- Who leads? Which actors dominate formal leadership positions, including chairing various working groups and committees.

- Who speaks? Which actors dominate discussions and mailing lists.

- Who publishes? Which actors author the largest number of technical standards.

article19.org/resources/intern

A cute cat in front of a graph
#InternetStandards#SDO#IETF
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
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!
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/

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
Stéphane Bortzmeyer

Interesting project at #IETF : "Authentication of non-human users to human-oriented Web sites / Discussion of use cases, requirements, and proposed solutions for authenticating non-human users ("bots") to Web sites intended for humans ("normal" Web sites). This is a follow-on from a side meeting at IETF 122."

mailman3.ietf.org/mailman3/lis

mailman3.ietf.orgInfo | web-bot-auth@ietf.org - IETF Mailman 3 Lists
Replied in thread
Public
Lars Eggert

@webmink Sometimes there are other choices than ISO. That ODF file format would have been suitable for an #IETF RFC, which are free to produce (for authors) and obtain (for everyone). I realize that the IETF has a much narrower mandate than ISO, but in this case it would have been an alternative.

ExploreLive feeds
About