IETF Logo Mail Archive

Re: [MEDIACTRL] New MRB document (-04)

Chris Boulton <chris@ns-technologies.com> Wed, 31 March 2010 08:14 UTC

Return-Path: <chris@ns-technologies.com>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4B433A67A7 for <mediactrl@core3.amsl.com>; Wed, 31 Mar 2010 01:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.391
X-Spam-Level:
X-Spam-Status: No, score=0.391 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fey5DVE0qi-g for <mediactrl@core3.amsl.com>; Wed, 31 Mar 2010 01:14:02 -0700 (PDT)
Received: from host.qbytedns.net (host.qbytedns.net [89.16.176.173]) by core3.amsl.com (Postfix) with ESMTP id 351A73A6784 for <mediactrl@ietf.org>; Wed, 31 Mar 2010 01:13:55 -0700 (PDT)
Received: from [62.239.63.126] (port=44138 helo=[192.168.102.26]) by host.qbytedns.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <chris@ns-technologies.com>) id 1Nwt4B-0005rq-FM for mediactrl@ietf.org; Wed, 31 Mar 2010 09:14:23 +0100
Message-ID: <4BB3045A.6030406@ns-technologies.com>
Date: Wed, 31 Mar 2010 09:14:18 +0100
From: Chris Boulton <chris@ns-technologies.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: mediactrl@ietf.org
References: <L042FF$134FE4783B95D232F07EEC807A863331@aruba.it>
In-Reply-To: <L042FF$134FE4783B95D232F07EEC807A863331@aruba.it>
Content-Type: multipart/alternative; boundary="------------000205070400090403020101"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.qbytedns.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ns-technologies.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [MEDIACTRL] New MRB document (-04)
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2010 08:14:03 -0000

> 2) Required/Support header in SIP
>
> Ben also pointed out that a proper piece of information, an option tag, may be needed in the Required/Supported headers for the Consumer-over-SIP case to address the use of multipart/mixed payloads in IAMM. A proper name for the option tag, considering the use case, might be just 'iamm'. Is it acceptable to specify such information in this document (and if so, is there any guideline that should be followed), or is it something that falls instead under the responsibility of other WGs, e.g., SIPCORE?
>
>    
[Chris] We had similar issues earlier in the MediaCtrl process that got 
a bit messy when we started adding stuff to MediaCtrl documents and have 
taken a wide berth since.  I think we will upset a few people by having 
it defined in the MRB doc - do the chairs agree in the new world of 
SIPCORE and DISPATCH?  I suspect to complete we do need an option tag - 
and I suspect it needs to be submitted to SIPCORE?  Eric/Spencer - thoughts?

Chris.

-- 
Chris Boulton
CTO & Co-founder
NS-Technologies <http://www.ns-technologies.com>
m: +44.7876.476681

v2.23.0 | Report a Bug | By Email