From: <stephane.proust@orange.com>
To: 'Martin Thomson' <martin.thomson@gmail.com>,
 'Harald Alvestrand' <harald@alvestrand.no>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
Thread-Index: AQHOj52YNf0VLpHUzEKr6spLBSmfVZmnooUwgBGAZICAABuoAIAAAqUAgAAR5ACAAAyZgIAAA3aAgAPJXtA=
Date: Mon, 9 Sep 2013 06:47:31 +0000
Message-ID: <12397_1378709252_522D6F04_12397_16983_1_2842AD9A45C83B44B57635FD4831E60A06C3B148@PEXCVZYM14.corporate.adroot.infra.ftgroup>
References: <20130802162957.17108.79281.idtracker@ietfa.amsl.com>
 <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se>
 <522A23C1.2030900@mozilla.com>
 <3879D71E758A7E4AA99A35DD8D41D3D91D527148@xmb-rcd-x14.cisco.com>
 <CABkgnnXo3BWLgsbgHi+MArc6xhOQ=vw3MFtA176=ngOh2nYdMA@mail.gmail.com>
 <3879D71E758A7E4AA99A35DD8D41D3D91D527209@xmb-rcd-x14.cisco.com>
 <522A56BF.7050509@alvestrand.no>
 <CABkgnnUMK2cP=2L7i_gPaYEjvUiqvxujRowP8WH=k0SEy6bo-w@mail.gmail.com>
In-Reply-To: <CABkgnnUMK2cP=2L7i_gPaYEjvUiqvxujRowP8WH=k0SEy6bo-w@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "'rtcweb@ietf.org'" <rtcweb@ietf.org>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
Precedence: list

Let's avoid reopening the whole discussion about this normative wording!=20

I would like to recall again that the proposal from Bo comes from a comprom=
ise statement that was almost reached in e-mail discussions last January (f=
rom an initial proposal from Andrew Allen) and almost reached now again
http://www.ietf.org/mail-archive/web/rtcweb/current/msg08501.html

So it confirms clearly that the consensus of the group is on the proposed t=
ext and especially because it does not include any formal normative languag=
e.=20
So I would strongly suggest to not reinvent anything new and close now this=
 long discussion on the last proposal from Bo on which several supports hav=
e been expressed and no objections, possibly with the slight modification s=
uggested by Mo Zanaty on the place where the text can be added (beginning o=
f section 3) which is a good idea that I support as well
http://www.ietf.org/mail-archive/web/rtcweb/current/msg08750.html

St=E9phane






-----Message d'origine-----
De=A0: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] De la part =
de Martin Thomson
Envoy=E9=A0: samedi 7 septembre 2013 00:40
=C0=A0: Harald Alvestrand
Cc=A0: rtcweb@ietf.org
Objet=A0: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt

On 6 September 2013 15:27, Harald Alvestrand <harald@alvestrand.no> wrote:
> That's why I'm so reluctant to use the word in cases where I think a=20
> large part of the implementors are going to ignore it, and where (in=20
> my opinion) no great harm comes to interoperability when they do.

I tend to agree, though we have to be careful not to end up with the RFC 69=
19, Section 1 problem at the same time.

I still try to do the "MUST, unless ..." form rather than SHOULD.
SHOULD is a bit wishy-washy.

In this case, I don't see the point of saying anything at all.  I'm sure th=
at browser implementers will add what they believe will be best for their u=
sers.  And avoiding transcoding is good, which should be sufficient.  Ultim=
ately, we're all grown-ups, and having the IETF tells us to eat our vegetab=
les is insulting.
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.