Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Administered by:

Server stats:

2.8K
active users

mathstodon.xyz: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#ietf

4 posts3 participants0 posts today
Jeffrey Haas<p>The IETF community survey gives a nice sense about how the organization is running, and how participation has been going.</p><p><a href="https://www.ietf.org/media/documents/IETF_Community_Survey_2024_-_DRAFT.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">ietf.org/media/documents/IETF_</span><span class="invisible">Community_Survey_2024_-_DRAFT.pdf</span></a></p><p><a href="https://a2mi.social/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a></p>
Smith<p>PHP implementation of IPcrypt, which provides methods for encrypting and decrypting IP addresses. The implementation follows the&nbsp;IPcrypt specification&nbsp;and provides three different encryption modes.</p><p><a href="https://piaille.fr/tags/notes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>notes</span></a> <a href="https://piaille.fr/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a> <a href="https://piaille.fr/tags/php" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>php</span></a> <a href="https://piaille.fr/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacy</span></a> <a href="https://piaille.fr/tags/vieprivee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vieprivee</span></a> </p><p><a href="https://github.com/jedisct1/php-ipcrypt" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/jedisct1/php-ipcryp</span><span class="invisible">t</span></a></p>
Stéphane Bortzmeyer<p>On an <a href="https://mastodon.gougere.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> mailing list, about an excellent property of data security (as opposed to channel security): "you can pick up your <a href="https://mastodon.gougere.fr/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNSSEC</span></a> answer from the street and still validate it".</p>
Stéphane Bortzmeyer<p>Normaliser les interactions techniques entre IA ? Quand deux robots se parlent, l'<a href="https://mastodon.gougere.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> définira peut-être comment ils peuvent le faire <a href="https://mailman3.ietf.org/mailman3/lists/agent2agent.ietf.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mailman3.ietf.org/mailman3/lis</span><span class="invisible">ts/agent2agent.ietf.org/</span></a></p>
Hippo 🍉<p>The EU is mandating messaging apps be compatible with each other, but the current plan is looking less like <a href="https://fosstodon.org/tags/federation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>federation</span></a> 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"</p><p>At the risk of preaching to the converted, here's <span class="h-card" translate="no"><a href="https://toot.igniterealtime.org/@guusdk" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>guusdk</span></a></span> advocating for *real* interoperability between messaging apps, using an existing, battle-tested, <a href="https://fosstodon.org/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a>-backed standard: <a href="https://fosstodon.org/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XMPP</span></a>! :xmpp:</p><p><a href="https://discourse.igniterealtime.org/t/it-s-time-for-real-interoperability-let-s-make-it-happen/95342" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">discourse.igniterealtime.org/t</span><span class="invisible">/it-s-time-for-real-interoperability-let-s-make-it-happen/95342</span></a></p>
Max Resing<p>Just wanted to share some thoughts on <a href="https://infosec.exchange/tags/RFC9715" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC9715</span></a> - an <a href="https://infosec.exchange/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> that defines standards on reducing the <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> issue of IP fragmentation over <a href="https://infosec.exchange/tags/UDP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UDP</span></a>. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the <a href="https://infosec.exchange/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Internet</span></a>. A great leap forward to (hopefully) reduce the reflection/amplification <a href="https://infosec.exchange/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DDoS</span></a> potential of DNS.</p><p>Just today I learned that <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Google</span></a> will share 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 <a href="https://infosec.exchange/tags/TCP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TCP</span></a>. </p><p><a href="https://infosec.exchange/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> <a href="https://infosec.exchange/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <a href="https://infosec.exchange/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a></p>
Fabrizio T.<p>The Internet isn't value-neutral, and neither is the <a href="https://mastodon.cisti.org/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a>. 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.<br>-- RFC 3935, Oct 2004</p>
Markus Schatten<p>The <a href="https://mastodon.social/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a> has formed a work group to develop a standard for <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> scraping preferences.</p><p><a href="https://www.theregister.com/2025/04/09/ietf_ai_preferences_working_group/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theregister.com/2025/04/09/iet</span><span class="invisible">f_ai_preferences_working_group/</span></a></p>
Xamanismo Coletivo<p><a href="https://hachyderm.io/tags/DigitalSovereignity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DigitalSovereignity</span></a> needs <a href="https://hachyderm.io/tags/StructuralPower" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>StructuralPower</span></a></p><p>"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">#<span>IETF</span></a> or the <a href="https://hachyderm.io/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a>?<br>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">#<span>digitalsphere</span></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">#<span>standards</span></a>. What matters is who has the <a href="https://hachyderm.io/tags/structuralpower" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>structuralpower</span></a> to deploy the standards they want to see and avoid those they dislike."<br><span class="h-card" translate="no"><a href="https://mastodon.social/@robin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>robin</span></a></span> </p><p><a href="https://berjon.com/digital-sovereignty/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">berjon.com/digital-sovereignty</span><span class="invisible">/</span></a></p>
T_X<p><span class="h-card" translate="no"><a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ffhl</span></a></span> <span class="h-card" translate="no"><a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>videolan</span></a></span> (wobei "proprietär" vll. doch etwas zu stark ist, gibt da zumindest <a href="https://chaos.social/tags/RFC2250" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC2250</span></a>, dass das <a href="https://chaos.social/tags/MPEG2TS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MPEG2TS</span></a> für <a href="https://chaos.social/tags/RTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RTP</span></a> spezifiziert. Und für die <a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> muss es ja eigentlich patentfrei sein? Aber ich bin an sich kein Freund von der <a href="https://chaos.social/tags/MPEG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MPEG</span></a>, die sonst für ihr Patentmafia-Wesen berüchtigt sind.)</p>
T_X<p><span class="h-card" translate="no"><a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ffhl</span></a></span> <span class="h-card" translate="no"><a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>videolan</span></a></span> die technische Hintergrund der neuen Streams:<br>Statt <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> / UDP / <a href="https://chaos.social/tags/RTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RTP</span></a> / <a href="https://chaos.social/tags/Opus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Opus</span></a>. Ist es jetzt: IPv6 / UDP / <a href="https://chaos.social/tags/MPEG2TS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MPEG2TS</span></a> / RTP / Opus.<br>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">#<span>IETF</span></a> <a href="https://chaos.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> standardisierte, native RTP-Opus, das kann erst der nightly/v4.<br>Sobald VLC endlich mal releasen sollte, schmeiß ich das MPEG-TS auch ganz schnell wieder weg.</p><p><a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>multicast</span></a></p>
securityskeptic :donor: :verified:<p>MailChannels Acquires SMTP Protocol from IETF for $50 Million</p><p><a href="https://www.linkedin.com/pulse/mailchannels-acquires-smtp-protocol-from-ietf-50-million-hbasc/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linkedin.com/pulse/mailchannel</span><span class="invisible">s-acquires-smtp-protocol-from-ietf-50-million-hbasc/</span></a></p><p><a href="https://infosec.exchange/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a> <a href="https://infosec.exchange/tags/smtp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>smtp</span></a> <a href="https://infosec.exchange/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a></p>
Tim Hergert<p>Was really looking forward to an April 1 IETF RFC this year - but it appears i will be disappointed this year. </p><p>Instead - I guess I'll have to share some of my favorites from years past </p><p>RFC 3514 "The Security Flag in the IPv4 Header"<br><a href="https://datatracker.ietf.org/doc/html/rfc3514" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/html/</span><span class="invisible">rfc3514</span></a></p><p>RFC 1149 "A Standard for the Transmission of IP Datagrams on Avian Carriers"</p><p><a href="https://datatracker.ietf.org/doc/html/rfc1149" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/html/</span><span class="invisible">rfc1149</span></a></p><p><a href="https://infosec.exchange/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> <a href="https://infosec.exchange/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> <a href="https://infosec.exchange/tags/AprilFools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AprilFools</span></a></p>
Brett Sheffield (he/him)<p><a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></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">#<span>Multicast</span></a> Listener Discovery ( <a href="https://chaos.social/tags/MLD2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MLD2</span></a> ).</p><p>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).</p><p>I've patched <a href="https://chaos.social/tags/libmld" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>libmld</span></a> and <a href="https://chaos.social/tags/librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>librecast</span></a> with the new timer value and the change will be included in the next release.</p><p><a href="https://datatracker.ietf.org/doc/html/rfc9777" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/html/</span><span class="invisible">rfc9777</span></a></p>
Evangelos🏴<p>A simple <a href="https://libretooth.gr/tags/nodejs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nodejs</span></a> server &amp; <a href="https://libretooth.gr/tags/htmx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>htmx</span></a> client to demo the new <a href="https://libretooth.gr/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a>'s draft on the <a href="https://libretooth.gr/tags/idempotency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>idempotency</span></a> key <a href="https://libretooth.gr/tags/header" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>header</span></a>:<br><a href="https://codeberg.org/evasync/the-idempotency-key" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/evasync/the-idemp</span><span class="invisible">otency-key</span></a></p><p>(draft spec can be found here: <a href="https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/draft</span><span class="invisible">-ietf-httpapi-idempotency-key-header/</span></a>)</p>
Emelia<p>Spent the past hour doing some updates to the Client ID Metadata Documents internet draft. Trying to find alignment with the Client ID Prefix internet draft and fix a few open issues. <a class="hashtag" href="https://bsky.app/search?q=%23ietf" rel="nofollow noopener noreferrer" target="_blank">#ietf</a> <a class="hashtag" href="https://bsky.app/search?q=%23oauth" rel="nofollow noopener noreferrer" target="_blank">#oauth</a></p>
Fly it.<p>Somebody here with some experience in <a href="https://chaos.social/tags/RFC5545" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC5545</span></a>? I would love to use the <a href="https://chaos.social/tags/EXRULE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EXRULE</span></a> feature for recurring exceptions, but it was deprecated. How can I replace it without determining specific actual dates?</p><p><a href="https://chaos.social/tags/iCalendar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iCalendar</span></a> <a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> <a href="https://chaos.social/tags/iCal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iCal</span></a> :BoostOK:</p>
lit<p>Let the <a href="https://mastodon.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></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">#<span>USA</span></a> <a href="https://boycott-ietf127.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">boycott-ietf127.org/</span><span class="invisible"></span></a></p>
jbz<p>🚫 Boycott IETF 127 </p><p>｢ 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 ｣</p><p><a href="https://boycott-ietf127.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">boycott-ietf127.org/</span><span class="invisible"></span></a></p><p><a href="https://indieweb.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> <a href="https://indieweb.social/tags/humanrights" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>humanrights</span></a> <a href="https://indieweb.social/tags/uspol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>uspol</span></a> <a href="https://indieweb.social/tags/BoycottIETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoycottIETF</span></a> <a href="https://indieweb.social/tags/BoycottIETF127" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoycottIETF127</span></a></p>
Shane Kerr<p>I signed up for the boycott. If you attend the IETF you should to:</p><p><a href="https://boycott-ietf127.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">boycott-ietf127.org/</span><span class="invisible"></span></a></p><p><a href="https://fosstodon.org/tags/ietf127" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf127</span></a> <a href="https://fosstodon.org/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a></p>
SearchLive feeds
About