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

RFC Errata System <rfc-editor@rfc-editor.org> Sat, 26 December 2020 11:07 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 94E553A0FF5 for <taps@ietfa.amsl.com>; Sat, 26 Dec 2020 03:07:15 -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 jrufqGMAatQB for <taps@ietfa.amsl.com>; Sat, 26 Dec 2020 03:07:14 -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 66EDD3A0FF4 for <taps@ietf.org>; Sat, 26 Dec 2020 03:07:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F3604F40715; Sat, 26 Dec 2020 03:06:50 -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: <20201226110650.F3604F40715@rfc-editor.org>
Date: Sat, 26 Dec 2020 03:06:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/IBP1lxcCBKCeRB-gVFjZN6ZidNk>
Subject: [Taps] [Editorial Errata Reported] RFC8304 (6371)
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 11:07:16 -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/eid6371

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

Section: 3.1

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


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

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