Re: [rtcweb] H.264 versus VP8 - are we really going to spend 2 full hours rehashing this?
Mary Barnes <mary.ietf.barnes@gmail.com> Mon, 14 October 2013 18:26 UTC
Return-Path: <mary.ietf.barnes@gmail.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 8D55421E80B3 for <rtcweb@ietfa.amsl.com>; Mon, 14 Oct 2013 11:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.58
X-Spam-Level:
X-Spam-Status: No, score=-101.58 tagged_above=-999 required=5 tests=[AWL=-0.647, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666, 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 Ag7Ys24RMWgS for <rtcweb@ietfa.amsl.com>; Mon, 14 Oct 2013 11:26:46 -0700 (PDT)
Received: from mail-qe0-x231.google.com (mail-qe0-x231.google.com [IPv6:2607:f8b0:400d:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 80BA521E80E3 for <rtcweb@ietf.org>; Mon, 14 Oct 2013 11:26:46 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id a11so472903qen.8 for <rtcweb@ietf.org>; Mon, 14 Oct 2013 11:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/6HTdNGYGmAiFy6kl4eaxICuNew+KKk4padQpwN7Ilo=; b=MyVys/A1IHDcqji2NlQNLgoukM6Q5kIso4eFW1YrTIM2c1s4HSwJCrVJu/kKUghu2G DEM+MoWW5LzmUeymyX7t9y9AgtZKJUzPZ7SLY1TpYSBHooiQuWgzj+ZCbtCqQGNfi4Kv MZzg1UzjXZa2ehTf3Ddpb1S8Z9XC8fuC665Zz8kQxu+245j/xIvasinDF/b+hA9CfoFI 00wyMWSJ+vrv+98nU8WUTXhxsPCw7ZN/SaajX1ZbcLPtbqkrQDhfax2/zy5iCwZsysq5 pCdf+9kAUXif+EOiOjHV6zl14Ab9LZr8xeWWWYjshYUNc+bCVOStwBDgrIMc/Uwu7f+A tVFA==
MIME-Version: 1.0
X-Received: by 10.49.25.1 with SMTP id y1mr40544620qef.22.1381775205881; Mon, 14 Oct 2013 11:26:45 -0700 (PDT)
Received: by 10.49.117.234 with HTTP; Mon, 14 Oct 2013 11:26:45 -0700 (PDT)
In-Reply-To: <525C3049.1000809@bbs.darktech.org>
References: <525BFB6F.5080403@alvestrand.no> <525C3049.1000809@bbs.darktech.org>
Date: Mon, 14 Oct 2013 13:26:45 -0500
Message-ID: <CAHBDyN5kH91fEFH6-2htmfB-QstX17aeZO3FKD-eykGwxX3z9A@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Content-Type: multipart/alternative; boundary="047d7b676e684e79b804e8b79c50"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] H.264 versus VP8 - are we really going to spend 2 full hours rehashing this?
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, 14 Oct 2013 18:26:47 -0000
Gili, The concern is around 2 hours on the agenda at the upcoming f2f meeting: http://www.ietf.org/mail-archive/web/rtcweb/current/msg09037.html We already spent around hours on this topic at a previous f2f IETF. Here's the multi-media recording for your enjoyment: http://ietf86.conf.meetecho.com/index.php/Recorded_Sessions#RTCWEB_III BTW, Meetecho is a great way for remote folks to follow the f2f IETF meetings. Regards, Mary. On Mon, Oct 14, 2013 at 12:56 PM, cowwoc <cowwoc@bbs.darktech.org> wrote: > Harald, > > What's the alternative? Whether the discussion happens on the mailing > list or a call it sounds to me like you've got people with entrenched > views. I'll take this opportunity to remind you of another option: mandate > a codec whose IPR has expired and have clients negotiate up from there. > This compromise displeases everyone equally, but it allows us to proceed > without any further delay. > > Gili > > > On 14/10/2013 10:10 AM, Harald Alvestrand wrote: > >> I've read the H.264 Constrained Baseline proposal. >> >> It contains no information that hasn't been presented to the list long >> ago; all but the performance evaluations were presented in Florida. >> >> I've written the VP8 proposal. >> It contains new information, but only in the form of pointing out that >> VP8 is more widely deployed, closer to being an ISO standard, and working >> better than when we discussed this in Florida. It is also being universally >> deployed in existing WebRTC implementations (Mozilla and Chrome). >> >> We know that for most participants, the IPR issue is the only real issue. >> So far, I haven't seen any of the people who were saying "we want to ship >> products but can't possibly use H.264" saying that they have changed their >> minds. >> >> Yet the chairs are proposing the following 2-hour agenda: >> >> Frame discussions and process and agenda: 10 min (chairs) >> >> VP8 presentation with clarify questions - 25 min (???) >> >> H.264 presentation with clarify questions - 25 min (???) >> >> Microphone discussions of pro/cons - 40 min (all) >> >> Call the question - 10 min ( chairs ) >> >> Wrap up and next steps - 10 min (chairs) >> >> Celebrate on our successful decision reach. >> >> >> Don't we have ways in which we can make better use of 2 hours? >> >> ______________________________**_________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb> >> > > ______________________________**_________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb> >
- [rtcweb] H.264 versus VP8 - are we really going t… Harald Alvestrand
- Re: [rtcweb] H.264 versus VP8 - are we really goi… Mary Barnes
- Re: [rtcweb] H.264 versus VP8 - are we really goi… Bernard Aboba
- Re: [rtcweb] H.264 versus VP8 - are we really goi… cowwoc
- Re: [rtcweb] H.264 versus VP8 - are we really goi… Mary Barnes
- Re: [rtcweb] H.264 versus VP8 - are we really goi… cowwoc
- Re: [rtcweb] H.264 versus VP8 - are we really goi… Mary Barnes
- Re: [rtcweb] H.264 versus VP8 - are we really goi… Ted Hardie