Re: [ippm] [Editorial Errata Reported] RFC5938 (2478)

"Murtaza Chiba (mchiba)" <mchiba@cisco.com> Thu, 19 August 2010 16:36 UTC

Return-Path: <mchiba@cisco.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E00193A6A4C for <ippm@core3.amsl.com>; Thu, 19 Aug 2010 09:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDNYQT0Kn+Jq for <ippm@core3.amsl.com>; Thu, 19 Aug 2010 09:36:24 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 9F4C63A6A48 for <ippm@ietf.org>; Thu, 19 Aug 2010 09:36:24 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAE76bEyrRN+J/2dsb2JhbACgUHGIJJpAnAOFNwSEM4grh1Y
X-IronPort-AV: E=Sophos;i="4.56,234,1280707200"; d="scan'208";a="242539411"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 19 Aug 2010 16:36:59 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o7JGaxY6001355; Thu, 19 Aug 2010 16:36:59 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 19 Aug 2010 09:36:59 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 19 Aug 2010 09:36:57 -0700
Message-ID: <D492339CC466C84EA5E0AF1CECB200810BA2D0FE@xmb-sjc-21b.amer.cisco.com>
In-Reply-To: <201008191533.o7JFXYlA013447@alpd052.aldc.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Editorial Errata Reported] RFC5938 (2478)
Thread-Index: Acs/s+vw603uisgUQh+q07uxNHDq6QAB5Nnw
References: <20100819151246.E8835E0692@rfc-editor.org> <201008191533.o7JFXYlA013447@alpd052.aldc.att.com>
From: "Murtaza Chiba (mchiba)" <mchiba@cisco.com>
To: Al Morton <acmorton@att.com>, RFC Errata System <rfc-editor@rfc-editor.org>, ietfdbh@comcast.net, lars.eggert@nokia.com, henk@ripe.net, matt@internet2.edu
X-OriginalArrivalTime: 19 Aug 2010 16:36:59.0415 (UTC) FILETIME=[BE96DA70:01CB3FBC]
Cc: ah@TR-Sys.de, rfc-editor@rfc-editor.org, ippm@ietf.org
Subject: Re: [ippm] [Editorial Errata Reported] RFC5938 (2478)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 19 Aug 2010 16:36:28 -0000

Agreed, so what is the procedure now?

Thanks,
-murtaza

-----Original Message-----
From: Al Morton [mailto:acmorton@att.com] 
Sent: Thursday, August 19, 2010 8:34 AM
To: RFC Errata System; Murtaza Chiba (mchiba); ietfdbh@comcast.net;
lars.eggert@nokia.com; henk@ripe.net; matt@internet2.edu
Cc: ah@TR-Sys.de; ippm@ietf.org; rfc-editor@rfc-editor.org
Subject: Re: [Editorial Errata Reported] RFC5938 (2478)

Alfred is right again,
Al

At 11:12 AM 8/19/2010, RFC Errata System wrote:

>The following errata report has been submitted for RFC5938,
>"Individual Session Control Feature for the Two-Way Active 
>Measurement Protocol (TWAMP)".
>
>--------------------------------------
>You may review the report below and at:
>http://www.rfc-editor.org/errata_search.php?rfc=5938&eid=2478
>
>--------------------------------------
>Type: Editorial
>Reported by: Alfred Hoenes <ah@TR-Sys.de>
>
>Section: 3.2 and 3.4
>
>Original Text
>-------------
>a) [[ second-to-last para of Section 3.2: ]]
>
>    The Server MUST respond with one or more Start-N-Ack messages
(which
>    SHOULD be sent as quickly as possible).  Start-N-Ack messages SHALL
>|  have the format defined in the next session.
>                                          ^^
>
>b) [[ last para of Section 3.4: ]]
>
>    The Server MUST respond with one or more Stop-N-Ack messages (which
>    SHOULD be sent as quickly as possible).  Stop-N-Ack messages SHALL
>|  have the format defined in the next session.
>                                          ^^
>
>Corrected Text
>--------------
>a)
>
>    The Server MUST respond with one or more Start-N-Ack messages
(which
>    SHOULD be sent as quickly as possible).  Start-N-Ack messages SHALL
>|  have the format defined in the next section.
>                                          ^^
>
>b)
>
>    The Server MUST respond with one or more Stop-N-Ack messages (which
>    SHOULD be sent as quickly as possible).  Stop-N-Ack messages SHALL
>|  have the format defined in the next section.
>                                          ^^
>
>Notes
>-----
>Rationale: potentially confusing typo (iterated)!
>
>Instructions:
>-------------
>This errata 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 (IESG)
>can log in to change the status and edit the report, if necessary.
>
>--------------------------------------
>RFC5938 (draft-ietf-ippm-twamp-session-cntrl-07)
>--------------------------------------
>Title               : Individual Session Control Feature for the 
>Two-Way Active Measurement Protocol (TWAMP)
>Publication Date    : August 2010
>Author(s)           : A. Morton, M. Chiba
>Category            : PROPOSED STANDARD
>Source              : IP Performance Metrics
>Area                : Transport
>Stream              : IETF
>Verifying Party     : IESG