Re: [xrblock] [Technical Errata Reported] RFC7003 (3735)
Alan Clark <alan.d.clark@telchemy.com> Tue, 24 September 2013 12:14 UTC
Return-Path: <alan.d.clark@telchemy.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26FD011E8116 for <xrblock@ietfa.amsl.com>; Tue, 24 Sep 2013 05:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zhfo6HYvF7GF for <xrblock@ietfa.amsl.com>; Tue, 24 Sep 2013 05:14:47 -0700 (PDT)
Received: from omx.cbeyond.com (omx.cbeyond.com [50.20.30.10]) by ietfa.amsl.com (Postfix) with ESMTP id BE27C11E811A for <xrblock@ietf.org>; Tue, 24 Sep 2013 05:14:44 -0700 (PDT)
X-SBRS: -4.0
X-HAT: Sender Group POORREP_BLACKLIST, Policy $SBRSPOOR applied.
X-Hostname: omx08bay.sys.cbeyond.net
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwTAGKBQVJi+2EaPGdsb2JhbAANMxqDP8EigTkDAQEBATiCWgEBAQMBOgIBPAUNAQiBCRQBAQQBDQWHfxI2qQKTOI9RB4QdA60zXg
X-IronPort-AV: E=Sophos;i="4.90,970,1371096000"; d="scan'208";a="37927395"
Received: from c-98-251-97-26.hsd1.ga.comcast.net (HELO [192.168.2.88]) ([98.251.97.26]) by omx.cbeyond.com with ESMTP/TLS/DES-CBC3-SHA; 24 Sep 2013 08:14:42 -0400
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Tue, 24 Sep 2013 08:14:41 -0400
From: Alan Clark <alan.d.clark@telchemy.com>
To: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, Rachel@huawei.com, sunseawq@huawei.com, rlb@ipv.sx, gonzalo.camarillo@ericsson.com, "Dan (Dan)" <dromasca@avaya.com>, Shida Schubert <shida@ntt-at.com>
Message-ID: <CE66FA71.54AB3%alan.d.clark@telchemy.com>
Thread-Topic: [Technical Errata Reported] RFC7003 (3735)
Thread-Index: Ac65H6VgLybI4YdT2020I5x4P+JfFQ==
In-Reply-To: <20130924115821.1052C8E019@rfc-editor.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: xrblock@ietf.org
Subject: Re: [xrblock] [Technical Errata Reported] RFC7003 (3735)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2013 12:14:51 -0000
I agree that this correction is necessary Alan Clark On 9/24/13 7:58 AM, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org> wrote: > The following errata report has been submitted for RFC7003, > "RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard > Metric Reporting". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=7003&eid=3735 > > -------------------------------------- > Type: Technical > Reported by: Dan Romascanu <dromasca@avaya.com> > > Section: 6.1 > > Original Text > ------------- > 6.1. New RTCP XR Block Type Value > > > > This document assigns the block type value 20 in the IANA "RTP > > Control Protocol Extended Reports (RTCP XR) Block Type Registry" to > > the "Burst/Gap Discard Metrics Block". > > > > > > Corrected Text > -------------- > 6.1. New RTCP XR Block Type Value > > > > This document assigns the block type value 21 in the IANA "RTP > > Control Protocol Extended Reports (RTCP XR) Block Type Registry" to > > the "Burst/Gap Discard Metrics Block". > > > > > > Notes > ----- > This error was introduced in the final editorial process before publication. > The change is needed because the correct value, as assigned in the IANA "RTP > > Control Protocol Extended Reports (RTCP XR) Block Type Registry", is 21. > > 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. > > -------------------------------------- > RFC7003 (draft-ietf-xrblock-rtcp-xr-burst-gap-discard-14) > -------------------------------------- > Title : RTP Control Protocol (RTCP) Extended Report (XR) Block > for Burst/Gap Discard Metric Reporting > Publication Date : September 2013 > Author(s) : A. Clark, R. Huang, Q. Wu, Ed. > Category : PROPOSED STANDARD > Source : Metric Blocks for use with RTCPs Extended Report > Framework > Area : Real-time Applications and Infrastructure > Stream : IETF > Verifying Party : IESG
- [xrblock] [Technical Errata Reported] RFC7003 (37… RFC Errata System
- Re: [xrblock] [Technical Errata Reported] RFC7003… Alan Clark
- Re: [xrblock] [Technical Errata Reported] RFC7003… Qin Wu
- Re: [xrblock] [Technical Errata Reported] RFC7003… Gonzalo Camarillo