Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt

Harald Alvestrand <harald@alvestrand.no> Thu, 05 September 2013 14:17 UTC

Return-Path: <harald@alvestrand.no>
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 972D311E81A4 for <rtcweb@ietfa.amsl.com>; Thu, 5 Sep 2013 07:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level:
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 nds9XVPwZCZt for <rtcweb@ietfa.amsl.com>; Thu, 5 Sep 2013 07:17:51 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB1621F9D8B for <rtcweb@ietf.org>; Thu, 5 Sep 2013 07:17:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id E927939E194 for <rtcweb@ietf.org>; Thu, 5 Sep 2013 16:17:47 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-4pj9Ogx+K4 for <rtcweb@ietf.org>; Thu, 5 Sep 2013 16:17:46 +0200 (CEST)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:7646:a0ff:fe90:e2bb]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 083F739E128 for <rtcweb@ietf.org>; Thu, 5 Sep 2013 16:17:45 +0200 (CEST)
Message-ID: <52289289.7040608@alvestrand.no>
Date: Thu, 05 Sep 2013 16:17:45 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20130802162957.17108.79281.idtracker@ietfa.amsl.com> <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se> <3879D71E758A7E4AA99A35DD8D41D3D91D5260A2@xmb-rcd-x14.cisco.com> <56C2F665D49E0341B9DF5938005ACDF80E8A65@DEMUMBX005.nsn-intra.net> <BBE9739C2C302046BD34B42713A1E2A22DF88232@ESESSMB105.ericsson.se> <CAGgHUiSK-bZrdXtxf-An8NM+pw-iqoWCrsG_bRUpxcD2DOCQrQ@mail.gmail.com>
In-Reply-To: <CAGgHUiSK-bZrdXtxf-An8NM+pw-iqoWCrsG_bRUpxcD2DOCQrQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040106030501040602060902"
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.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: Thu, 05 Sep 2013 14:17:55 -0000

On 09/05/2013 04:06 PM, Leon Geyser wrote:
> It would be nice if a word like mandated/mandatory is present in the 
> new text like it was in the old text. Maybe REQUIRED in uppercase?

REQUIRED is an RFC 2119 reserved word, and means the same thing as MUST.
I would strenously object to REQUIRED.

RECOMMENDED is also an RFC 2119 reserved word, and means the same thing 
as SHOULD.
I have misgivings about giving such a strongly worded recommendation, 
but I can live with it.


