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

Justin Uberti <juberti@google.com> Mon, 30 July 2012 17:22 UTC

Return-Path: <juberti@google.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 65EE711E8141 for <rtcweb@ietfa.amsl.com>; Mon, 30 Jul 2012 10:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.691
X-Spam-Level:
X-Spam-Status: No, score=-102.691 tagged_above=-999 required=5 tests=[AWL=0.285, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 FKmEXyNp9-en for <rtcweb@ietfa.amsl.com>; Mon, 30 Jul 2012 10:22:26 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 753CD11E8143 for <rtcweb@ietf.org>; Mon, 30 Jul 2012 10:22:26 -0700 (PDT)
Received: by qadz3 with SMTP id z3so1116544qad.10 for <rtcweb@ietf.org>; Mon, 30 Jul 2012 10:22:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=LDbVUknKytyB1Zsxg48SI1NbK8RHFTBA/oT5ZDPiLrk=; b=ANeG/jjcInxTDIYC/OI1i3fkqjsGluIfV0mogzymLJm4uJQqasqzkR0yoXfHTJk7j2 FSZcAF+GYLAFtyaLzXJswio7KR7HZo4sHLP619DUlDYTwKT5te1OGH+0WHJWHFIXu6KT 5VIry/UNGJaWN0qKLxaaX35C04wOrTfSLD80YdfxI9+yug5D8WeR72QndFd7vq8o4x26 87N91bIbnaz+BrgBv1O+Wr+qmjyID9dOsisKIy9bcOqtkok6qKI1C/kK0S6yTnAdg8ZY ju4wsZXbpZ6sOabb7WRZo0Uzps8CFL5LJSauU3utLvbDiLMbYrNZBpsYB9FBmAWdwjaA Dn+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=LDbVUknKytyB1Zsxg48SI1NbK8RHFTBA/oT5ZDPiLrk=; b=XTsnk7kSmq3Aa75EoWp+TV17hu5YtO2MHav1gJb5No2zSkuzNykHKSB39dRteXwKbW r9TJGg2d2q4ez6J7mc8zUy1QqbX7WEESoEyznJqbLN/6gMs0y/j2uo5KxGI6AohYa2e1 Pqxz8vOz4lQZ0QSly6yC7yyOKI9A1SUY3XrYaWWIwCs5CTQC6rVz4/cXuj4vM23DQM0L 7mvy/bchbKzO4t3yszUikKPK2sKmZCksulrb5Xs3/NY/S1ys+nYGPX2MGP4FenzNlEy0 t5PrPKyAZBYFdM39wpW7XsJR3L+iibKdW88R/1dEAYdSEVMvnmwsgERlzH89Zwsre1fY Yv/g==
Received: by 10.224.186.20 with SMTP id cq20mr24408877qab.32.1343668945988; Mon, 30 Jul 2012 10:22:25 -0700 (PDT)
Received: by 10.224.186.20 with SMTP id cq20mr24408856qab.32.1343668945839; Mon, 30 Jul 2012 10:22:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.59.66 with HTTP; Mon, 30 Jul 2012 10:22:05 -0700 (PDT)
In-Reply-To: <34966E97BE8AD64EAE9D3D6E4DEE36F207BD4A03@szxeml525-mbx.china.huawei.com>
References: <34966E97BE8AD64EAE9D3D6E4DEE36F207BD4A03@szxeml525-mbx.china.huawei.com>
From: Justin Uberti <juberti@google.com>
Date: Mon, 30 Jul 2012 10:22:05 -0700
Message-ID: <CAOJ7v-2YLY-5vzMLoAcbtskz_DVoFzOpQgod7QTtfXcGA-a7eQ@mail.gmail.com>
To: Likepeng <likepeng@huawei.com>
Content-Type: multipart/alternative; boundary="485b397dcddd36667504c60f4ee4"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQlQyauqMob0BhviP51s5PFXdvNTc2HcXLx7iF8HavnzJztUp82eoB86isVBewFEbqKIHbD00HMMdzNTF31XAWE53BvKzWhg2fx7QObLhDzfsHdMcdROObwUstBED4o0YS3JFKL9aSBfwl9oTYE9jVcBBdoRdKG6+WtIrGkUCY8RpLh16ow=
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: Mon, 30 Jul 2012 17:22:27 -0000

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> 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]
> 发送时间: 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
> https://www.ietf.org/mailman/listinfo/rtcweb
>