IETF Logo Mail Archive

Re: [hybi] NAT reset recovery? Was: Extensibility mechanisms?

Pieter Hintjens <ph@imatix.com> Mon, 19 April 2010 20:09 UTC

Return-Path: <pieterh@gmail.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 4B7DD3A6B09 for <hybi@core3.amsl.com>; Mon, 19 Apr 2010 13:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.134
X-Spam-Level:
X-Spam-Status: No, score=-1.134 tagged_above=-999 required=5 tests=[AWL=0.843, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 raYNzpZCp0sO for <hybi@core3.amsl.com>; Mon, 19 Apr 2010 13:09:44 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 97FD43A6AF4 for <hybi@ietf.org>; Mon, 19 Apr 2010 13:09:44 -0700 (PDT)
Received: by pvf33 with SMTP id 33so3429215pvf.31 for <hybi@ietf.org>; Mon, 19 Apr 2010 13:09:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:received:message-id :subject:to:cc:content-type; bh=InNW3FCscng+GMeojz9g+MKWtTT9IBXa2irEzYuMgaY=; b=GDEyNQZJwo9ZQ+Olk2kJ4c7FYg6rcwlkzr4+eBbqao+sDL2bwn8MYNUvkwqhW2YC9E j1y7nfih93QxIf+X0/gD5wE2LpXg8sDxmMD/srTxmOd0Rcv/qxprmAuxT3BDuh0ZD5vS 2yqn7PAjXTg2KD8MFlMmA3wOf+YJcbZEjNrUQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=FSrxgOGgI4IpyHCGV/XLRSGMrWNq/iOQwBmoTxVetPcdZU7rsLcMU8NOUYiM95dZ3x X65W7XfL9lm6oLoQWMfi5qXp2y1yZlQ5f/XsSuCRoiS0u24onqpu2s844Peq2AippnCP JpaXivW38mVfYmkC8Mq/F5KVU+fcxQ2Pr2J54=
MIME-Version: 1.0
Sender: pieterh@gmail.com
Received: by 10.140.225.18 with HTTP; Mon, 19 Apr 2010 13:09:13 -0700 (PDT)
In-Reply-To: <B3F72E5548B10A4A8E6F4795430F841832040F78C0@NOK-EUMSG-02.mgdnok.nokia.com>
References: <Pine.LNX.4.64.1004181812370.751@ps20323.dreamhostps.com> <j2n5c4444771004181403o81184b00r294f3c3b878f24f6@mail.gmail.com> <20100419091736.GA28758@shareable.org> <p2w2a10ed241004190222ne3a61417i47b021dbe0422f71@mail.gmail.com> <B3F72E5548B10A4A8E6F4795430F841832040920C4@NOK-EUMSG-02.mgdnok.nokia.com> <20100419121000.GG28758@shareable.org> <87764B8E-5872-40EE-AA2F-D4E659B94F63@d2dx.com> <20100419140423.GC3631@shareable.org> <6959E9B3-B1AC-4AFB-A53D-AB3BA340208C@d2dx.com> <B3F72E5548B10A4A8E6F4795430F841832040F78C0@NOK-EUMSG-02.mgdnok.nokia.com>
From: Pieter Hintjens <ph@imatix.com>
Date: Mon, 19 Apr 2010 22:09:13 +0200
X-Google-Sender-Auth: 23e06130963642cb
Received: by 10.140.251.20 with SMTP id y20mr2148209rvh.206.1271707773247; Mon, 19 Apr 2010 13:09:33 -0700 (PDT)
Message-ID: <w2q5821ea241004191309t7362de42p922788d380119dc4@mail.gmail.com>
To: Markus.Isomaki@nokia.com
Content-Type: text/plain; charset="ISO-8859-1"
Cc: hybi@ietf.org
Subject: Re: [hybi] NAT reset recovery? Was: Extensibility mechanisms?
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: Mon, 19 Apr 2010 20:09:45 -0000

On Mon, Apr 19, 2010 at 9:53 PM,  <Markus.Isomaki@nokia.com> wrote:

> I think the websocket spec should define two special frames explicitly for
> keepalive purpose...

For what it's worth, the keep alive design from AMQP used only one
frame.  Senders are responsible for issuing KAs at regular intervals.
Receivers treat these as no-ops except to register "activity" on the
connection.  Any other frame also acts as activity, obviously.  If no
activity is received within X seconds, the connection can be killed.
There is no notion of request-response for KA in AMQP.

-Pieter

v2.23.0 | Report a Bug | By Email