Re: [hybi] WebSocket Version Numbers

Greg Wilkins <gregw@intalio.com> Tue, 21 June 2011 23:40 UTC

Return-Path: <gregw@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B734111E8152 for <hybi@ietfa.amsl.com>; Tue, 21 Jun 2011 16:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.873
X-Spam-Level:
X-Spam-Status: No, score=-2.873 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSbdd8Z2Bq1n for <hybi@ietfa.amsl.com>; Tue, 21 Jun 2011 16:40:25 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1298611E8135 for <hybi@ietf.org>; Tue, 21 Jun 2011 16:40:24 -0700 (PDT)
Received: by vxi40 with SMTP id 40so281725vxi.31 for <hybi@ietf.org>; Tue, 21 Jun 2011 16:40:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.169.66 with SMTP id ac2mr3639063vdc.238.1308699624242; Tue, 21 Jun 2011 16:40:24 -0700 (PDT)
Received: by 10.52.108.9 with HTTP; Tue, 21 Jun 2011 16:40:24 -0700 (PDT)
In-Reply-To: <4E00A2FE.8010601@stpeter.im>
References: <20110621061036.ef1fc80126c74c6c202a919c41c7bb0b.7a63d337a6.wbe@email03.secureserver.net> <4E00A2FE.8010601@stpeter.im>
Date: Wed, 22 Jun 2011 09:40:24 +1000
Message-ID: <BANLkTin35icuwjNVbJc4fAsA0ezGj8HqJQ@mail.gmail.com>
From: Greg Wilkins <gregw@intalio.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org, Bob Gezelter <gezelter@rlgsc.com>
Subject: Re: [hybi] WebSocket Version Numbers
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: Tue, 21 Jun 2011 23:40:25 -0000

On 21 June 2011 23:56, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> On 6/21/11 7:10 AM, Bob Gezelter wrote:
> Once again I recommend borrowing from the text in RFC 6120 if
> appropriate, see Section 4.7.5...


+1

although I think we must now also say that a single integer should
considered a minor version with major version being 0.
So 8 == 0.8

cheers



> ###
>
>   The numbering scheme for XMPP versions is "<major>.<minor>".  The
>   major and minor numbers MUST be treated as separate integers and each
>   number MAY be incremented higher than a single digit.  Thus, "XMPP
>   2.4" would be a lower version than "XMPP 2.13", which in turn would
>   be lower than "XMPP 12.3".  Leading zeros (e.g., "XMPP 6.01") MUST be
>   ignored by recipients and MUST NOT be sent.
>
>   The major version number will be incremented only if the stream and
>   stanza formats or obligatory actions have changed so dramatically
>   that an older version entity would not be able to interoperate with a
>   newer version entity if it simply ignored the elements and attributes
>   it did not understand and took the actions defined in the older
>   specification.
>
>   The minor version number will be incremented only if significant new
>   capabilities have been added to the core protocol (e.g., a newly
>   defined value of the 'type' attribute for message, presence, or IQ
>   stanzas).  The minor version number MUST be ignored by an entity with
>   a smaller minor version number, but MAY be used for informational
>   purposes by the entity with the larger minor version number (e.g.,
>   the entity with the larger minor version number would simply note
>   that its correspondent would not be able to understand that value of
>   the 'type' attribute and therefore would not send it).