[hybi] #2: Connection persistence requirements
"hybi issue tracker" <trac@tools.ietf.org> Wed, 12 May 2010 10:49 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 4F6733A6B21 for <hybi@core3.amsl.com>; Wed, 12 May 2010 03:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level:
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, 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 ofTGflG9fXHN for <hybi@core3.amsl.com>; Wed, 12 May 2010 03:49:29 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 351AE3A6B2F for <hybi@ietf.org>; Wed, 12 May 2010 03:49:28 -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 1OC9V8-0005tG-9p; Wed, 12 May 2010 03:49:18 -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:49:18 -0000
X-URL: http://tools.ietf.org/hybi/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/hybi/trac/ticket/2
Message-ID: <068.0df304963b661f922a187d8906f2e888@tools.ietf.org>
X-Trac-Ticket-ID: 2
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] #2: Connection persistence requirements
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:49:30 -0000
#2: Connection persistence requirements
-------------------------------------------+--------------------------------
Reporter: salvatore.loreto@… | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: websocket-requirements | Version:
Severity: - | Keywords:
-------------------------------------------+--------------------------------
There has been a long discussion on the mailing list about how to deal
with keepalives and connection failures due to NAT timer resets or
reboots.
here the mail thread: http://www.ietf.org/mail-
archive/web/hybi/current/msg01741.html
This ticket is being created to track the major discussion points and
check the consensus for eventual requirements.
--
Ticket URL: <http://trac.tools.ietf.org/wg/hybi/trac/ticket/2>
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.
- [hybi] #2: Connection persistence requirements hybi issue tracker