[alto] some comments on "ALTO for the blockchain draft-hommes-alto-blockchain-02"
Lili Liu <lili.liu@yale.edu> Thu, 29 June 2017 22:25 UTC
Return-Path: <lili.liu@yale.edu>
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 5384412773A for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 ldmggdYIajhB for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:25:43 -0700 (PDT)
Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (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 6C86A12EA6A for <alto@ietf.org>; Thu, 29 Jun 2017 15:25:42 -0700 (PDT)
Received: by mail-qt0-x244.google.com with SMTP id w12so13013713qta.2 for <alto@ietf.org>; Thu, 29 Jun 2017 15:25:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=uP/umbp2HFXoBGon0f//94B/po6W439HLLdS9T/aLIE=; b=fWRF6JSuo14tk7pmIT02be0rDaKvJ0DjRs5aTDvbUzrNShwisYmvriNM9sw+0jqmfl AKUMbzgQIfqxdiFHrpXH8PD4HAbkOiGPHG32Z3YSPFpGiNz3Ly5nX9yfZVouzvxoSrRU nYh2k7C30Gq9qBusnoI3F10BGNEBXpU7UCPUo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=uP/umbp2HFXoBGon0f//94B/po6W439HLLdS9T/aLIE=; b=dk87594UmQ6ZfM/LaikSO7I9khf3UjG/IMq/9fCsilrpGJYAtzhSSUx+HuTnu7mdvS r9N1htr7keaTi62cdsnP3E3q8fdFIPuNBE8fo2BMhUlHnJ3E5M6b2bty1p6a3jf40L9Y AZ6UbLOBMFFUU2IJmoj5Si4RaT4KbIErlombhXgnHA2cTA2Q5+axCITATxQdgqDajSfn AjeUqBfp1C6czDdTgQ/YKyQdrnK9GTEwWmuv21Msozge3qogmuFH904QxeoK6497aUNV AWX6hXVQMVpvfxHUMduqhM/ebvP625BDy0AIACrT530Zb+pQnc2iySxIc3FrFQFuBssa 8tKw==
X-Gm-Message-State: AKS2vOw9ukfCa0OThvYtoA2WMyFxG8JyLuIfwZYn9G8yy8YePT0vJtwU 7XYiBYb1e+btJFkorS4vDA==
X-Received: by 10.200.42.27 with SMTP id k27mr23969123qtk.40.1498775141230; Thu, 29 Jun 2017 15:25:41 -0700 (PDT)
Received: from [192.168.0.19] (cpe-66-108-205-11.nyc.res.rr.com. [66.108.205.11]) by smtp.gmail.com with ESMTPSA id m3sm4612254qkd.58.2017.06.29.15.25.40 for <alto@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 29 Jun 2017 15:25:40 -0700 (PDT)
From: Lili Liu <lili.liu@yale.edu>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C5FEE81-4696-4817-9C57-3139E4CD7223@yale.edu>
Date: Thu, 29 Jun 2017 18:25:39 -0400
To: alto@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/7cuCZgtsTPq2iz8qiQtR5J3kYqw>
Subject: [alto] some comments on "ALTO for the blockchain draft-hommes-alto-blockchain-02"
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 29 Jun 2017 22:26:47 -0000
Dear everyone, I’ve been reading "ALTO for the blockchain draft-hommes-alto-blockchain-02” recently, and I have some opinions on the draft. The authors present the benefits of ALTO in a blockchain network, and consider three categories of blockchain networks: private, consortium and public. The authors introduce the background and three kinds of blockchain networks in detail. But the problem is that the author describe the benefits and deployment too simply, which makes it hard to become a standard and to understand well. In addition, the authors didn’t introduce how to deploy ALTO in a blockchain network and how blockchain network benefits from ALTO. All we know is that ALTO can provide guidance by selecting the optimal route to other peers in order to optimize the network metrics and to assure QoS requirements, but not how in detail. And there’re some grammar errors in the draft: page7 last para: line 2: send->sent line 3: a similar message-> similar messages In total, this draft is written with good logic. If it could be completed in detail, it would be much better. Best, Lili