Re: [hybi] Reliable message delivery (was Re: Technical feedback.)

Salvatore Loreto <salvatore.loreto@ericsson.com> Sun, 07 March 2010 18:43 UTC

Return-Path: <salvatore.loreto@ericsson.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 DEF1F28C16B for <hybi@core3.amsl.com>; Sun, 7 Mar 2010 10:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level:
X-Spam-Status: No, score=-2.69 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599]
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 AqDRzDA9mbXw for <hybi@core3.amsl.com>; Sun, 7 Mar 2010 10:43:56 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id A99383A8A37 for <hybi@ietf.org>; Sun, 7 Mar 2010 10:43:55 -0800 (PST)
X-AuditID: c1b4fb39-b7c2dae000007b99-98-4b93f3ed93f2
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 7A.C3.31641.DE3F39B4; Sun, 7 Mar 2010 19:43:57 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Sun, 7 Mar 2010 19:43:57 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Sun, 7 Mar 2010 19:43:56 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 144AB2522; Sun, 7 Mar 2010 20:43:57 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id C70544EF88; Sun, 7 Mar 2010 20:43:56 +0200 (EET)
Received: from [IPv6:::1] (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 2E65E4E87E; Sun, 7 Mar 2010 20:43:56 +0200 (EET)
Message-ID: <4B93F3EB.3070606@ericsson.com>
Date: Sun, 07 Mar 2010 20:43:55 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: Adam Barth <ietf@adambarth.com>
References: <06912AB8-D55D-46F4-AAEC-0A2146FB3BB8@apple.com> <292090.96637.qm@web95403.mail.in2.yahoo.com> <5c902b9e1002030855u13d07708pc6af886d00dc33ce@mail.gmail.com> <4B69AC26.70606@caucho.com> <4B93EF2C.60808@ericsson.com> <5c4444771003071034q21abb408u963d52f4bff2f4b8@mail.gmail.com>
In-Reply-To: <5c4444771003071034q21abb408u963d52f4bff2f4b8@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 07 Mar 2010 18:43:57.0040 (UTC) FILETIME=[24E36F00:01CABE26]
X-Brightmail-Tracker: AAAAAA==
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
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: Sun, 07 Mar 2010 18:43:57 -0000

On 03/07/2010 08:34 PM, Adam Barth wrote:
> On Sun, Mar 7, 2010 at 10:23 AM, Salvatore Loreto
> <salvatore.loreto@ericsson.com>  wrote:
>    
>> in the HyBi charter we clearly state:
>>
>>   Wide browser support is a goal for the bidirectional communication
>>   mechanism, however the solution should also be suitable for clients
>>   other than Web Browsers.
>>
>> so the protocol MUST support also non-browser clients.
>>      
> Doesn't that say "should" rather than "must"?
>
> Adam
>    
you are right Adam,  it is a should ...
but it is in some way more that a should if we consider
the following statement in the charter:

  The Working Group will work to standardize a
   generic solution that can work efficiently in as many of the deployed
   environments as possible and in particular in all the elements of the
   web infrastructure (e.g. web browser, generic HTTP client, HTTP server
   and HTTP-aware intermediaries like proxies, load balancers, caches,
   etc.) and it is not specific for just one.


in any case at moment we do not have any requirement about it;

do people think it would be better have a specific one
in the requirement draft?


/Sal

Salvatore Loreto
www.sloreto.com