Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt

Константин Буркалев <kostik.hunter@gmail.com> Mon, 14 September 2015 16:57 UTC

Return-Path: <kostik.hunter@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E6D01B35F2 for <hybi@ietfa.amsl.com>; Mon, 14 Sep 2015 09:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FSL_MY_NAME_IS=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FyNJ4PZ0CpNG for <hybi@ietfa.amsl.com>; Mon, 14 Sep 2015 09:57:36 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F33431B2EE3 for <hybi@ietf.org>; Mon, 14 Sep 2015 09:57:35 -0700 (PDT)
Received: by lamp12 with SMTP id p12so89894001lam.0 for <hybi@ietf.org>; Mon, 14 Sep 2015 09:57:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=35Vabkp9FBdXV03XPegeTGvnCw2hQzdEoCNmwXDjrts=; b=RCbA6xqLesfDhCvMlSxY/TKhHXMPZN49g5l9jRLtVOsLvPk7KLAAAX8ZLZTM5hdvLc ZHqKwkO5/yBZd3sGEEctwuFjNLR70QAXyTwxwaF1C6b001LdE5hddfltykBz8LUsjnO6 QT9ufte7dPYGV6/HMIG7awiBUjEPtzRrlrinoita2kOVOJI8muBberJvm6y5N3pofyat oezq2b0j1YXsgGTYl3CLb05Ryj1IG0BsVvw8ppywD50vMML2RtfXWSZ40LgJIXxFTQew VImJ1UMS05CJsTE90pRX2daTjdHYOhJXCHEDXv7fN2PqvR7Ly2ATkQecFjuYZvG3yhCz 4PkA==
X-Received: by 10.112.25.69 with SMTP id a5mr15333279lbg.16.1442249854109; Mon, 14 Sep 2015 09:57:34 -0700 (PDT)
Received: from [192.168.24.200] ([212.83.3.189]) by smtp.gmail.com with ESMTPSA id k15sm2547612laa.30.2015.09.14.09.57.33 for <hybi@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Sep 2015 09:57:33 -0700 (PDT)
From: Константин Буркалев <kostik.hunter@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B53D5F4E-C6BF-4A23-A48E-296C242940F4"
Message-Id: <8027DC26-AE4B-4988-B6D5-9D57F090A518@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Date: Mon, 14 Sep 2015 19:57:31 +0300
References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <CAH9hSJbDBih=-pc=F0E9=7hLcL+nyHo+qc=nvsYaXmV=hiA7ZQ@mail.gmail.com> <CAC4RtVAgrr5jK9xu3PfEqbmC8fB6pfZ98SDR6z+yKyRBEgcFSA@mail.gmail.com> <CAH9hSJYLDrio25+vboJ1GzsW937s2yRURjhdXhT5A25bDKdOyw@mail.gmail.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <CAC4RtVDbC7+DD84MULXDa0wPuud_1msLdy4AdLoQN7_x8HHAbw@mail.gmail.com> <55F5E021.2000803@tavendo.de> <CAH9hSJaoU273_jSOYWYuPvtRO3+v6p0a4Xjup-fLzkzU2JuPAw@mail.gmail.com> <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> <55F6AFA1.9070404@tavendo.de> <CALaySJJ_srH+URwOxart+rwYkOJ2je7X0UfX-ek99h_tiK+hag@mail.gmail.com>
To: hybi@ietf.org
In-Reply-To: <CALaySJJ_srH+URwOxart+rwYkOJ2je7X0UfX-ek99h_tiK+hag@mail.gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/KNogD5C8AekeAzj9y13mNpVgueE>
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Sep 2015 17:06:49 -0000

Hi, Barry, Salvatore and all!

My name is Konstantin, i’m a software architect in telecommunication company, 
also i’m author and maintainer of 3 WAMP implementations.

Just want to say, that from my point of view there is enough interest in WAMP libraries, 
which, of course, are based on WAMP protocol. 
I am already involved in development of WAMP spec, and i’m willing to continue work on WAMP as RFC.

I know different cases of WAMP usage, among them there are:
* IoT devices and systems, I’m also working on a subject. And right now small chips and devices (for ex. ESP8266) support only http/1.1.
* Mobile applications, based on JavaScript engines and platforms like React Native
And so on. 

We (i mean WAMP implementators, like Tobias or Emile) are already doing a big work in developing WAMP specification and fulfilling the gaps, and there are more and more 
people, involved in WAMP community. Just check the WAMP mailing list (https://groups.google.com/forum/#!forum/wampws <https://groups.google.com/forum/#!forum/wampws>)


> 14 сент. 2015 г., в 16:20, Barry Leiba <barryleiba@computer.org> написал(а):
> 
>>> In order for the wg to be recharted / resurrected
>>> It is necessary to be enough interest in the work from several
>>> peoples/companies on the items
>> 
>> I figured that, and asked around in the WAMP community:
> ...
>> How "much" interest is needed? How should we "proof"? Should I ask all to
>> speak up on this mailing list?
> 
> It's hard to put a number on it, but there needs to be enough interest
> and commitment to participate that we can rely on progressing
> documents and getting meaningful review.  We have been having a lot of
> trouble with that over the past couple of *years*, so it's not just a
> moderate slowdown.
> 
> That said, if we really *do* have enough commitment, I'm willing to
> recharter the working group.  I can't speak for the chairs about
> whether they're willing to continue, but perhaps we could get new
> chairs to take it forward -- Salvatore and Gabriel have chaired this
> working group for a long time now.
> 
>> So do we need a draft RFC written _before_ we can request to recharter the
>> WG?
> 
> We don't *need* it, though a draft and some reviews of it would be
> some evidence that there's enough interest.
> 
>>> At moment it seems that people are more interested to evolve HTTP2 then
>>> in WebSocket.
>> 
>> Not sure, maybe there is a misunderstanding: what we would like to work on
>> is a specific WebSocket _subprotocol_: an application layer protocol on top
>> of WebSocket. We don't want to work on a WebSocket V2.0 or such.
> 
> The point is that implementors are less interested in implementing
> websocket things, now that http/2 is here.  Layering things on
> websockets might not be very useful if implementors are moving to
> http/2 instead, for such functions in the future.
> 
> But, again, if there really is enough interest in implementing new
> function on websockets, and we can see that interest in commitment to
> work on the specs, then that might be fine.
> 
> Barry
> 
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi

With best regards, KOsTIK
kostik.hunter@gmail.com