IETF Logo Mail Archive

Re: [xrblock] [MMUSIC][XRBLOCK] SDP Directorate: Review of draft-ietf-xrblock-rtcp-xr-synchronization-02

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Thu, 07 March 2013 09:25 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 CA66D21F8C9D; Thu, 7 Mar 2013 01:25:04 -0800 (PST)
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 OrPu-KNgxkYJ; Thu, 7 Mar 2013 01:25:04 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D1A4C21F8B08; Thu, 7 Mar 2013 01:25:02 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APC69904; Thu, 07 Mar 2013 09:25:01 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 7 Mar 2013 09:24:47 +0000
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, 7 Mar 2013 09:25:01 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.45]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Thu, 7 Mar 2013 17:24:55 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, "draft-ietf-xrblock-rtcp-xr-synchronization@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-synchronization@tools.ietf.org>
Thread-Topic: [MMUSIC][XRBLOCK] SDP Directorate: Review of draft-ietf-xrblock-rtcp-xr-synchronization-02
Thread-Index: AQHOGxWgn8HkHKZ3JEu//kKUXrOOSA==
Date: Thu, 07 Mar 2013 09:24:54 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB4572227F@nkgeml501-mbs.china.huawei.com>
References: <C15918F2FCDA0243A7C919DA7C4BE9940CF47F88@xmb-aln-x01.cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE9940CF47F88@xmb-aln-x01.cisco.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
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "xrblock@ietf.org" <xrblock@ietf.org>
Subject: Re: [xrblock] [MMUSIC][XRBLOCK] SDP Directorate: Review of draft-ietf-xrblock-rtcp-xr-synchronization-02
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, 07 Mar 2013 09:25:05 -0000

Hi Ali,

Thanks for your review. Please see inline.

Best Regards!
Rachel

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Ali C. Begen (abegen)
Sent: Thursday, March 07, 2013 10:50 AM
To: draft-ietf-xrblock-rtcp-xr-synchronization@tools.ietf.org
Cc: mmusic@ietf.org
Subject: [MMUSIC] SDP Directorate: Review of draft-ietf-xrblock-rtcp-xr-synchronization-02

I am the assigned SDP directorate reviewer for this draft. For background on the SDP directorate, please see the FAQ at
http://www.ietf.org/iesg/directorate/sdp.html

Please wait for direction from your document shepherd or AD before posting a new version of the draft.

Summary:
- The RTCP XR extension syntax has some issues, see below
- There are a few editorial issues

Issues:
1) Section 1.4, parag. 1 is confusing. I understand what you mean but there are some plural/singular issues that need to be fixed.

[Rachel]: Okay. We'll check and fix them.

2) Section 5.1. As I understand the two blocks can be used separately or together (Correct me if I am wrong). So, the ABNF should be as follows:

   xr-format =/ xr-rfisd-block / xr-rfso-block
   xr-rfisd-block = "init-syn-delay"
   xr-rfso-block = "syn-offset"

[Rachel]:Oh, we missed the first "/" in our ABNF definition. Thanks for pointing out.  

3) I actually prefer "sync" instead of "syn" in the registrations since syn is something related to TCP and might be confusing here.

[Rachel]:Will fix this.

4) Section 6. Write the full name of the registry (RTP Control Protocol Extended Reports (RTCP XR) Session Description Protocol (SDP) Parameters Registry). Also, the parameters you are registering should be "init-syn-delay" and "syn-offset" according to Section 5.1.

[Rachel]:Okay.

5) Section 5.2. It is not specified whether this parameter is unilateral or not.

[Rachel]: Right. We will rewrite it as following

"When SDP is used in offer-answer context, the SDP Offer/Answer usage defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters applies. For detailed usage of Offer/Answer for unilateral parameter, refer to section 5.2 of [RFC3611]." 

6) Section 6. Write the full name of the registry (RTP Control Protocol Extended Reports (RTCP XR) Block Type Registry).

[Rachel]: Okay.

7) Section 6. Put a note for the RFC editor asking to replace the <RFISD> and <RFSO> with the actual values upon publications. 

[Rachel]: Will do.

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

v2.23.0 | Report a Bug | By Email