Re: [Sip] Presence architecture for fixed line network

"Vijay K. Gurbani" <vkg@lucent.com> Fri, 18 April 2003 15:51 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17744 for <sip-archive@odin.ietf.org>; Fri, 18 Apr 2003 11:51:34 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3IG1EZ25305 for sip-archive@odin.ietf.org; Fri, 18 Apr 2003 12:01:14 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3IG0I825155; Fri, 18 Apr 2003 12:00:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3IFnD824523 for <sip@optimus.ietf.org>; Fri, 18 Apr 2003 11:49:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17417 for <sip@ietf.org>; Fri, 18 Apr 2003 11:39:03 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196XzW-0000Ei-00 for sip@ietf.org; Fri, 18 Apr 2003 11:41:30 -0400
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 196XzV-0000EZ-00 for sip@ietf.org; Fri, 18 Apr 2003 11:41:29 -0400
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39]) by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3IFfC214955; Fri, 18 Apr 2003 11:41:12 -0400 (EDT)
Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id KAA02684; Fri, 18 Apr 2003 10:41:12 -0500 (CDT)
Message-ID: <3EA01C33.1030008@lucent.com>
Date: Fri, 18 Apr 2003 10:39:31 -0500
From: "Vijay K. Gurbani" <vkg@lucent.com>
Organization: Lucent Technologies, Inc./Bell Laboratories
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Ashish Naik <ashishn@mahindrabt.com>, "Sip@Ietf. Org" <sip@ietf.org>
Subject: Re: [Sip] Presence architecture for fixed line network
References: <NFBBIJAAOFNEMIHBIFPIIEJDDHAA.ashishn@mahindrabt.com> <3E9F0772.7070705@lucent.com> <3E9F97B2.4050707@dynamicsoft.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Jonathan Rosenberg wrote:
> Vijay, I'm confused.
> 
> Last I checked, draft-ietf-simple-presence discussed presence, and to my 
> knowledge it wasnt specific to wireline or wireless, but to any network 
> that used IP. I am not sure what relation spirits has. I certainly hope 
> you are not proposing that spirits represents a presence protocol 
> specific for wireline?

Heavens, no.  The original poster wanted to know which network
elements may contribute to the derivation of presence information
for fixed-line networks; and that's where the tie-in to SPIRITS
comes in.

Rest assured, I am not proposing yet another presence protocol for
wireline networks.  In fact, if you skim over my implementation
I-D, I reuse the application/cpim+pidf MIME type and all the other
work in IMPP and SIMPLE WGs.

Regards,

- vijay
-- 
Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and Services
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216

_______________________________________________
Sip mailing list  https://www1.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