IETF Logo Mail Archive

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

"Roy, Radhika R CIV (US)" <radhika.r.roy.civ@mail.mil> Fri, 02 November 2012 14:41 UTC

Return-Path: <radhika.r.roy.civ@mail.mil>
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 5813D21F87B4 for <simple@ietfa.amsl.com>; Fri, 2 Nov 2012 07:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.927
X-Spam-Level:
X-Spam-Status: No, score=-1.927 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, 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 d6lcO5QDfk6b for <simple@ietfa.amsl.com>; Fri, 2 Nov 2012 07:41:21 -0700 (PDT)
Received: from edge-cols.mail.mil (edge-cols.mail.mil [131.64.100.9]) by ietfa.amsl.com (Postfix) with ESMTP id 741BA21F8AAC for <simple@ietf.org>; Fri, 2 Nov 2012 07:41:21 -0700 (PDT)
Received: from UCOLHP3M.easf.csd.disa.mil (131.64.100.152) by ucolhp2w.easf.csd.disa.mil (131.64.100.9) with Microsoft SMTP Server (TLS) id 14.2.309.2; Fri, 2 Nov 2012 14:41:01 +0000
Received: from UCOLHP9H.easf.csd.disa.mil ([169.254.5.171]) by UCOLHP3M.easf.csd.disa.mil ([131.64.100.152]) with mapi id 14.02.0309.003; Fri, 2 Nov 2012 14:41:00 +0000
From: "Roy, Radhika R CIV (US)" <radhika.r.roy.civ@mail.mil>
To: Ben Campbell <ben@nostrum.com>, Iñaki Baz Castillo <ibc@aliax.net>
Thread-Topic: [Simple] SIMPLE and OMA and 3Gpp and RCS and… (new subject)
Thread-Index: AQHNuQU/vgk3FIIRWEuLGSQng3VFCZfWmkPA
Date: Fri, 02 Nov 2012 14:40:58 +0000
Message-ID: <8486C8728176924BAF5BDB2F7D7EEDDF486515F0@ucolhp9h.easf.csd.disa.mil>
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> <4BB9B7CC-7866-4406-BE3B-20A266D34E53@ag-projects.com> <CALiegfmmbOtw6TLfMd5AS2iQLr1maxKi+8tjnaoDa9OQB8SxaQ@mail.gmail.com> <F07738BF-C267-43B6-BC5D-F129C95718AD@ag-projects.com> <CALiegfkpeRhQW=tJpy3A8q0-KG8dWs=in9WFmOnkBYEi7DyZ_Q@mail.gmail.com> <52C2C109-CFBD-4577-AF63-E36F82F6A809@nostrum.com>
In-Reply-To: <52C2C109-CFBD-4577-AF63-E36F82F6A809@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [131.64.62.4]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_000E_01CDB8E6.851ECEB0"
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 02 Nov 2012 07:42:47 -0700
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 14:41:22 -0000

Folks:

Like Ben, I also believe that to start from the scratch is a non-starter as
people do not know yet what the "magic model" exists to have the golden
opportunity of interworking. 

No one is sure how all these interoperability problems will be solved as
people are adding a lot intelligence based on requirements what they feel
need to be added in IM and Presence.

It indicates one fundamental thing: These applications are popular and will
be used now and in the future not only as a stand-alone application, but
integration with audio, and video including emergency calls.

So, it would be prudent for all of us who have gained real in-depth
understanding after working in building specs, developing, and implementing
SIMPLE and XMPP to guide the entire commercial industry to adopt a kind of
standard-based IM and Presence model.

Let us be prepared that all of these will be a kind of learn, adopt, modify,
and create at time goes on in supporting and building the popular
application protocols like IM and Presence.

BR/Radhika


-----Original Message-----
From: simple-bounces@ietf.org [mailto:simple-bounces@ietf.org] On Behalf Of
Ben Campbell
Sent: Friday, November 02, 2012 10:20 AM
To: Iñaki Baz Castillo
Cc: Bernard Aboba; DRAGE, Keith (Keith); simple@ietf.org
Subject: Re: [Simple] SIMPLE and OMA and 3Gpp and RCS and… (new subject)

(as individual)

On Nov 2, 2012, at 7:27 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

>> I'd love to see a better model endorsed by SIMPLE and then happily
implement it. I think we do share this goal :-)
> 
> Sure we agree here. The key is: reusing SIMPLE/XCAP specs? or making
> something better from scratch (after learning from current SIMPLE/XMPP
> specs)?

Do you really believe nothing is salvageable? For example, would you
jettison all of the below?

-- Using SIP in the first place
-- SIP Events
-- RLS
-- SIP Message
-- MSRP
-- XCAP
-- etc

>From the discussions so far, it sounds like most of the complaints are in
the area of reusing user lists between clients (e.g. contact lists, presence
rules, etc). Do people really hate the entire SIMPLE suite, or is it just an
XCAP issue.

If the scope of the work is "start over from scratch", then it seems like we
would be better served starting with XMPP. I'd be very surprised if we could
get support for creating "yet another presence and IM protocol".

We've been there before and it wasn't pretty.





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

v2.23.0 | Report a Bug | By Email