Re: [Sip] Presence architecture for fixed line network

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Fri, 18 April 2003 06:21 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 CAA03665 for <sip-archive@odin.ietf.org>; Fri, 18 Apr 2003 02:21:03 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3I6UU222024 for sip-archive@odin.ietf.org; Fri, 18 Apr 2003 02:30:30 -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 h3I6U3822004; Fri, 18 Apr 2003 02:30:03 -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 h3I6M2821564 for <sip@optimus.ietf.org>; Fri, 18 Apr 2003 02:22:02 -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 CAA02825 for <sip@ietf.org>; Fri, 18 Apr 2003 02:12:05 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196P8p-0005Af-00 for sip@ietf.org; Fri, 18 Apr 2003 02:14:31 -0400
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 196P8o-0005AE-00 for sip@ietf.org; Fri, 18 Apr 2003 02:14:30 -0400
Received: from dynamicsoft.com ([63.113.46.20]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h3I6EFBd019130; Fri, 18 Apr 2003 02:14:16 -0400 (EDT)
Message-ID: <3E9F97B2.4050707@dynamicsoft.com>
Date: Fri, 18 Apr 2003 02:14:10 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@lucent.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>
In-Reply-To: <3E9F0772.7070705@lucent.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

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?

-Jonathan R.

Vijay K. Gurbani wrote:
> Ashish Naik wrote:
> 
>> Can someone point me to an architecture documents of SIP based 
>> presence architecture in fixed line network ?
>>  
>> I want to know which network elements will be part of this as compared 
>> to presence server in 3G networks.
> 
> 
> Take a look at some of the work in the SPIRITS WG:
> 
> http://www.ietf.org/internet-drafts/draft-gurbani-spirits-implementation-00.txt 
> 
> http://www.ietf.org/internet-drafts/draft-ietf-spirits-protocol-04.txt
> 
> Regards,
> 
> - vijay

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Scientist                             Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
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