IETF Logo Mail Archive

Re: [alto] Draft: Alto for the blockchain

Shenshen Chen <cs90911@gmail.com> Mon, 13 March 2017 19:50 UTC

Return-Path: <cs90911@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 08AA5129AF3; Mon, 13 Mar 2017 12:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3kLNhwUZtV1P; Mon, 13 Mar 2017 12:50:46 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 A16BC129AE4; Mon, 13 Mar 2017 12:50:29 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id u30so160249251uau.0; Mon, 13 Mar 2017 12:50:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=EfnM8Gnje2/Xe9qICRY1yfq13QAckTjbUqwOGbjo/bs=; b=felAGMhNvuayzioObuid05sbSCarebodk6hpxFe9uBO70FKiHitw3DR+uWq7H6GDEl a/5gl6fxiWbha8sOJPiuyTd50QVHpzdf3gY25Gd/q8hYg2F7QkDsNbO4fG+9nAkVARZP y4LEzQLD6A73/aZsnthcxCCvQLXM2DlTeNPCv4Gcc9Ea7Msvxt2OaZUqHgk+RqcnD7RC lWAZuI54EPLGLAIWPIdLh3zQYZkOmqC2Uo7Hn3GwtF7LWHYU1CnD6Ee8BzPL3jdOCI8O 7IcI5efYRjs4wL9IY08UOhYVinED44vnp3Ng8jC3GaMxpJ8dN5beYd1N0ykJtYAbPw0U B3AQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=EfnM8Gnje2/Xe9qICRY1yfq13QAckTjbUqwOGbjo/bs=; b=FABT741z+FhOy88ZYrLUDmDT/ozOhCpnRz+7aZ7gWE2xQfUX0m0ypxWawTeBE2dcDo NhlkuaLdmGquYzim+RnPEyomVL7GFfdtX7/kWg//OwmfyfEfWy2CLId8niV+laQPaOuR Ve/SSvxx9f9/lzG5w7W7qkQdP/cJQj0D1Eu+EoXnJVCPqJCFjpq+OceiIvSRVYAM6w/7 3EbCfumHnVGeTCiV3ahndCEfTFJYL/Z7pJCWBSCotzk/6CB5KZF+JOv7mJ7NwssVyFup P21i9HH9cznYT6KLB6uZYt75buc4pOmu8Plf+mdVfWdqNjVSPvzcz+IP67A/EQuEUCvh HG8A==
X-Gm-Message-State: AMke39kY2oy/xBVVvpH6BKkJUXE78QmApvEnuoun4aBWoU3y32zUzWvamPyBup2JeC1+Gff6P8lJJXsv5BCD8A==
X-Received: by 10.159.39.39 with SMTP id a36mr13862021uaa.32.1489434628564; Mon, 13 Mar 2017 12:50:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.254.129 with HTTP; Mon, 13 Mar 2017 12:49:48 -0700 (PDT)
In-Reply-To: <F8F5B448CE8B1B48BB53A5855ACEB05CBDFEC667@hoshi.uni.lux>
References: <CAKRjQSAC7K0x9AqTHshjtEfpmgPtfF3LjFSNPS71J8SxMkHGLQ@mail.gmail.com> <F8F5B448CE8B1B48BB53A5855ACEB05CBDFEC667@hoshi.uni.lux>
From: Shenshen Chen <cs90911@gmail.com>
Date: Tue, 14 Mar 2017 03:49:48 +0800
Message-ID: <CAKRjQSD6tLeYtsAi5e5XT1ZJXa+oRqgXNwEBwfRb4nMX+TUL6w@mail.gmail.com>
To: draft-hommes-alto-blockchain@ietf.org, Stefan HOMMES <Stefan.Hommes@uni.lu>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ESo7VP6DAtIopKye5Vo7rFmaWoI>
Cc: alto@ietf.org
Subject: Re: [alto] Draft: Alto for the blockchain
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 13 Mar 2017 19:50:47 -0000

Hi Stefan,

Sorry about my poor knowledge. I didn't find any special requirements
for the healthcare blockchain. It should be no more than a blockchain
for ALTO.

By the way, there may be a trivial issue I am not sure about: does
alto help defending weakness of blockchain? Avoiding the creation of
clusters in sec 3.3 may help to avoid Sybil attack.

Best Regards,
Shenshen

2017-03-13 22:56 GMT+08:00 Stefan HOMMES <Stefan.Hommes@uni.lu>:
> Hello Shenshen,
>
> Thanks for your comment. Yes, health care is another use case for the blockchain. The Bitcoin scenario is currently the best representative for public blockchain networks. I guess health care would be an example for a consortium blockchain. Except for the fact that it is a use case, do you have more info's on any special requirements concerning ALTO?
>
> Kind Regards,
> Stefan
>
> -----Original Message-----
> From: Shenshen Chen [mailto:cs90911@gmail.com]
> Sent: 13 March 2017 15:45
> To: draft-hommes-alto-blockchain@ietf.org
> Cc: alto@ietf.org
> Subject: [alto] Draft: Alto for the blockchain
>
> Dear authors,
>
> In draft-hommes-alto-blockchain-02 section 5, it mainly talks about bitcoin. Would you be glad to add another section about health care?
>
> The healthcare has a great interest in the blockchain. A doctor needs patient’s record from different hospitals. A patient cares about the security of his medical record. The blockchain could be the solution since it keeps secure data in a distributed, encrypted ledger and control who has access to that ledger. It treats a doctor’s visit as a transaction. Then people validate the transactions—in health care, likely a physician or pharmacist trusted with an access key.
>
> More use cases make the draft more general, especially about “be aware of different roles for bitcoin”.  Rules in healthcare are patient, doctor and hospitals. Those roles may be treated as wallet, miner and relay nodes. By showing other use cases of blockchain still use those standard roles, it’s more convincing to claim that Alto should be aware of those 3 different roles.
>
> Hope this helps.
>
> Best Regards,
> Shenshen

v2.23.0 | Report a Bug | By Email