IETF Logo Mail Archive

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

"Olle E. Johansson" <oej@edvina.net> Thu, 01 November 2012 21:13 UTC

Return-Path: <oej@edvina.net>
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 E961A21F8DBA for <simple@ietfa.amsl.com>; Thu, 1 Nov 2012 14:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.318
X-Spam-Level:
X-Spam-Status: No, score=-2.318 tagged_above=-999 required=5 tests=[AWL=-0.018, 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 RcRkJ5mStm3A for <simple@ietfa.amsl.com>; Thu, 1 Nov 2012 14:13:09 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) by ietfa.amsl.com (Postfix) with ESMTP id D8FDB21F8D5C for <simple@ietf.org>; Thu, 1 Nov 2012 14:13:06 -0700 (PDT)
Received: from [192.168.40.19] (h87-96-134-129.dynamic.se.alltele.net [87.96.134.129]) by smtp7.webway.se (Postfix) with ESMTPA id CD6DD754A8A7; Thu, 1 Nov 2012 21:13:05 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <axjp925efdvel8fmpey6jc73.1351800528451@email.android.com>
Date: Thu, 01 Nov 2012 22:13:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0C42E85-1C67-435E-BCB8-F8F980DD9FE4@edvina.net>
References: <axjp925efdvel8fmpey6jc73.1351800528451@email.android.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1499)
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: Thu, 01 Nov 2012 21:13:10 -0000

1 nov 2012 kl. 21:08 skrev Hannes Tschofenig <hannes.tschofenig@gmx.net>:

> Murray was the liaison person to the OMA from the IETF side. Murray recently discontinued his participation in the OMA (due to a job change). We discussed the need to appoint a new liaison person in the IAB and came to the conclusion that no new appointment is necessary; the required need to interact with the OMA had decreased over time. 
> 
> Does anyone on this list believe that there is a need for cooperation with the OMA?

For me, it is too early to answer. I'm just trying to assemble information about how we ended up where we are with all these organizations working with SIMPLE, not contributing back and leaving the IETF with huge gaps and a set of specs that seems uncomplete and not focused on developers being able to produce running interoperable code. 

I have no insights in the politics at that time, so I have no insight into why OMA produced all these documents without trying to feed them back to the IETF.

My opinion on OMA cooperation is that if we can kick off work in this group to complete and/or correct IETF simple into an interoperable state for buddy lists and Xcap, and we see a need for using OMA documents within the IETF we can revisit your question and produce an answer. 

Any other opinions?

/O

v2.23.0 | Report a Bug | By Email