Re: [Blockchain-interop] New Version Notification for draft-chen-dlt-gateway-identification-00.txt
Thomas Hardjono <hardjono@mit.edu> Mon, 07 June 2021 21:27 UTC
Return-Path: <hardjono@mit.edu>
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 06E1A3A120C for <blockchain-interop@ietfa.amsl.com>; Mon, 7 Jun 2021 14:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RqAjtBw4wkO6 for <blockchain-interop@ietfa.amsl.com>; Mon, 7 Jun 2021 14:27:06 -0700 (PDT)
Received: from outgoing-exchange-5.mit.edu (outgoing-exchange-5.mit.edu [18.9.28.59]) (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 B00033A11F3 for <blockchain-interop@ietf.org>; Mon, 7 Jun 2021 14:27:06 -0700 (PDT)
Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 157LR0DL021328; Mon, 7 Jun 2021 17:27:02 -0400
Received: from w92expo23.exchange.mit.edu (18.7.74.77) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 7 Jun 2021 17:25:43 -0400
Received: from oc11expo23.exchange.mit.edu (18.9.4.88) by w92expo23.exchange.mit.edu (18.7.74.77) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 7 Jun 2021 17:26:40 -0400
Received: from oc11expo23.exchange.mit.edu ([18.9.4.88]) by oc11expo23.exchange.mit.edu ([18.9.4.88]) with mapi id 15.00.1497.015; Mon, 7 Jun 2021 17:26:40 -0400
From: Thomas Hardjono <hardjono@mit.edu>
To: Michael McBride <mmcbride@futurewei.com>, "blockchain-interop@ietf.org" <blockchain-interop@ietf.org>
Thread-Topic: New Version Notification for draft-chen-dlt-gateway-identification-00.txt
Thread-Index: AQHXW6xdxeNzuJS740WzuIzft9TNVqsIoXM3gABYZWCAABSTHg==
Date: Mon, 07 Jun 2021 21:26:40 +0000
Message-ID: <b9ee603fe5b1493f80e0b487a5233306@oc11expo23.exchange.mit.edu>
References: <162307738614.18121.4904884207348330572@ietfa.amsl.com> <679028cde6fd44768c4e1bbba003e705@oc11expo23.exchange.mit.edu>, <BYAPR13MB2582854CF1C847F5A3BF3C49D0389@BYAPR13MB2582.namprd13.prod.outlook.com>
In-Reply-To: <BYAPR13MB2582854CF1C847F5A3BF3C49D0389@BYAPR13MB2582.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [73.167.220.69]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/blockchain-interop/sg02dVdjrdp6mok79GLSpsBO7WI>
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: Mon, 07 Jun 2021 21:27:21 -0000
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 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 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 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
- [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