c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Server stats:

2.9K
active users

#rfc

4 posts4 participants1 post today
Kevin Bowen :xfce:<p>The inspiration for above mentioned re-reading of <a href="https://fosstodon.org/tags/RFC9413" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC9413</span></a> for fun. </p><p>I've always respected Jon Postel's work and, from what I know, took them as inspiration and "guiding principles" in my work as a network engineer and architect. It's good to see, in my opinion, them getting re-evaluated rather than thrown out with the bathwater. YMMV of course.</p><p><a href="https://alexgaynor.net/2025/mar/25/postels-law-and-the-three-ring-circus/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">alexgaynor.net/2025/mar/25/pos</span><span class="invisible">tels-law-and-the-three-ring-circus/</span></a></p><p><a href="https://fosstodon.org/tags/standards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>standards</span></a> <a href="https://fosstodon.org/tags/protocols" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>protocols</span></a> <a href="https://fosstodon.org/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>networking</span></a> <a href="https://fosstodon.org/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a></p>
Kevin Bowen :xfce:<p>As good a time as any to re-read an <a href="https://fosstodon.org/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> and re-visit Postel's "law" - "be conservative in what you send, and liberal in what you accept".</p><p>I appreciate the consideration put into this as well as the pertinent examples.</p><p><a href="https://datatracker.ietf.org/doc/html/rfc9413" 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">rfc9413</span></a><br><a href="https://fosstodon.org/tags/protocols" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>protocols</span></a> <a href="https://fosstodon.org/tags/standards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>standards</span></a> <a href="https://fosstodon.org/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>networking</span></a></p>
Tim<p><span class="h-card" translate="no"><a href="https://mastodon.social/@RadioAzureus" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>RadioAzureus</span></a></span> <a href="https://mastodon.world/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rfc</span></a> request to comment</p>
Stéphane Bortzmeyer<p>RFC 9724: Randomized and Changing MAC Address State of Affairs</p><p>Dans le contexte de la surveillance massive qui s'exerce contre les utilisateurices de l'Internet, tout identifiant un peu stable peut être utilisé pour pister quelqu'un. On en laisse, des traces ! C'est par exemple le cas avec l'<a href="https://mastodon.gougere.fr/tags/adresseMAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>adresseMAC</span></a>. Ce nouveau <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> décrit les mécanismes existants pour diminuer le risque de pistage par l'adresse MAC. Il ne spécifie pas un protocole, il liste les solutions.</p><p><a href="https://www.bortzmeyer.org/9724.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9724.html</span><span class="invisible"></span></a></p>
Edorian<p>My first <a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PHP</span></a> <a href="https://phpc.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> with a lot richer discussion passed today :)</p><p><a href="https://wiki.php.net/rfc/marking_return_value_as_important" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wiki.php.net/rfc/marking_retur</span><span class="invisible">n_value_as_important</span></a></p><p>48 Mails all in all: <a href="https://externals.io/message/126232" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">externals.io/message/126232</span><span class="invisible"></span></a> with some additional feedback on social media.</p><p>Thanks to everyone :) </p><p>What to do next now 🤔</p>
Stéphane Bortzmeyer<p>RFC 9694: Guidelines for the Definition of New Top-Level Media Types</p><p>Vous savez que les types de médias comportent un type de premier niveau et un sous-type. Dans image/gif, image est le type de premier niveau et gif le sous-type. La création du type haptics (données haptiques), qui a été faite dans le <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> 9695, a été l'occasion de formaliser un peu plus le processus de création de types de médias.</p><p><a href="https://www.bortzmeyer.org/9694.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9694.html</span><span class="invisible"></span></a></p>
Stéphane Bortzmeyer<p>RFC 9695: The 'haptics' Top-level Media Type</p><p>L'enregistrement d'un nouveau type de média de premier niveau est plutôt rare (le dernier avait été font/ en 2017). Notre <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> introduit le type haptics/, pour les formats de fichier des interfaces haptiques, celles qu'on touche et qui vous touchent (une manette de jeu vidéo à retour d'effort, par exemple). </p><p><a href="https://www.bortzmeyer.org/9695.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9695.html</span><span class="invisible"></span></a></p><p><a href="https://mastodon.gougere.fr/tags/haptique" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>haptique</span></a> <a href="https://mastodon.gougere.fr/tags/haptics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>haptics</span></a></p>
RFC Editor<p>RFC 9775: IRTF Code of Conduct, C. S. Perkins, <a href="https://www.rfc-editor.org/info/rfc9775" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9775</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> This document describes the code of conduct for participants in the Internet Research Task Force (IRTF). The IRTF believes that research is most effective when done in an open and inclusive forum that encourages diversity of ideas and participation. Through this code of conduct, the IRTF continues to 1/2</p>
RFC Editor<p>RFC 9695: The 'haptics' Top-Level Media Type, Y. K. Muthusamy, et al., <a href="https://www.rfc-editor.org/info/rfc9695" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9695</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> This memo registers and documents the 'haptics' top-level media type, under which subtypes for representation formats for haptics may be registered. This document also serves as a registration for a set of subtypes, which are representative of some existing subtypes already in 1/2</p>
RFC Editor<p>RFC 9694: Guidelines for the Definition of New Top-Level Media Types, M.J. Dürst, <a href="https://www.rfc-editor.org/info/rfc9694" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9694</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> This document defines best practices for defining new top-level media types. It also introduces a registry for top-level media types, and contains a short history of top-level media types. It updates RFC 6838. This document is a product of the Media Type Maintenance 1/2</p>
Stéphane Bortzmeyer<p>RFC 9745: The Deprecation HTTP Header Field</p><p>Ce nouveau champ de l'en-tête <a href="https://mastodon.gougere.fr/tags/HTTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTP</span></a> sert à indiquer que la ressource demandée va être (ou a été) abandonnée et qu'il faut penser à migrer. Il sert surtout pour les <a href="https://mastodon.gougere.fr/tags/API" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>API</span></a> HTTP. </p><p><a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> </p><p><a href="https://www.bortzmeyer.org/9745.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9745.html</span><span class="invisible"></span></a></p>
RFC Editor<p>RFC 9724: State of Affairs for Randomized and Changing Media Access Control (MAC) Addresses, JC. Zúñiga, et al., <a href="https://www.rfc-editor.org/info/rfc9724" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9724</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> Internet users are becoming more aware that their activity over the Internet leaves a vast digital footprint, that communications might not always be properly secured, and that their location and actions can be tracked. One of the main 1/3</p>
Stéphane Bortzmeyer<p>RFC 9743: Specifying New Congestion Control Algorithms</p><p>La lutte contre la <a href="https://mastodon.gougere.fr/tags/congestion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>congestion</span></a> du réseau est une tâche permanente dans l'Internet. Si les émetteurs de données envoyaient des octets aussi vite qu'ils le pouvaient, l'Internet s'écroulerait vite. Les protocoles contiennent donc des algorithmes de contrôle de la congestion. Il y en a plusieurs et ce <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> explique comment de nouveaux algorithmes doivent être évalués avant d'être déployés en vrai. </p><p><a href="https://www.bortzmeyer.org/9743.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9743.html</span><span class="invisible"></span></a></p>
RFC Editor<p>RFC 9743: Specifying New Congestion Control Algorithms, M. Duke, Ed., et al., <a href="https://www.rfc-editor.org/info/rfc9743" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9743</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> RFC 5033 discusses the principles and guidelines for standardizing new congestion control algorithms. This document obsoletes RFC 5033 to reflect changes in the congestion control landscape by providing a framework for the development and assessment of congestion control 1/2</p>
Daniel Supernault<p>Pixelfed Friend Discovery ✨</p><p>Check your contacts to see if they are on Pixelfed, without compromising their privacy, or sharing their info by using the k-Anonymity algo:</p><p>- Your address book/contact list stays on your device<br>- We only send anonymized, partially-hashed data<br>- k-Anonymity ensures no individual can be identified<br>- Discovery service operated by the Pixelfed Foundation, and opt-in per user</p><p>We would love your feedback! </p><p><a href="https://mastodon.social/tags/pixelfed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pixelfed</span></a> <a href="https://mastodon.social/tags/onboarding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>onboarding</span></a> <a href="https://mastodon.social/tags/FindYourFriends" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FindYourFriends</span></a> <a href="https://mastodon.social/tags/PrivacyMatters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PrivacyMatters</span></a> <a href="https://mastodon.social/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rfc</span></a></p>
DFN-CERT<p>PSA: die Weiterverwendung der obsoleten DNS-Blockliste "NixSpam" / ix.dnsbl.manitu.net führt zu Fehlern bei der Zustellung von E-Mails. Administratoren der E-Mail-Server müssen hier selbst aktiv werden.</p><p>Hinweise dazu:<br><a href="https://nixspam.net/help/enduser/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">nixspam.net/help/enduser/</span><span class="invisible"></span></a></p><p><a href="https://infosec.exchange/tags/nixspam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nixspam</span></a> <a href="https://infosec.exchange/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a></p>
Stéphane Bortzmeyer<p>RFC 9741: CDDL Additional Control Operators for the Conversion and Processing of Text</p><p>Le langage <a href="https://mastodon.gougere.fr/tags/CDDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CDDL</span></a>, qui permet de créer un schéma formel pour des formats comme <a href="https://mastodon.gougere.fr/tags/CBOR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CBOR</span></a>, peut s'étendre via l'ajout d'« opérateurs de contrôle ». Ce <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> en spécifie quelques uns, notamment pour agir sur du texte ou convertir d'une forme dans un autre.</p><p><a href="https://www.bortzmeyer.org/9741.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9741.html</span><span class="invisible"></span></a></p>
RFC Editor<p>RFC 9741: Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text, C. Bormann, <a href="https://www.rfc-editor.org/info/rfc9741" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9741</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> The Concise Data Definition Language (CDDL), standardized in RFC 8610, provides "control operators" as its main language extension point. RFCs have added to this extension point in both an application-specific and a 1/2</p>
RFC Editor<p>RFC 9678: Forward Secrecy Extension to the Improved Extensible Authentication Protocol Method for Authentication and Key Agreement (EAP-AKA' FS), J. Arkko, et al., <a href="https://www.rfc-editor.org/info/rfc9678" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9678</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> This document updates RFC 9048, "Improved Extensible Authentication Protocol Method for 3GPP Mobile Network Authentication and Key Agreement (EAP-AKA')", and its predecessor RFC 5448 1/3</p>
RFC Editor<p>RFC 9740: New IPFIX Information Elements for TCP Options and IPv6 Extension Headers, M. Boucadair, et al., <a href="https://www.rfc-editor.org/info/rfc9740" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9740</span><span class="invisible"></span></a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> This document specifies new IP Flow Information Export (IPFIX) Information Elements (IEs) to solve issues with existing ipv6ExtensionHeaders and tcpOptions IPFIX IEs, especially the ability to export any observed IPv6 extension headers or TCP 1/2</p>