Re: [payload] [Technical Errata Reported] RFC6190 (3711)

"Wang, Ye-Kui" <yekuiw@qti.qualcomm.com> Fri, 11 October 2013 03:45 UTC

Return-Path: <yekuiw@qti.qualcomm.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAE8821E819F for <payload@ietfa.amsl.com>; Thu, 10 Oct 2013 20:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.148
X-Spam-Level:
X-Spam-Status: No, score=-105.148 tagged_above=-999 required=5 tests=[AWL=1.450, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 tEIQWiq6q5oV for <payload@ietfa.amsl.com>; Thu, 10 Oct 2013 20:45:15 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id C2D0611E8115 for <payload@ietf.org>; Thu, 10 Oct 2013 20:45:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1381463106; x=1412999106; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=v4uDqea+CO+CB5Wy6Ojrw4lKc5c0zXkxj0qbt2qtAgA=; b=MhjC8OpSaCebjhEmUxDoRH32aflN1Z9pjipSVYtTTazCTmEVt123wQJQ IcRLFOdO8D912xz3rNb6Xq6Or0CEsXEudbIXdNgFMNC/5XY7lT9fpgsK/ ecuiB+TIlGUWe92SyW6hzWAa7pvDbH+L1Vn6zK+00R1EELoZ/lfAwDcFD E=;
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="80243712"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 10 Oct 2013 20:45:06 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="531665633"
Received: from nasanexhc03.na.qualcomm.com ([172.30.48.26]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 10 Oct 2013 20:45:04 -0700
Received: from NASANEXD02F.na.qualcomm.com ([169.254.8.158]) by NASANEXHC03.na.qualcomm.com ([172.30.48.26]) with mapi id 14.03.0158.001; Thu, 10 Oct 2013 20:45:03 -0700
From: "Wang, Ye-Kui" <yekuiw@qti.qualcomm.com>
To: Richard Barnes <rlb@ipv.sx>, RFC Errata System <rfc-editor@rfc-editor.org>
Thread-Topic: [payload] [Technical Errata Reported] RFC6190 (3711)
Thread-Index: AQHOonnvCEDPrF6dvUOMNHeKrvvlvpnvEtiAgAAPoIA=
Date: Fri, 11 Oct 2013 03:45:03 +0000
Message-ID: <8BA7D4CEACFFE04BA2D902BF11719A83385B3410@nasanexd02f.na.qualcomm.com>
References: <20130826162642.54E0B8E018@rfc-editor.org> <CAL02cgT_6brgOBVDTjoNzfyxb4CX=C0ULv1Ce+hwTZZw-fxr2w@mail.gmail.com>
In-Reply-To: <CAL02cgT_6brgOBVDTjoNzfyxb4CX=C0ULv1Ce+hwTZZw-fxr2w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.30.48.1]
Content-Type: multipart/alternative; boundary="_000_8BA7D4CEACFFE04BA2D902BF11719A83385B3410nasanexd02fnaqu_"
MIME-Version: 1.0
Cc: "ts@thomas-schierl.de" <ts@thomas-schierl.de>, "payload@ietf.org" <payload@ietf.org>
Subject: Re: [payload] [Technical Errata Reported] RFC6190 (3711)
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Oct 2013 03:45:31 -0000

The erratum is correct, though to me it is obviously a (relatively minor) typo.

BR, YK

From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On Behalf Of Richard Barnes
Sent: Thursday, October 10, 2013 12:45 PM
To: RFC Errata System
Cc: yekui.wang@huawei.com; payload@ietf.org; ts@thomas-schierl.de
Subject: Re: [payload] [Technical Errata Reported] RFC6190 (3711)

Do any PAYLOAD folks have a comment on this?  This seems like a pretty major erratum, if correct.

Thanks,
--Richard

On Mon, Aug 26, 2013 at 12:26 PM, RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>> wrote:
The following errata report has been submitted for RFC6190,
"RTP Payload Format for Scalable Video Coding".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6190&eid=3711

--------------------------------------
Type: Technical
Reported by: Xiaohui Wei (Joanne) <weix@avaya.com<mailto:weix@avaya.com>>

Section: 1.1.3

Original Text
-------------
   N:    1 bit
         no_inter_layer_pred_flag.  This flag specifies, when present in
         a coded slice NAL unit, whether inter-layer prediction may be
         used for decoding the coded slice (when equal to 1) or not
         (when equal to 0).

Corrected Text
--------------
   N:    1 bit
         no_inter_layer_pred_flag.  This flag specifies, when present in
         a coded slice NAL unit, whether inter-layer prediction may be
         used for decoding the coded slice (when equal to 0) or not
                                                          ^
         (when equal to 1).
                        ^

Notes
-----


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.

--------------------------------------
RFC6190 (draft-ietf-avt-rtp-svc-27)
--------------------------------------
Title               : RTP Payload Format for Scalable Video Coding
Publication Date    : May 2011
Author(s)           : S. Wenger, Y.-K. Wang, T. Schierl, A. Eleftheriadis
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport Payloads
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG