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

Patrick McManus <pmcmanus@mozilla.com> Tue, 24 May 2011 23:53 UTC

Return-Path: <pmcmanus@mozilla.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 D265CE06D7 for <hybi@ietfa.amsl.com>; Tue, 24 May 2011 16:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 m6PKvwUDrRJ6 for <hybi@ietfa.amsl.com>; Tue, 24 May 2011 16:53:50 -0700 (PDT)
Received: from linode.ducksong.com (linode.ducksong.com [64.22.125.164]) by ietfa.amsl.com (Postfix) with ESMTP id 58B40E064E for <hybi@ietf.org>; Tue, 24 May 2011 16:53:49 -0700 (PDT)
Received: by linode.ducksong.com (Postfix, from userid 1000) id B059B10307; Tue, 24 May 2011 19:53:48 -0400 (EDT)
Received: from [192.168.16.226] (cpe-67-253-92-25.maine.res.rr.com [67.253.92.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by linode.ducksong.com (Postfix) with ESMTPSA id 99E6E102A7 for <hybi@ietf.org>; Tue, 24 May 2011 19:53:44 -0400 (EDT)
From: Patrick McManus <pmcmanus@mozilla.com>
To: hybi <hybi@ietf.org>
In-Reply-To: <BANLkTikaOXg0u+4d8Ly6OxUQ7PFUU=udgQ@mail.gmail.com>
References: <BANLkTi=vOQDtL5GobitKe8yiUoQFb2go_Q@mail.gmail.com> <BANLkTikaOXg0u+4d8Ly6OxUQ7PFUU=udgQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 24 May 2011 19:53:43 -0400
Message-ID: <1306281223.1782.9.camel@ds9>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2
Content-Transfer-Encoding: 7bit
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: Tue, 24 May 2011 23:53:50 -0000

I apologize for quoting from so deep in the archive, but the thread is
still, somewhat to my horror, active:

On Wed, 2011-04-27 at 21:16 -0400, John Tamplin wrote:
> We had this discussion during the framing discussion, and we couldn't
> reach consensus then.  So, instead we simply said that each extension
> defines how bits are to be interpreted.   That could mean the bits are
> statically allocated, or it could mean some negotiation scheme like
> what you propose.
> 
> 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 agree with everything John says above. Our AD has given strong
guidance to create a IANA registry to record this, and I think that
makes sense as well.