[ippm] [Technical Errata Reported] RFC6038 (6410)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 25 January 2021 08:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AD13A0C8B for <ippm@ietfa.amsl.com>; Mon, 25 Jan 2021 00:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level:
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[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 bM_TlgodeIZe for <ippm@ietfa.amsl.com>; Mon, 25 Jan 2021 00:17:03 -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 AD05E3A0C8A for <ippm@ietf.org>; Mon, 25 Jan 2021 00:17:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D2A05F4074C; Mon, 25 Jan 2021 00:17:02 -0800 (PST)
To: acmorton@att.com, lencia@att.com, martin.h.duke@gmail.com, magnus.westerlund@ericsson.com, ianswett@google.com, tpauly@apple.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nmalykh@ieee.org, ippm@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210125081702.D2A05F4074C@rfc-editor.org>
Date: Mon, 25 Jan 2021 00:17:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/otMsPFK7O5V7HocSMTLJLRGNXW8>
Subject: [ippm] [Technical Errata Reported] RFC6038 (6410)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 08:17:05 -0000

The following errata report has been submitted for RFC6038,
"Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features".

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

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

Section: 5.2.1

Original Text
-------------
   Section 4.2.1 of [RFC5357] recommends a padding truncation process
   for use in TWAMP.  When using that process in conjunction with the
   Reflect Octets mode, the Session-Reflector MUST reflect the
   designated octets from the Session-Sender's test packet in the Packet
   Padding (from Session-Sender) field, and MAY re-use additional Packet
   Padding from the Session-Sender.  The Session-Reflector MUST truncate
   the padding such that the highest number octets are discarded, and
   the test packet length equals the Session-Sender's packet length.
   When using the recommended truncation process, the Session-Reflector
   MUST truncate exactly 27 octets of padding in Unauthenticated mode,
   and exactly 56 octets in Authenticated and Encrypted modes.



Corrected Text
--------------
   Section 4.2.1 of [RFC5357] recommends a padding truncation process
   for use in TWAMP.  When using that process in conjunction with the
   Reflect Octets mode, the Session-Reflector MUST reflect the
   designated octets from the Session-Sender's test packet in the Packet
   Padding (from Session-Sender) field, and MAY re-use additional Packet
   Padding from the Session-Sender.  The Session-Reflector MUST truncate
   the padding such that the highest number octets are discarded, and
   the test packet length equals the Session-Sender's packet length.
   When using the recommended truncation process, the Session-Reflector
   MUST truncate exactly 27 octets of padding in Unauthenticated mode,
   and exactly 64 octets in Authenticated and Encrypted modes.



Notes
-----
Invalid required padding size (56 instead of 64) for modes with authentication and encryption.

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. 

--------------------------------------
RFC6038 (draft-ietf-ippm-twamp-reflect-octets-09)
--------------------------------------
Title               : Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features
Publication Date    : October 2010
Author(s)           : A. Morton, L. Ciavattone
Category            : PROPOSED STANDARD
Source              : IP Performance Measurement
Area                : Transport
Stream              : IETF
Verifying Party     : IESG