Re: [hybi] New charter for HyBi wg

John Tamplin <jat@google.com> Fri, 20 January 2012 19:36 UTC

Return-Path: <jat@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E3121F8647 for <hybi@ietfa.amsl.com>; Fri, 20 Jan 2012 11:36:15 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgXNnvDF6Xdg for <hybi@ietfa.amsl.com>; Fri, 20 Jan 2012 11:36:15 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E624D21F8646 for <hybi@ietf.org>; Fri, 20 Jan 2012 11:36:14 -0800 (PST)
Received: by vbbfr13 with SMTP id fr13so685849vbb.31 for <hybi@ietf.org>; Fri, 20 Jan 2012 11:36:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:x-system-of-record:content-type; bh=6lIJT5OfLtqwMN3XgHVQBR7kdTDBRBz0hxUaCUBqYaQ=; b=OhgQ8MGQLRdtRjuaoQsaXMD1NTDDFXrt4s4YWnykN9RU6mDCZr1frfpwuSBk+owQo/ JwE/dfAVMqivcNEgkVnmNyvUJtvM/yZRBmH0SYdSnTX2noVSz0fmVFvDrA+CUkkD2RSG pNxyvo2AQnM79aVuP7LjbpCdNLSHsXpLmfmqE=
Received: by 10.52.33.77 with SMTP id p13mr15570399vdi.18.1327088173526; Fri, 20 Jan 2012 11:36:13 -0800 (PST)
Received: by 10.52.33.77 with SMTP id p13mr15570389vdi.18.1327088173371; Fri, 20 Jan 2012 11:36:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.117.132 with HTTP; Fri, 20 Jan 2012 11:35:51 -0800 (PST)
In-Reply-To: <CAPHPUsKOaYA8PL5EmEvjB7A8zMGtGJ_dZ3LSqsvTD1oy5EiSFg@mail.gmail.com>
References: <0FDF715F51EF4B4BA69B4A7B865DBD9B3A637AB5D6@ESESSCMS0363.eemea.ericsson.se> <CABLsOLCXd798TjVoE656B9R4JRo6pZcDDNq77QbE0zi2FPtSuA@mail.gmail.com> <4F19947A.6080904@isode.com> <CAPHPUsKOaYA8PL5EmEvjB7A8zMGtGJ_dZ3LSqsvTD1oy5EiSFg@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Fri, 20 Jan 2012 14:35:51 -0500
Message-ID: <CABLsOLAi-rkeqf5hx20q71Q1=3cJ=h-v6XcUQVFrSO2iZF5sfQ@mail.gmail.com>
To: Jesse McConnell <jesse.mcconnell@gmail.com>
X-System-Of-Record: true
Content-Type: multipart/alternative; boundary="20cf307d02e028d21504b6facbd4"
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] New charter for HyBi wg
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 19:36:15 -0000

On Fri, Jan 20, 2012 at 1:14 PM, Jesse McConnell
<jesse.mcconnell@gmail.com>wrote:

> Is it safe to assume that the starting place for the mux extension
> will be John's google-mux draft?  If so, would it make sense to start
> off the extensions discussions there, or does it make more sense to
> work on some 'official' simple extensions before tackling that more
> complex one?  I am a bit torn on where it would be best to start.  I
> would like to see the mux 'official' as soon as possible but I am
> unclear if individual extensions could have much of an effect on the
> mux extension or vis versa.
>
> Just curious as he has some nice work done there which could be a nice
> starting point.
>

If someone has an alternate proposal, that is fine, but in the absence of
that I suggest http://tools.ietf.org/html/draft-tamplin-hybi-google-mux-01 is
as good a place to start as any.

I suspect per-frame compression will be easier to get agreement on, and so
could be completed more quickly.  There is a pressing need for both, but
shortest-job-first scheduling gets something useful deployed faster.

-- 
John A. Tamplin
Software Engineer (GWT), Google