Re: [MMUSIC] RID update (draft-pthatcher-mmusic-rid-01,> )

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 16 October 2015 03:04 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA6E1B2DA2 for <mmusic@ietfa.amsl.com>; Thu, 15 Oct 2015 20:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l1HnpHbQuAPk for <mmusic@ietfa.amsl.com>; Thu, 15 Oct 2015 20:04:15 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 228101A1A11 for <mmusic@ietf.org>; Thu, 15 Oct 2015 20:04:15 -0700 (PDT)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-04v.sys.comcast.net with comcast id Vf4B1r0022Qkjl901f4EU3; Fri, 16 Oct 2015 03:04:14 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-15v.sys.comcast.net with comcast id Vf4D1r00T3Ge9ey01f4E2H; Fri, 16 Oct 2015 03:04:14 +0000
To: mmusic@ietf.org
References: <56202075.3000202@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <5620692D.5030703@alum.mit.edu>
Date: Thu, 15 Oct 2015 23:04:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56202075.3000202@nostrum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1444964654; bh=/zJYhbPAV13iEN7C8uNEBbwCR4/iAFF3Gi70updtne0=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Xa44lqoG6ZrJVTjkxekWHlR+yto2D5ui50MGWRxKf1inbsANGlCsrk3Itw4TU0EEu wWqyaMTt/YNP5pbq7+wn6NPgatDnj6DW5Anz9zS1ai+3l+LOrqWcvVmkn9fQTcLQEu KB7gnJwPdEbILeZKGAFN5LqB5zITmluX723J/bsKFr51WTJ/B6Gy1eIpCySH5KnEp6 Docy8p9nVBDL5gfhR+rpFO7wYOBtL4GQyPVnMLV9apr1DsyQULqBCwwUiTXkEWtApB AzxCpXkr7gOwm3keHi282I4ZeLMLgCw3a7uOI9MH0fwRKnWVSAcoGbNduw4dgurwiB 9xM+PoqWRrDkA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Nzd1j9m_-_tvhz1RPZDcGLmjGT8>
Subject: Re: [MMUSIC] RID update (draft-pthatcher-mmusic-rid-01,> )
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 16 Oct 2015 03:04:16 -0000

* Section 7.1:

In:

  1. It MUST generate a 'rid-identifier' that is unique within a media
     description

IIUC, the rid-identifier must be unique within an RTP session, including 
all the media descriptions pertaining to that RTP session.

* Section 7.2.2, item 2:

Restating my earlier comment, why not simply check the PT against those 
listed in the m-line? There could be default PTs in use that have no 
rtpmap or fmtp. Those are only defined for audio, but there *could* be 
rid constraints applied to audio. (I think max-br would potentially be 
applicable. Or new ones might be defined that apply.) At least it seems 
harmless to define it this way.

* Section 7.4, item 4:

I think there should be a check that the PTs in the answer are a subset 
of those in the offer.

(And, while it can be inferred, it might be good to state somewhere that 
in cases where the answerer m-line PT values differ from those in the 
offer, the PTs in the answer rid use the offerer's PT values.)

* Section 10:

As somebody noted, it is confusing to have ";" separate multiple PT 
*values* within rid-fmt-list, and also to separate rid-params.

Possible solutions:
- use a different separator for fmt values
- use a different separator for params
- use a "pt=" for *each* fmt.

	Thanks,
	Paul