IETF Logo Mail Archive

[hybi] #1: HTTP Compliance

"hybi issue tracker" <trac@tools.ietf.org> Wed, 12 May 2010 10:37 UTC

Return-Path: <trac@tools.ietf.org>
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 8B5FE3A6963 for <hybi@core3.amsl.com>; Wed, 12 May 2010 03:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.471
X-Spam-Level:
X-Spam-Status: No, score=-101.471 tagged_above=-999 required=5 tests=[AWL=-0.730, BAYES_20=-0.74, NO_RELAYS=-0.001, 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 eSqku0SjVROu for <hybi@core3.amsl.com>; Wed, 12 May 2010 03:37:32 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id E59E03A67EA for <hybi@ietf.org>; Wed, 12 May 2010 03:37:32 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1OC9JZ-0003I5-8X; Wed, 12 May 2010 03:37:21 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: hybi issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: salvatore.loreto@ericsson.com
X-Trac-Project: hybi
Date: Wed, 12 May 2010 10:37:21 -0000
X-URL: http://tools.ietf.org/hybi/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/hybi/trac/ticket/1
Message-ID: <068.d07026741c6694cd80652d2a7d34f236@tools.ietf.org>
X-Trac-Ticket-ID: 1
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: salvatore.loreto@ericsson.com, hybi@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Sat, 15 May 2010 15:32:49 -0700
Cc: hybi@ietf.org
Subject: [hybi] #1: HTTP Compliance
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
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, 12 May 2010 10:37:33 -0000

#1: HTTP Compliance
-------------------------------------------+--------------------------------
 Reporter:  salvatore.loreto@…             |       Owner:     
     Type:  defect                         |      Status:  new
 Priority:  major                          |   Milestone:     
Component:  websocket-requirements         |     Version:     
 Severity:  -                              |    Keywords:     
-------------------------------------------+--------------------------------
 REQ.7 currently states:

      When sharing host and "well known" port with HTTP, the
      WebSocket protocol MUST be HTTP compatible until both ends have
      established the WebSocket protocol.

 at the Anaheim meeting there was some consensus to change this to "HTTP
 compliant".
 However there is a lot of misunderstanding about what compliance to HTTP
 means and implies.
 The Requirement draft should clarify it, as it may have non trivial impact
 on the protocol design.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/hybi/trac/ticket/1>
hybi <http://tools.ietf.org/hybi/>
The Hypertext-Bidirectional (HyBi) working group will seek
standardization of one approach to maintain bidirectional
communications between the HTTP client, server and intermediate
entities, which will provide more efficiency compared to the current
use of hanging requests.

v2.23.0 | Report a Bug | By Email