bildung.social

1 Beitrag1 Beteiligte*r0 Beiträge heute

Xamanismo Coletivo<a href="https://hachyderm.io/tags/DigitalSovereignity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DigitalSovereignity</a> needs <a href="https://hachyderm.io/tags/StructuralPower" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StructuralPower</a>"Who enforces digital standards such as those that come from the <a href="https://hachyderm.io/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> or the <a href="https://hachyderm.io/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#W3C</a>? 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 <a href="https://hachyderm.io/tags/digitalsphere" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#digitalsphere</a> have stopped being open, competitive markets over a decade ago so that the market no longer has a credible disciplining function to enforce <a href="https://hachyderm.io/tags/standards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#standards</a>. What matters is who has the <a href="https://hachyderm.io/tags/structuralpower" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#structuralpower</a> to deploy the standards they want to see and avoid those they dislike." <a href="https://mastodon.social/@robin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@robin</a> <a href="https://berjon.com/digital-sovereignty/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://berjon.com/digital-sovereignty/</a>

T_X<a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> <a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@videolan</a> die technische Hintergrund der neuen Streams: Statt <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> / UDP / <a href="https://chaos.social/tags/RTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RTP</a> / <a href="https://chaos.social/tags/Opus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Opus</a>. Ist es jetzt: IPv6 / UDP / <a href="https://chaos.social/tags/MPEG2TS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MPEG2TS</a> / 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 <a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> <a href="https://chaos.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> 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.<a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a>

Brett Sheffield (he/him)<a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> RFC 9777 was released last month, replacing RFC 3810 for <a href="https://chaos.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a> Listener Discovery ( <a href="https://chaos.social/tags/MLD2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MLD2</a> ).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 <a href="https://chaos.social/tags/libmld" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libmld</a> and <a href="https://chaos.social/tags/librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librecast</a> with the new timer value and the change will be included in the next release.<a href="https://datatracker.ietf.org/doc/html/rfc9777" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/doc/html/rfc9777</a>

Fly it.Somebody here with some experience in <a href="https://chaos.social/tags/RFC5545" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC5545</a>? I would love to use the <a href="https://chaos.social/tags/EXRULE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EXRULE</a> feature for recurring exceptions, but it was deprecated. How can I replace it without determining specific actual dates?<a href="https://chaos.social/tags/iCalendar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iCalendar</a> <a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> <a href="https://chaos.social/tags/iCal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iCal</a> :BoostOK:

litLet the <a href="https://mastodon.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> know that they can no longer have international meetings in the <a href="https://mastodon.social/tags/USA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#USA</a> <a href="https://boycott-ietf127.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://boycott-ietf127.org/</a>

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 ｣<a href="https://boycott-ietf127.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://boycott-ietf127.org/</a><a href="https://indieweb.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> <a href="https://indieweb.social/tags/humanrights" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#humanrights</a> <a href="https://indieweb.social/tags/uspol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uspol</a> <a href="https://indieweb.social/tags/BoycottIETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BoycottIETF</a> <a href="https://indieweb.social/tags/BoycottIETF127" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BoycottIETF127</a>

Shane KerrI signed up for the boycott. If you attend the IETF you should to:<a href="https://boycott-ietf127.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://boycott-ietf127.org/</a><a href="https://fosstodon.org/tags/ietf127" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ietf127</a> <a href="https://fosstodon.org/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ietf</a>

Stéphane Bortzmeyer<a href="https://mastodon.gougere.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> drama about a meeting in the USA <a href="https://boycott-ietf127.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://boycott-ietf127.org/</a>

Vesna Manojlović<a href="https://expressional.social/@phloggen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@phloggen</a> <a href="https://glauca.space/@q" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@q</a> in the meantime there is some activity about environmental sustainability for protocols design : IAB workshops, IRTF research group & an <a href="https://social.v.st/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> GREEN working group <a href="https://wiki.techinc.nl/Sustainability#IETF_documents" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://wiki.techinc.nl/Sustainability#IETF_documents</a>

Alexander BochmannThere's an initiative trying to force the IETF to hold meetings outside of the US by ways of a boycott:<a href="https://boycott-ietf127.org" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://boycott-ietf127.org</a><a href="https://mastodon.infra.de/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ietf</a> <a href="https://mastodon.infra.de/tags/ietf127" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ietf127</a>

Stéphane BortzmeyerInteresting project at <a href="https://mastodon.gougere.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> : "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."<a href="https://mailman3.ietf.org/mailman3/lists/web-bot-auth.ietf.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mailman3.ietf.org/mailman3/lists/web-bot-auth.ietf.org/</a>

Lars Eggert<a href="https://meshed.cloud/@webmink" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@webmink</a> Sometimes there are other choices than ISO. That ODF file format would have been suitable for an <a href="https://social.secret-wg.org/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> 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.

Jan Schaumann"Time to be crypto* agile, not fragile." - good criticism of the IETF's slow move on post-quantum cryptography adoption. "Stop getting in the way of consensus."<a href="https://datatracker.ietf.org/meeting/122/materials/slides-122-pquip-ietf-is-quantum-fragile-01.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/meeting/122/materials/slides-122-pquip-ietf-is-quantum-fragile-01.pdf</a>* "crypto" means cryptography; always has, always will<a href="https://mstdn.social/tags/pqc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pqc</a> <a href="https://mstdn.social/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ietf</a>

Daniel GultschMy first RFC has been published! This has been a bucket list item of mine for a long time. 🥳 🎉<a href="https://www.rfc-editor.org/rfc/rfc9749.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.rfc-editor.org/rfc/rfc9749.html</a><a href="https://gultsch.social/tags/JMAP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JMAP</a> <a href="https://gultsch.social/tags/WebPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebPush</a> <a href="https://gultsch.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a>

Stéphane Bortzmeyer<a href="https://mastodon.gougere.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> <a href="https://mastodon.gougere.fr/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a>"BGP Color-Aware Routing" We are going to paint the routers and the links?

Paul HoffmanToday is the thrice-annual day where <a href="https://infosec.exchange/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> folks rush around doing writing work they should have done over the past four months because there is a document deadline at UTC 2359. We should have a name for the day.

Karsten SchmidtAnyone knows why the HTML versions of IETF RFCs are insisting on replicating the (unnecessary) page breaks from the plain text version? Also apart from being able to jump to bibliography and to document sections from the TOC, why aren't the HTML versions making proper use of internal hyperlinking? Feels like a grand missed opportunity to make these specs a lot more usable? Especially hard to use when trying to implement vs just using an RFC for a quick consult/check...<a href="https://mastodon.thi.ng/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> <a href="https://mastodon.thi.ng/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> <a href="https://mastodon.thi.ng/tags/HyperText" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HyperText</a>

Stéphane BortzmeyerJe crois qu'on peut en faire une loi : tout protocole Internet peut tourner au-dessus de tous les protocoles de transport que produit l'<a href="https://mastodon.gougere.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a>. Là, on a <a href="https://mastodon.gougere.fr/tags/EPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EPP</a> sur <a href="https://mastodon.gougere.fr/tags/QUIC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#QUIC</a> : <a href="https://datatracker.ietf.org/doc/draft-ietf-regext-epp-quic/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-regext-epp-quic/</a>

Stéphane Bortzmeyer<a href="https://mastodon.gougere.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> Argh, le futur RFC sur l'exportation des clés <a href="https://mastodon.gougere.fr/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLS</a> (SSLKEYLOGFILE), qui avait été approuvé, a été retiré de la file d'attente des RFC. Vu le retard pris, il fallait lui ajouter les derniers trucs (notamment <a href="https://mastodon.gougere.fr/tags/ECH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ECH</a>). Bref, ce n'est pas encore normalisé. (Alors que c'est crucial pour le déboguage, cf. mon talk à Capitole du Libre <a href="https://cfp.capitoledulibre.org/cdl-2022/talk/P79YC7/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://cfp.capitoledulibre.org/cdl-2022/talk/P79YC7/</a> )

sylvain#XMPP XMPP (Extensible Messaging and Presence Protocol) est un protocole ouvert et standardisé pour la messagerie instantanée et la présence en temps réel. Il est largement utilisé pour permettre la communication entre différents systèmes de messagerie et applications. Voici un aperçu détaillé de XMPP :Historique et OriginesXMPP a été initialement développé sous le nom de Jabber en 1999 par Jeremie Miller. Le projet Jabber visait à créer un système de messagerie instantanée […] <a href="https://project4geeks.org/xmpp/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://project4geeks.org/xmpp/</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#ietf