[Taps] [Errata Held for Document Update] RFC8304 (6370)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 19 January 2021 23:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA2D3A0912; Tue, 19 Jan 2021 15:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yV0iOo34Msid; Tue, 19 Jan 2021 15:42:54 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87C7B3A03C9; Tue, 19 Jan 2021 15:42:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 45AECF40760; Tue, 19 Jan 2021 15:42:38 -0800 (PST)
To: nmalykh@ieee.org, gorry@erg.abdn.ac.uk, tom@erg.abdn.ac.uk
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: martin.h.duke@gmail.com, iesg@ietf.org, taps@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210119234238.45AECF40760@rfc-editor.org>
Date: Tue, 19 Jan 2021 15:42:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Atkq6jZQUx2ENKA4C2hsvBSnRkM>
Subject: [Taps] [Errata Held for Document Update] RFC8304 (6370)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 23:42:59 -0000

The following errata report has been held for document update 
for RFC8304, "Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6370

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh <nmalykh@ieee.org>
Date Reported: 2020-12-26
Held by: Martin Duke (IESG)

Section: 3.1

Original Text
-------------
   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.

Corrected Text
--------------
   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

--------------------------------------
RFC8304 (draft-ietf-taps-transports-usage-udp-07)
--------------------------------------
Title               : Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)
Publication Date    : February 2018
Author(s)           : G. Fairhurst, T. Jones
Category            : INFORMATIONAL
Source              : Transport Services
Area                : Transport
Stream              : IETF
Verifying Party     : IESG