Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-07.txt
Dario Crivelli <dario.crivelli@lightstreamer.com> Thu, 28 March 2013 16:41 UTC
Return-Path: <dario.crivelli@lightstreamer.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 648CF21F8FC4 for <hybi@ietfa.amsl.com>; Thu, 28 Mar 2013 09:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.483
X-Spam-Level: *
X-Spam-Status: No, score=1.483 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_ILLEGAL_IP=1.908, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsHTlg8W55Cd for <hybi@ietfa.amsl.com>; Thu, 28 Mar 2013 09:41:25 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4274521F8EEC for <hybi@ietf.org>; Thu, 28 Mar 2013 09:41:24 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hn17so3500640wib.16 for <hybi@ietf.org>; Thu, 28 Mar 2013 09:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lightstreamer.com; s=google; h=x-received:mime-version:x-originating-ip:from:date:message-id :subject:to:content-type; bh=3Px9nVreRYqvAYioiyGTQaiMDpsOGuLYtXwkDOlwVPQ=; b=TXrdlh4YOWQY53FnacHQ8gWGghiPeSoVcvEOiCV96NNu20G479mzLR/yEClihWhq/t zlFWPq8vEFeVhr2eolRHeQIbwDJYL5LjEO1z+DXFA0bEw5gGgzrhvLTUmhEnnQi7DuzC eybFdbOX/yGBh7Qdf5Pr2fpU5zZlNXXzwb+PA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-originating-ip:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=3Px9nVreRYqvAYioiyGTQaiMDpsOGuLYtXwkDOlwVPQ=; b=jAryijwZrHxAbEKcqppaldXWqiVerHAG4QSrOJBZe9GccpmhgHE8l8/QR5sv5SsJUp xC7mD0osdZKEMFFwLSS/c9r/QpSDfwxuOdX25lgq4gtTaNDMAnYXiSwMHyOFqlLo2foj WGMPRrEAIq828qX8pcz/JQLTSdBDb8IRnTvH0+EQrgVyAHVezSSjaYVMsxe9YABmTdn1 J3A1Mjb0iaLlxxv+zjvpVkx9z/ZB8me2ugRenOgZcIeM++xzJsmV5ge6jk3QdMiTpoXA hJXyM5kq+cT4stCHyit4LzxMVQGT1R8j/ppZEO7iI/66t2LoVGmddCgIdwSQUYrDN2IU OIkw==
X-Received: by 10.194.235.196 with SMTP id uo4mr39490082wjc.30.1364488884209; Thu, 28 Mar 2013 09:41:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.104.199 with HTTP; Thu, 28 Mar 2013 09:41:04 -0700 (PDT)
X-Originating-IP: [2.238.52.66]
From: Dario Crivelli <dario.crivelli@lightstreamer.com>
Date: Thu, 28 Mar 2013 17:41:04 +0100
Message-ID: <CAPwYjp=0NZEbY7Feod7UeHiFaT5pfm85rkpV6KByjcsB72MxLw@mail.gmail.com>
To: hybi@ietf.org, Takeshi Yoshino <tyoshino@google.com>
Content-Type: multipart/alternative; boundary="089e01419d7c3e645104d8fed3d8"
X-Gm-Message-State: ALoCoQk7wEnELl6dTVJDhr/TZd2sd6aCqghY7ddFCsOUP4v4lj+RBZrk2auDd0mLFi7F8wUNNOya
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-07.txt
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: Thu, 28 Mar 2013 16:41:27 -0000
Hi Takeshi, Regarding the observations I expressed about version 05 of the draft, I confirm that the new text, along with your answers by email, do clarify my doubts. In the new version, I found just a few unclear points. We know from RFC4655 (and also from the permessage-deflate extension case) that when a server accepts a PMCE offer, it can use, in the response, parameters different from those used in the offer; as a consequence, the extension specification should determine when the response parameters are legal with respect to the offer. In the description of the general negotiation mechanism, in paragraph 4, as far as I can see, this is not restated explicitly. I suggest restating that, though redundantly, because the description of the offering/acceptance mechanism may be misleading. In fact, the mechanism allows the client to include multiple offers of the same PMCE with different parameters; so, this may deceive one into thinking that the acceptance only consists in the server choosing one of the offerings as is, with no further freedom to use different parameters in the response. In paragraph 6.2 the following form is used several times: "If a server accepts an offer with ..." I think that the concept of "accepting an offer" should only pertain to paragraph 6.1. In paragraph 6.2 we are referring to the configuration parameters already agreed-upon. I see that in paragraph 4 there is a mention to "the configuration parameters of the PMCE to use in detail" which would be a better reference point, although it is not formally defined. Do you think that introducing a concept similar to the _Extensions In Use_ of RFC6455 would be worthwhile? I'm still concerned about how multiple extensions can coexist and how this specification can interoperate with specifications of other extensions. With reference to paragraph 5.1, as far as this specification is meant as a specialization of RFC6455, it is clear how the indicated steps should replace the corresponding base steps in RFC6455 (even though RFC6455 was not expressed in terms of steps). However, the specification in paragraph 5.1 replaces the base steps from the "payload data portion of the original message" to the frames being sent. It seems to me that this formulation excludes in advance the cooperation with any other extension, otherwise conflicts in the two specifications would arise and it might not be obvious how the two specifications should merge. On the other hand, I think it is obvious to all of us that a PMCE should only operate on the message payload and should not interfere with any extension to be applied subsequently (operating either on the payload or on the frames), provided that it doesn't conflict on the use of the RSV1 bit. I'm not sure if the current specification conveys this idea. By the way, in paragraph 4 it is said that an extension can be "applied to output of" another extension; however, in RFC6455 I can only find the concept of an "order of operations" (in 9.1), which seems to me a broader one. Regards Dario Crivelli > Message: 2 > Date: Tue, 19 Mar 2013 17:36:48 +0900 > From: Takeshi Yoshino <tyoshino@google.com> > To: "hybi@ietf.org" <hybi@ietf.org> > Subject: Re: [hybi] I-D Action: > draft-ietf-hybi-permessage-compression-07.txt > Message-ID: > < > CAH9hSJZCFZpvQPjVsRXDGeLD8BNSttoEHVU6PNupjv4F548a0A@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Reorganization, rephrasing, grammar correction. > > I'm happy if someone could take a look. > > Takeshi > >
- Re: [hybi] I-D Action: draft-ietf-hybi-permessage… Dario Crivelli
- [hybi] I-D Action: draft-ietf-hybi-permessage-com… internet-drafts
- Re: [hybi] I-D Action: draft-ietf-hybi-permessage… Takeshi Yoshino
- Re: [hybi] I-D Action: draft-ietf-hybi-permessage… Takeshi Yoshino
- Re: [hybi] I-D Action: draft-ietf-hybi-permessage… Dario Crivelli
- Re: [hybi] I-D Action: draft-ietf-hybi-permessage… Takeshi Yoshino