Re: [hybi] HyBi BOF announcement

SM <sm@resistor.net> Thu, 29 October 2009 20:59 UTC

Return-Path: <sm@resistor.net>
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 83C563A6A1D for <hybi@core3.amsl.com>; Thu, 29 Oct 2009 13:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level:
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 fPdjeQujxruM for <hybi@core3.amsl.com>; Thu, 29 Oct 2009 13:59:18 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 914AB3A694A for <hybi@ietf.org>; Thu, 29 Oct 2009 13:59:18 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4.Beta0/8.14.4.Beta0) with ESMTP id n9TKxPCW023743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <hybi@ietf.org>; Thu, 29 Oct 2009 13:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1256849973; x=1256936373; bh=iWg7cJbWBsPd+1XAZTNPBI5rQIfaFUcY7zrenucGc0o=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=tz9+o3JYJv+Ppzpy5O03MwA9k78aFEWqKavex2Rer0kVwR8pPlUzyuNH6MeNg+wZa 77gnKAo/xZBPrJhjsER27NDOmBSFH/ZjR5rvpCo2PdkIOaJXow4255I5gmC0PAIei+ sFk1dts/IPEBpZ0ME0i+BHWkCLkE0iPN0a/krrpw=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=TO4IS1lK1vrRvk6TcDYSoCAtslNjQ8sIw7Xffdxt+umo07f37OQhhY9qCuCj/ijLN XRPOhJr/jQHFOkQ4CqafJoSqyXSZPVGuHs+B9BegY6PjD1w85YfdoQUZKaSS6pji5Xb CVBzSfYzlrbtc8lXE/W65QidRaitLnAG9wE2y+E=
Message-Id: <6.2.5.6.2.20091029132020.03232b88@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Oct 2009 13:57:30 -0700
To: hybi@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <4AAB7CCB.9010805@ericsson.com>
References: <4AAB7CCB.9010805@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: Re: [hybi] HyBi BOF announcement
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: Thu, 29 Oct 2009 20:59:19 -0000

At 07:40 23-10-2009, Peter Saint-Andre wrote:
>And I wonder if there is a "v3d" ("version three digits") problem

Probably.

>lurking in the tools we use to process Internet-Drafts. I've never seen
>an I-D with a version greater than 99.

Neither have I.

At 03:49 12-09-2009, Salvatore Loreto wrote:
>We are still working on the Charter Proposal and on the Agenda so 
>all the proposal and comments are welcome!

 From the proposal:

   "In particular, the working group will liaison with the W3C
    WebApps working group around the WebSockets protocol and the
    requirements to support the WebSocket API; if agreed by both
    parties, the HyBi working group may take on prime responsibility
    on the specification of the WebSockets protocol."

Are the two working group in agreement on who has prime 
responsibility?  I ask as there seems to be some misunderstanding 
about how work get done within the IETF.  BTW, prime responsibility 
doesn't mean that the two working groups should not work together.

    "Ability to achieve broad implementation"

Will the work be dropped if there isn't broad implementation?  If you 
are going for Proposed Standard, it may be worth considering whether 
the bar is not set too high.

    "Ability to address broader use cases than may be contemplated
     by the original authors"

I suggest changing that as this is (IETF) Working Group work:

   Ability to address broader use cases

Regards,
-sm