Re: [rtcweb] Fw: New Version Notification for draft-li-rtcweb-jsep-xmpp-mapping-00.txt

Likepeng <likepeng@huawei.com> Fri, 03 August 2012 08:44 UTC

Return-Path: <likepeng@huawei.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C756321F8D77 for <rtcweb@ietfa.amsl.com>; Fri, 3 Aug 2012 01:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 lhURcL6zsUbO for <rtcweb@ietfa.amsl.com>; Fri, 3 Aug 2012 01:44:08 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id B5D1821F8D7E for <rtcweb@ietf.org>; Fri, 3 Aug 2012 01:44:07 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIM18679; Fri, 03 Aug 2012 00:44:07 -0800 (PST)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 3 Aug 2012 01:41:06 -0700
Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 3 Aug 2012 01:41:12 -0700
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.5]) by szxeml422-hub.china.huawei.com ([10.82.67.161]) with mapi id 14.01.0323.003; Fri, 3 Aug 2012 16:41:05 +0800
From: Likepeng <likepeng@huawei.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: [rtcweb] Fw: New Version Notification for draft-li-rtcweb-jsep-xmpp-mapping-00.txt
Thread-Index: AQHNbiTIl1A6XHCWTUGcMhcvyZeTZ5dBi+BwgAABaICABjysIA==
Date: Fri, 3 Aug 2012 08:41:05 +0000
Message-ID: <34966E97BE8AD64EAE9D3D6E4DEE36F207BD5E41@szxeml525-mbx.china.huawei.com>
References: <34966E97BE8AD64EAE9D3D6E4DEE36F207BD4A03@szxeml525-mbx.china.huawei.com> <CAOJ7v-2YLY-5vzMLoAcbtskz_DVoFzOpQgod7QTtfXcGA-a7eQ@mail.gmail.com>
In-Reply-To: <CAOJ7v-2YLY-5vzMLoAcbtskz_DVoFzOpQgod7QTtfXcGA-a7eQ@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.110.124]
Content-Type: multipart/alternative; boundary="_000_34966E97BE8AD64EAE9D3D6E4DEE36F207BD5E41szxeml525mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Fw: New Version Notification for draft-li-rtcweb-jsep-xmpp-mapping-00.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 08:44:08 -0000

>I didn't see a section where it explains how to map the Jingle messages to the JSEP API, or the payloads of these messages to SDP (as required by the API).

I revise the draft according to the suggestion:
http://www.ietf.org/internet-drafts/draft-li-rtcweb-jsep-xmpp-mapping-01.txt

I would appreciate your further comments and feedbacks.

Thanks,

Kind Regards
Kepeng

发件人: Justin Uberti [mailto:juberti@google.com]
发送时间: 2012年7月31日 1:22
收件人: Likepeng
抄送: rtcweb@ietf.org
主题: Re: [rtcweb] Fw: New Version Notification for draft-li-rtcweb-jsep-xmpp-mapping-00.txt

Likepeng,

This draft shows how JS clients could use the Jingle protocol to establish a session, but I didn't see a section where it explains how to map the Jingle messages to the JSEP API, or the payloads of these messages to SDP (as required by the API).

I think this could be easily added - for example, a received session-initiate will map to a setRemoteDescription - but in order for a developer to implement an Jingle client in JS, these mappings need to be clearly defined.

On Mon, Jul 30, 2012 at 2:20 AM, Likepeng <likepeng@huawei.com<mailto:likepeng@huawei.com>> wrote:
Welcome your comments to this draft.

Have a nice meeting in Vancouver!

Kind Regards
Kepeng
-----邮件原件-----
发件人: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>]
发送时间: 2012年7月30日 15:27
收件人: Likepeng
抄送: Likepeng
主题: New Version Notification for draft-li-rtcweb-jsep-xmpp-mapping-00.txt

A new version of I-D, draft-li-rtcweb-jsep-xmpp-mapping-00.txt
has been successfully submitted by Kepeng and posted to the
IETF repository.

Filename:        draft-li-rtcweb-jsep-xmpp-mapping
Revision:        00
Title:           RTCWeb JSEP XMPP/Jingle Mapping
Creation date:   2012-07-30
WG ID:           Individual Submission
Number of pages: 10
URL:             http://www.ietf.org/internet-drafts/draft-li-rtcweb-jsep-xmpp-mapping-00.txt
Status:          http://datatracker.ietf.org/doc/draft-li-rtcweb-jsep-xmpp-mapping
Htmlized:        http://tools.ietf.org/html/draft-li-rtcweb-jsep-xmpp-mapping-00

Abstract:
   This document proposes mapping message representations between RTCWeb
   Javascript Session Establishment Protocol(JSEP) scheme and XMPP/
   Jingle [XEP-0166] messaging scheme.  Such a signaling mapping is
   intended to enable Javascript to use XMPP/Jingle to establish a
   session between two RTCWeb enabled browsers.

The IETF Secretariat
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb