
From rjsparks@nostrum.com  Wed Sep  2 07:18:07 2009
Return-Path: <rjsparks@nostrum.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA81328C84F; Wed,  2 Sep 2009 07:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQyUohAFi79l; Wed,  2 Sep 2009 07:18:06 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id C470728C810; Wed,  2 Sep 2009 07:18:05 -0700 (PDT)
Received: from [192.168.2.2] (pool-71-170-52-89.dllstx.fios.verizon.net [71.170.52.89]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n82EIHVf077973 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 Sep 2009 09:18:18 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-Id: <647F7FDD-633E-48F4-86F5-386FC6B1DC60@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: sipcore-chairs@tools.ietf.org, simple mailing list <simple@ietf.org>, rai@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 2 Sep 2009 09:18:17 -0500
X-Mailer: Apple Mail (2.936)
Received-SPF: pass (nostrum.com: 71.170.52.89 is authenticated by a trusted mechanism)
Subject: [Simple] SIPit25 registration closes in 2 days
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Sep 2009 14:18:07 -0000

Registration for SIPit 25 closes this Friday.

If you plan to attend and haven't registered, please do so now.

Information about the event and a link to the registration website can  
be found at http://www.sipit.net

RjS

From ben@estacado.net  Wed Sep  2 08:58:00 2009
Return-Path: <ben@estacado.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 228BD3A684D for <simple@core3.amsl.com>; Wed,  2 Sep 2009 08:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbwixUobEOvg for <simple@core3.amsl.com>; Wed,  2 Sep 2009 08:57:59 -0700 (PDT)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id 4FE6E3A67B0 for <simple@ietf.org>; Wed,  2 Sep 2009 08:56:40 -0700 (PDT)
Received: from dn3-213.estacado.net (dn3-213.estacado.net [172.16.3.213]) (authenticated bits=0) by estacado.net (8.14.2/8.14.2) with ESMTP id n82FuqoI012921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <simple@ietf.org>; Wed, 2 Sep 2009 10:56:52 -0500 (CDT) (envelope-from ben@estacado.net)
From: Ben Campbell <ben@estacado.net>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Date: Wed, 2 Sep 2009 10:56:47 -0500
References: <20090831222303.30DD928C3D1@core3.amsl.com>
To: Simple WG <simple@ietf.org>
Message-Id: <533E7C3E-A105-4745-8D38-11369903B9FC@estacado.net>
Mime-Version: 1.0 (Apple Message framework v1075.2)
X-Mailer: Apple Mail (2.1075.2)
Subject: [Simple] Fwd: Nomcom 2009-10: Reminder Call for Nominations, Local Office  hours, Nominee Questionnaires available
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Sep 2009 15:58:00 -0000

Please note the 18 September deadline for nominations. The NOMCOM will  
appreciate all the nominations it can get :-)

Thanks!

Ben.

Begin forwarded message:

> From: Mary Barnes <mary.barnes@nortel.com>
> Date: August 31, 2009 5:23:03 PM CDT
> To: IETF Announcement list <ietf-announce@ietf.org>
> Cc: ietf@ietf.org
> Subject: Nomcom 2009-10: Reminder Call for Nominations, Local Office  
> hours, Nominee Questionnaires available
>
> Hi all,
>
> This email covers 3 topics:
> 1) Reminder: Call for Nominations
> 2) New: Local Office Hours
> 3) New: Questionnaires available for nominees
>
> Best Regards,
> Mary Barnes
> nomcom-chair@ietf.org
> mary.h.barnes@gmail.com
> mary.barnes@nortel.com
>
>
> = 
> = 
> = 
> = 
> = 
> = 
> = 
> = 
> = 
> ======================================================================
> 1) Call for Nominations
> ------------------------
> The nomination period ends in less than 3 weeks on Sept. 18th, 2009.  
> We
> appreciate the folks that have taken the time to make nominations thus
> far. But, we do need more nominations. Please use the online tool to
> nominate - it's easy and secure:
> https://wiki.tools.ietf.org/group/nomcom/09/nominate
>
> Details on the open positions, as well as other details and options  
> for
> making nominations are available on the Nomcom homepage:
> https://wiki.tools.ietf.org/group/nomcom/09/
>
> Please consider that the sooner you make the nominations, the more  
> time
> your nominee(s) will have to complete the necessary questionnaire  
> (item 3
> below).  As well, please consider nominating more than one person  
> for a
> particular position. You will have the opportunity to provide  
> additional
> feedback later and it's important to consider that not all nominees  
> will
> be able to accept the nomination.
>
>
> 2) Local office hours
> -----------------------
>
> In order to facilitate additional feedback, the Nomcom is planning to
> make themselves available for office areas at various geographic  
> locations
> for 3 weeks in September, starting on the 8th.
>
> Below please find the list of locations where Nomcom members will be
> available for these f2f meetings . Unless dates are identified  
> below, the
> Nomcom member is generally available for part of the day during the  
> weeks
> of Sept 8-11, Sept 14-18 and Sept 21-25. Also, languages other than
> English in which the Nomcom member is fluent are identfied.
>
> Please contact a Nomcom member in a specific geographic location to
> arrange a convenient meeting time and place. Most Nomcom members are
> flexible as to meeting locations - i.e., we can travel to your office,
> meet at our offices or somewhere in between.
>
> As a reminder folks can always contact any Nomcom member to provide
> feedback at anytime - i.e., you don't need to participate in these f2f
> sessions to provide feedback.
>
>
> Belgium:
>     Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be  
> (Sept
> 21-25) (Languages: French)
>
> Boston, Mass, USA:
>     Stephen Kent - kent@bbn.com  (Sept 16-18)
>
> Boulder, CO, USA:
>     Wassim Haddad - wmhaddad@gmail.com (Sept 14-18)
>
> Dallas/Ft. Worth, TX, USA:
>     Mary Barnes  - mary.h.barnes@gmail.com
>     Lucy Yong - lucyyong@huawei.com  (Languages: Chinese)
>
> Helsinki, Finland:
>      Simo Veikkolainen - simo.veikkolainen@nokia.com (Languages:  
> Finnish)
>
>
> Ithaca, NY, USA:
>      Scott Brim - scott.brim@gmail.com
>
> Montevideo, Uruguay:
>      Roque Gagliano - roque@lacnic.net (Sept 14-18, 21-25) (Languages:
> Spanish, Portuguese)
>
> Montreal, Quebec, Canada
>     Wassim Haddad - wmhaddad@gmail.com (Sept 8-11)
>     -- Can also be available in Ottawa if folks are interested
>
> Paris, France:
>      Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
> (Sept 15-18)  (Languages: French)
>
> San Diego, CA, USA:
>      Randall Gellens - rg+ietf@qualcomm.com
>      Dave Crocker - dcrocker@bbiw.net  (Sept 16-18)
>
> Silicon Valley/SF Bay,  CA, USA:
>      Dave Crocker - dcrocker@bbiw.net  (Sept 8-11, Sept 14-15, Sept
> 21-25)
>      Dorothy Gellert - Dorothy.gellert@gmail.com
>
> 3) Questionnaires available for nominees:
>
> For folks that have been notified that they have been nominated for  
> any
> of the positions, the questionnaires are now available on the Nomcom09
> tools website:
> https://wiki.tools.ietf.org/group/nomcom/09/iab-questionnaire
> https://wiki.tools.ietf.org/group/nomcom/09/iaoc-questionnaire
> https://wiki.tools.ietf.org/group/nomcom/09/iesg-questionnaire
>
> If you have any questions, please let me know. I will be contacting
> everyone individually, as well as sending reminders before the  
> deadline.
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From ben@nostrum.com  Tue Sep 22 15:44:10 2009
Return-Path: <ben@nostrum.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28E873A68C3 for <simple@core3.amsl.com>; Tue, 22 Sep 2009 15:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lAwWGtJ5fSgq for <simple@core3.amsl.com>; Tue, 22 Sep 2009 15:44:08 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 940253A69A8 for <simple@ietf.org>; Tue, 22 Sep 2009 15:43:51 -0700 (PDT)
Received: from [10.0.1.193] (adsl-68-94-23-215.dsl.rcsntx.swbell.net [68.94.23.215]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n8MMirA6033240 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 22 Sep 2009 17:44:53 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
From: Ben Campbell <ben@nostrum.com>
Date: Tue, 22 Sep 2009 17:44:50 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <9AE9EE67-5AF4-4D66-A983-050509C7B9F0@nostrum.com>
References: <2DEAEEA0-F262-4522-8507-968F0D6EC385@nostrum.com>
To: Simple WG <simple@ietf.org>
X-Mailer: Apple Mail (2.1076)
Received-SPF: pass (nostrum.com: 68.94.23.215 is authenticated by a trusted mechanism)
Subject: [Simple] Repeat WGLC: draft-ietf-simple-intradomain-federation-04
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Sep 2009 22:44:10 -0000

This is a _repeat_ WGLC for comments on http://tools.ietf.org/html/draft-ietf-simple-intradomain-federation-04 
. We did not get sufficient comments the first time around. Please  
send your comments to the editor and the list by 5 October, 2009.

Even if your comment is "The draft is okay", that's helpful.

Thanks,

Ben.

Begin forwarded message:

> From: Ben Campbell <ben@nostrum.com>
> Date: August 18, 2009 3:13:03 PM CDT
> To: Simple WG <simple@ietf.org>
> Subject: [Simple] WGLC: draft-ietf-simple-intradomain-federation-04
>
> Folks -
>
> This is a Working Group Last Call for comments on
> http://tools.ietf.org/html/draft-ietf-simple-intradomain-federation-04
>
> The editor believes this draft is ready to last call, and we did not  
> have objections to doing so in the Stockholm meeting.
>
> Please have your comments to the editor and list by 2 September, 2009.
>
> Thanks,
>
> Ben.
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


From ag@ag-projects.com  Mon Sep 28 13:07:53 2009
Return-Path: <ag@ag-projects.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C42D03A6781 for <simple@core3.amsl.com>; Mon, 28 Sep 2009 13:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.924
X-Spam-Level: 
X-Spam-Status: No, score=-0.924 tagged_above=-999 required=5 tests=[AWL=-0.184, BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxrxKPmy0OFg for <simple@core3.amsl.com>; Mon, 28 Sep 2009 13:07:53 -0700 (PDT)
Received: from node05.dns-hosting.info (node05.dns-hosting.info [85.17.186.5]) by core3.amsl.com (Postfix) with ESMTP id CE0B53A63EC for <simple@ietf.org>; Mon, 28 Sep 2009 13:07:52 -0700 (PDT)
Received: from mit.xs4all.nl ([80.101.96.20] helo=[192.168.1.124]) by node05.dns-hosting.info with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <ag@ag-projects.com>) id 1MsMNL-0003Qd-IJ for simple@ietf.org; Mon, 28 Sep 2009 21:59:13 +0200
Message-Id: <7F183F19-4A72-47A5-BBE9-E5637F59BF67@ag-projects.com>
From: Adrian Georgescu <ag@ag-projects.com>
To: simple@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 28 Sep 2009 22:09:01 +0200
X-Mailer: Apple Mail (2.936)
X-SA-Exim-Connect-IP: 80.101.96.20
X-SA-Exim-Mail-From: ag@ag-projects.com
X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000)
X-SA-Exim-Scanned: Yes (on node05.dns-hosting.info)
Subject: [Simple] Soon you can Blink!
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Sep 2009 20:07:53 -0000

