Re: [Sip] New I-D - TOTE - "INFO" on the media path

Hadriel Kaplan <HKaplan@acmepacket.com> Mon, 25 February 2008 15:13 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B409928C44D; Mon, 25 Feb 2008 07:13:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.388
X-Spam-Level:
X-Spam-Status: No, score=-0.388 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 1HoHQb2Bn37m; Mon, 25 Feb 2008 07:13:39 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E4BE28C341; Mon, 25 Feb 2008 07:13:35 -0800 (PST)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8ADB28C211 for <sip@core3.amsl.com>; Mon, 25 Feb 2008 07:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 ya1WIx2NP6tx for <sip@core3.amsl.com>; Mon, 25 Feb 2008 07:13:32 -0800 (PST)
Received: from etmail.acmepacket.com (host6.216.41.24.conversent.net [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 88BDD28C24C for <sip@ietf.org>; Mon, 25 Feb 2008 07:12:09 -0800 (PST)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.240.5; Mon, 25 Feb 2008 10:11:48 -0500
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Mon, 25 Feb 2008 10:11:49 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Chris Boulton <cboulton@avaya.com>, Dean Willis <dean.willis@softarmor.com>, Ted Hardie <hardie@qualcomm.com>
Date: Mon, 25 Feb 2008 10:11:48 -0500
Thread-Topic: [Sip] New I-D - TOTE - "INFO" on the media path
Thread-Index: Achz70OBX+stLb6OTUmvxIECQEdZxgDrLc3wAAkHf6A=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30BC7600393@mail.acmepacket.com>
References: <47B6345B.4030807@cisco.com><p06240601c3e0e71e3fef@[129.46.226.27]><8F90CB13-F83A-4D95-82E4-63794937E8A9@softarmor.com><p06240602c3e173da4d57@[24.4.239.115]> <AC12F0BB-E1BA-421A-B540-82DBC0CA2752@softarmor.com> <D8A411E49D63A648BFA87E44904FEDCF36306C@gbnewp0758m.eu.ubiquity.net>
In-Reply-To: <D8A411E49D63A648BFA87E44904FEDCF36306C@gbnewp0758m.eu.ubiquity.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: IETF SIP List <sip@ietf.org>
Subject: Re: [Sip] New I-D - TOTE - "INFO" on the media path
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Well, looking at draft-ietf-mediactrl-sip-control-framework-01.txt for the first time, I would say one reason is that the TOTE mechanism has a better chance of success in more environments.  At least across SBCs, if that matters to you. (it matters to me, obviously, but not everyone)

Also, TOTE is a lot lighter weight, although I'm sure after a few rounds of drafts with lots of people's inputs it will probably grow to be not far off. :)

-hadriel



> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Chris Boulton
> Sent: Monday, February 25, 2008 5:52 AM
> To: Dean Willis; Ted Hardie
> Cc: IETF SIP List
> Subject: Re: [Sip] New I-D - TOTE - "INFO" on the media path
>
> On Feb 20, 2008, at 12:28 AM, Ted Hardie wrote:
> >
> > .  If the idea is that the specification of
> > "pic"  or "name" is at the level of the specification of an event
> > package,
> > then we are dealing with something else entirely and the draft can
> > be re-written to express that.  But I would expect, in that case,
> > for each
> > of the registered purposes to be very carefully specified as to what
> > the
> > acting application would do with them.  And I suspect pretty much
> > everything like "name" would have to go.
>
> Ok, I think I agree with you here. Each "purpose" would need to be
> very clearly specified, at roughly the same level of detail as is
> required for an event package or would be required for an INFO package
> if we were to go that way. And yes, the draft is a bit short on this
> right now.
>
> [Chris Boulton] BUT then we are just recreating the Control Framework
> (http://www.ietf.org/internet-drafts/draft-ietf-mediactrl-sip-control-fr
> amework-01.txt) from the MediaCtrl work group - just called a different
> name.  I'm not sure why we can't just use that.
>
> Chris.
>
>
> --
> Dean
>
>
> _______________________________________________
> Sip mailing list  http://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
> _______________________________________________
> Sip mailing list  http://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  http://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip