RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Held for Document Update (2)

RFC 8304, "Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)", February 2018

Source of RFC: taps (tsv)

Errata ID: 6370
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Nikolai Malykh
Date Reported: 2020-12-26
Held for Document Update by: Martin Duke
Date Held: 2021-01-19

Section 3.1 says:

   GET_ECN:  The GET_ECN primitive is a network-layer function that
      returns the value of the ECN field in the IP header of a received
      UDP datagram.  Section 3.1.5 of [RFC8085] states that a UDP
      receiver "MUST check the ECN field at the receiver for each UDP
      datagram that it receives on this port", requiring the UDP
      receiver API to pass the received ECN field up to the application
      layer to enable appropriate congestion feedback.

It should say:

   GET_ECN:  The GET_ECN primitive is a network-layer function that
      returns the value of the ECN field in the IP header of a received
      UDP datagram.  Section 3.1.7 of [RFC8085] states that a UDP
      receiver "MUST check the ECN field at the receiver for each UDP
      datagram that it receives on this port", requiring the UDP
      receiver API to pass the received ECN field up to the application
      layer to enable appropriate congestion feedback.

Notes:

Incorrect reference to RFC 8085

Errata ID: 6371
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Nikolai Malykh
Date Reported: 2020-12-26
Held for Document Update by: Martin Duke
Date Held: 2021-01-19

Section 3.1 says:

   ERROR_REPORT:  The ERROR_REPORT event informs an application of "soft
      errors", including the arrival of an ICMP or ICMPv6 error message.
      Section 4.1.4 of the requirements for Internet hosts [RFC1122]
      states that "UDP MUST pass to the application layer all ICMP error
      messages that it receives from the IP layer."  For example, this
      event is required to implement ICMP-based Path MTU Discovery
      [RFC1191] [RFC8201].  UDP applications must perform a CONNECT to
      receive ICMP errors.

It should say:

   ERROR_REPORT:  The ERROR_REPORT event informs an application of "soft
      errors", including the arrival of an ICMP or ICMPv6 error message.
      Section 4.1.3.3 of the requirements for Internet hosts [RFC1122]
      states that "UDP MUST pass to the application layer all ICMP error
      messages that it receives from the IP layer."  For example, this
      event is required to implement ICMP-based Path MTU Discovery
      [RFC1191] [RFC8201].  UDP applications must perform a CONNECT to
      receive ICMP errors.

Notes:

Incorrect reference to RFC 1122

Report New Errata