http://wiki.icanblink.com/

Blink implements RTP audio sessions (VoIP), session based Instant  
Messaging (IM), File Transfer and multi-party chat sessions using MSRP  
protocol and its relay extension, desktop sharing using VNC protocol,  
publication and subscription for rich presence information such as  
availability, moods, activities and geo-location, management for the  
presence rules, resource lists, RLS services documents using XCAP  
protocol.

You can receive a notification when the software become available or  
participate to our early adopter program by registering on the mailing  
list:

http://lists.ag-projects.com/mailman/listinfo/blink

The software implements most of the SIP SIMPLE working group items and  
will have an open source license.

--
Adrian

From ibc@aliax.net  Tue Sep 29 02:37:39 2009
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF2BA28C128 for <simple@core3.amsl.com>; Tue, 29 Sep 2009 02:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Af6W1OUi1nfZ for <simple@core3.amsl.com>; Tue, 29 Sep 2009 02:37:38 -0700 (PDT)
Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by core3.amsl.com (Postfix) with ESMTP id 487993A6A8A for <simple@ietf.org>; Tue, 29 Sep 2009 02:37:38 -0700 (PDT)
Received: by fxm27 with SMTP id 27so2485193fxm.42 for <simple@ietf.org>; Tue, 29 Sep 2009 02:38:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.102.130 with SMTP id g2mr1095876fao.52.1254217133774; Tue,  29 Sep 2009 02:38:53 -0700 (PDT)
In-Reply-To: <7F183F19-4A72-47A5-BBE9-E5637F59BF67@ag-projects.com>
References: <7F183F19-4A72-47A5-BBE9-E5637F59BF67@ag-projects.com>
Date: Tue, 29 Sep 2009 11:38:53 +0200
Message-ID: <cc1f582e0909290238y5fdd1822s123e3d175277d7ad@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Adrian Georgescu <ag@ag-projects.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: simple@ietf.org
Subject: Re: [Simple] Soon you can Blink!
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Sep 2009 09:37:39 -0000

