[OAUTH-WG] FW: OMA IETF MIF API Workshop - Room info

Hannes Tschofenig <hannes.tschofenig@nsn.com> Tue, 27 March 2012 12:08 UTC

Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFC621E814E for <oauth@ietfa.amsl.com>; Tue, 27 Mar 2012 05:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.747
X-Spam-Level:
X-Spam-Status: No, score=-105.747 tagged_above=-999 required=5 tests=[AWL=-0.545, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a1YPeEuY5UIZ for <oauth@ietfa.amsl.com>; Tue, 27 Mar 2012 05:08:04 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 3A8AD21E8188 for <oauth@ietf.org>; Tue, 27 Mar 2012 05:08:02 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q2RC81GE002949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <oauth@ietf.org>; Tue, 27 Mar 2012 14:08:02 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2RC80R4011390 for <oauth@ietf.org>; Tue, 27 Mar 2012 14:08:01 +0200
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 27 Mar 2012 14:07:39 +0200
Received: from 10.144.248.121 ([10.144.248.121]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server webmail.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Tue, 27 Mar 2012 12:07:39 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Tue, 27 Mar 2012 15:06:49 +0200
From: Hannes Tschofenig <hannes.tschofenig@nsn.com>
To: oauth@ietf.org
Message-ID: <CB978809.9B10%hannes.tschofenig@nsn.com>
Thread-Topic: OMA IETF MIF API Workshop - Room info
Thread-Index: Ac0MEhZ/eyKYBMsjtk66B1SapHAJAQ==
In-Reply-To: <CANF0JMBijns_ks33Qfie55GUo2cQtENBkdjdRYmYjGAsVfxzAA@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3415705661_18058355"
X-OriginalArrivalTime: 27 Mar 2012 12:07:39.0404 (UTC) FILETIME=[348A5CC0:01CD0C12]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 5366
X-purgate-ID: 151667::1332850082-00003570-A934A744/0-0/0-0
Subject: [OAUTH-WG] FW: OMA IETF MIF API Workshop - Room info
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2012 12:08:06 -0000

FYI: I mentioned to some of you that there is another OAuth related event
during this week. 

------ Forwarded Message
From: Hui Deng <denghui02@gmail.com>
Date: Mon, 26 Mar 2012 19:28:50 +0200
To: MIF Mailing List <mif@ietf.org>, Internet Area <int-area@ietf.org>, IETF
Discussion <ietf@ietf.org>
Cc: <thierry.berisot@telekom.de>, <jerry.shih@att.com>,
<liliana.dinale@ericsson.com>, Ralph Droms <rdroms@cisco.com>
Subject: OMA IETF MIF API Workshop - Room info

OMA IETF MIF API Workshop
 
Time: Tuesday: 18:10-20:00
Location: room 212/213
 
1) Program
1.1) OMA OpenCMAPI activity (Thierry Berisot, OMA)
1.2) IETF MIF API Design (Ted Lemon, IETF)
1.3) IETF API related consideration (TBD)
1.4) OMA API Program (Liliana Dinale, OMA)
1.5) Vendor's today implementation (Maybe)
1.6) Next step between IETF and OMA (Thierry, Margaret, and Hui)
 
2) Purpose
2.1) From IETF, this workshop would help to explain the API related topic,
and clarify what is recommended and not recommended to do and standardized,
if possible, either publish a information document or adding word into the
current MIF api draft about how to use those MIF API for Internet developer.
and some current practices information how today smart terminal is doing.
 
2.2) From OMA perspective, to socialize OMA¹s published specifications and
current ongoing standards activities in the area of APIs. To make sure that
the standards landscape for APIs is coordinated and harmonized. To solicit
feedback about OMA¹s specification for Authorization4APIs, which is built
on IETF OAuth as well as OpenCMAPI.
 
3) Outcomes:
3.1) Future work about how to use those MIF API in an IETF information
 document or inside current MIF API documentfor Internet developers.

3.2) Outcomes OMA: Improved understanding of each others¹ activities,
 and a coordinated approach going forward

3.3) Better mutual understanding of the work of both organizations,
 and how to cooperate in the future.


------ End of Forwarded Message