IETF Logo Mail Archive

Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Thu, 22 August 2013 06:07 UTC

Return-Path: <rachel.huang@huawei.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 88F4D11E80D1 for <xrblock@ietfa.amsl.com>; Wed, 21 Aug 2013 23:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 RGkFLqfFZX3F for <xrblock@ietfa.amsl.com>; Wed, 21 Aug 2013 23:07:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8D51411E80D7 for <xrblock@ietf.org>; Wed, 21 Aug 2013 23:07:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUP51711; Thu, 22 Aug 2013 06:07:06 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 22 Aug 2013 07:06:10 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 22 Aug 2013 07:06:40 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.198]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Thu, 22 Aug 2013 14:06:31 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock]RE: 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe
Thread-Index: Ac6ec09GHHfi6gZPQpu/64wywp7WoQAiCAdA
Date: Thu, 22 Aug 2013 06:06:31 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB45889FDE@nkgeml501-mbs.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA128B4B0F@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA128B4B0F@AZ-FFEXMB04.global.avaya.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe
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: Thu, 22 Aug 2013 06:07:16 -0000

Hi, 

I have read this draft and believe it's in good shape. I have only one minor comment:

In the section 3.2
"
Reserved: 6 bits

      This field is reserved for future definition.  In the absence of
      such a definition, the bits in this field MUST be set to zero and
      ignored by the receiver (See RFC6709 section 4.2).

"

In What kind of case such a definition will be absent?

Best regards,
Rachel


-----Original Message-----
From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Wednesday, August 21, 2013 9:36 PM
To: xrblock@ietf.org
Subject: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe

Hi,

This is the second WGLC for the Internet-Draft 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MoS Metric Reporting' previously known as 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for QoE Metric Reporting'. Please send your comments, questions, and concerns to the WG list before Wednesday 9/4. If you have no comments or questions and you believe that this document is ready for submission to the IESG for consideration as a Proposed Standard, please send a message stating this. 

The latest version of the document can be retrieved from http://www.ietf.org/id/draft-ietf-xrblock-rtcp-xr-qoe-10.txt.

Thanks and Regards,

Dan



_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock

v2.23.0 | Report a Bug | By Email