2009/9/28 Adrian Georgescu <ag@ag-projects.com>:
> http://wiki.icanblink.com/
>
> Blink implements RTP audio sessions (VoIP), session based Instant Messagi=
ng
> (IM), File Transfer and multi-party chat sessions using MSRP protocol and
> its relay extension, desktop sharing using VNC protocol, publication and
> subscription for rich presence information such as availability, moods,
> activities and geo-location, management for the presence rules, resource
> lists, RLS services documents using XCAP protocol.
>
> You can receive a notification when the software become available or
> participate to our early adopter program by registering on the mailing li=
st:
>
> http://lists.ag-projects.com/mailman/listinfo/blink
>
> The software implements most of the SIP SIMPLE working group items and wi=
ll
> have an open source license.


Let me a question. After studying all the SIMPLE and XCAP stuff (and
implement part of it), I get a simple conclusion: XCAP and SIMPLE
specifications *don't* exist.

With it I mean that SIMPLE and XCAP (as specified by IETF) don't
provide a fixed and strict set of rules and specifications and it's
*impossible* to get interoperability. Some examples:

- RFC 5025 (pres rules) doesn't specify which is the default action to
perform is a watcher URI is not listed in the document.

- RFC 5025 doesn't clarify which should be the presence server
behavior if the same watcher URI appears in a rule with "allow" action
and also in a rule with "blocked" action. Which one has preference?
the first one? the second one?

- Again with RFC 5025: The pres-rules format is *really* wide and
ambiguous. There are 10000 ways to create a pres-rules document with
same meaning. It's *impossible* that two implementations could share
the same document. This is: vendor A softphone generates a valid
pres-rules document and uploads to the XCAP server. Vendor B softphone
(same SIP account) gets that document and, of course, it doesn't
understand it since it would use a completely different pres-rules
document format to get the same meaning.
I've realized that AG-Projects software implementing XCAP uses a
***custom*** pres-rules format based on 3 rules with id
"pres_whitelist" (action "allow"), "pres_blacklist" (action "block")
and "pres_politeblocked" (action "politeblock"). Can I ask *why*? just
because CounterPath softphones use a similar pres-rules format? This
is just a vendor specific format, no more. IETF doesn't specify it at
all so interoperability is not possible.

- In a presentity there can be a "note" element in various places:
  - Inside the "tuple" section.
  - Inside the "person" section.
  - As a main element in the "presentity" element.
This is annoying and I've seen some implementations setting *all*
these "notes" with same text. But the fact is that nobody can know
which element will other implementation choose to show to the user.

- Resource list stuff: If a user adds a resource list in a pres-rules
rule the the presence server inspecting the pres-rules should also
read the resource-list. What about if the user modifies the
resource-list via XCAP? Then the XCAP server should notify a change to
the presence server in order it to inspect again the pres-rules. Does
IETF RFC's specify it? not at all.


So, what we have? nothing. We have a hyper-complex and ambiguous set
of specifications which don't provide interoperability at all. When I
read "this softphones implements XCAP" I understand "this softphone
implements XCAP so it works ONLY with same vendor's softphones, XCAP
server and presence server". Is this what we want?

OMA's XDM specification is a specification layer on top of XCAP/SIMPLE
documents which tries to create a fixed and strict subset of IETF
specifications in order to make it feasible for clients adoption. For
example it defines a very strict format for the pres-rules document.
It also defines the XCAP server behavior (XDMS server).

I really think that this should be a task of IETF rather than OMA. I
cannot understand why IETF has published such useless and half-done
documents, can I ask *why*?? sharing a simple budy list or privacy
rules is IMPOSSIBLE with IETF's specifications!!!. Anyhow this is what
we have.

Which should be the way to go? perhaps implement OMA's XDM specs?
(I've read XDM documents and they are designed to be SIP core agnostic
(valid for IMS or any kind of SIP core).


Sorry for this mail, but this subject is really depressing for me.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Tue Sep 29 03:27:29 2009
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 606E73A683F for <simple@core3.amsl.com>; Tue, 29 Sep 2009 03:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNRqnsctG-my for <simple@core3.amsl.com>; Tue, 29 Sep 2009 03:27:28 -0700 (PDT)
Received: from mail-bw0-f210.google.com (mail-bw0-f210.google.com [209.85.218.210]) by core3.amsl.com (Postfix) with ESMTP id 6EDBB3A6800 for <simple@ietf.org>; Tue, 29 Sep 2009 03:27:28 -0700 (PDT)
Received: by bwz6 with SMTP id 6so1879597bwz.37 for <simple@ietf.org>; Tue, 29 Sep 2009 03:28:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.54.15 with SMTP id o15mr1136413fag.96.1254220124362; Tue,  29 Sep 2009 03:28:44 -0700 (PDT)
In-Reply-To: <cc1f582e0909290238y5fdd1822s123e3d175277d7ad@mail.gmail.com>
References: <7F183F19-4A72-47A5-BBE9-E5637F59BF67@ag-projects.com> <cc1f582e0909290238y5fdd1822s123e3d175277d7ad@mail.gmail.com>
Date: Tue, 29 Sep 2009 12:28:44 +0200
Message-ID: <cc1f582e0909290328l4e8f94ddx6b9c475fa875419e@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Adrian Georgescu <ag@ag-projects.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: simple@ietf.org
Subject: Re: [Simple] Soon you can Blink!
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Sep 2009 10:27:29 -0000

2009/9/29 I=C3=B1aki Baz Castillo <ibc@aliax.net>:
> So, what we have? nothing. We have a hyper-complex and ambiguous set
> of specifications which don't provide interoperability at all. When I
> read "this softphones implements XCAP" I understand "this softphone
> implements XCAP so it works ONLY with same vendor's softphones, XCAP
> server and presence server". Is this what we want?
>
> OMA's XDM specification is a specification layer on top of XCAP/SIMPLE
> documents which tries to create a fixed and strict subset of IETF
> specifications in order to make it feasible for clients adoption. For
> example it defines a very strict format for the pres-rules document.
> It also defines the XCAP server behavior (XDMS server).
>
> I really think that this should be a task of IETF rather than OMA. I
> cannot understand why IETF has published such useless and half-done
> documents, can I ask *why*?? sharing a simple budy list or privacy
> rules is IMPOSSIBLE with IETF's specifications!!!. Anyhow this is what
> we have.
>
> Which should be the way to go? perhaps implement OMA's XDM specs?
> (I've read XDM documents and they are designed to be SIP core agnostic
> (valid for IMS or any kind of SIP core).
>
>
> Sorry for this mail, but this subject is really depressing for me.


Of course, I really appreciate the effort AG-Projects is doing in SIP
presence stuff, really amazing!

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>
