Re: [hybi] Proposal: HTTP upgrade process

"Shelby Moore" <shelby@coolpage.com> Tue, 17 August 2010 12:55 UTC

Return-Path: <shelby@coolpage.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 579AC3A6960 for <hybi@core3.amsl.com>; Tue, 17 Aug 2010 05:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.831
X-Spam-Level:
X-Spam-Status: No, score=-1.831 tagged_above=-999 required=5 tests=[AWL=0.768, 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 9dgq7qf3AYCF for <hybi@core3.amsl.com>; Tue, 17 Aug 2010 05:55:06 -0700 (PDT)
Received: from www5.webmail.pair.com (www5.webmail.pair.com [66.39.3.83]) by core3.amsl.com (Postfix) with SMTP id 48A6B3A695D for <hybi@ietf.org>; Tue, 17 Aug 2010 05:55:06 -0700 (PDT)
Received: (qmail 43045 invoked by uid 65534); 17 Aug 2010 12:55:41 -0000
Received: from 121.97.54.174 ([121.97.54.174]) (SquirrelMail authenticated user shelby@coolpage.com) by sm.webmail.pair.com with HTTP; Tue, 17 Aug 2010 08:55:41 -0400
Message-ID: <f9a51a59f44f8d90dcf85f248542d9c6.squirrel@sm.webmail.pair.com>
In-Reply-To: <4C6A8110.90502@ericsson.com>
References: <AANLkTi=aR8+LgcoXDVhuu-HC2k3TB6YP2WcXEo8yC1Jz@mail.gmail.com> <A311A6D0-B88B-4842-867C-A9D254DE0132@apple.com> <4C6A8110.90502@ericsson.com>
Date: Tue, 17 Aug 2010 08:55:41 -0400
From: Shelby Moore <shelby@coolpage.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: hybi@ietf.org
Subject: Re: [hybi] Proposal: HTTP upgrade process
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shelby@coolpage.com
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: Tue, 17 Aug 2010 12:55:07 -0000

[snip]

> So in order to move the work forward I would invite people to send out
> text (in an adhoc thread) proposing an handshake that address all the
> concerns raised from
> different people (in the same way is happening for the frame issue).

Process question follows.

I understand you are referring to moving forward on the handshake for WS
on HTTP port 80.  I understand that can be an orthogonal process to
decisions about whether we should use HTTP port 80 for WS.

I have an unanswered question/challenge about whether we can use HTTP port
80 for WS reliably:

http://www.ietf.org/mail-archive/web/hybi/current/msg03299.html
http://www.ietf.org/mail-archive/web/hybi/current/msg03303.html

What is the standard process to follow? Is the standard or amicable
procedure to assume that if no one replies a challenge, then the challenge
does not deserve merit, or to assume it was correct on merits? Or is the
interpretation an individual decision and ambigious for the group
decision?

I intuitively understand that a WG is a concensus building process, so am
I correct to assume that if no one replies to a challenge, then it means
you've been effectively told that your ideas are not worthy?

Thanks in advance for the clarification on process.