>
>
> On 5 September 2013 15:05, Bo Burman <bo.burman@ericsson.com 
> <mailto:bo.burman@ericsson.com>> wrote:
>
>     I also support it.
>     /Bo
>
>     > -----Original Message-----
>     > From: Rauschenbach, Uwe (NSN - DE/Munich)
>     [mailto:uwe.rauschenbach@nsn.com <mailto:uwe.rauschenbach@nsn.com>]
>     > Sent: den 5 september 2013 12:14
>     > To: ext Mo Zanaty (mzanaty); Bo Burman; rtcweb@ietf.org
>     <mailto:rtcweb@ietf.org>
>     > Subject: RE: I-D Action: draft-ietf-rtcweb-audio-02.txt
>     >
>     > I support this proposal.
>     >
>     > Kind regards,
>     > Uwe
>     >
>     >
>     > > -----Original Message-----
>     > > From: rtcweb-bounces@ietf.org <mailto:rtcweb-bounces@ietf.org>
>     [mailto:rtcweb-bounces@ietf.org <mailto:rtcweb-bounces@ietf.org>] On
>     > > Behalf Of ext Mo Zanaty (mzanaty)
>     > > Sent: Wednesday, September 04, 2013 10:03 PM
>     > > To: Bo Burman; rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     > > Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
>     > >
>     > > I support the proposed text addition. But rather than adding
>     at the
>     > > end of section 3, replace the beginning of section 3 as below.
>     > >
>     > > OLD:
>     > >    To ensure a baseline level of interoperability between WebRTC
>     > >    clients, a minimum set of required codecs are specified below.
>     > >    While this section specifies the codecs that will be
>     mandated for
>     > > all
>     > >    WebRTC client implementations, it leaves the question of
>     supporting
>     > >    additional codecs to the will of the implementer.
>     > >
>     > > NEW:
>     > >    To ensure a baseline level of interoperability between WebRTC
>     > >    clients, a minimum set of required codecs are specified below.
>     > >    If other suitable audio codecs are available to the browser
>     to use,
>     > >    it is RECOMMENDED that they are also included in the offer
>     in order
>     > >    to maximize the possibility to establish the session
>     without the
>     > > need
>     > >    for audio transcoding.
>     > >
>     > > Mo
>     > >
>     > > -----Original Message-----
>     > > From: rtcweb-bounces@ietf.org <mailto:rtcweb-bounces@ietf.org>
>     [mailto:rtcweb-bounces@ietf.org <mailto:rtcweb-bounces@ietf.org>] On
>     > > Behalf Of Bo Burman
>     > > Sent: Tuesday, August 27, 2013 10:53 AM
>     > > To: rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     > > Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
>     > >
>     > > Based on the previous discussion thread http://www.ietf.org/mail-
>     > > archive/web/rtcweb/current/msg08501.html, I believe there is
>     support
>     > > to add some text into this document.
>     > >
>     > > I thus propose to add the following text at the end of section 3:
>     > >
>     > > If other suitable audio codecs are available to the browser to
>     use, it
>     > > is RECOMMENDED that they are also included in the offer in
>     order to
>     > > maximize the possibility to establish the session without the
>     need for
>     > > audio transcoding
>     > >
>     > > Cheers,
>     > > Bo
>     > >
>     > > > -----Original Message-----
>     > > > From: i-d-announce-bounces@ietf.org
>     <mailto:i-d-announce-bounces@ietf.org> [mailto:i-d-announce-
>     <mailto:i-d-announce->
>     > > bounces@ietf.org <mailto:bounces@ietf.org>] On Behalf Of
>     internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>     > > > Sent: den 2 augusti 2013 18:30
>     > > > To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
>     > > > Cc: rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     > > > Subject: I-D Action: draft-ietf-rtcweb-audio-02.txt
>     > > >
>     > > >
>     > > > A New Internet-Draft is available from the on-line
>     Internet-Drafts
>     > > directories.
>     > > >  This draft is a work item of the Real-Time Communication in
>     WEB-
>     > > browsers Working Group of the IETF.
>     > > >
>     > > >   Title           : WebRTC Audio Codec and Processing
>     Requirements
>     > > >   Author(s)       : Jean-Marc Valin
>     > > >                           Cary Bran
>     > > >   Filename        : draft-ietf-rtcweb-audio-02.txt
>     > > >   Pages           : 6
>     > > >   Date            : 2013-08-02
>     > > >
>     > > > Abstract:
>     > > >    This document outlines the audio codec and processing
>     requirements
>     > > >    for WebRTC client application and endpoint devices.
>     > > >
>     > > >
>     > > > The IETF datatracker status page for this draft is:
>     > > > https://datatracker.ietf.org/doc/draft-ietf-rtcweb-audio
>     > > >
>     > > > There's also a htmlized version available at:
>     > > > http://tools.ietf.org/html/draft-ietf-rtcweb-audio-02
>     > > >
>     > > > A diff from the previous version is available at:
>     > > > http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-audio-02
>     > > >
>     > > >
>     > > > Please note that it may take a couple of minutes from the
>     time of
>     > > submission until the htmlized version and diff are
>     > > > available at tools.ietf.org <http://tools.ietf.org>.
>     > > >
>     > > > Internet-Drafts are also available by anonymous FTP at:
>     > > > ftp://ftp.ietf.org/internet-drafts/
>     > > >
>     > > > _______________________________________________
>     > > > I-D-Announce mailing list
>     > > > I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
>     > > > https://www.ietf.org/mailman/listinfo/i-d-announce
>     > > > Internet-Draft directories: http://www.ietf.org/shadow.html or
>     > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>     > > _______________________________________________
>     > > rtcweb mailing list
>     > > rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     > > https://www.ietf.org/mailman/listinfo/rtcweb
>     > > _______________________________________________
>     > > rtcweb mailing list
>     > > rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     > > https://www.ietf.org/mailman/listinfo/rtcweb
>     _______________________________________________
>     rtcweb mailing list
>     rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb