Re: [hybi] Technical feedback. was: Process!

Greg Wilkins <gregw@webtide.com> Wed, 03 February 2010 04:29 UTC

Return-Path: <gregw@webtide.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D0D03A6A2B for <hybi@core3.amsl.com>; Tue, 2 Feb 2010 20:29:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level:
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqNZM8A9LnwZ for <hybi@core3.amsl.com>; Tue, 2 Feb 2010 20:29:05 -0800 (PST)
Received: from mail-yx0-f174.google.com (mail-yx0-f174.google.com [209.85.210.174]) by core3.amsl.com (Postfix) with ESMTP id 9273C3A6879 for <hybi@ietf.org>; Tue, 2 Feb 2010 20:29:05 -0800 (PST)
Received: by yxe4 with SMTP id 4so944411yxe.32 for <hybi@ietf.org>; Tue, 02 Feb 2010 20:29:42 -0800 (PST)
Received: by 10.90.62.2 with SMTP id k2mr6311833aga.56.1265171382315; Tue, 02 Feb 2010 20:29:42 -0800 (PST)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id 13sm4492817gxk.5.2010.02.02.20.29.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Feb 2010 20:29:41 -0800 (PST)
Message-ID: <4B68FBAE.2010406@webtide.com>
Date: Wed, 03 Feb 2010 15:29:34 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Jamie Lokier <jamie@shareable.org>
References: <4B62C5FE.8090904@it.aoyama.ac.jp> <Pine.LNX.4.64.1001291134350.22020@ps20323.dreamhostps.com> <4B62E516.2010003@webtide.com> <5c902b9e1001290756r3f585204h32cacd6e64fbebaa@mail.gmail.com> <4B636757.3040307@webtide.com> <BBF3CE06-3276-4A7C-8961-7B3DDEE406D0@apple.com> <4B63DC2D.4090702@webtide.com> <5c902b9e1001292325p423d7e82o9478441893e34523@mail.gmail.com> <DF402A25-D858-4E56-811D-464C85226800@apple.com> <4B64B42D.5090007@webtide.com> <20100203013500.GJ32743@shareable.org>
In-Reply-To: <20100203013500.GJ32743@shareable.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Technical feedback. was: Process!
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Feb 2010 04:29:06 -0000

Jamie Lokier wrote:
> Greg Wilkins wrote:

>>   + Who controls allocation of the frame type byte?  So far every
>>     suggestion of usage for that (eg a bit to indicate that the
>>     frame contains meta-data headers) has been rejected.  So are
>>     binary users simply to pick their own bytes and hope for no
>>     collisions?  Will IANA eventually allocate values?  is 7 bits
>>     enough?
> 
> There will be no collisions for frame bytes which depend on the
> sub-protocol name, as those frame bytes are privately agreed between
> client and server.

Good point.

But then we do need to ensure that there are no sub-protocol name
clashes.     My suggestion is to use real URLs as sub-protocol
names, like DTDs

Also I think a single sub protocol name is not very flexible.
You might want to combine multiple sub protocols - one for
gzip, one for orderly close etc.   or is that a subprotocol
that supports optional features?

regards