From nobody Wed Feb 9 14:19:30 2022 Return-Path: X-Original-To: tcpm@ietfa.amsl.com Delivered-To: tcpm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF423A0122 for ; Wed, 9 Feb 2022 14:19:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 6O9GyJorOCKS for ; Wed, 9 Feb 2022 14:19:23 -0800 (PST) Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 336F43A0A10 for ; Wed, 9 Feb 2022 14:19:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 14097425A344; Wed, 9 Feb 2022 14:19:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sp2tQkMbcWzQ; Wed, 9 Feb 2022 14:19:23 -0800 (PST) Received: from [192.168.1.16] (cpe-76-95-228-63.socal.res.rr.com [76.95.228.63]) by c8a.amsl.com (Postfix) with ESMTPSA id B566D424B435; Wed, 9 Feb 2022 14:19:22 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Chris Smiley In-Reply-To: <20211226085938.97471F0F1F@rfc-editor.org> Date: Wed, 9 Feb 2022 14:19:22 -0800 Cc: yaakovjstein@gmail.com, david.borman@quantum.com, braden@isi.edu, vanj@google.com, rs@netapp.com, tcpm@ietf.org, RFC Errata System Content-Transfer-Encoding: quoted-printable Message-Id: References: <20211226085938.97471F0F1F@rfc-editor.org> To: martin.h.duke@gmail.com, Zaheduzzaman Sarker X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [tcpm] [Editorial Errata Reported] RFC7323 (6798) X-BeenThere: tcpm@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: TCP Maintenance and Minor Extensions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2022 22:19:28 -0000 Greetings, We are unable to verify this erratum that the submitter marked as = editorial. =20 Please note that we have changed the =E2=80=9CType=E2=80=9D of the = following errata=20 report to =E2=80=9CTechnical=E2=80=9D. As Stream Approver, please = review and set the=20 Status and Type accordingly (see the definitions at=20 https://www.rfc-editor.org/errata-definitions/). You may review the report at:=20 https://www.rfc-editor.org/errata/eid6798 Please see https://www.rfc-editor.org/how-to-verify/ for further=20 information on how to verify errata reports. Further information on errata can be found at:=20 https://www.rfc-editor.org/errata.php. Thank you. RFC Editor/cs > On Dec 26, 2021, at 12:59 AM, RFC Errata System = wrote: >=20 > The following errata report has been submitted for RFC7323, > "TCP Extensions for High Performance". >=20 > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid6798 >=20 > -------------------------------------- > Type: Editorial > Reported by: Yaakov Stein >=20 > Section: GLOBAL >=20 > Original Text > ------------- > The Timestamps option may appear in any data or segment, adding >=20 > The timestamp clock may be derived from a system clock that is >=20 > A random offset may be added to the timestamp clock on a per- >=20 > Corrected Text > -------------- > The Timestamps option MAY appear in any data or segment, adding >=20 > The timestamp clock MAY be derived from a system clock that is >=20 > A random offset MAY be added to the timestamp clock on a per- >=20 > Notes > ----- > several "MAY"s were incorrectly written as non RFC 2119 "may"s >=20 > 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 =20 > can log in to change the status and edit the report, if necessary.=20 >=20 > -------------------------------------- > RFC7323 (draft-ietf-tcpm-1323bis-21) > -------------------------------------- > Title : TCP Extensions for High Performance > Publication Date : September 2014 > Author(s) : D. Borman, B. Braden, V. Jacobson, R. = Scheffenegger, Ed. > Category : PROPOSED STANDARD > Source : TCP Maintenance and Minor Extensions > Area : Transport > Stream : IETF > Verifying Party : IESG >=20