[MMUSIC] SDPCapNeg Issue #1: To Add, Delete and Replace Attributes

Flemming Andreasen <fandreas@cisco.com> Mon, 25 June 2007 17:13 UTC

Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2s7r-0004zm-H1; Mon, 25 Jun 2007 13:13:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2s7q-0004yL-HP for mmusic@ietf.org; Mon, 25 Jun 2007 13:13:18 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2s7p-0000ev-6e for mmusic@ietf.org; Mon, 25 Jun 2007 13:13:18 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 25 Jun 2007 10:13:16 -0700
X-IronPort-AV: i="4.16,460,1175497200"; d="scan'208"; a="4733007:sNHT20354766"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l5PHDGC0025797 for <mmusic@ietf.org>; Mon, 25 Jun 2007 10:13:16 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5PHD9n0028329 for <mmusic@ietf.org>; Mon, 25 Jun 2007 17:13:16 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Jun 2007 10:13:13 -0700
Received: from [10.21.112.189] ([10.21.112.189]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Jun 2007 10:13:13 -0700
Message-ID: <467FF7A8.6040303@cisco.com>
Date: Mon, 25 Jun 2007 13:13:12 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jun 2007 17:13:14.0086 (UTC) FILETIME=[1D551060:01C7B74C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1195; t=1182791596; x=1183655596; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fandreas@cisco.com; z=From:=20Flemming=20Andreasen=20<fandreas@cisco.com> |Subject:=20SDPCapNeg=20Issue=20#1=3A=20To=20Add, =20Delete=20and=20Replac e=20Attributes |Sender:=20; bh=RkWLNg6JmpKvYSOrKiHsx4+huY11uQKslNwgsjPrfKM=; b=LN97pkGu20c61m/A5FPJ6IW0Zet1vMPCgyhYLtO8by3oBd5qHHKy/mcRlLiff6nMix6w5OEz 7M38iIHLXjOi+PkODfSfE3UgFb9zRYmAX+3VtuJOFdv/pxyVHk4HjDkm;
Authentication-Results: sj-dkim-4; header.From=fandreas@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [MMUSIC] SDPCapNeg Issue #1: To Add, Delete and Replace Attributes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Probably the biggest open issue we have in the SDP Capability 
Negotiation Framework at this point is the ability to replace and delete 
attributes from an actual configuration SDP when generating a potential 
configuration. At the Prague IETF, people asked for some more 
motiviation and use cases for this feature before deciding whether we 
should include it in the core capability negotiation framework or not. I 
have written a short I-D in the subject, which you can find at:

    
http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdpcapneg-att-del-00.txt

Please take a look at this and let me know how you think we should 
resolve this issue. Options include:

A) Remove the ability to delete and replace attributes completely.
B) Remove the ability to delete and replace individual attributes, but 
allow for complete removal of all attributes (clean slate)
C) Keep the current ability to delete and remove individual and all 
attributes.

My personal preference is for option A, however in the interest of 
moving forward and making a reasonable compromise between functionality 
and complexity, my recommendation is option B.

Thanks

-- Flemming








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