Re: [rtcweb] Use of offer / answer semantics

Bernard Aboba <bernard_aboba@hotmail.com> Thu, 08 September 2011 04:43 UTC

Return-Path: <bernard_aboba@hotmail.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 D461821F8BB1 for <rtcweb@ietfa.amsl.com>; Wed, 7 Sep 2011 21:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 8OQorlEIHDk0 for <rtcweb@ietfa.amsl.com>; Wed, 7 Sep 2011 21:43:37 -0700 (PDT)
Received: from blu0-omc1-s21.blu0.hotmail.com (blu0-omc1-s21.blu0.hotmail.com [65.55.116.32]) by ietfa.amsl.com (Postfix) with ESMTP id F131221F8BAE for <rtcweb@ietf.org>; Wed, 7 Sep 2011 21:43:36 -0700 (PDT)
Received: from BLU152-W50 ([65.55.116.9]) by blu0-omc1-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 7 Sep 2011 21:45:28 -0700
Message-ID: <BLU152-W507A8040FD123508451E51931E0@phx.gbl>
Content-Type: multipart/alternative; boundary="_1327175e-311a-44fd-b17e-6189dc38585e_"
X-Originating-IP: [70.88.131.169]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <harald@alvestrand.no>, <rtcweb@ietf.org>
Date: Wed, 7 Sep 2011 21:45:27 -0700
Importance: Normal
In-Reply-To: <4E6756C1.9060207@alvestrand.no>
References: <DB0C463A-FF5F-4C15-B2B4-E81B7DF92351@cisco.com>, <4E6756C1.9060207@alvestrand.no>
MIME-Version: 1.0
X-OriginalArrivalTime: 08 Sep 2011 04:45:28.0468 (UTC) FILETIME=[21D70D40:01CC6DE2]
Subject: Re: [rtcweb] Use of offer / answer semantics
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: Thu, 08 Sep 2011 04:43:37 -0000


> > 1) The media negotiations will be done using the same SDP offer/answer semantics that are used in SIP.
> To be precise - you're suggesting that we use RFC 3264 offer/answer 
> semantics. (That RFC is 25 pages long. RFC 3261, the core SIP document, 
> is 269 pages, and is NOT a normative reference from 3264. I am anxious 
> to avoid having a normative dependency on 3261.)
> 
> I agree with this.

[BA] I do *not* agree that RTCWEB should have to support every aspect of SDP offer/answer.   Basic offer/answer, sure.  All potential corner cases?  Not necessarily. 

> > 2) It will be possible to gateway between legacy SIP devices that support ICE and appropriate RTP / SDP mechanisms and codecs without using a media gateway. A signaling gateway to convert between the signaling on the web side to the SIP signaling may be needed.

> I agree with this - I think the "may be needed" will turn out to be 
> "will be needed", but some portion of that gateway can be implemented by 
> Javascript running in the browser, if desirable.

[BA] This seems like a good principle, but I'm not clear that it will work with all use cases.  For example, what happens in the E911 use cases when an RTCWEB implementation attempts to make a call to a PSAP implementing NENA i3 Stage 3?  If you don't have a media gateway, then the browser will need to implement one of the mandated codecs on the PSAP side.  So in those use cases, eliminating the media gateway implies making G.711 and H.264 mandatory-to-implement.  

> > 3) When a new codec is specified, and the SDP for the new codec is specified in the MMUSIC WG, no other standardization would should be required for it to be possible to use that in the web browsers. Adding a new codecs which might have new SDP parameters should not change the APIs between the browser and javascript application. As soon as the browsers support the new codec, old applications written before the codecs was specified should automatically be able to use the new codec where appropriate with no changes to the JS applications.
> I agree with this (modulo spelling and WG name fixups).

[BA] Agree with "no new standardization".  But that doesn't mean that applications will automatically "just work", right?  That's a much harder requirement.

> I decided that the fight against SDP was not worth fighting after 
> listening to the dozens of WGs doing SDP extensions for various 
> purposes, many of which might make sense to incorporate in a browser 
> platform, and concluding that SDP wouldn't hold still enough for us to 
> specify a gateway from/to it.

[BA] Agree that it's not worth fighting, but making it clear what we do and do not support will be a "fight" of sorts.  That is, unless you're willing to require that the browser be able to *everything* enabled by RFC 3264.  Personally, I don't think that is worthwhile.