Re: [xrblock] [MMUSIC] SDP Directorate review ofdraft-ietf-xrblock-rtcp-xr-discard

"Qin Wu" <bill.wu@huawei.com> Mon, 24 December 2012 07:35 UTC

Return-Path: <bill.wu@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 76E7721F8846; Sun, 23 Dec 2012 23:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.548
X-Spam-Level:
X-Spam-Status: No, score=-1.548 tagged_above=-999 required=5 tests=[AWL=-3.046, BAYES_00=-2.599, FORGED_MUA_OUTLOOK=3.116, FORGED_OUTLOOK_TAGS=0.001, HTML_MESSAGE=0.001, SARE_RECV_IP_211216=0.978, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icYL-eChrV0E; Sun, 23 Dec 2012 23:35:49 -0800 (PST)
Received: from WIN-CDPOO5N337C (gw.ntelia.co.kr [175.196.232.146]) by ietfa.amsl.com (Postfix) with ESMTP id 87F0D21F8909; Sun, 23 Dec 2012 23:35:49 -0800 (PST)
Received: from mail pickup service by WIN-CDPOO5N337C with Microsoft SMTPSVC; Mon, 24 Dec 2012 16:34:51 +0900
Content-Transfer-Encoding: 7bit
x-sender: bill.wu@huawei.com
x-receiver: hongkee67@gmail.com
Received: from smtpinbound02.entumoffice.com (10.10.0.47) by GW-SMTPIN1.entumoffice.com (10.10.0.225) with Microsoft SMTP Server id 14.2.247.3; Tue, 18 Dec 2012 11:20:44 +0900
Received: from spamgw.bizmeka.com ([211.218.127.38]) by smtpinbound02.entumoffice.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 18 Dec 2012 11:20:44 +0900
Received: from unknown (HELO mail.ietf.org) (64.170.98.30) by 211.218.127.38 with ESMTP; 18 Dec 2012 11:19:32 +0900
X-Original-SENDERIP: 64.170.98.30
X-Original-MAILFROM: mmusic-bounces@ietf.org
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 967B011E8097; Mon, 17 Dec 2012 18:20:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1355797239; bh=Gqy2ADU5RrcoU19S0VK3x+GAoHm9uhVOucCQqAmUty0=; h=Message-ID:From:To:References:Date:MIME-Version:Cc:Subject: List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=XKcj9iZsKv9P8ScwntDYQcJ7pNQ4CvVIPqBr2mEjVrAqTFRfoRuyFQPfZCuDidN2p vyHirCY7jdy8fW40Fk0LDHsQSbZbBztuLvV8oqrEapFtZ5DWRJB/UtmQ2kA9on4UDg 49fR0Rwpb7OnwTugHNTRcRavml+YmtQx+c36Y9dY=
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0E9C11E8097; Mon, 17 Dec 2012 18:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVx9UCUcP1XH; Mon, 17 Dec 2012 18:20:33 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4DA21F8584; Mon, 17 Dec 2012 18:20:30 -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 AMO97833; Tue, 18 Dec 2012 02:20:29 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) bylhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Dec 2012 02:20:22 +0000
Received: from szxeml459-hub.china.huawei.com (10.82.67.202) bylhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Dec 2012 02:20:28 +0000
Received: from w53375 (10.138.41.149) by szxeml459-hub.china.huawei.com(10.82.67.202) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Dec 2012 10:20:24 +0800
Message-ID: <1.07ee4cc80a7559a4f08c@huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Glen Zorn <gwz@net-zen.net>, Jonathan Lennox <jonathan@vidyo.com>
References: <C3759687E4991243A1A0BD44EAC823034DFB915B07@BE235.mail.lan><50CFCBF9.3070301@net-zen.net>
Date: Tue, 18 Dec 2012 10:20:23 +0800
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-OriginalArrivalTime: 18 Dec 2012 02:20:44.0162 (UTC) FILETIME=[48805E20:01CDDCC6]
X-MS-Exchange-Organization-AuthSource: GW-SMTPIN1.entumoffice.com
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_CDFC_E1E65C5C.2F434373"
Cc: gwz@net-zen.net, draft-ietf-xrblock-rtcp-xr-discard@tools.ietf.org, mmusic@ietf.org, xrblock@ietf.org
Subject: Re: [xrblock] [MMUSIC] SDP Directorate review ofdraft-ietf-xrblock-rtcp-xr-discard
X-BeenThere: xrblock@ietf.org
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: Mon, 24 Dec 2012 07:35:50 -0000

I guess the reference "RFC3711 section 5" Jonathan mentioned should be
 corrected as "RFC3611 section 5".
If my understanding is correct, what Jonathan suggested is to have the
 following change:
OLD TEXT:
"
   RFC 3611 defines the use of SDP (Session Description Protocol)
   [RFC4566] for signaling the use of RTCP XR blocks.  XR blocks MAY be
   used without prior signaling.

"
NEW TEXT:
"
   RFC 3611 defines the use of SDP (Session Description Protocol)
   [RFC4566] for signaling the use of RTCP XR blocks.  However XR blocks MAY
 be
   used without prior signaling (see section 5 of RFC3611).
"
Please correct me if I am wrong.

Regards!
-Qin
----- Original Message ----- 
From: "Glen Zorn" <gwz@net-zen.net>
To: "Jonathan Lennox" <jonathan@vidyo.com>
Cc: <mmusic@ietf.org>; <draft-ietf-xrblock-rtcp-xr-discard@tools.ietf.org>;
 <gwz@net-zen.net>
Sent: Tuesday, December 18, 2012 9:50 AM
Subject: Re: SDP Directorate review of draft-ietf-xrblock-rtcp-xr-discard


> On 12/17/2012 10:49 PM, Jonathan Lennox wrote:
> 
>> I have been asked to perform  the SDP Directorate review for
> > draft-ietf-xrblock-rtcp-xr-discard. I reviewed the -10 version of the
> > document.
> >
> >
> >
> > Syntactically, the SDP usage in this document seems fine. It is a
> > simple and correct usage of an extension point defined in RFC 3711.
> >
> >
> >
> > However, the statement in Section 4 that "XR blocks MAY be used
> > without explicit signaling" is confusing, as it implies that the
> > entire SDP section is entirely optional. This document should at
> > least reference Section 5 of RFC 3711, which gives guidance as to
> > when SDP signaling of the use of XR blocks is recommended.
> >
> 
> I'm not sure why this is confusing (aside from fact that RFC 3711 is 
> itself confusing: it says "although the use of SDP signaling for XR 
> blocks may be optional, if used, it MUST be used as defined here". /May/ 
> be optional?  Optionality seems pretty black and white to me ;-).  That 
> said, however, it does seem to be relatively clear that the usage of SDP 
> /is/ optional & along with it the section on SDP in this and other 
> similar drafts.  What am I missing?
> 
> ...
>
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic