Gea-Suan Lin走 RFC 2136 更新 DNS record 的 Dynamic DNS 服務
Dmitri Goosens 
So listened to @brendt (https://www.youtube.com/watch?v=4wpW98S2xJQ)
and read @Girgias (https://gpb.moe/blog/opinion-bound-erased-generics.html) about #Generics in #PHP
both are good
Was very in favor and even enthusiastic of the #RFC at first...
But, I have the feeling some of us, me included, would want those Generics so bad, we would settle for an early compromise that would, in fact, potentially, have very negative consequences for the future of #PHP and break some of the basic standards we adopted in regards of type checking...
The final boss. Generics in PHP
Gina Peter BanyardI've written about the recent #PHP #RFC to add bound erased generic types to PHP: https://gpb.moe/blog/opinion-bound-erased-generics.html
Not used to writing article, even less so articles clocking in at 2.3k words.
RFC EditorRFC 9993: RTP Payload Format for Haptics, HS Yang, et al., https://www.rfc-editor.org/info/rfc9993 #RFC This memo specifies an RTP payload format for MPEG-I haptic data. A haptic media stream is composed of MPEG-I Haptic Stream (MIHS) units including a MIHS unit header and zero or more MIHS packets. The RTP payload header format allows for packetization of a MIHS unit in an RTP packet payload 1/3
RFC 9993: RTP Payload Format for Haptics | RFC Editor
This memo specifies an RTP payload format for MPEG-I haptic data. A haptic media stream is composed of MPEG-I Haptic Stream (MIHS) units including a MIHS unit header and zero or more MIHS packets. The RTP payload header format allows for packetization of a MIHS unit in an RTP packet payload as well as fragmentation of a MIHS unit into multiple RTP packets. The original subtype registration for 'haptics/hmpg' (RFC 9695) did not include any required or optional parameters. This memo updates RFC 9695 and the 'haptics/hmpg' registration to add optional parameters. It also provides Session Description Protocol (SDP) usage information for the 'haptics' media type.
RFC 9981: Resource Public Key Infrastructure (RPKI) Manifest Number Handling, T. Harrison, et al., https://www.rfc-editor.org/info/rfc9981 #RFC The Resource Public Key Infrastructure (RPKI) makes use of signed objects called "manifests", each of which includes a "manifest number". This document updates RFC 9286 by specifying issuer and Relying Party (RP) behaviour when a manifest number 1/2
RFC 9981: Resource Public Key Infrastructure (RPKI) Manifest Number Handling | RFC Editor
The Resource Public Key Infrastructure (RPKI) makes use of signed objects called "manifests", each of which includes a "manifest number". This document updates RFC 9286 by specifying issuer and Relying Party (RP) behaviour when a manifest number reaches the largest possible value, a situation not considered in RFC 9286.
RFC 9979: Registration of Further IMAP/JMAP Keywords and Mailbox Name Attributes, N. Jenkins, et al., https://www.rfc-editor.org/info/rfc9979 #RFC This document defines a number of keywords and mailbox name attributes that have been in use across different server and client implementations. It defines the intended use of these keywords and mailbox name attributes. This document registers 1/2
RFC 9979: Registration of Further IMAP/JMAP Keywords and Mailbox Name Attributes | RFC Editor
This document defines a number of keywords and mailbox name attributes that have been in use across different server and client implementations. It defines the intended use of these keywords and mailbox name attributes. This document registers all of these with IANA to avoid name collisions.
RFC 9977: Publishing End-Site Prefix Lengths, O. Gasser, et al., https://www.rfc-editor.org/info/rfc9977 #RFC This document specifies how to augment the Routing Policy Specification Language (RPSL) inetnum: class to refer specifically to prefixlen files, which are Comma-Separated Values (CSV) files used to specify end-site prefix lengths. This document also describes an optional mechanism 1/2
RFC 9977: Publishing End-Site Prefix Lengths | RFC Editor
This document specifies how to augment the Routing Policy Specification Language (RPSL) inetnum: class to refer specifically to prefixlen files, which are Comma-Separated Values (CSV) files used to specify end-site prefix lengths. This document also describes an optional mechanism that uses the Resource Public Key Infrastructure (RPKI) to authenticate the prefixlen files.
Tamme Dittrich
Stéphane BortzmeyerRFC 9987: Secure Shell (SSH) Agent Protocol, D. Miller, https://www.rfc-editor.org/info/rfc9987 #RFC This document specifies a key agent protocol for use in the Secure Shell (SSH) protocol. This document is a product of the Secure Shell Maintenance Working Group of the IETF.
