IETF Logo Mail Archive

Re: [hybi] I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt

Gabriel Montenegro <gmonte@microsoft.com> Thu, 02 September 2010 16:57 UTC

Return-Path: <gmonte@microsoft.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 D69F03A65A5 for <hybi@core3.amsl.com>; Thu, 2 Sep 2010 09:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level:
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 AKBSr3W7UMBW for <hybi@core3.amsl.com>; Thu, 2 Sep 2010 09:57:00 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id E49313A69A3 for <hybi@ietf.org>; Thu, 2 Sep 2010 09:56:45 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 2 Sep 2010 09:57:15 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.1.218.10; Thu, 2 Sep 2010 09:57:15 -0700
Received: from TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com ([169.254.5.40]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Thu, 2 Sep 2010 09:57:15 -0700
From: Gabriel Montenegro <gmonte@microsoft.com>
To: Julian Reschke <julian.reschke@gmx.de>, James Graham <jgraham@opera.com>
Thread-Topic: [hybi] I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt
Thread-Index: AQHLSiecTcuCS82oKkqUwTe7FRd7lZL/CmGAgAAEqoD//9p7cA==
Date: Thu, 02 Sep 2010 16:57:25 +0000
Message-ID: <CA566BAEAD6B3F4E8B5C5C4F61710C110FAFE4D7@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <20100901224502.0519B3A687C@core3.amsl.com> <4C7F8EE7.1040106@opera.com> <4C7F92D1.20106@gmx.de>
In-Reply-To: <4C7F92D1.20106@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt
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: Thu, 02 Sep 2010 16:57:00 -0000

The real issue here is that MUST is the right keyword if something is required for interoperability. A SHOULD means you are recommended to do a certain thing, but you may depart from that recommendation if you know better or have a good reason. MAY is for optional stuff. 

My take on it is that the basic framing is absolutely a MUST. Optional stuff like multiplexing or compression are MAYs (when and if we get to them). Fragmentation support sounds like a SHOULD.

> -----Original Message-----
> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
> Julian Reschke
> Sent: Thursday, September 02, 2010 5:05 AM
> To: James Graham
> Cc: hybi@ietf.org
> Subject: Re: [hybi] I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt
> 
> On 02.09.2010 13:47, James Graham wrote:
> > On 09/02/2010 12:45 AM, Internet-Drafts@ietf.org wrote:
> >
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-ietf-hybi-thewebsocketproto
> >> col-01.txt
> >>
> >
> > A few initial comments:
> >
> > The framing sections seem to have a lot of SHOULDs. This is worrying
> > as SHOULD-level conditions can't really be tested (it is not an error
> > to violate them) and can be a source of interoperability problems. I
> > would
>  > ...
> 
> Nothing stops you from testing them; you just need to either state that you
> reported SHOULD failures as violations, or need to report different compliance
> levels.
> 
> Best regards, Julian
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi

v2.23.0 | Report a Bug | By Email