
From yang.r.yang@gmail.com  Tue Apr  2 14:00:22 2013
Return-Path: <yang.r.yang@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8C521F8A66 for <alto@ietfa.amsl.com>; Tue,  2 Apr 2013 14:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 WhIVM762-EG2 for <alto@ietfa.amsl.com>; Tue,  2 Apr 2013 14:00:21 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id C7DDC21F8A51 for <alto@ietf.org>; Tue,  2 Apr 2013 14:00:21 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id y10so451377pdj.12 for <alto@ietf.org>; Tue, 02 Apr 2013 14:00:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2FnTPEsXnLJFiXiQmTL/KRNzIXD20vqrn515PSDUZdI=; b=mLGc7REcJV/DfyaN6XutLjAOZERb6xT0qbaOQSAn6uWnRIUPVmN0PZuKCa9WPbIc4H lWmX6yjfpNXP6AmZ6A5itrhOAQ4RfAd50DomjabImGQWtMBebW/SO7DxlAztv0g9G3G+ IZSThS9D53k4egKawcyF1hWMSMwzAyGI42fcBw2VRdfO1MXRTkGVnhaRsEMeKuQBkcc6 zzSDHueNxVJ80vJJ51nWEphDytMF87zU7dYKwO9AF6uMmFFBrfnIE65tOR7OlA5DtPA3 9ViXKBl0Ln12I4zCSAjcQPGoOfoRZrGJgHqZrwqD06nwrIiv+GcNWbETuf9RHMqdxAjc dUSg==
MIME-Version: 1.0
X-Received: by 10.66.253.232 with SMTP id ad8mr27694113pad.119.1364936421638;  Tue, 02 Apr 2013 14:00:21 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.68.131.2 with HTTP; Tue, 2 Apr 2013 14:00:21 -0700 (PDT)
In-Reply-To: <CD7087F3.40448%w.roome@alcatel-lucent.com>
References: <CD7087F3.40448%w.roome@alcatel-lucent.com>
Date: Tue, 2 Apr 2013 17:00:21 -0400
X-Google-Sender-Auth: vPMDesS0p4bijMRAcj9vtXxd-io
Message-ID: <CANUuoLqekwWsJGu53dFKqiufno2bOWEu5kC_oZx6aBTVjQjCRg@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=047d7b15b20d8d886504d96706ed
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Interop question: How strict should a server be?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 21:00:22 -0000

--047d7b15b20d8d886504d96706ed
Content-Type: text/plain; charset=ISO-8859-1

Hi Wendy,

I am not sure if there is a precise answer to your question. In an ideal,
simplistic setting, rejecting a non-conforming request is the correct
behavior. On the other hand, we have the Postel's Law saying that your
server accepting the request, despite that the request misses some
parameters, is reasonable, as long as there is a reasonable interpretation.

Richard


On Thu, Mar 21, 2013 at 9:48 AM, Wendy Roome <w.roome@alcatel-lucent.com>wrote:

> I just discovered that the current draft requires the client to provide
> the cost-type and cost-mode parameters for a filtered cost map request.
> Early drafts said they were optional, with defaults of routingcost and
> numerical. I hadn't noticed the change, so my ALTO server still treats
> them as optional.
>
> As a result, my server accepts requests that other servers reject. Clients
> may think that those other servers are broken, while in reality, my server
> is incorrect. Some of you may recall a parallel with the browser wars of
> the 90s. Internet Explorer tolerated common HTML errors, while Netscape
> didn't. Pages that looked fine in Explorer didn't work in Netscape, so
> users (and some developers!) thought that Netscape wasn't working.
>
> So here's my question for the group: how strictly should a server enforce
> such rules? And should our interop tests check for strict enforcement of
> required parameters?
>
>         - Wendy Roome
>
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--047d7b15b20d8d886504d96706ed
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Wendy,<div><br></div><div style>I am not sure if there =
is a precise answer to your question. In an ideal, simplistic setting, reje=
cting a non-conforming request is the correct behavior. On the other hand, =
we have the Postel&#39;s Law saying that your server accepting the request,=
 despite that the request misses some parameters, is reasonable, as long as=
 there is a reasonable interpretation.</div>
<div style><br></div><div style>Richard</div></div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Thu, Mar 21, 2013 at 9:48 AM, Wend=
y Roome <span dir=3D"ltr">&lt;<a href=3D"mailto:w.roome@alcatel-lucent.com"=
 target=3D"_blank">w.roome@alcatel-lucent.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I just discovered that the current draft req=
uires the client to provide<br>
the cost-type and cost-mode parameters for a filtered cost map request.<br>
Early drafts said they were optional, with defaults of routingcost and<br>
numerical. I hadn&#39;t noticed the change, so my ALTO server still treats<=
br>
them as optional.<br>
<br>
As a result, my server accepts requests that other servers reject. Clients<=
br>
may think that those other servers are broken, while in reality, my server<=
br>
is incorrect. Some of you may recall a parallel with the browser wars of<br=
>
the 90s. Internet Explorer tolerated common HTML errors, while Netscape<br>
didn&#39;t. Pages that looked fine in Explorer didn&#39;t work in Netscape,=
 so<br>
users (and some developers!) thought that Netscape wasn&#39;t working.<br>
<br>
So here&#39;s my question for the group: how strictly should a server enfor=
ce<br>
such rules? And should our interop tests check for strict enforcement of<br=
>
required parameters?<br>
<br>
=A0 =A0 =A0 =A0 - Wendy Roome<br>
<br>
<br>
<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote></div><br></div>

--047d7b15b20d8d886504d96706ed--

From johnsonhammond2@hushmail.com  Sat Apr 27 15:48:29 2013
Return-Path: <johnsonhammond2@hushmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D713A21F8EA5 for <alto@ietfa.amsl.com>; Sat, 27 Apr 2013 15:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level: 
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130,  BAYES_00=-2.599]
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 MW+QRyTtsUdg for <alto@ietfa.amsl.com>; Sat, 27 Apr 2013 15:48:29 -0700 (PDT)
Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by ietfa.amsl.com (Postfix) with ESMTP id 056A821F8899 for <alto@ietf.org>; Sat, 27 Apr 2013 15:48:29 -0700 (PDT)
Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by smtp2.hushmail.com (Postfix) with SMTP id 59360E7CF8 for <alto@ietf.org>; Sat, 27 Apr 2013 17:17:33 +0000 (UTC)
X-hush-relay-time: 211
X-hush-relay-id: b1bd903faba185ee07e5a0ed3a1fde37
Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52]) by smtp2.hushmail.com (Postfix) with ESMTP for <alto@ietf.org>; Sat, 27 Apr 2013 17:17:33 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id 1A16914DBDE; Sat, 27 Apr 2013 17:17:33 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 27 Apr 2013 13:17:32 -0400
To: alto@ietf.org
From: johnsonhammond2@hushmail.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20130427171733.1A16914DBDE@smtp.hushmail.com>
Subject: [alto] Biggest Fake Conference in Computer Science
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Apr 2013 22:48:30 -0000

Biggest Fake Conference in Computer Science


We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.


We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware


Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 


We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the 
conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of
http://sites.google.com/site/dumpconf for comments from well-known researchers 
about WORLDCOMP. 


The status of your WORLDCOMP papers can be changed from scientific
to other (i.e., junk or non-technical) at any time. Better not to have a paper than 
having it in WORLDCOMP and spoil the resume and peace of mind forever!


Our study revealed that WORLDCOMP is a money making business, 
using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing 
out a small chunk of that money (around 20 dollars per paper published 
in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) 
who publicizes WORLDCOMP and also defends it at various forums, using 
fake/anonymous names. The puppet uses fake names and defames other conferences
to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to 
threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). 
That is, the puppet does all his best to get a maximum number of papers published 
at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. 


Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has 
refused to provide the venue for WORLDCOMP’13 because of the fears of their image 
being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 
is taking place at a different resort. WORLDCOMP will not be held after 2013. 


The draft paper submission deadline is over but still there are no committee 
members, no reviewers, and there is no conference Chairman. The only contact 
details available on WORLDCOMP’s website is just an email address! 

Let us make a direct request to Prof. Hamid arabnia: publish all reviews for 
all the papers (after blocking identifiable details) since 2000 conference. Reveal 
the names and affiliations of all the reviewers (for each year) and how many 
papers each reviewer had reviewed on average. We also request him to look at 
the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 


Sorry for posting to multiple lists. Spreading the word is the only way to stop 
this bogus conference. Please forward this message to other mailing lists and people. 


We are shocked with Prof. Hamid Arabnia and his puppet’s activities 
http://worldcomp-fake-bogus.blogspot.com   Search Google using the 
keyword worldcomp fake for additional links.


From michael.scharf@alcatel-lucent.com  Mon Apr 29 03:54:18 2013
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D467921F9D2E for <alto@ietfa.amsl.com>; Mon, 29 Apr 2013 03:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.39
X-Spam-Level: 
X-Spam-Status: No, score=-8.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 2JSrPYL2mSYZ for <alto@ietfa.amsl.com>; Mon, 29 Apr 2013 03:54:18 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2FEEA21F9D24 for <alto@ietf.org>; Mon, 29 Apr 2013 03:54:17 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r3TAsFkg003907 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <alto@ietf.org>; Mon, 29 Apr 2013 12:54:15 +0200
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 29 Apr 2013 12:54:15 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "alto@ietf.org" <alto@ietf.org>
Date: Mon, 29 Apr 2013 12:54:14 +0200
Thread-Topic: Duplicate entries in resource directory?
Thread-Index: Ac5Ex+NfQSty5wN7TKiMiVU8Qm2EZw==
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AB12A726F@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: [alto] Duplicate entries in resource directory?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 10:54:19 -0000

Hi all,

draft -14 states regarding multiple entries in the directory:
  =20
   It is possible that multiple entries in the directory match a desired
   Information Resource.  For instance, in the example in Section 7.6.3,
   a full Cost Map with "numerical" Cost Mode and "routingcost" Cost
   Type could be retrieved via a GET request to
   "http://alto.example.com/costmap/num/routingcost", or via a POST
   request to "http://custom.alto.example.com/costmap/filtered".

Is my understanding correct that a directory response with duplicate entrie=
s for the exactly same service (including the same cost mode etc.) is allow=
ed as well?

Example for network map:

   HTTP/1.1 200 OK
   Content-Length: 1472
   Content-Type: application/alto-directory+json

   {
     "resources" : [
       {
         "uri" : "http://alto.example.com/networkmap",
         "media-types" : [ "application/alto-networkmap+json" ]
       },
       {
         "uri" : "http://alto2.example.com/alternative/networkmap,
         "media-types" : [ "application/alto-networkmap+json" ]
       }
     ]
   }

We just wonder what an ALTO client should do if it gets such a response - p=
robably it would pick a random URI. This could actually achieve some simple=
 load balancing.

Thanks

Michael
