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

Glen Zorn <gwz@net-zen.net> Tue, 18 December 2012 01:50 UTC

Return-Path: <gwz@net-zen.net>
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 B58FA11E8097 for <mmusic@ietfa.amsl.com>; Mon, 17 Dec 2012 17:50:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2aBCsij3nisk for <mmusic@ietfa.amsl.com>; Mon, 17 Dec 2012 17:50:56 -0800 (PST)
Received: from sg2plout10-01.prod.sin2.secureserver.net (sg2plout10-01.prod.sin2.secureserver.net [182.50.145.4]) by ietfa.amsl.com (Postfix) with SMTP id 7A21B21F882B for <mmusic@ietf.org>; Mon, 17 Dec 2012 17:50:54 -0800 (PST)
Received: (qmail 27839 invoked from network); 18 Dec 2012 01:50:50 -0000
Received: from unknown (110.169.202.60) by sg2plout10-01.prod.sin2.secureserver.net (182.50.145.4) with ESMTP; 18 Dec 2012 01:50:50 -0000
Message-ID: <50CFCBF9.3070301@net-zen.net>
Date: Tue, 18 Dec 2012 08:50:49 +0700
From: Glen Zorn <gwz@net-zen.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Jonathan Lennox <jonathan@vidyo.com>
References: <C3759687E4991243A1A0BD44EAC823034DFB915B07@BE235.mail.lan>
In-Reply-To: <C3759687E4991243A1A0BD44EAC823034DFB915B07@BE235.mail.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 17 Dec 2012 22:27:58 -0800
Cc: "draft-ietf-xrblock-rtcp-xr-discard@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-discard@tools.ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, gwz@net-zen.net
Subject: Re: [MMUSIC] SDP Directorate review of draft-ietf-xrblock-rtcp-xr-discard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 01:50:56 -0000

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?

...