Re: [Simple] SIMPLE and OMA and 3Gpp and RCS and… (new subject)

Saúl Ibarra Corretgé <saul@ag-projects.com> Fri, 02 November 2012 12:00 UTC

Return-Path: <saul@ag-projects.com>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0789521F9970 for <simple@ietfa.amsl.com>; Fri, 2 Nov 2012 05:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.417
X-Spam-Level:
X-Spam-Status: No, score=-1.417 tagged_above=-999 required=5 tests=[AWL=0.271, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q0YF0Odnwxeo for <simple@ietfa.amsl.com>; Fri, 2 Nov 2012 05:00:43 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7CE21F996F for <simple@ietf.org>; Fri, 2 Nov 2012 05:00:43 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id E658CB35DA; Fri, 2 Nov 2012 13:00:41 +0100 (CET)
Received: from imac.saghul.lan (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id 30855B00F7; Fri, 2 Nov 2012 13:00:41 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="iso-8859-1"
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <CALiegfmBNCTxcK0ZVdWXToDsYLWgtp9vyprt6Yj0_C=81yFWQQ@mail.gmail.com>
Date: Fri, 02 Nov 2012 13:00:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BB9B7CC-7866-4406-BE3B-20A266D34E53@ag-projects.com>
References: <axjp925efdvel8fmpey6jc73.1351800528451@email.android.com> <E0C42E85-1C67-435E-BCB8-F8F980DD9FE4@edvina.net> <2C9DA935-CBBD-4DCF-A2A4-FF0139FB62B2@ag-projects.com> <CALiegfmBNCTxcK0ZVdWXToDsYLWgtp9vyprt6Yj0_C=81yFWQQ@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.1085)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "simple@ietf.org" <simple@ietf.org>
Subject: Re: [Simple] SIMPLE and OMA and 3Gpp and RCS and… (new subject)
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 12:00:44 -0000

On Nov 2, 2012, at 11:46 AM, Iñaki Baz Castillo wrote:

> 2012/11/2 Saúl Ibarra Corretgé <saul@ag-projects.com>:
>> - Having a oma pres-rules document which just points to a resource-lists document means that we can no longer get the policy for a watcher by just looking at pre-rules. This makes me think that we need a single document to store a buddy-list, which also contains the  policy for each buddy.
> 
> SO what I say and repeat 1000 times: authorization MUST be an
> *attribute* of each buddy. Period. Drop "users lists" named
> "allowed-buddies" / "blocked-buddies", that's not the way to go.
> 

And when did I say otherwise? :-O

> buddylist:
> --------------------
> sip:alice@example.com {
>  presence-subscribe-to: true,
>  presence-allowed: true,
>  presence-blocked: false
> }
> 
> sip:bob@example.com {
>  presence-subscribed-to: true,
>  presence-allowed: true,
>  presence-blocked: true
> }
> --------------------
> 
> And that's all. This is easy to render for the watcher and easy to
> process for the server. Single "document" with buddies and their
> attributes.
> 
> No need for "external references to other XCAP documents in any other
> server in the world", no need for generating a coredump if the same
> buddy is contained in "oma_my_buddies" list and "my_blocked_contacts"
> list and "oma_PoC_contacts" list and "oma_featured_buddies" list.
> 

This is what we did in our addressbook implementation, while maintaining compatibility to the highest possible degree.

--
Saúl Ibarra Corretgé
AG Projects