Re: [hybi] New charter for HyBi wg

Gabriel Montenegro <Gabriel.Montenegro@microsoft.com> Fri, 20 January 2012 19:56 UTC

Return-Path: <Gabriel.Montenegro@microsoft.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 5952C21F8508 for <hybi@ietfa.amsl.com>; Fri, 20 Jan 2012 11:56:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 9frFl6VwqdII for <hybi@ietfa.amsl.com>; Fri, 20 Jan 2012 11:56:15 -0800 (PST)
Received: from DB3EHSOBE002.bigfish.com (db3ehsobe002.messaging.microsoft.com [213.199.154.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB0E21F84FB for <hybi@ietf.org>; Fri, 20 Jan 2012 11:56:14 -0800 (PST)
Received: from mail114-db3-R.bigfish.com (10.3.81.254) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Fri, 20 Jan 2012 19:56:11 +0000
Received: from mail114-db3 (localhost [127.0.0.1]) by mail114-db3-R.bigfish.com (Postfix) with ESMTP id B86EE20507; Fri, 20 Jan 2012 19:56:11 +0000 (UTC)
X-SpamScore: -24
X-BigFish: VS-24(zz9371Ic89bhc857h98dKzz1202hzz1033IL8275bh8275dhz2fhc1bhc31hc1ahc1bhc31hc1ah2a8h668h839h)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC101.redmond.corp.microsoft.com; RD:none; EFVD:NLI
Received-SPF: pass (mail114-db3: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=Gabriel.Montenegro@microsoft.com; helo=TK5EX14HUBC101.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail114-db3 (localhost.localdomain [127.0.0.1]) by mail114-db3 (MessageSwitch) id 1327089371530003_8533; Fri, 20 Jan 2012 19:56:11 +0000 (UTC)
Received: from DB3EHSMHS012.bigfish.com (unknown [10.3.81.252]) by mail114-db3.bigfish.com (Postfix) with ESMTP id 7378E600053; Fri, 20 Jan 2012 19:56:11 +0000 (UTC)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.8) by DB3EHSMHS012.bigfish.com (10.3.87.112) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 20 Jan 2012 19:56:10 +0000
Received: from TK5EX14MLTW653.wingroup.windeploy.ntdev.microsoft.com (157.54.24.14) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server (TLS) id 14.2.247.5; Fri, 20 Jan 2012 11:56:11 -0800
Received: from TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com ([169.254.4.102]) by TK5EX14MLTW653.wingroup.windeploy.ntdev.microsoft.com ([157.54.24.14]) with mapi id 14.01.0355.003; Fri, 20 Jan 2012 11:56:10 -0800
From: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
To: John Tamplin <jat@google.com>, Jesse McConnell <jesse.mcconnell@gmail.com>
Thread-Topic: [hybi] New charter for HyBi wg
Thread-Index: AczV9NDcLG3qqhUYRnuolEHotiaefABv5IEAAAeMrgAAA/cSAAAC1PGAABA+aKA=
Date: Fri, 20 Jan 2012 19:56:10 +0000
Message-ID: <CA566BAEAD6B3F4E8B5C5C4F61710C1147E51918@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
References: <0FDF715F51EF4B4BA69B4A7B865DBD9B3A637AB5D6@ESESSCMS0363.eemea.ericsson.se> <CABLsOLCXd798TjVoE656B9R4JRo6pZcDDNq77QbE0zi2FPtSuA@mail.gmail.com> <4F19947A.6080904@isode.com> <CAPHPUsKOaYA8PL5EmEvjB7A8zMGtGJ_dZ3LSqsvTD1oy5EiSFg@mail.gmail.com> <CABLsOLAi-rkeqf5hx20q71Q1=3cJ=h-v6XcUQVFrSO2iZF5sfQ@mail.gmail.com>
In-Reply-To: <CABLsOLAi-rkeqf5hx20q71Q1=3cJ=h-v6XcUQVFrSO2iZF5sfQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.42]
Content-Type: multipart/alternative; boundary="_000_CA566BAEAD6B3F4E8B5C5C4F61710C1147E51918TK5EX14MBXW604w_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
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:56:16 -0000

Yes, the assumption is that multiplexing will use John’s draft as a starting point, and the compression will use Takeshi’s draft as a starting point. I agree that the compression extension is better understood and more contained, which is why it is targeted as finishing earlier, although some parallel work might be ok as one tapers off. We can always modify dates and estimates later on, but this is just a first stab.

I agree that the mux extension is more complex and invite discussion as to how the WG sees it and whether the currently proposed milestones are within the ballpark (it’s ok for them to be somewhat optimistic, as were our original charter’s milestones).

From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of John Tamplin
Sent: 20 January, 2012 11:36
To: Jesse McConnell
Cc: hybi@ietf.org
Subject: Re: [hybi] New charter for HyBi wg

On Fri, Jan 20, 2012 at 1:14 PM, Jesse McConnell <jesse.mcconnell@gmail.com<mailto: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