IETF Logo Mail Archive

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

Dale.Worley@comcast.net Wed, 20 February 2008 21:44 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 C34D528C9BA; Wed, 20 Feb 2008 13:44:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.713
X-Spam-Level:
X-Spam-Status: No, score=-0.713 tagged_above=-999 required=5 tests=[AWL=-0.276, 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 Pfb7Z6FjNyFF; Wed, 20 Feb 2008 13:44:33 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B17F028C8FB; Wed, 20 Feb 2008 13:44:33 -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 43EA928C8CA for <sip@core3.amsl.com>; Wed, 20 Feb 2008 13:44: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 gXaFvStto6pi for <sip@core3.amsl.com>; Wed, 20 Feb 2008 13:44:22 -0800 (PST)
Received: from QMTA10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by core3.amsl.com (Postfix) with ESMTP id 98BE328C473 for <sip@ietf.org>; Wed, 20 Feb 2008 13:44:22 -0800 (PST)
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by QMTA10.emeryville.ca.mail.comcast.net with comcast id rojZ1Y0070x6nqcAA0WH00; Wed, 20 Feb 2008 21:43:33 +0000
Received: from dragon.ariadne.com ([24.34.79.42]) by OMTA12.emeryville.ca.mail.comcast.net with comcast id rxk51Y00F0umElk8Y00000; Wed, 20 Feb 2008 21:44:08 +0000
X-Authority-Analysis: v=1.0 c=1 a=oLHs5Kn5MywA:10 a=iv0-ODH01Rv8_8RZ9PUA:9 a=D-4XSc3ErUP9SlJfE3FaUIdkaFkA:4 a=mnQxEUBslVAA:10 a=8y7tGHue6YMA:10
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id m1KLi5Mj024165 for <sip@ietf.org>; Wed, 20 Feb 2008 16:44:05 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id m1KLi5WJ024161; Wed, 20 Feb 2008 16:44:05 -0500
Date: Wed, 20 Feb 2008 16:44:05 -0500
Message-Id: <200802202144.m1KLi5WJ024161@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <AC12F0BB-E1BA-421A-B540-82DBC0CA2752@softarmor.com> (dean.willis@softarmor.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>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Dean Willis <dean.willis@softarmor.com>

   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.

IMHO the purposes need to be specified in *more* detail than an event
package.  The reason is that an event package is "pull" information,
the meaning of the information is defined by the event-name, but the
requestor is presumed to know *why* it wants the information, that is,
what it intends to do based on that information.  A TOTE object, like
an INFO, is "push" information, and the attached meta-data must
specify not only what the information means, but how the recipient is
expected to act on it.

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

v2.23.0 | Report a Bug | By Email