RFC 9948: Internet Protocol Police (IPP) - Schedule of Punishments, G.R. Beard, et al., https://www.rfc-editor.org/info/rfc9948 #RFC The Internet Protocol Police (IPP) is in charge of punishing willful infractions of the Collected Wisdom of the IETF community. This document sets out the schedule of punishments for such infractions.
Information on RFC 9948 » RFC Editor

Heute kein #RFC :(
#AprilFools

For April Fool's, I give you the "IP over Burrito Carriers" RFC (IETF Request for Comment): https://datatracker.ietf.org/doc/html/draft-lohsen-ip-burrito-00

#IETF #RFC #Humor #Humour

IP over Burrito Carriers

IP over Burrito Carriers describes an experimental method for the creation of edible data packets. This standard is intended to be implemented in metropolitan area networks due to the preexisting burrito delivery infrastructure. While currently only flour tortillas have been found acceptable for encapsulating the data contained in the packet, tests are underway to determine the viability of using corn tortillas. One must be wary of disreputable IP over Burrito service providers as packet corruption and bad data handling can result in damage to the receiving unit and may result in an extremely messy packet rejection. Conveniently, there is a rating system already in place. While the rating by the health department doesn't ensure proper data encapsulation, it does allow the end user to determine if the service provider's quality to cost ratio is adequate. This is an experimental standard, not a recommended standard.

IETF Datatracker
RFC 9950: A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+), M. Boucadair, Ed., et al., https://www.rfc-editor.org/info/rfc9950 #RFC This document defines a Terminal Access Controller Access-Control System Plus (TACACS+) client YANG module that augments the System Management data model, defined in RFC 7317, to allow devices to make use of TACACS+ servers 1/2
Information on RFC 9950 » RFC Editor

RFC 9953: DNS over the Constrained Application Protocol (DoC)

Le protocole #CoAP est un protocole léger, conçu pour les objets connectés. Ce #RFC décrit comment faire du #DNS au-dessus de CoAP. Si votre brosse à dents a besoin de faire du DNS, c'est ce RFC qu'il faut lire.

@miri64

https://www.bortzmeyer.org/9953.html

Blog Stéphane Bortzmeyer: RFC 9953: DNS over the Constrained Application Protocol (DoC)

#RFC to #Wikipedia to #book rabbit hole:

I read the RFC2445 for ics-files today to write a bug report and stumbled over the authors. One was from Lotus.

So I searched Wikipedia because I knew Lotus Notes, which was horrible, and sold in 2013 by IBM.

Then I read that Mitch Kapor founded Lotus and remembered that I read "Dreaming in Code" by Scott Rosenberg more than a decade ago, because somebody lent it to me to read it.

So I just ordered the book to reread it.

#code #projectmanagement

RFC 9952: Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLS, M. S. Lenders, et al., https://www.rfc-editor.org/info/rfc9952 #RFC This document specifies an Application-Layer Protocol Negotiation (ALPN) ID for Constrained Application Protocol (CoAP) services that are secured by DTLS. This document is a product of the Constrained RESTful Environments Working Group of the IETF.
Information on RFC 9952 » RFC Editor

RFC 9953: DNS over CoAP (DoC), M. S. Lenders, et al., https://www.rfc-editor.org/info/rfc9953 #RFC This document defines a protocol for exchanging DNS queries (OPCODE 0) over the Constrained Application Protocol (CoAP). These CoAP messages can be protected by (D)TLS-Secured CoAP or Object Security for Constrained RESTful Environments (OSCORE) to provide encrypted DNS message exchange for 1/2
Information on RFC 9953 » RFC Editor

RFC 1178 (1990): Choosing a Name for Your Computer.
Three decades later, the advice still holds. #cybersecurity #infosec #security #rfc #rfc1178
RFC 9928: DHCPv4 over DHCPv6 with Relay Agent Support, C. Porfiri, et al., https://www.rfc-editor.org/info/rfc9928 #RFC This document describes a mechanism for networks with legacy IPv4-only clients to use services provided by DHCPv4 over DHCPv6 in a Relay Agent. RFC 7341 specifies the use of DHCPv4 over DHCPv6 in the client only. This document specifies an approach based on RFC 7341 that 1/2
Information on RFC 9928 » RFC Editor