rfceditor

Official twitter account for the RFC Editor. New RFCs announced at

[rfceditor @RFCEditor]

from causing premature slow start exit. 3/3

[rfceditor @RFCEditor]

RFC 9406: HyStart++: Modified Slow Start for TCP, P. Balasubramanian, et al., https://t.co/ERxrkAKqoJ #RFC This document describes HyStart++, a simple modification to the slow start phase of congestion control algorithms. Slow start 1/3

[rfceditor @RFCEditor]

can overshoot the ideal send rate in many cases, causing high packet loss and poor performance. HyStart++ uses increase in round-trip delay as a heuristic to find an exit point before possible overshoot. It also adds a mitigation to prevent jitter 2/3

[rfceditor @RFCEditor]

information in the packet while the packet traverses a path between two points in the network. This document provides a framework for IOAM deployment and provides IOAM deployment considerations and guidance. 2/2

[rfceditor @RFCEditor]

RFC 9378: In Situ Operations, Administration, and Maintenance (IOAM) Deployment, F. Brockners, Ed., et al., https://t.co/n0111nPmSa #RFC In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry 1/2

[rfceditor @RFCEditor]

and attribute certificates. This document obsoletes RFCs 3709 and 6170. 2/2

[rfceditor @RFCEditor]

RFC 9399: Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates, S. Santesson, et al., https://t.co/86nMdRGIrM #RFC This document specifies a certificate extension for including logotypes in public key certificates 1/2

[rfceditor @RFCEditor]

identifies them for removal from the "int" top-level domain. Any implementations that involve these domains are now deprecated. This document also changes the status of RFC 1528 and RFC 1706 to Historic. 2/2

[rfceditor @RFCEditor]

RFC 9121: Deprecating Infrastructure "int" Domains, K. Davies, et al., https://t.co/GrKEAYhYgH #RFC This document deprecates the use of any "int" domain names that were designated for infrastructure purposes by the IETF, and it 1/2

[rfceditor @RFCEditor]

Have you ever read an RFC? We need your help!

Talk to us about how you use https://t.co/G5RrCkieuU so that we can improve it. We particularly want to hear from people who are new to RFCs, including students, researchers and industry pros. Apply here:
https://t.co/ifQZAe0OQU

[rfceditor @RFCEditor]

Can you spare an hour to help us improve https://t.co/G5RrCkieuU (the official home of RFCs)? If you’ve used RFCs for work, school or research, we’d love to learn from you - particularly if you're new here! Volunteer by answering a few quick questions: https://t.co/ifQZAe0OQU

[rfceditor @RFCEditor]

new PEN and how to modify a current PEN. It also gives a brief overview of PEN uses. 2/2

[rfceditor @RFCEditor]

RFC 9371: Registration Procedures for Private Enterprise Numbers (PENs), A. Baber, et al., https://t.co/Vlq9xD4VqX #RFC This document describes how Private Enterprise Numbers (PENs) are registered by IANA. It shows how to request a 1/2

[rfceditor @RFCEditor]

fragmentation Rules. 2/2

[rfceditor @RFCEditor]

RFC 9363: A YANG Data Model for Static Context Header Compression (SCHC), A. Minaburo, et al., https://t.co/Yww2f2xpCY #RFC This document describes a YANG data model for the Static Context Header Compression (SCHC) compression and 1/2

[rfceditor @RFCEditor]

rates for large amounts of data with less packet interchanges as well as support for faster recovery should any of the blocks get lost in transmission (especially during DDoS attacks). 3/3

[rfceditor @RFCEditor]

RFC 9362: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission, M. Boucadair, et al., https://t.co/7yPzKoRN2I #RFC This document specifies new DDoS Open 1/3

[rfceditor @RFCEditor]

Threat Signaling (DOTS) signal channel configuration parameters that can be negotiated between DOTS peers to enable the use of Q-Block1 and Q-Block2 Constrained Application Protocol (CoAP) options. These options enable robust and faster transmission 2/3

[rfceditor @RFCEditor]

as a sequence of topological elements called "segments". It can be implemented over the MPLS or the IPv6 data plane. This document describes the IS-IS extensions required to support SR over the IPv6 data plane. 2/2

[rfceditor @RFCEditor]

RFC 9352: IS-IS Extensions to Support Segment Routing over the IPv6 Data Plane, P. Psenak, Ed., et al., https://t.co/rnx7ZCXapf, The Segment Routing (SR) architecture allows a flexible definition of the end-to-end path by encoding it 1/2

[rfceditor @RFCEditor]

Definition (FAD). This definition is provisioned on one or more routers and propagated through the network by OSPF and IS-IS flooding. 3/3

[rfceditor @RFCEditor]

RFC 9351: Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement, K. Talaulikar, Ed., et al., https://t.co/edZgTF7ifI, Flexible Algorithm is a solution that allows some routing protocols (e.g., 1/3

[rfceditor @RFCEditor]

OSPF and IS-IS) to compute paths over a network based on user-defined (and hence, flexible) constraints and metrics. The computation is performed by routers participating in the specific network in a distributed manner using a Flexible Algorithm 2/3