[Taps] [Editorial Errata Reported] RFC8304 (6370)

RFC Errata System <rfc-editor@rfc-editor.org> Sat, 26 December 2020 10:54 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 5829E3A0FED for <taps@ietfa.amsl.com>; Sat, 26 Dec 2020 02:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 jFLJgf9sjMGI for <taps@ietfa.amsl.com>; Sat, 26 Dec 2020 02:54:56 -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 0EBC93A0FEB for <taps@ietf.org>; Sat, 26 Dec 2020 02:54:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 63241F406DB; Sat, 26 Dec 2020 02:54:31 -0800 (PST)
To: gorry@erg.abdn.ac.uk, tom@erg.abdn.ac.uk, martin.h.duke@gmail.com, magnus.westerlund@ericsson.com, aaron.falk@gmail.com, Zaheduzzaman.Sarker@ericsson.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nmalykh@ieee.org, taps@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20201226105431.63241F406DB@rfc-editor.org>
Date: Sat, 26 Dec 2020 02:54:31 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/ltIQhiTpaofgIyUcLcJa4uMyYu0>
Subject: [Taps] [Editorial Errata Reported] 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: Sat, 26 Dec 2020 10:54:57 -0000

The following errata report has been submitted 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

--------------------------------------
Type: Editorial
Reported by: Nikolai Malykh <nmalykh@ieee.org>

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

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

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