Re: [rtcweb] Agenda request: Overall Approach to defining SDP usage in WebRTC

Justin Uberti <juberti@google.com> Fri, 12 October 2012 05:42 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 5805221F84C9 for <rtcweb@ietfa.amsl.com>; Thu, 11 Oct 2012 22:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OM7TRbNFOTId for <rtcweb@ietfa.amsl.com>; Thu, 11 Oct 2012 22:42:32 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7A27A21F8484 for <rtcweb@ietf.org>; Thu, 11 Oct 2012 22:42:32 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id s14so2298885qcg.31 for <rtcweb@ietf.org>; Thu, 11 Oct 2012 22:42:31 -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=nEp2yYMD6/pEF4Vni8pfSTF+ctQyQGK/0byS9eB39J8=; b=RAl+Srnh8nu2uM5tdbBVJvDTz0PcIt5cX6GxGZpKjfn51siKDhpYTBOazZWwuR8bKe ycFndBxZpHqq17InpbTz6hHI6Qfhb1c2ks9mNRW/GE9r6qL2U+mtEXyHGh5e2ccn8PqN VSnNWYgTvgGXgi9JdFojLhWoR1HKHh17GekieBS/y9YEqiRqj45UHs1uojKbTwTBKgLf HrjquGS9XHnViwZkvvLI4gG+xEZ2Pi1KwJHIn7PsOkm0CvXAkUmGxDO4B1kcc8WVaOCK MbIWRFBrVbdhehSgE2CWqgeo2QruLTdL0C9w/ggUgyMfKX5UBtwawEUsgkfKUEiQO1YF ZfhA==
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=nEp2yYMD6/pEF4Vni8pfSTF+ctQyQGK/0byS9eB39J8=; b=kqOPmKNhgyZ9SPzv+8McMvpo5whiYwyhjv45R0RI895G2GuaIOCnvTAGr9aOF5Z15g axeoNdV9FD0mCzGCazQkxiexDZSwGVbSyUJ10FWvnam1G9HvXN0g2KnejyR4xRa7uXDC QshAsGBzsMLv8h9BqIsPWyFmHrV9xLHysCMjjOrRWU4GdKwqFY/GDw+3EAOYd1l22gTC RJ+oScVl/YUi/2nFcL/yYsZ5QXtsS9ydkmTpHQvSLUYAosUuklCeur4M9RcCDSw2dTA4 oJei/8Y9LlvfvyuNEMD70dBqD2da9z5Dh+2i/Z+Gzbd9k/aC6Ho0CGdUMOfWKYmzT/Wg D1Mg==
Received: by 10.229.209.167 with SMTP id gg39mr1433524qcb.154.1350020551619; Thu, 11 Oct 2012 22:42:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.216.194 with HTTP; Thu, 11 Oct 2012 22:42:11 -0700 (PDT)
In-Reply-To: <BLU169-DS31FC5595F5CB38B9F089E7938D0@phx.gbl>
References: <BLU169-DS31FC5595F5CB38B9F089E7938D0@phx.gbl>
From: Justin Uberti <juberti@google.com>
Date: Thu, 11 Oct 2012 22:42:11 -0700
Message-ID: <CAOJ7v-150RM-CuiEYsVwn_NRCS67tnBu2H4k-CgPdvDF6sDGyQ@mail.gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: multipart/alternative; boundary=0016e6d260886b35d104cbd627a3
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQnpEfevDc2Sd1VgtQ/ZbiSoqzy6nCp7rHqt0Rb8HSF1qydaAlyUwwFZo6uSqcoqS6jUpJUwc9556B+2vEui6JDI9v/d82/cGYf+0+aj0okOfrGBg0grRod+CoPzee3vgTRFM+LWRpwyMHCW12N/k4D9U/odAt2cvFyT1RHrXL1eUqw9oMbXVaD8KTID4TOW5UoenOmc
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Agenda request: Overall Approach to defining SDP usage in WebRTC
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, 12 Oct 2012 05:42:33 -0000

I am planning to address some of what you mention in the JSEP -02, and also
have some slides on this for the JSEP discussion.


On Thu, Oct 11, 2012 at 11:58 AM, Bernard Aboba
<bernard_aboba@hotmail.com>wrote;wrote:

> In addition to covering "fascinating" topics such as MTI codecs and JSEP
> support of O/A at IETF 85, I'd like to suggest that we also set some time
> aside at IETF 85 to discuss the overall approach to defining SDP usage in
> WebRTC.  ****
>
> ** **
>
> In this "big picture" discussion, I'd like to try to figure out how we
> will answer some of the following questions:****
>
> ** **
>
>    1. What SDP functionality MUST/SHOULD/MAY be implemented/used in
>    WebRTC API implementations?****
>    2. What is the overall model for SDP usage in JSEP?****
>    3. How much of this discussion belongs in W3C, how much in IETF? ****
>
> ** **
>
> The goal of this discussion is **not** to get into the details of the
> answer to the questions, but rather to focus on what work needs to be
> done,  what form it takes (adding material in existing docs, new docs,
> etc.), and what is handled in what org (W3C, IETF, etc.).****
>
> ** **
>
> To some extent, answers to question #1 are derivable from the RTP usage
> draft, but I'm not clear that it makes sense to cover all aspects of SDP
> usage there.  Also, it would be useful to discuss the plan for documenting
> SDP in current usage that has no corresponding RFC or I-D (e.g. are all the
> bases covered?). ****
>
> ** **
>
> In question #2, I would include questions such as the role of the
> constraints API (versus hacking SDP), what SDP lines/fields can or cannot
> be edited by applications and how SDP errors are handled. ****
>
> ** **
>
> While it would certainly be possible to write a -00 draft, without
> understanding the overall plan, getting into detail probably doesn't make
> much sense.  IMHO, slides should be sufficient, and I have some available
> to stimulate discussion. ****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>