OMA IETF MIF API Workshop - Room info

Hui Deng <denghui02@gmail.com> Mon, 26 March 2012 17:28 UTC

Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 512C221E80BC; Mon, 26 Mar 2012 10:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.381
X-Spam-Level:
X-Spam-Status: No, score=-103.381 tagged_above=-999 required=5 tests=[AWL=0.217, 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 H3zeu6uB39Xu; Mon, 26 Mar 2012 10:28:51 -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 E40DD21E80E5; Mon, 26 Mar 2012 10:28:50 -0700 (PDT)
Received: by yenm5 with SMTP id m5so4465469yen.31 for <multiple recipients>; Mon, 26 Mar 2012 10:28:50 -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:cc:content-type; bh=E/RzDaHuekNZWCc1VMUlQY/8x40p/ArRb4iArllNmIg=; b=Pp5LSlX2DP7rIwDrKzJx6/xdoWrR6XGneLrVVavgd1/WWDtucQpp7KgITFlERkMQBd Vsx0BGRcPcXOrEBE/J90mkcAt+gWBPJik+ubUAXTpMSEi1xOROO3WJkiJUkFuENRzvN+ 1KAwUQncqfvlVYxyp6kMvY6ojvd7fpX0mVkSFJmN2LZShoPbYEkn4bvF2nz3dSmuTV4a 4n3heGZDa8XSky7OBhu9WrNhCt/I3PfRa34H1/5T+HXBcf7rd7cQGA+FJYdAxYuVSdqN 2EwDaOjHexvLgN/1ZlpGrfeNLh0MikvnRyYCQxITTBFIA0HP98Gb29bnqHXnpL7GzdD/ xM8w==
MIME-Version: 1.0
Received: by 10.236.46.232 with SMTP id r68mr23062351yhb.80.1332782930398; Mon, 26 Mar 2012 10:28:50 -0700 (PDT)
Received: by 10.146.20.14 with HTTP; Mon, 26 Mar 2012 10:28:50 -0700 (PDT)
Date: Mon, 26 Mar 2012 19:28:50 +0200
Message-ID: <CANF0JMBijns_ks33Qfie55GUo2cQtENBkdjdRYmYjGAsVfxzAA@mail.gmail.com>
Subject: OMA IETF MIF API Workshop - Room info
From: Hui Deng <denghui02@gmail.com>
To: MIF Mailing List <mif@ietf.org>, Internet Area <int-area@ietf.org>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf303bfe24210f7f04bc28b539
Cc: thierry.berisot@telekom.de, jerry.shih@att.com, liliana.dinale@ericsson.com, Ralph Droms <rdroms@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 17:28:52 -0000

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.