[hybi] Additional WebSocket Close Error Codes

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 16 May 2012 09:40 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0BBDF21F8759 for <hybi@ietfa.amsl.com>; Wed, 16 May 2012 02:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id fKvtrmnMWbdl for <hybi@ietfa.amsl.com>; Wed, 16 May 2012 02:40:39 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id D2FC221F870B for <hybi@ietf.org>; Wed, 16 May 2012 02:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1337161237; d=isode.com; s=selector; i=@isode.com; bh=vUy9gYz40FBgeWL7zbce98JTD2Z0dWDsK3aCKNC7hwY=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=OqaeANTNYgU20hUBe0kzO2QdRs1SIAnrPBpFl3Qw81ABj7ZWx6Ne34JG7KOchEcjw76u4P JeBjIsoMWa6XL7CLiCv3zkFVI8N0h3BLgw6eL4YT0MUVgzS4kjIiy1i+baV//uDqQANCBe aLvFXZ8EOJL+ady40T8F9V7iRRGbzEI=;
Received: from [] ((unknown) []) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <T7N2FQAIRmUs@rufus.isode.com>; Wed, 16 May 2012 10:40:37 +0100
Message-ID: <4FB3765D.5060308@isode.com>
Date: Wed, 16 May 2012 10:41:49 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Hybi <hybi@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [hybi] Additional WebSocket Close Error Codes
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 May 2012 09:40:47 -0000

Hi WG,
I am sorry I didn't followup on this when the following 2 codes were 
suggested (See 

1012/Service Restart
1012 indicates that the service is restarted. a client may reconnect, 
and if it choses to do, should reconnect using a randomized delay of 5 - 

Use case:
restart a service with 100k clients connected
clients present an informative user notification ("service restarting .. 
reconnecting in N secs)
clients should not reconnect all at exactly the same time .. thus the 
randomized delay

1013/Service Overload
1013 indicates that the service is experiencing overload. a client 
should only connect to a different IP (when there are multiple for the 
target) or reconnect to the same IP upon user action.

Use case:
clients present an informative user notification ("service overload .. 
try later or try different IP)


Do people use these and is there still some interest in registering them?

Best Regards,