…nd its lower layer to expose access to them for sent and received packets (see [RFC3168]). The implementations of DTLS and its lower layer have to provide this support. If this is not possible (for example, due to implementation restrictions), ECN can't be used by SCTP. 6. SCTP C…
…d its lower layer to expose access to them for sent and received packets (see [ RFC3168 ]). The implementations of DTLS and its lower layer have to provide this support. If this is not possible (for example, due to implementation restrictions), ECN can't be used by SCTP. 6 . SCTP…
…irection towards the classifier. Explicit Congestion Notification (ECN) field [ RFC3168 ] Preferred Behavior: Set the outgoing value to the incoming value, UNLESS the server is doing Active Queue Management, the incoming ECN field is ECT(1) (=0b01) or ECT(0) (=0b10), and the serv…
…d its lower layer to expose access to them for sent and received packets (see [ RFC3168 ]). The implementations of DTLS and its lower layer have to provide this support. If this is not possible (for example, due to implementation restrictions), ECN can't be used by SCTP. 6 . SCTP…
…ection towards the classifier. ¶ Explicit Congestion Notification (ECN) field [ RFC3168 ] ¶ Preferred Behavior: Set the outgoing value to the incoming value. The server may perform Active Queue Management, in which case it SHOULD behave as an ECN-aware router [ RFC3168 ] and can …
…ion Protocol September 2007 Appendix A . Explicit Congestion Notification ECN [ RFC3168 ] describes a proposed extension to IP that details a method to become aware of congestion outside of datagram loss. This is an optional feature that an implementation MAY choose to add to SCT…
…QUIC-RECOVERY 13.4. Explicit Congestion Notification QUIC endpoints can use ECN RFC3168 to detect and respond to network congestion. ECN allows an endpoint to set an ECN-Capable Transport (ECT) codepoint in the ECN field of an IP packet. A network node can then indicate congestio…
… enable fall back to non-ECN. Currently, this knob implements the fallback from RFC3168, section 6.1.1.1., but we reserve that in future, additional detection mechanisms could be implemented under this knob. The value is not used, if tcp_ecn or per route (or congestion control) E…
…treatment (e.g., IP DS Field [RFC2780], Explicit Congestion Notification (ECN) [RFC3168], or RSVP) changes. It should say: The value of Type-P-One-way-Packet-Loss could change if the protocol (UDP or TCP), port number, size, or arrangement for special treatment (e.g., IP DS Field…
…treatment (e.g., IP DS Field [RFC2780], Explicit Congestion Notification (ECN) [RFC3168], or RSVP) changes. It should say: The value of Type-P-One-way-Packet-Loss could change if the protocol (UDP or TCP), port number, size, or arrangement for special treatment (e.g., IP DS Field…