Shakedown Social

Kevin Bowen :xfce:A nifty <a href="https://fosstodon.org/tags/CLI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CLI</a> tool for reading <a href="https://fosstodon.org/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> documents and drafts:<a href="https://github.com/bfontaine/rfc" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/bfontaine/rfc</a>

Kevin Karhan :verified:<a href="https://suya.place/users/bogdan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bogdan</a> anything that mandates <a href="https://infosec.space/tags/2FA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2FA</a> and doesn't provide <a href="https://infosec.space/tags/TOTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TOTP</a> or <a href="https://infosec.space/tags/HOTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HOTP</a> support as per <a href="https://infosec.space/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> but demand something like <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PhoneNumbers</a> that are <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PII</a> should be outlawed.<ul><li>I can accept <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a>-based 2FA as a compromise...</li></ul>

mkjAhh, here it is. Maybe the IETF should publish a list or something including the publication date, so they can be found more easily.RFC 9759, Unified Time Scaling for Temporal Coordination Frameworks<a href="https://datatracker.ietf.org/doc/html/rfc9759" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/doc/html/rfc9759</a><a href="https://social.mkj.earth/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> <a href="https://social.mkj.earth/tags/RFC9759" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC9759</a> <a href="https://social.mkj.earth/tags/TwoWeekPrinciple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TwoWeekPrinciple</a>

RFC EditorRFC 9726: Operational Considerations for Use of DNS in Internet of Things (IoT) Devices, M. Richardson, et al., <a href="https://www.rfc-editor.org/info/rfc9726" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.rfc-editor.org/info/rfc9726</a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> This document details considerations about how Internet of Things (IoT) devices use IP addresses and DNS names. These concerns become acute as network operators begin deploying Manufacturer Usage Descriptions (MUD), as specified in RFC 1/2

Kevin Bowen :xfce:The inspiration for above mentioned re-reading of <a href="https://fosstodon.org/tags/RFC9413" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC9413</a> for fun. 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.<a href="https://alexgaynor.net/2025/mar/25/postels-law-and-the-three-ring-circus/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://alexgaynor.net/2025/mar/25/postels-law-and-the-three-ring-circus/</a><a href="https://fosstodon.org/tags/standards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#standards</a> <a href="https://fosstodon.org/tags/protocols" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protocols</a> <a href="https://fosstodon.org/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> <a href="https://fosstodon.org/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a>

Kevin Bowen :xfce: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">#RFC</a> and re-visit Postel's "law" - "be conservative in what you send, and liberal in what you accept".I appreciate the consideration put into this as well as the pertinent examples.<a href="https://datatracker.ietf.org/doc/html/rfc9413" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/doc/html/rfc9413</a> <a href="https://fosstodon.org/tags/protocols" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protocols</a> <a href="https://fosstodon.org/tags/standards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#standards</a> <a href="https://fosstodon.org/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a>

RFC EditorRFC 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">https://www.rfc-editor.org/info/rfc9743</a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</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

Daniel SupernaultPixelfed Friend Discovery ✨Check your contacts to see if they are on Pixelfed, without compromising their privacy, or sharing their info by using the k-Anonymity algo:- Your address book/contact list stays on your device - We only send anonymized, partially-hashed data - k-Anonymity ensures no individual can be identified - Discovery service operated by the Pixelfed Foundation, and opt-in per userWe would love your feedback! <a href="https://mastodon.social/tags/pixelfed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pixelfed</a> <a href="https://mastodon.social/tags/onboarding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#onboarding</a> <a href="https://mastodon.social/tags/FindYourFriends" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FindYourFriends</a> <a href="https://mastodon.social/tags/PrivacyMatters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrivacyMatters</a> <a href="https://mastodon.social/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rfc</a>

RFC EditorRFC 9748: Updating the NTP Registries, R. Salz, <a href="https://www.rfc-editor.org/info/rfc9748" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.rfc-editor.org/info/rfc9748</a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> The Network Time Protocol (NTP) and Network Time Security (NTS) documents define a number of registries, collectively called the NTP registries.

RFC EditorRFC 9707: Report from the IAB Workshop on Barriers to Internet Access of Services (BIAS), M. Kühlewind, et al., <a href="https://www.rfc-editor.org/info/rfc9707" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.rfc-editor.org/info/rfc9707</a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> The "Barriers to Internet Access of Services (BIAS)" workshop was convened by the Internet Architecture Board (IAB) from January 15-17, 2024 as a three-day online meeting. Based on the submitted position papers, the workshop covered 1/2

Gary "grim" KramlichI just put together a big long post on what if anything <a href="https://fosstodon.org/@pidgin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pidgin</a> 3 should do when it comes to original messages after their authors have edited or deleted them.We're still a long way away from this, but it's good to thing about these things before we actually get to implement.Voting and registration is required via our identity provider which is just meant to fight spam.At any rate, let me know what you think!<a href="https://discourse.imfreedom.org/t/rfc-archiving-of-edited-redacted-and-ephemeral-messages/251" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://discourse.imfreedom.org/t/rfc-archiving-of-edited-redacted-and-ephemeral-messages/251</a><a href="https://mastodon.social/tags/Pidgin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pidgin</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://mastodon.social/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://mastodon.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> <a href="https://mastodon.social/tags/Logging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Logging</a>

Aaron PareckiAt long last, the OAuth working group has finished the Best Current Practice for OAuth 2.0 Security and it was just published as RFC9700! This has been a long time in the works, and I'm very thankful to everyone who has helped out with it over the years! <a href="https://www.rfc-editor.org/rfc/rfc9700.html" rel="nofollow noopener noreferrer" target="_blank">https://www.rfc-editor.org/rfc/rfc9700.html</a> This is one of the major inputs to OAuth 2.1, so I'm also very excited to be able to move that forward this year as well!

RFC EditorRFC 9704: Establishing Local DNS Authority in Validated Split-Horizon Environments, T. Reddy.K, et al., <a href="https://www.rfc-editor.org/info/rfc9704" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.rfc-editor.org/info/rfc9704</a> <a href="https://mastodon.online/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> When split-horizon DNS is deployed by a network, certain domain names can be resolved authoritatively by a network-provided DNS resolver. DNS clients that are not configured to use this resolver by default can use it for these specific domains 1/2

Stéphane BortzmeyerRFC 9718: DNSSEC Trust Anchor Publication for the Root ZoneL'authentification <a href="https://mastodon.gougere.fr/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNSSEC</a> repose sur la même structure arborescente que le <a href="https://mastodon.gougere.fr/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> : une zone publie un lien sécurisé vers les clés de ses sous-zones. Un résolveur validant n'a donc besoin que d'une seule clé publique, celle de la racine. Reste donc à configurer la clé de la racine dans le résolveur. Comment est-ce que l'ICANN publie cette clé cruciale ? C'est documenté dans ce <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> qui remplace le RFC 7958.<a href="https://www.bortzmeyer.org/9718.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bortzmeyer.org/9718.html</a>

Paul HoffmanAnd another new RFC I have co-authored: DNSSEC Trust Anchor Publication for the Root Zone <a href="https://datatracker.ietf.org/doc/rfc9718/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/doc/rfc9718/</a><a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> <a href="https://infosec.exchange/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNSSEC</a> <a href="https://infosec.exchange/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> <a href="https://infosec.exchange/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a>

h o ʍ l e t t→ RFC 9421: HTTP Message Signatures (par <a href="https://mastodon.gougere.fr/@bortzmeyer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bortzmeyer</a>) <a href="https://www.bortzmeyer.org/9421.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bortzmeyer.org/9421.html</a>« Ce RFC spécifie comment on peut signer cryptographiquement et vérifier des messages HTTP, afin de s'assurer de leur authenticité. »<a href="https://mamot.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> <a href="https://mamot.fr/tags/HTTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTTP</a>

Gary "grim" KramlichThey say when you use regex you have two problems. I tend to have one less problem...Case in point, here's a tokenizer for <a href="https://www.rfc-editor.org/rfc/rfc5801.html#section-4" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.rfc-editor.org/rfc/rfc5801.html#section-4</a>.^(?:(?P<nonstd>F),)?(?P<cb>[npy])(?:=(?P<cbname>[^,]+))?,(?:a=(?P<authzid>[^,]+))?,Validation still has to be done in the application, but this is still way easier than writing and maintaining a lexer.<a href="https://mastodon.social/tags/regex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#regex</a> <a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://mastodon.social/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rfc</a>

uvokThis cheetah SHOULD receive regular cuddles, otherwise he MAY get sad. That SHOULD NOT happen, as his performance is degraded otherwise.<a href="https://furry.engineer/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rfc</a>

BoneQuestToday in BoneQuest History for November 15th 2003 "ASS TO BALLS TRANSFER PROTOCOL" <a href="https://bonequest.com/1869" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bonequest.com/1869</a> <a href="https://bonequest.net/tags/bonequest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bonequest</a> :deuce: :pants: <a href="https://bonequest.net/tags/ass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ass</a> <a href="https://bonequest.net/tags/balls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#balls</a> <a href="https://bonequest.net/tags/deuce_pants" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#deuce_pants</a> <a href="https://bonequest.net/tags/fucking_shut_up" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fucking_shut_up</a> <a href="https://bonequest.net/tags/icq" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#icq</a> <a href="https://bonequest.net/tags/protocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protocol</a> <a href="https://bonequest.net/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rfc</a>

BoneQuestToday in BoneQuest History for November 9th 2006 "HI COCKS PROTOCOL" <a href="https://bonequest.com/2931" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bonequest.com/2931</a> <a href="https://bonequest.net/tags/bonequest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bonequest</a> :deuce: :pants: <a href="https://bonequest.net/tags/client_server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#client_server</a> <a href="https://bonequest.net/tags/clip_art" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clip_art</a> <a href="https://bonequest.net/tags/clipart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clipart</a> <a href="https://bonequest.net/tags/deuce_pants" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#deuce_pants</a> <a href="https://bonequest.net/tags/protocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protocol</a> <a href="https://bonequest.net/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rfc</a> <a href="https://bonequest.net/tags/short_bus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#short_bus</a> <a href="https://bonequest.net/tags/title_mismatch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#title_mismatch</a>

Recent searches

Search options

Administered by:

Server stats:

#rfc