[alto] Draft: Alto for the blockchain

Shenshen Chen <cs90911@gmail.com> Mon, 27 February 2017 15:10 UTC

MIME-Version: 1.0
From: Shenshen Chen <cs90911@gmail.com>
Date: Mon, 27 Feb 2017 23:10:01 +0800
Message-ID: <CAKRjQSDKoE4HBj9Nj09NBDaAYiTA4PqrCv08CG9e+rokbVLcXA@mail.gmail.com>
To: draft-hommes-alto-blockchain@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/t3m4G1mzg5deGx5kh-2dR6uDUCU>
Cc: alto@ietf.org
Subject: [alto] Draft: Alto for the blockchain
Precedence: list

Dear authors,

I’m interested in ALTO for the blockchain,
draft-hommes-alto-blockchain-02 and have written some comments for 01
version. This draft looks pretty cool, but it may not fit "Intended
status: Standards Track" because of missing of definition.

As a standard, I guess it should define the format of request/response
and IRD for sec 3.1, 3.2 and bootstrap mechanism. According to RFC
7285, an ALTO client requests IRD to discover available information
resources provided by an ALTO server, which includes resource id,
media type, encoding and so on. The IRD may be something like this:

“available-peers" : {
        "uri" : “http://alto.example.com/blockchin/peers",
        "media-types" : [ "application/alto-blockchain+json" ],
        "role" : "miner",
        "metric" : "latency",
        .
        .
        .

Hope this helps.

Best Regards,
Shenshen

[alto] Draft: Alto for the blockchain Shenshen Chen