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

Adam Roach <adam@dynamicsoft.com> Thu, 26 June 2003 01:56 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20089; Wed, 25 Jun 2003 21:56:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VLzc-0004GP-00; Wed, 25 Jun 2003 21:56:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VLzW-0004GM-00; Wed, 25 Jun 2003 21:56:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VLzU-0001Xe-Jo; Wed, 25 Jun 2003 21:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VLyk-0001Wq-T9 for simple@optimus.ietf.org; Wed, 25 Jun 2003 21:55:14 -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 VAA20008 for <simple@ietf.org>; Wed, 25 Jun 2003 21:55:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VLyh-0004Fa-00 for simple@ietf.org; Wed, 25 Jun 2003 21:55:11 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100]) by ietf-mx with esmtp (Exim 4.12) id 19VLyW-0004E5-00 for simple@ietf.org; Wed, 25 Jun 2003 21:55:00 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8]) by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h5Q1rvxk016751; Wed, 25 Jun 2003 21:53:58 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19) id <N4YYSX60>; Wed, 25 Jun 2003 20:53:58 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E861A4@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: 'Sean Olson' <seancolson@yahoo.com>, Adam Roach <adam@dynamicsoft.com>, simple@ietf.org
Subject: RE: [Simple] draft-roach-simple-blconf-00
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: Wed, 25 Jun 2003 20:53:57 -0500

Sean Olson writes:

> 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.

Hmm... perhaps I muddied my description. The intention
was not to imply that this would be *part* *of*
device configuration; simply that it would use
event packages in the same way. The intended solution
is more like user 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.

That's an interesting proposition. It still runs
afoul the two problems I cite in the draft: it
constrains you to a single list, and it requires
that list to be maintained by the same domain that
handles your presence.

> This has the implication that routing of these
> requests will generally follow the same path as
> subscribing to that user's presence.

Which is, IMHO, an unnecessary restriction.
I prefer a model that allows a la carte service
selection by users over one that requires some
sort of monolithic service provider.

/a

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