Re: [hybi] WebSocket feedback
Joe Hildebrand <joe.hildebrand@webex.com> Thu, 04 March 2010 18:28 UTC
Return-Path: <Joe.Hildebrand@webex.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 9601B3A8E28 for <hybi@core3.amsl.com>; Thu, 4 Mar 2010 10:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.532
X-Spam-Level:
X-Spam-Status: No, score=-104.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
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 TBu--Bj4FbZ9 for <hybi@core3.amsl.com>; Thu, 4 Mar 2010 10:28:18 -0800 (PST)
Received: from gw2.webex.com (gw2.webex.com [64.68.122.209]) by core3.amsl.com (Postfix) with SMTP id 822E43A8DDD for <hybi@ietf.org>; Thu, 4 Mar 2010 10:28:18 -0800 (PST)
Received: from SRV-EXSC03.webex.local ([192.168.252.198]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 4 Mar 2010 10:28:20 -0800
Received: from 64.101.74.200 ([64.101.74.200]) by SRV-EXSC03.webex.local ([192.168.252.200]) with Microsoft Exchange Server HTTP-DAV ; Thu, 4 Mar 2010 18:27:50 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Thu, 04 Mar 2010 11:27:48 -0700
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Greg Wilkins <gregw@webtide.com>, Hybi <hybi@ietf.org>
Message-ID: <C7B549B4.1EFF0%joe.hildebrand@webex.com>
Thread-Topic: [hybi] WebSocket feedback
Thread-Index: Acq7yGQO5mgH7tyv6kCnemsfY8w4DA==
In-Reply-To: <4B8F6056.8060809@webtide.com>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 04 Mar 2010 18:28:20.0756 (UTC) FILETIME=[77949540:01CABBC8]
Subject: Re: [hybi] WebSocket feedback
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, 04 Mar 2010 18:28:19 -0000
On 3/4/10 12:25 AM, "Greg Wilkins" <gregw@webtide.com> wrote: > However, I hope that this type of mass update is a once off due > to the circumstances we find in starting off the WG. In general > I think it would be far easier handle changes in smaller > increments and individual threads. Also it would be good > to see proposed diffs to the draft before they are actually > just put in the draft. Sorry - don't mean to rain on your > parade when you've done so much. The chairs were concerned about the number of changes that had to flow through the IETF backend systems associated with many small changes. Larger changes getting batched up before formal submittal is the way we want to go for now. Keep in mind that we'll need to have consensus over the whole document by the time we're done, so I don't see a need to propose individual chunks of text before they're inserted in the document, particularly at this early stage. At the same time, particularly as this becomes a WG draft, a quick "I'm about to..." mail to the list before a large change will help build that consensus more quickly. Each working group is a little different in this regard, and we're still trying to find out what works for this crowd. Of course, as always, whenever proposing a change to the document, it is much more likely to get included in the way you want if you also propose text. -- Joe Hildebrand (as chair)
- Re: [hybi] WS ABNF Dave Cridland
- Re: [hybi] WS ABNF Julian Reschke
- Re: [hybi] WS ABNF Greg Wilkins
- Re: [hybi] WS ABNF Thomson, Martin
- [hybi] WS ABNF Thomson, Martin
- Re: [hybi] WS ABNF Dave Cridland
- Re: [hybi] WS ABNF Julian Reschke
- Re: [hybi] WS ABNF Jamie Lokier
- Re: [hybi] WS ABNF Pieter Hintjens
- Re: [hybi] WS ABNF Dave Cridland
- Re: [hybi] WS ABNF Dave Cridland
- Re: [hybi] WS ABNF Greg Wilkins
- Re: [hybi] WS ABNF Scott Ferguson
- Re: [hybi] WS ABNF Dave Cridland
- Re: [hybi] WS ABNF Scott Ferguson
- Re: [hybi] WebSocket feedback Thomson, Martin
- [hybi] WebSocket feedback Ian Hickson
- Re: [hybi] WebSocket feedback Ian Hickson
- Re: [hybi] WebSocket feedback Greg Wilkins
- Re: [hybi] WebSocket feedback Vladimir Katardjiev
- Re: [hybi] WebSocket feedback Greg Wilkins
- Re: [hybi] WebSocket feedback Greg Wilkins
- Re: [hybi] WebSocket feedback Vladimir Katardjiev
- [hybi] Publishing drafts, Re: WebSocket feedback Julian Reschke
- Re: [hybi] Publishing drafts, Re: WebSocket feedb… Julian Reschke
- [hybi] Framing, was Re: WebSocket feedback Dave Cridland
- Re: [hybi] WebSocket feedback Greg Wilkins
- Re: [hybi] WebSocket feedback Vladimir Katardjiev
- Re: [hybi] WebSocket feedback Greg Wilkins
- Re: [hybi] WebSocket feedback Joe Hildebrand
- Re: [hybi] WebSocket feedback Greg Wilkins
- Re: [hybi] WebSocket feedback Greg Wilkins
- Re: [hybi] WebSocket feedback Julian Reschke
- Re: [hybi] WebSocket feedback Mridul Muralidharan
- [hybi] requirement: backwards compatible?. was : … Greg Wilkins
- Re: [hybi] requirement: backwards compatible?. wa… Anne van Kesteren
- Re: [hybi] requirement: backwards compatible?. wa… Vladimir Katardjiev