[Simple] draft-roach-simple-blconf-00

Sean Olson <seancolson@yahoo.com> Wed, 25 June 2003 15:45 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17349; Wed, 25 Jun 2003 11:45:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VCSS-0005oN-8P; Wed, 25 Jun 2003 11:45:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VBzQ-0007wP-3L for simple@optimus.ietf.org; Wed, 25 Jun 2003 11:15:16 -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 VAA02369 for <simple@ietf.org>; Tue, 24 Jun 2003 21:47:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UzNK-0001NT-00 for simple@ietf.org; Tue, 24 Jun 2003 21:47:06 -0400
Received: from web41502.mail.yahoo.com ([66.218.93.85]) by ietf-mx with smtp (Exim 4.12) id 19UzNA-0001Mv-00 for simple@ietf.org; Tue, 24 Jun 2003 21:46:56 -0400
Message-ID: <20030625014545.28000.qmail@web41502.mail.yahoo.com>
Received: from [207.46.228.31] by web41502.mail.yahoo.com via HTTP; Tue, 24 Jun 2003 18:45:45 PDT
From: Sean Olson <seancolson@yahoo.com>
To: adam@dynamicsoft.com, simple@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Simple] draft-roach-simple-blconf-00
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, 24 Jun 2003 18:45:45 -0700

This is a problem that should be solved.

I don't like the -buddies option

I don't like requiring support for device
configuration to get this to work, especially since
that will usually be a separate operation from buddy
list configuration.

I think there is a third option that should be
considered. Use the user's URI as the buddy list
URI and indicate through a Event: parameter that the
buddy list is the intended target and not the user.
This has the implication that routing of these
requests will generally follow the same path as
subscribing to that user's presence.

SUBSCRIBE sip:adam@pres.example.com SIP/2.0
To: <sip:adam@pres.example.com>
From: <sip:adam@example.com>;tag=ie4hbb8t
Call-ID: cdB34qLToC@terminal.example.com
CSeq: 322723822 SUBSCRIBE
Contact: <sip:terminal.example.com>
Event: presence ; contactlist
Expires: 7200
Require: eventlist
Accept: application/cpim-pidf+xml
Accept: application/rlmi+xml
Accept: multipart/related
Accept: multipart/signed
Accept: multipart/encrypted

my two cents
Sean

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple