Re: [Blockchain-interop] New Version Notification for draft-chen-dlt-gateway-identification-00.txt
Rafael Belchior <rafael.belchior@tecnico.ulisboa.pt> Sat, 19 June 2021 12:37 UTC
Return-Path: <rafael.belchior@tecnico.ulisboa.pt>
X-Original-To: blockchain-interop@ietfa.amsl.com
Delivered-To: blockchain-interop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D697F3A0C6B for <blockchain-interop@ietfa.amsl.com>; Sat, 19 Jun 2021 05:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level:
X-Spam-Status: No, score=-1.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tecnico.ulisboa.pt
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 P3BkgFu2To0c for <blockchain-interop@ietfa.amsl.com>; Sat, 19 Jun 2021 05:37:20 -0700 (PDT)
Received: from smtp1.tecnico.ulisboa.pt (smtp1.tecnico.ulisboa.pt [193.136.128.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11B353A0C64 for <blockchain-interop@ietf.org>; Sat, 19 Jun 2021 05:37:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.tecnico.ulisboa.pt (Postfix) with ESMTP id 2EC706001403; Sat, 19 Jun 2021 13:37:13 +0100 (WEST)
X-Virus-Scanned: by amavisd-new-2.11.0 (20160426) (Debian) at tecnico.ulisboa.pt
Received: from smtp1.tecnico.ulisboa.pt ([127.0.0.1]) by localhost (smtp1.tecnico.ulisboa.pt [127.0.0.1]) (amavisd-new, port 10025) with LMTP id a8paMPV_j5FY; Sat, 19 Jun 2021 13:37:09 +0100 (WEST)
Received: from mail1.tecnico.ulisboa.pt (mail1.ist.utl.pt [IPv6:2001:690:2100:1::b3dd:b9ac]) by smtp1.tecnico.ulisboa.pt (Postfix) with ESMTPS id 1C78E6000855; Sat, 19 Jun 2021 13:37:08 +0100 (WEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tecnico.ulisboa.pt; s=mail; t=1624106229; bh=8ahNEav2Pxf5TeAJ72MtuAYSvKoP7IOR++m//+vsorI=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Wgy+6sHPN3xMXgftREUZjPf/ZTtLIzXWMWitO+RGVIRnU0EPrQcfeZZLhN0yEUdFz yTkFY6lexwDrsVeFo2+7g1LwSO22HBCcvyJbwoRKiZ0v/qlH3N9+oiYS5H3J1awhlA nBszSTOsYxOPpemnaiz56aml4dwG2pbFcU1Cz7pU=
Received: from webmail.tecnico.ulisboa.pt (webmail3.tecnico.ulisboa.pt [IPv6:2001:690:2100:1::912f:b135]) (Authenticated sender: ist180970) by mail1.tecnico.ulisboa.pt (Postfix) with ESMTPSA id 4EAB1360077; Sat, 19 Jun 2021 13:37:05 +0100 (WEST)
Received: from bl8-19-152.dsl.telepac.pt ([85.241.19.152]) via vs1.ist.utl.pt ([2001:690:2100:1::33]) by webmail.tecnico.ulisboa.pt with HTTP (HTTP/1.1 POST); Sat, 19 Jun 2021 13:37:05 +0100
MIME-Version: 1.0
Date: Sat, 19 Jun 2021 13:37:05 +0100
From: Rafael Belchior <rafael.belchior@tecnico.ulisboa.pt>
To: "Chen, Shiping (Data61, Eveleigh)" <Shiping.Chen@data61.csiro.au>
Cc: Rafael Belchior <rafael.belchior=40tecnico.ulisboa.pt@dmarc.ietf.org>, blockchain-interop@ietf.org, Thomas Hardjono <hardjono@mit.edu>
In-Reply-To: <SYBPR01MB396122940D04B99DF5272027D10C9@SYBPR01MB3961.ausprd01.prod.outlook.com>
References: <162307738614.18121.4904884207348330572@ietfa.amsl.com> <679028cde6fd44768c4e1bbba003e705@oc11expo23.exchange.mit.edu>, <BYAPR13MB2582854CF1C847F5A3BF3C49D0389@BYAPR13MB2582.namprd13.prod.outlook.com> <b9ee603fe5b1493f80e0b487a5233306@oc11expo23.exchange.mit.edu> <a578f6f5b4e56fb253c45d7f02d4adef@tecnico.ulisboa.pt> <SYBPR01MB396122940D04B99DF5272027D10C9@SYBPR01MB3961.ausprd01.prod.outlook.com>
Message-ID: <8346fb03658c83f17ef455095e3607ab@tecnico.ulisboa.pt>
X-Sender: rafael.belchior@tecnico.ulisboa.pt
User-Agent: Roundcube Webmail/1.3.15
Content-Type: multipart/alternative; boundary="=_16c23b4f2ec2d7e8e01e0b793ddbc44d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/blockchain-interop/lDz6sQk5p0zzOjsRFmNOIG0ZCQg>
Subject: Re: [Blockchain-interop] New Version Notification for draft-chen-dlt-gateway-identification-00.txt
X-BeenThere: blockchain-interop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Blockchain Gateway Interoperability Protocol <blockchain-interop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/blockchain-interop>, <mailto:blockchain-interop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/blockchain-interop/>
List-Post: <mailto:blockchain-interop@ietf.org>
List-Help: <mailto:blockchain-interop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/blockchain-interop>, <mailto:blockchain-interop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jun 2021 12:37:26 -0000
Hey Shiping, Thanks very much for your comments, I am clarified. Have an excellent weekend, Cheers, A 2021-06-19 02:45, Chen, Shiping (Data61, Eveleigh) escreveu: > Thank Rafael for your comments. > > Here are my 2-cents thoughts on your comments, also called comments on comments 😊 > >> isn't this still on the network layer, since it is relative to the participation on a DLN? > > _Yes, more preciously it is to bind a DLN to a specific blockchain gateway service/application operated by a specific BGSP. _ > >> It looks like this corresponds to ODAP's first phase, on the gateway verification. Are we performing this on discovery + ODAP? > > _Except for the offline interactions, all the real-time interactions can be implemented/incorporated into ODAP's phase 1, I guess._ > >> I think we should add that gateways may not be DLN nodes but rather software components that connect to DLN nodes (e.g., Hyperledger Cactus ODAP plugin using a Fabric Connector). > > _It is subject to the value of the gateway service business and the corresponding trust requirement._ > > _We can leave it to the BGSP to negotiate each other and configure their gateways as they agree._ > > _ _ > >> Essentially the verification comes up to trust a centralized party? > >> The problem of verifying if a software component is indeed a gateway is deferred to those BGSPs, correct? > > _Yes, the same answer as the above, i.e. let markets/BGSPs decide which centralized certification party they trust, and what (network/hardware/software) level of certifications required for them to establish their business trust._ > > Cheers > > - > > Shiping > > _ _ > > -----Original Message----- > From: Blockchain-interop <blockchain-interop-bounces@ietf.org> On Behalf Of Rafael Belchior > Sent: Friday, 18 June 2021 9:10 PM > To: blockchain-interop@ietf.org > Subject: Re: [Blockchain-interop] New Version Notification for draft-chen-dlt-gateway-identification-00.txt > > Hello All, > > Shipping, Thomas, thanks a lot for putting this together. > > A few comments: > > " (a) Application layer: At the application layer a gateway > > identification scheme is needed that permits an organization who > > participate in a given DLN to declare (advertise) one or more > > gateways into that DLN. This permits organizations to establish > > peering agreements (contracts) based on the asset type, DLN and > > jurisdictions, identifying (specifying) the gateways that will be " > > isn't this still on the network layer, since it is relative to the participation on a DLN? > > On 4.1: > > " (iii) asset type transferability: verification that a remote gateway > > for a destination DLN is mechanically capable to receive the type of > > asset and that legally permitted to receive the type of asset. > > " > > It looks like this corresponds to ODAP's first phase, on the gateway verification. Are we performing this on discovery + ODAP? > > On "Depending on the specific technical > > constraints of a given DLN (e.g. consensus model), not every node > > within the DLN may be designated to be a gateway capable of > > participating in an asset transfer between two DLNs. As such, the > > service provider must nominate its nodes or systems specifically as > > gateways" > > I think we should add that gateways may not be DLN nodes but rather software components that connect to DLN nodes (e.g., Hyperledger Cactus ODAP plugin using a Fabric Connector). > > " To ensure the safety of the transferred digital assets, blockchain > > gateway service providers (BGSP) must be trustworthy to clients who > > use the services. As a result, they must meet a high standard to > > ensure security and trust at different levels, ranging from business > > to networking, from hardware device to software protocol. > > " > > Essentially the verification comes up to trust a centralized party? > > The problem of verifying if a software component is indeed a gateway is deferred to those BGSPs, correct? > > Cheers, > > A 2021-06-07 22:26, Thomas Hardjono escreveu: > >> Thanks Mike, > >> > >> RPKI is an good possibility, such as for cases when not all the > >> Gateways (i.e. their IP addresses) are immediately visible from > >> outside the network. > >> > >> Its certainly an easy way for an asset service provider (i.e. VASP) to > >> declare ownership of a set of IP addresses for the gateways it owns. > >> > >> > >> Best > >> > >> --thomas > >> > >> ________________________________________ > >> From: Michael McBride [mmcbride@futurewei.com] > >> Sent: Monday, June 7, 2021 4:16 PM > >> To: Thomas Hardjono; blockchain-interop@ietf.org > >> Subject: RE: New Version Notification for > >> draft-chen-dlt-gateway-identification-00.txt > >> > >> Looks good Thomas. > >> > >> Since an AS/BGP will be required between gateways (correct? Or only > >> when a BGSP is involved?) we can also leverage RPKI to help ensure the > >> route being announced between gateways is coming from the legitimate > >> route (and subsequent data) owner. > >> > >> mike > >> > >> -----Original Message----- > >> From: Blockchain-interop <blockchain-interop-bounces@ietf.org> On > >> Behalf Of Thomas Hardjono > >> Sent: Monday, June 07, 2021 7:53 AM > >> To: blockchain-interop@ietf.org > >> Subject: [Blockchain-interop] FW: New Version Notification for > >> draft-chen-dlt-gateway-identification-00.txt > >> > >> > >> Folks, > >> > >> Here is a first-cut rough draft of the Gateway Identification & > >> Discovery work. > >> > >> A couple of the diagrams are still missing, but will be added in the > >> next revision. > >> > >> Best > >> > >> > >> Shiping & Thomas > >> > >> ________________________________________ > >> From: internet-drafts@ietf.org [internet-drafts@ietf.org] > >> Sent: Monday, June 7, 2021 10:49 AM > >> To: Shiping Chen; Thomas Hardjono > >> Subject: New Version Notification for > >> draft-chen-dlt-gateway-identification-00.txt > >> > >> A new version of I-D, draft-chen-dlt-gateway-identification-00.txt > >> has been successfully submitted by Thomas Hardjono and posted to the > >> IETF repository. > >> > >> Name: draft-chen-dlt-gateway-identification > >> Revision: 00 > >> Title: Gateway Identification and Discovery for Decentralized > >> Ledger Networks > >> Document date: 2021-06-08 > >> Group: Individual Submission > >> Pages: 13 > >> URL: > >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-chen-dlt-gateway-identification-00.txt&data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=0iyS9OXfeZzlemwyS2zq01YbrCsj1Y3Rtn7T8LapusM%3D&reserved=0 [1] > >> Status: > >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-chen-dlt-gateway-identification%2F&data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nmHNbDjw1CBAfpLzgNfRVRwOudemR7gjA5mcpDr6q28%3D&reserved=0 [2] > >> Htmlized: > >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-chen-dlt-gateway-identification&data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1TxVwx0D6gMJJrfwtYydVD1YQJEenGVL%2BFe9%2F2Ytc7M%3D&reserved=0 [3] > >> > >> > >> Abstract: > >> Today there is a growth in the number of blockchain and > >> decentralized > >> ledger networks (DLN) around the world, and interoperability across > >> different networks represents a challenge for the value proposition > >> of these networks. > >> > >> One approach for blockchain interoperability to be achieved is to > >> employ gateways that permit assets to flow across the relevant > >> networks of blockchains. > >> > >> However, a core requirement for interoperability is the correct > >> identification of computer systems that act as gateways and the > >> correct validation of the ownership of the gateway. A secondary > >> requirement is for a gateway to inquire as to the existence of an > >> entity address (public key) within a given decentralized ledger > >> network. > >> > >> This memo discusses options with regards gateway identification and > >> verification strategies. It looks at addressing the problem from > >> the > >> application layer and from the network layer. It also discusses > >> other options, such as relying on a third-party > >> blockchain-registered > >> identifiers and resolver services > >> > >> > >> > >> > >> The IETF Secretariat > >> > >> > >> -- > >> Blockchain-interop mailing list > >> Blockchain-interop@ietf.org > >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fblockchain-interop&data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6FtJXXNd0WfgssWVR%2F3Dc2nCXLiSUjgyo3rKeXCLvqc%3D&reserved=0 [4] > > -- > > -- Rafael Belchior > > Ph.D. student in Computer Science and Engineering, Blockchain - Técnico > > Lisboa > > https://rafaelapb.github.io/ [5] > > https://www.linkedin.com/in/rafaelpbelchior/ [6] > > -- > > Blockchain-interop mailing list > > Blockchain-interop@ietf.org > > https://www.ietf.org/mailman/listinfo/blockchain-interop [7] -- -- Rafael Belchior Ph.D. student in Computer Science and Engineering, Blockchain - Técnico Lisboa https://rafaelapb.github.io/ https://www.linkedin.com/in/rafaelpbelchior/ Links: ------ [1] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-chen-dlt-gateway-identification-00.txt&amp;data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=0iyS9OXfeZzlemwyS2zq01YbrCsj1Y3Rtn7T8LapusM%3D&amp;reserved=0 [2] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-chen-dlt-gateway-identification%2F&amp;data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=nmHNbDjw1CBAfpLzgNfRVRwOudemR7gjA5mcpDr6q28%3D&amp;reserved=0 [3] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-chen-dlt-gateway-identification&amp;data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=1TxVwx0D6gMJJrfwtYydVD1YQJEenGVL%2BFe9%2F2Ytc7M%3D&amp;reserved=0 [4] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fblockchain-interop&amp;data=04%7C01%7Cmmcbride%40futurewei.com%7Cbd91c83d605b4c3881d508d929c3f4cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637586743887921613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=6FtJXXNd0WfgssWVR%2F3Dc2nCXLiSUjgyo3rKeXCLvqc%3D&amp;reserved=0 [5] https://rafaelapb.github.io/ [6] https://www.linkedin.com/in/rafaelpbelchior/ [7] https://www.ietf.org/mailman/listinfo/blockchain-interop
- [Blockchain-interop] FW: New Version Notification… Thomas Hardjono
- Re: [Blockchain-interop] New Version Notification… Michael McBride
- Re: [Blockchain-interop] New Version Notification… Thomas Hardjono
- Re: [Blockchain-interop] New Version Notification… Rafael Belchior
- Re: [Blockchain-interop] New Version Notification… Chen, Shiping (Data61, Eveleigh)
- Re: [Blockchain-interop] New Version Notification… Rafael Belchior