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

Dean Willis <dean.willis@softarmor.com> Wed, 20 February 2008 18:31 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 301423A6ADF; Wed, 20 Feb 2008 10:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.617
X-Spam-Level:
X-Spam-Status: No, score=-0.617 tagged_above=-999 required=5 tests=[AWL=-0.180, 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 qcf+vOQaCasd; Wed, 20 Feb 2008 10:31:02 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1256928C1CD; Wed, 20 Feb 2008 10:31:02 -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 84B023A68C9 for <sip@core3.amsl.com>; Wed, 20 Feb 2008 10:31:00 -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 fQ1P2EQnQs4g for <sip@core3.amsl.com>; Wed, 20 Feb 2008 10:30:59 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 9B8403A69A2 for <sip@ietf.org>; Wed, 20 Feb 2008 10:30:59 -0800 (PST)
Received: from [192.168.2.100] (cpe-76-185-142-113.tx.res.rr.com [76.185.142.113]) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id m1KIUsq4017408 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 20 Feb 2008 12:30:55 -0600
Message-Id: <AC12F0BB-E1BA-421A-B540-82DBC0CA2752@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Ted Hardie <hardie@qualcomm.com>
In-Reply-To: <p06240602c3e173da4d57@[24.4.239.115]>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 20 Feb 2008 12:30:48 -0600
References: <47B6345B.4030807@cisco.com> <p06240601c3e0e71e3fef@[129.46.226.27]> <8F90CB13-F83A-4D95-82E4-63794937E8A9@softarmor.com> <p06240602c3e173da4d57@[24.4.239.115]>
X-Mailer: Apple Mail (2.919.2)
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

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.

--
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