Gea-Suan Lin
RFC EditorRFC 7757: Explicit Address Mappings for Stateless IP/ICMP Translation, T. Anderson, et al., https://www.rfc-editor.org/info/rfc7757 #RFC This document extends the Stateless IP/ICMP Translation Algorithm (SIIT) with an Explicit Address Mapping (EAM) algorithm and formally updates RFC 6145. The EAM algorithm facilitates stateless IP/ICMP translation between arbitrary (non-IPv4-translatable) 1/2
RFC 7755: SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments, T. Anderson, https://www.rfc-editor.org/info/rfc7755 #RFC This document describes the use of the Stateless IP/ICMP Translation Algorithm (SIIT) in an IPv6 Internet Data Center (IDC). In this deployment model, traffic from legacy IPv4-only clients on the Internet is translated to IPv6 upon reaching the IDC 1/3
RFC 7755: SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments, T. Anderson, https://www.rfc-editor.org/info/rfc7755 #RFC This document describes the use of the Stateless IP/ICMP Translation Algorithm (SIIT) in an IPv6 Internet Data Center (IDC). In this deployment model, traffic from legacy IPv4-only clients on the Internet is translated to IPv6 upon reaching the IDC 1/3
RFC 7756: Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation Mode, T. Anderson, et al., https://www.rfc-editor.org/info/rfc7756 #RFC This document describes an extension of the Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC) architecture, which allows applications, protocols, or nodes that are incompatible 1/3
RFC 6493: The Resource Public Key Infrastructure (RPKI) Ghostbusters Record, R. Bush, https://www.rfc-editor.org/info/rfc6493 #RFC In the Resource Public Key Infrastructure (RPKI), resource certificates completely obscure names or any other information that might be useful for contacting responsible parties to deal with issues of certificate expiration, maintenance, roll-overs, compromises, 1/3
T_X (-> FOSDEM)Only started to read into this "new" , informational #IETF #RFC, called "#Multicast Lessons Learned from Decades of Deployment Experience", but it's already a super interesting read:
https://datatracker.ietf.org/doc/draft-ietf-pim-multicast-lessons-learned/
https://datatracker.ietf.org/doc/draft-ietf-pim-multicast-lessons-learned/
Multicast Lessons Learned from Decades of Deployment Experience
This document gives a historical perspective about the design and deployment of multicast routing protocols. The document describes the technical challenges discovered from building these protocols. Even though multicast has enjoyed success of deployment in special use-cases, this draft discusses what were, and are, the obstacles for mass deployment across the Internet. Individuals who are working on new multicast related protocols will benefit by knowing why certain older protocols are no longer in use today.
Cusy Design SystemWe have significantly expanded our German-language documentation guide on the technical writing of top-level domains, IP addresses and telephone numbers: https://www.cusy.design/writing/wordlist.html
#TechnicalWriting #RFC
#TechnicalWriting #RFC
Kevin Karhan 
Addendum: I was wrong.
Thanks for correcting me everyone!
@hisold WTF?
WHO AT #IETF decided to allow this #Enshittification???
#JavaScript is malware and #JS does not belong into any #RFC!!!
RFC 9893: Dynamic Link Exchange Protocol (DLEP) Credit-Based Flow Control Messages and Data Items, B. Cheng, et al., https://www.rfc-editor.org/info/rfc9893 #RFC This document defines new Dynamic Link Exchange Protocol (DLEP) Data Items that are used to support credit-based flow control. Credit window flow control is used to regulate when data may be sent to an associated virtual or physical 1/2