RFC Editor<p>RFC 9722: Fast Recovery for EVPN Designated Forwarder Election, P. Brissette, et al., <a href="https://www.rfc-editor.org/info/rfc9722" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9722</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 Ethernet Virtual Private Network (EVPN) solution in RFC 7432 provides Designated Forwarder (DF) election procedures for multihomed Ethernet Segments. These procedures have been enhanced further by applying the Highest Random Weight (HRW) algorithm for DF 1/3</p>
Recent searches
No recent searches
Search options
Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.
Administered by:
Server stats:
218active users
eupolicy.social: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.6
#rfc
3 posts · 1 participant · 0 posts today
RFC Editor<p>RFC 9780: Bidirectional Forwarding Detection (BFD) for Multipoint Networks over Point-to-Multipoint MPLS Label Switched Paths (LSPs), G. Mirsky, et al., <a href="https://www.rfc-editor.org/info/rfc9780" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9780</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 procedures for using Bidirectional Forwarding Detection (BFD) for multipoint networks to detect data plane failures in point-to-multipoint MPLS Label Switched Paths (LSPs) 1/3</p>
RFC Editor<p>RFC 9772: Active Operations, Administration, and Maintenance (OAM) for Use in Generic Network Virtualization Encapsulation (Geneve), G. Mirsky, et al., <a href="https://www.rfc-editor.org/info/rfc9772" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9772</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> Geneve (Generic Network Virtualization Encapsulation) is a flexible and extensible network virtualization overlay protocol designed to encapsulate network packets for transport across underlying 1/3</p>
RFC Editor<p>RFC 9723: BGP Colored Prefix Routing (CPR) for Services Based on Segment Routing over IPv6 (SRv6), H. Wang, et al., <a href="https://www.rfc-editor.org/info/rfc9723" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9723</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 a mechanism to advertise IPv6 prefixes in BGP that are associated with Color Extended Communities to establish end-to-end intent-aware paths for Segment Routing over IPv6 (SRv6) services. Such IPv6 prefixes are 1/4</p>
RFC Editor<p>RFC 9782: Entity Attestation Token (EAT) Media Types, L. Lundblade, et al., <a href="https://www.rfc-editor.org/info/rfc9782" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9782</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 payloads used in Remote ATtestation procedureS (RATS) may require an associated media type for their conveyance, for example, when the payloads are used in RESTful APIs. This memo defines media types to be used for Entity Attestation Tokens (EATs). This document is a 1/2</p>
RFC Editor<p>RFC 9781: A Concise Binary Object Representation (CBOR) Tag for Unprotected CBOR Web Token Claims Sets (UCCS), H. Birkholz, et al., <a href="https://www.rfc-editor.org/info/rfc9781" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9781</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 the Unprotected CWT Claims Set (UCCS), a data format for representing a CBOR Web Token (CWT) Claims Set without protecting it by a signature, Message Authentication Code (MAC), or encryption. UCCS 1/3</p>
RFC Editor<p>RFC 9769: NTP Interleaved Modes, M. Lichvar, et al., <a href="https://www.rfc-editor.org/info/rfc9769" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9769</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 interleaved modes for the Network Time Protocol (NTP). These new modes improve the accuracy of time synchronization by enabling the use of more accurate transmit timestamps that are available only after the transmission of NTP messages. These enhancements are intended to 1/2</p>
RFC Editor<p>RFC 9760: Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages, D. Arnold, et al., <a href="https://www.rfc-editor.org/info/rfc9760" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9760</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 a Precision Time Protocol (PTP) Profile (IEEE Standard 1588-2019) for use in an IPv4 or IPv6 enterprise information system environment. The PTP Profile uses the End-to-End delay measurement mechanism, 1/2</p>
RFC Editor<p>RFC 9758: Updates to the 'ipn' URI Scheme, R. Taylor, et al., <a href="https://www.rfc-editor.org/info/rfc9758" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9758</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 the specification of the 'ipn' URI scheme previously defined in RFC 6260 and the IANA registries established in RFC 7116. It also updates the rules for the encoding and decoding of these URIs when used as an Endpoint Identifier (EID) in the Bundle Protocol version 7 1/2</p>
Stéphane Bortzmeyer<p><a href="https://mastodon.gougere.fr/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BGP</span></a> Vous connaissez le préfixe IP 67.204.16.0/22 ? C'est un des rares dans la table de routage mondiale qui a comme origine non pas un AS mais un ensemble d'AS (un AS_SET). Ce nouveau <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> dit qu'il ne faut plus faire ça.</p><p><a href="https://www.bortzmeyer.org/9774.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9774.html</span><span class="invisible"></span></a></p>
RFC Editor<p>RFC 9774: Deprecation of AS_SET and AS_CONFED_SET in BGP, W. Kumari, et al., <a href="https://www.rfc-editor.org/info/rfc9774" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9774</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> BCP 172 (i.e., RFC 6472) recommends not using AS_SET and AS_CONFED_SET AS_PATH segment types in the Border Gateway Protocol (BGP). This document advances that recommendation to a standards requirement in BGP; it prohibits the use of the AS_SET and AS_CONFED_SET path 1/3</p>
Stéphane Bortzmeyer<p><a href="https://mastodon.gougere.fr/tags/juridique" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>juridique</span></a> <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> </p><p>RFC 9676: A Uniform Resource Name (<a href="https://mastodon.gougere.fr/tags/URN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>URN</span></a>) Namespace for Sources of Law (<a href="https://mastodon.gougere.fr/tags/LEX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LEX</span></a>)</p><p>Les textes de loi ne sont pas évidents à trouver et donc à citer. Ce RFC crée un espace URN, lex, pour pouvoir identifier les textes juridiques. </p><p>urn:lex:fr:etat:loi:2011-03-22;2011-302 </p><p><a href="https://www.bortzmeyer.org/9676.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9676.html</span><span class="invisible"></span></a></p>
RFC Editor<p>RFC 9676: LEX: A Uniform Resource Name (URN) Namespace for Sources of Law, P. Spinosa, et al., <a href="https://www.rfc-editor.org/info/rfc9676" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9676</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 LEX, a Uniform Resource Name (URN) namespace identifier that identifies, names, assigns, and manages persistent resources in the legal domain. This specification allows adoption of a common convention by multiple jurisdictions to 1/2</p>
Hugo van Kemenade<p>FEPs, SLEPs, APEs, AIPs, PEEPs, CEPs, SKIPs, SPECs, TIPs, CFEPs, NEPs, JEPs, BIPs, DEPs, DEPs, KEPs, JEPs, WEPs, IPEPs...</p><p>A lot of projects name proposals after PEPs rather than RFCs.</p><p>What are they? Where did PEPs come from? Here's <span class="h-card" translate="no"><a href="https://fosstodon.org/@flufl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>flufl</span></a></span> on the origin!</p><p><a href="https://hugovk.dev/blog/2025/peps-and-co/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hugovk.dev/blog/2025/peps-and-</span><span class="invisible">co/</span></a><br><a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a> <a href="https://mastodon.social/tags/PEP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PEP</span></a> <a href="https://mastodon.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> <a href="https://mastodon.social/tags/etymology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>etymology</span></a> <a href="https://mastodon.social/tags/history" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>history</span></a> <a href="https://mastodon.social/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>blog</span></a></p>
Guillaume-Jean Herbiet<p>Question <a href="https://mamot.fr/tags/francophonie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>francophonie</span></a> du jour pour ceux qui suivent (de près ou de loin) les travaux de l’<a href="https://mamot.fr/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a>. Quand il s’agit de se référer à un document de type <a href="https://mamot.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a>, vous dites :</p><p>Cc. <span class="h-card" translate="no"><a href="https://mastodon.online/@ietf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ietf</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.gougere.fr/@bortzmeyer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bortzmeyer</span></a></span></p>
Friedrich Delgado<p>"This ABNF could have been a regular expression." </p><p><a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://mastodon.social/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rfc</span></a></p>
🏳️🌈🤘 Blain SmithWrote up an <a href="https://snac.rblgk.sh?t=rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> to get feedback on adding <a href="https://snac.rblgk.sh?t=activitypub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> support to <a href="https://apply.coop" rel="nofollow noopener noreferrer" target="_blank">https://apply.coop</a> soon after we launch. If anyone else has feedback it is certainly welcome! It does require a Codeberg account to comment, but we're open to email feedback as well.<br><br>I am not an ActivityPub expert so a lot of this was learning while planning this out.<br><br><a href="https://codeberg.org/limeleaf/apply.coop/issues/213" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/limeleaf/apply.coop/issues/213</a><br><br><a href="https://snac.rblgk.sh?t=coop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coop</a> <a href="https://snac.rblgk.sh?t=jobboard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JobBoard</a> <a href="https://snac.rblgk.sh?t=buildinpublic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BuildInPublic</a><br>
Stéphane Bortzmeyer<p>RFC 9771: Properties of AEAD Algorithms</p><p>Aujourd'hui, sur l'Internet, on n'utilise plus que des algorithmes de <a href="https://mastodon.gougere.fr/tags/chiffrement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>chiffrement</span></a> <a href="https://mastodon.gougere.fr/tags/AEAD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AEAD</span></a>. Ils assurent confidentialité et intégrité des données. Mais on peut être gourmand et vouloir en plus d'autres propriétés. Ce nouveau <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> classe ces propriétés et définit la terminologie. <br> <br><a href="https://www.bortzmeyer.org/9771.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9771.html</span><span class="invisible"></span></a></p>
stf<p>whoohooo, "RFC 9771 on Properties of Authenticated Encryption with Associated Data (AEAD) Algorithms" </p><p>is a thing now: <a href="https://www.rfc-editor.org/info/rfc9771" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">rfc-editor.org/info/rfc9771</span><span class="invisible"></span></a></p><p>congrats to the authors.</p><p><a href="https://chaos.social/tags/crypto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>crypto</span></a> <a href="https://chaos.social/tags/rfc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rfc</span></a> <a href="https://chaos.social/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>encryption</span></a></p>
Stéphane Bortzmeyer<p>RFC 9292: Binary Representation of HTTP Messages</p><p>Un message <a href="https://mastodon.gougere.fr/tags/HTTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTP</span></a> est traditionnellement représenté comme du texte mais ce <a href="https://mastodon.gougere.fr/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> spécifie une alternative, une représentation binaire d'un message. </p><p><a href="https://www.bortzmeyer.org/9292.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">bortzmeyer.org/9292.html</span><span class="invisible"></span></a></p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload