IETF Logo Mail Archive

Re: [hybi] method of allocation of reserved bits to extensions

John Tamplin <jat@google.com> Wed, 25 May 2011 05:14 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 799AAE0699 for <hybi@ietfa.amsl.com>; Tue, 24 May 2011 22:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level:
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4WJJ31jXqZL for <hybi@ietfa.amsl.com>; Tue, 24 May 2011 22:14:30 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id C57DEE065B for <hybi@ietf.org>; Tue, 24 May 2011 22:14:29 -0700 (PDT)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id p4P5ESQ1008339 for <hybi@ietf.org>; Tue, 24 May 2011 22:14:29 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306300469; bh=3uu0f8EK6HQLGLlNET9zYZLZJWk=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=OWSRtQS/8fMM/xd/xDNniVlFJLNA3Ofi9SbO3gvqYIjKlvV37U3NT0O9gvzbvn1Ms Qq/v5ZcdrHqigDfoQSpBA==
Received: from gyf2 (gyf2.prod.google.com [10.243.50.66]) by hpaq11.eem.corp.google.com with ESMTP id p4P5EQIV015541 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Tue, 24 May 2011 22:14:27 -0700
Received: by gyf2 with SMTP id 2so3605401gyf.25 for <hybi@ietf.org>; Tue, 24 May 2011 22:14:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=63aJ4Lc6gqdcQxYaAdkaxnigaaaaXuVmZAIpSHAfXYE=; b=aIjniDSWlukImBKiiyRCvcwb9iOlATPzXy/ebTEhlC6A3UU0R1lz7GcF44PJz2khSn 6djzHVReKdwCHffc2yeg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=K0H/Jl8HzL2gBCFg++lUwAVcxz36xi0U0mQQZ6j9HlULZ6vCFJ7UF28aQ2/lOaaMai YNR0PFQbg/Zdn0ElQmBw==
Received: by 10.150.73.3 with SMTP id v3mr4753087yba.173.1306300466172; Tue, 24 May 2011 22:14:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Tue, 24 May 2011 22:14:04 -0700 (PDT)
In-Reply-To: <BANLkTintB9i-qRV=b3UGSQM+12u6cVJ1jA@mail.gmail.com>
References: <BANLkTi=vOQDtL5GobitKe8yiUoQFb2go_Q@mail.gmail.com> <BANLkTikaOXg0u+4d8Ly6OxUQ7PFUU=udgQ@mail.gmail.com> <BANLkTikiUkivJitZGU-+q6wBfJ3VW45F8g@mail.gmail.com> <BANLkTindmLQ0KE6K5qUX2ue+=hoLUaznLA@mail.gmail.com> <BANLkTim9w83iSY-TH1yuVAUXxypJk_tmrw@mail.gmail.com> <BANLkTimnMBwNgP_e29exT6dUkp60s2xU3g@mail.gmail.com> <BANLkTi==RTfqaYFT3CQs1pM5Tb501rk2Vg@mail.gmail.com> <BANLkTinqQiMQ4N1vWjyCe682BmdisW-=KA@mail.gmail.com> <BANLkTik1a6CEA8LiiLgsnBt9qHCaybmWfg@mail.gmail.com> <4DBA3809.4010004@oracle.com> <CA566BAEAD6B3F4E8B5C5C4F61710C11402DB23F@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com> <BANLkTim8dkW3R2R1ukAqwkXOM0=uqfiPmA@mail.gmail.com> <4DD61D35.10404@warmcat.com> <BANLkTi=57EYWnuOv3n=crHsgC5t3x=PPkA@mail.gmail.com> <BANLkTi=hP1CPNE+3PSHUTWcBHW_WPxCBQw@mail.gmail.com> <BANLkTikwysTjCw62aZSi_3faHrQjYW=fuw@mail.gmail.com> <BANLkTiku1qznAK-yv4jUdfpuRVfuaBD7Hg@mail.gmail.com> <BANLkTim2y1_5GYgJo6xQY+0E7Bz96qF9vg@mail.gmail.com> <BANLkTintB9i-qRV=b3UGSQM+12u6cVJ1jA@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Wed, 25 May 2011 01:14:04 -0400
Message-ID: <BANLkTimvfi-j6Of28Gw1uxXKFQFJQhJRag@mail.gmail.com>
To: Greg Wilkins <gregw@intalio.com>
Content-Type: multipart/alternative; boundary="000e0cd58e2a4194e804a412c78f"
X-System-Of-Record: true
Cc: Hybi <hybi@ietf.org>, Alan Coopersmith <alan.coopersmith@oracle.com>, "jg@freedesktop.org" <jg@freedesktop.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, Brodie Thiesfield <brodie@jellycan.com>
Subject: Re: [hybi] method of allocation of reserved bits to extensions
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: Wed, 25 May 2011 05:14:30 -0000

On Wed, May 25, 2011 at 1:08 AM, Greg Wilkins <gregw@intalio.com> wrote:

> > Again, that isn't what Greg was suggesting.
> > Also, if reserved opcodes can't be used (which Greg was also suggesting),
> > then there is no room for any experimentation, which seems a recipe for
> poor
> > progress getting useful extensions.
>
> Extensions can always have their own opcodes by putting them as a byte
> in the payload (which is what you have previously advocated for
> extension opcodes anyway).


Not if you don't define some extension opcode.  Ie, if I can't use a
reserved opcode, saying my frame is a binary frame and the first byte is
really a new opcode doesn't work with fragmentation and multiplexing being
done by intermediaries which think it is just a regular binary frame.

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

v2.23.0 | Report a Bug | By Email