home.social

#ietf — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ietf, aggregated by home.social.

fetched live
  1. @argv_minus_one @stefan327 @leanderlindahl @patrick_schreiner

    Und: #Jabber/#XMPP ist ein #OpenStandard der #IETF und der #XSF. Matrix ist zumindest soweit dokumentiert, daß unabhängige Implementierungen möglich sind. Delta basiert auf Standards, eine unabhängige Implementierung gilt aber als extrem schwierig. Matrix und Delta werden relativ stark von jeweils einer Firma dominiert, während Jabber/XMPP ein diverses Ökossystem darstellt. Mit allen Vor- und Nachteilen 😉

  2. RE: mastodon.archive.org/@internet

    "...[W]hen should individuals and organizations be able to use automated tools or “bots” to collect data from or interact with openly published websites — whether we call it “scraping”, “crawling,” or simply automated data collection? Conversely, what kind of control should websites have over when that happens, or what use the collected data is put to?"

    #AI #internetArchive #IETF #webscraping #freedom #copyright #archiving

  3. 🚨 Breaking News! 🚨 The #NSA and #IETF continue their epic saga of cryptographic ping-pong. 🏓 If you thought the last eight parts were thrilling, part 9 is here to remind you that you can, in fact, fall asleep with your eyes open. 😴🔍
    blog.cr.yp.to/20260814-update. #BreakingNews #Cryptography #TechSaga #Cybersecurity #HackerNews #ngated

  4. Один DNS‑запрос породил 329 запросов. Я полез разбираться, куда они все ушли

    Один DNS‑запрос. Пустой кеш. И 329 исходящих запросов вслед за ним. Сначала я решил, что где‑то неправильно понял цифры. Потом полез разбираться и выяснил, что recursive resolver внутри делает намного больше работы, чем видно по обычному dig . Разбираю, откуда берутся эти сотни запросов, при чём здесь CNAME, glue, DNSSEC, IPv6 PTR и почему разные версии BIND на одном и том же запросе могут отличаться почти в три раза.

    habr.com/ru/articles/1070280/

    #DNS #BIND #recursive_resolver #DNSSEC #IPv6 #PTR #cold_cache #CNAME #Wireshark #IETF

  5. I've been working on updating a decision making process in a #coop from #voting to #consensus inspired by #ietf #decisionMaking process when a colleague made me realize that consensus process is not compatible with many #neurodivergent cognitive styles. It disproportionately favors #Neurotypicals and extraverted ppl while putting more introverted and less verbal type people at a disadvantage. Also it's yet another "social capital" dominated decision making process. Less social capital - less likely you'll actually speak up against the crowd.

    The "no one left behind" goal is not fulfilled by the "no loud opposition" decision process. What process does that? We're staying with the simplistic voting for now but adding a prolonged debate. Any ideas? How other #cooperatives do that? Especially #anarchist ones?

    #autism #adhd #audhd #dyslexia #socialAnxiety #ptsd #spectrum #anarchism #anarchistOrder #socialism #cooperative

  6. Do you remember the times when #IETF was fun instead of being a place for personal drama and ad hominem?

  7. heise+ | Streit um Post-Quantum-Schlüsselverfahren: Mit oder ohne Sicherheitsgurt?

    Google-Kryptografin Sophie Schmieg erklärt im Interview die IETF-Debatte um reines ML-KEM und warum sie meint, dass das Verfahren spezifiziert werden sollte.

    heise.de/hintergrund/Streit-um

    #IETF #IT #NSA #Quantencomputer #Sicherheitslücken #Verschlüsselung #news

  8. 📄 I have published my summary of the Internet Research Task Force (IRTF) activities at #IETF126 in Vienna.

    The report covers the Applied Networking Research Workshop (ANRW), the IRTF Open Meeting, and all 14 Research Groups—from AI networking and Internet architecture to routing, transport, privacy, sustainability, quantum networking, and more.

    One aspect that makes the IRTF particularly valuable is its research model. Rather than organizing around individual publications, the IRTF is organized around long-lived research communities where researchers, engineers, implementers, operators, and standards experts collaboratively explore fundamental Internet challenges over many years.

    At a time when AI is transforming how research is written, reviewed, and disseminated, sustained technical dialogue and open collaboration are becoming increasingly important.

    🔗 dirk-kutscher.info/irtf/ietf-1

    #IRTF #IETF #Networking #Internet #Research #OpenStandards

  9. At the latest in Vienna, we decided to run a peculiar experiment... stream the sessions using itself! All using our existing infrastructure as the source for the media. If you want to learn more, this blog post is a detailed overview on how we made that happen. Feedback (and boosts) welcome!

    meetecho.com/blog/moq-ietf126/

  10. Following some discussions during #IETF last week (in the hallway and on various mailing lists), the awesome #IPvFoo extension now shows in Mozilla #FireFox if connections used H1, H2, or H3, not just IPv4-vs-IPv6! This is helpful for seeing how that angle of Happy Eyeballs works.

    (It would work in the Chrome version as well but the interface for getting at this info is broken and always returns H1.)

    Note that if the connection starts with H2 but then switches to H3 for later objects on the hostname (eg, if you have an Alt-Svc record) then it will show H3 rather than H2.

    addons.mozilla.org/en-US/firef

    #QUIC #HTTP2 #HTTP3 #IPv6 #HappyEyeballs

  11. RE: social.heise.de/@heiseonlineen

    Best quote from this #IETF on #EUpol: "Two people poison the well, and we effectively restrict access to water generally for certain groups."

  12. Last day of this #IETF starts and promises to be relaxed: All my currently busy drafts (on #CBOR and #LAKE formerly called #EDHOC) were discussed, #CBOR met and makes progress – now it's about hallway meetings, and finding out about things I missed :-)