#RfC

2026-01-30

RFC 9915: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), T. Mrugalski, et al., rfc-editor.org/info/rfc9915 #RFC This document specifies the Dynamic Host Configuration Protocol for IPv6 (DHCPv6), an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly or in combination with 1/3

2026-01-30

RFC 9896: SVG in RFCs, A. Rossi, et al., rfc-editor.org/info/rfc9896 #RFC This document defines policy for the inclusion of Scalable Vector Graphics (SVG) in the definitive versions of RFCs and relevant publication formats. It contains policy requirements from RFC 7996 but removes all requirements related to using a specific SVG profile or implementation code. It also makes the 1/2

2026-01-30

RFC 9880: Semantic Definition Format (SDF) for Data and Interactions of Things, M. Koster, Ed., et al., rfc-editor.org/info/rfc9880 #RFC The Semantic Definition Format (SDF) is a format for domain experts to use in the creation and maintenance of data and interaction models that describe Things, i.e., physical objects that are available for interaction over a network. An SDF 1/3

Gregor Wolf-15kWp☀️/13kWh🏡🔋gregorw@chaos.social
2026-01-30

Please support my new #SAP Influencing request to add support for #Websocket #RFC to @sap/cds-rfc and @sap-rfc/node-rfc-library: influence.sap.com/sap/ino/#/id (SAP S-User required) #SAPCAP #SAPBTP #SAPCloudERP #S4HANA #ABAP

Hype for the Future 90B: The novaTop Plan for YouTube

Overview

Through the beginning of February, novaTopFlex shall schedule references to HTTP Status Codes and the RFC (Request for Comments) system as appropriate for the context. The videos shall be uploaded at a relatively standard pacing—up to three (3) at 9:00 AM, 12:00 PM, 3:00 PM, and 6:00 PM every day.

2026-01-28

RFC 9917: IGP Flexible Algorithms Reverse Affinity Constraint, P. Psenak, et al., rfc-editor.org/info/rfc9917 #RFC An IGP Flexible Algorithm (Flex-Algorithm) enables the computation of constraint-based paths within an IGP domain, allowing operators to influence path selection according to administrative policies. This document defines an extension to Flex-Algorithm that allows the 1/3

Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2026-01-27

RFC 9816: Usage and Applicability of BGP-SPF in Data Centers

Le RFC 9815 normalise l'utilisation de l'algorithme de routage #SPF avec #BGP. Dans quels cas est-ce que ça peut s'appliquer à l'intérieur d'un centre de données ? Ce #RFC 9816 donne des éléments de réponse.

bortzmeyer.org/9816.html

Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2026-01-27

RFC 9815: BGP Link-State Shortest Path First Routing

Vous le savez (peut-être), le protocole de #routage #BGP est du type « vecteur de chemin ». Mais il peut aussi transporter des états des liens, si on souhaite faire des choses plus proches des protocoles à état des liens. Ce #RFC décrit comment, avec ces informations sur l'état des liens, décider du routage par l'algorithme #SPF (Shortest Path First) plutôt que par la méthode traditionnelle de BGP.

bortzmeyer.org/9815.html

2026-01-23

Who did know of #RFC 9886’s HHIT(67) and BRID(68) #dns resource records? #CVE_2025_13878

2026-01-22

Backward-трассировка требований в Git

Меня зовут Александр Мачулин, я основатель Gramax – open source системы для ведения документации в подходе Docs as Code с визуальным редактором. Сегодня я расскажу вам идею, как вести всю документацию по проекту и весь цикл разработки в одном Git-репозитории и настроить backward-трассировку требований в Git. Интересно, давай!

habr.com/ru/companies/gram_ax/

#трассировка #docs_as_code #adr #rfc #prd

:rss: 4Gamer.net − 注目の記事のみ4gamer@rss-mstdn.studiofreesia.com
2026-01-22

「RAIDEN FIGHTERS REMIX COLLECTION」,一般向け発売前試遊会を1月31日に高田馬場ゲーセンミカドで開催
4gamer.net/games/841/G084166/2

#4gamer # #Ǻ_2026_01_22_12_00 #ץ_åȥե_PS5 #ץ_åȥե_Nintendo_Switch #ץ_åȥե_PS4 #塼_ƥ #RAIDEN_FIGHTERS_REMIX_COLLECTION # #ťե #饤_ǥ_ե_ߥå_쥯 #RFC

Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2026-01-08

RFC 9910: #RDAP #RIR Search

Le protocole RDAP, successeur de whois, n'est pas utilisé que par les registres de noms de domaine. Il sert aussi chez les RIR, pour obtenir des informations sur les entités qui sont derrière une adresse IP (ou un AS). RDAP dispose dès le début de fonctions de recherche mais ce nouveau #RFC ajoute des choses en plus.

bortzmeyer.org/9910.html

2026-01-08

RFC 9897: Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses, M. Amend, Ed., et al., rfc-editor.org/info/rfc9897 #RFC Datagram Congestion Control Protocol (DCCP) communications, as defined in RFC 4340, are inherently restricted to a single path per connection, despite the availability of multiple network paths between peers. The 1/4

2026-01-08

RFC 9910: Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search, T. Harrison, et al., rfc-editor.org/info/rfc9910 #RFC The Registration Data Access Protocol (RDAP) is used by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs) to provide access to their resource registration information. The core specifications for RDAP define basic 1/3

2026-01-06

RFC 9908: Clarification and Enhancement of the CSR Attributes Definition in RFC 7030, M. Richardson, Ed., et al., rfc-editor.org/info/rfc9908 #RFC This document updates RFC 7030, "Enrollment over Secure Transport" (EST), clarifying how the Certificate Signing Request (CSR) Attributes Response can be used by an EST server to specify both CSR attribute Object Identifiers (OIDs) and 1/3

Pontiff Fractal Tiampft@infosec.exchange
2026-01-03

SPF is unnecessarily complex: it's a DNS txt record which more than often is on the zone apex and so cannot be CNAMEd. Their solution: a special policy called redirect (example from RFC 7280:

sf.example.com. TXT "v=spf1 redirect=_spf.example.com"
_spf.example.com. TXT "v=spf1 mx:example.com -all"

guess what? You could've designated a dedicate namespace similar to DMARC (e.g., _dmarc.example.com) and CNAME that to wherever you want.

#spf #dns #rfc

Hype for the Future 57I: Hartford, Connecticut

Introduction The City of Hartford is located within the interior region of the State of Connecticut, well to the north of New Haven along Interstate 91 and United States Route 5 and along the Connecticut River upstream from the Haddam area and, ultimately, from the Saybrook area that has originally defined the State of Connecticut in the colonial era. The State of Connecticut While not the largest city within the State of Connecticut, the City of Hartford serves as the capital city of the […]

novatopflex.wordpress.com/2025

Hype for the Future 57H: Research Stats

Conclusion Of the four (4) cities presented to the community by novaTopFlex (Northampton, Springfield, Hartford, New Haven), the City of Hartford, Connecticut, would ultimately be the most selected. Though only three (3) people have voted on the poll, which has not gone viral on Mastodon as of yet, the poll remains vital to identifying how to divide and conquer special interests. Of the three people, two (2) have voted on Hartford, and one (1) has voted on Springfield, just over the line […]

novatopflex.wordpress.com/2025

Hype for the Future 56B: The Plan for geoTopFlex

Highway Channel geoTopFlex shall continue to be primarily focused on the roads and highways of the United States of America and possibly other countries. Map data shall always be derived from OpenStreetMap contributors and associated contributions, and the goals for novaTopFlex shall remain based on OSM. Tourist attractions can be mentioned under the Third Identity banner if any historical interest is involved.

novatopflex.wordpress.com/2025

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst