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

Brodie Thiesfield <brodie@jellycan.com> Thu, 28 April 2011 01:43 UTC

Return-Path: <brofield@gmail.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 71EC0E0914 for <hybi@ietfa.amsl.com>; Wed, 27 Apr 2011 18:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 DZyRrTiHOIMs for <hybi@ietfa.amsl.com>; Wed, 27 Apr 2011 18:43:52 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfa.amsl.com (Postfix) with ESMTP id DD7D0E0911 for <hybi@ietf.org>; Wed, 27 Apr 2011 18:43:52 -0700 (PDT)
Received: by pvh1 with SMTP id 1so1872673pvh.31 for <hybi@ietf.org>; Wed, 27 Apr 2011 18:43:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=di7XIrcvRHDikyLK72o5SnI1vSuFXSBTVvxcssGFU7I=; b=vIgHbSsvYDdZo9gxXHbtO2wUiK8x7FgfBDazByJChR6I7mwIKIg5OJBbE5bLFuro9/ NH6lqJkNRAz37mGJOJfb95cXF+HKXaPaffBNQim3t0IyeVpgC3lnn0H2e5+2qYg1dczM Q5pgjSiMhBjKzfoCPBz3qgmemoziCZU4ndac0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=JKp90mUUju21hvyaVCSGzPK6H0rWObrQE8og7xl1oJO90/41A/ghWJVRDaLutNpIUw id+p6i+lGNUqBBPZ9TWquXc5TfZ4OeBDMRplYbLOlH+b2daTfzz4p+YbQ3hmPa2f5uyQ /z7b9LdfyNvA5e3xGynbtNWo76n2TEN3JNV1A=
MIME-Version: 1.0
Received: by 10.68.44.197 with SMTP id g5mr3045884pbm.509.1303955032532; Wed, 27 Apr 2011 18:43:52 -0700 (PDT)
Sender: brofield@gmail.com
Received: by 10.68.54.35 with HTTP; Wed, 27 Apr 2011 18:43:52 -0700 (PDT)
In-Reply-To: <BANLkTikiUkivJitZGU-+q6wBfJ3VW45F8g@mail.gmail.com>
References: <BANLkTi=vOQDtL5GobitKe8yiUoQFb2go_Q@mail.gmail.com> <BANLkTikaOXg0u+4d8Ly6OxUQ7PFUU=udgQ@mail.gmail.com> <BANLkTikiUkivJitZGU-+q6wBfJ3VW45F8g@mail.gmail.com>
Date: Thu, 28 Apr 2011 10:43:52 +0900
X-Google-Sender-Auth: THv8xUr36CpM-ucKYDNY4wM7DrY
Message-ID: <BANLkTin9ONOimqCCkAO00J5pHbyDwY+SKw@mail.gmail.com>
From: Brodie Thiesfield <brodie@jellycan.com>
To: Greg Wilkins <gregw@intalio.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Hybi <hybi@ietf.org>
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: Thu, 28 Apr 2011 01:43:53 -0000

On Thu, Apr 28, 2011 at 10:38 AM, Greg Wilkins <gregw@intalio.com> wrote:
> On 28 April 2011 11:16, John Tamplin <jat@google.com> wrote:
>> I would be opposed to delaying the spec to try and get consensus on
>> negotiating the usage of reserved bits into the base spec, since it can be
>> just as easily postponed until the first extension that wants to make use of
>> some reserved bit.
>
> I also am not keen to see any unreasonable delay.   But I think that
> many of the issues surrounding framing and extensions are now better
> understood and I think that it is worth while to at least revisit
> unresolved issues such as these to see if we can resolve them.

Agreed.

> Currently we have the assumption that if we look at a negotiated WS
> connection and if we know all the extensions that have been
> negotiated, then we will be able to decode the bytes on the wire.
> Unfortunately, as Brodie has pointed out, that does not hold if there
> is more than one extension that uses reserved bits.     I think this
> is an oversight that must be fixed, but I'm not sure that we need
> additional headers etc. for it.
>
> I think it would be sufficient to say that reserved bits are allocated
> to extensions in the order in which the extensions are negotiated (and
> I don't think we need optional bits):

This would work. I'd be happy with this too.

Brodie