[mif] OMA IETF MIF API Workshop

Hui Deng <denghui02@gmail.com> Thu, 22 March 2012 01:49 UTC

Return-Path: <denghui02@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359B821E8015; Wed, 21 Mar 2012 18:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.37
X-Spam-Level:
X-Spam-Status: No, score=-103.37 tagged_above=-999 required=5 tests=[AWL=0.228, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 LeuIIPQTwqCg; Wed, 21 Mar 2012 18:49:53 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACBC21E800C; Wed, 21 Mar 2012 18:49:53 -0700 (PDT)
Received: by yenm5 with SMTP id m5so1618625yen.31 for <multiple recipients>; Wed, 21 Mar 2012 18:49:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=j5dWFsWs95m5VbEDQPgAQLeC7hO7tS6sD+ItVuJ8w8c=; b=pTRphpzZk8lS55R1Ur6dn+CQKFpClkKzYKAx3NZA1n+q9iaErblLsfpVTAu5+G8U77 fE7Lq7kPs+EnwbXwcD1Pfi/e8C3smgepYuUbzhRD1r9Z5/hcxMuRvWCX4+iWGtVdV9vm x2i2DP3yTIKU5CHeG59QmiScDeKnUz2WXJb90ITlXHRdGXK+tmctg3EdSMblzj+y/trn j9G+YnXVYyVwECvJStHcrRyF7ecnoLZMyDw2uK74OvHzCwS9RZCGpR76+LFUuDJ5EDYy rAeabZPuoy63lVEM7/fFmLzYR3VdPnSPLQsE+FUS+T+XrvQEQZqBC0SXRSh7Zepeebqx IZUg==
MIME-Version: 1.0
Received: by 10.101.128.14 with SMTP id f14mr1886430ann.21.1332380992977; Wed, 21 Mar 2012 18:49:52 -0700 (PDT)
Received: by 10.147.112.1 with HTTP; Wed, 21 Mar 2012 18:49:52 -0700 (PDT)
Date: Thu, 22 Mar 2012 09:49:52 +0800
Message-ID: <CANF0JMCw1DZCc1dHoEYidYrKA19skLXYZz69iHyWNuG=NQWjtg@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: MIF Mailing List <mif@ietf.org>, IETF Discussion <ietf@ietf.org>, Internet Area <int-area@ietf.org>
Content-Type: multipart/alternative; boundary="001636c597a3cabbcb04bbcb1f26"
Subject: [mif] OMA IETF MIF API Workshop
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 01:49:54 -0000

OMA IETF MIF API Workshop

Time: Tuesday: 18:10-20:00
Location: TBD

1) Program
1.1) OMA OpenCMAPI activity (Thierry)
1.2) IETF MIF API Design (Ted Lemon)
1.3) IETF API related work (TBD)
1.4) OMA API Program (OMA Member)
1.5) Vendor's today implementation (Maybe)
1.6) Next step between IETF and OMA (Thierry 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.