RE: [Simple] SIP and HTTP for presence publication

"Peterson, Jon" <jon.peterson@neustar.biz> Tue, 04 March 2003 21:00 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 QAA10264 for <simple-archive@odin.ietf.org>; Tue, 4 Mar 2003 16:00:29 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h24LB7n14200 for simple-archive@odin.ietf.org; Tue, 4 Mar 2003 16:11:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24LB7514197 for <simple-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 16:11:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10233 for <simple-web-archive@ietf.org>; Tue, 4 Mar 2003 15:59:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24LB4514189; Tue, 4 Mar 2003 16:11:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24LAo514164 for <simple@optimus.ietf.org>; Tue, 4 Mar 2003 16:10:50 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10228 for <simple@ietf.org>; Tue, 4 Mar 2003 15:59:41 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11]) by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h24L1gC08025; Tue, 4 Mar 2003 21:01:43 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19) id <ZH2JRH8F>; Tue, 4 Mar 2003 16:01:46 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EAF@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: 'Neil Deason' <ndeason@ubiquity.net>, simple@ietf.org
Subject: RE: [Simple] SIP and HTTP for presence publication
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: simple-admin@ietf.org
Errors-To: simple-admin@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/simple/>
Date: Tue, 04 Mar 2003 16:01:45 -0500

Well, I'm really loath to re-open this discussion... we've already moved
pretty far down one path, and it isn't clear that any other has genuine
advantages over our current direction.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Neil Deason [mailto:ndeason@ubiquity.net]
> Sent: Monday, March 03, 2003 9:37 AM
> To: simple@ietf.org
> Subject: [Simple] SIP and HTTP for presence publication
> 
> 
> draft-ietf-simple-publish-reqs-00 discusses the use of either HTTP or
> SIP for presence state publication as if they have to be mutually
> exclusive.
> 
> As the draft points out HTTP provides a much better data transfer
> mechanism than SIP. SIP has application layer routing 
> richness that HTTP
> does not. So why not use SIP to initiate/modify/terminate a presence
> state data transfer session that uses HTTP?
> 
> Cheers,
> Neil.
> 
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www1.ietf.org/mailman/listinfo/simple
> 
_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple