Re: [Blockchain-interop] Thoughts on unique DLT numbering/identification

Miguel Correia <miguel.p.correia@tecnico.ulisboa.pt> Mon, 12 October 2020 15:38 UTC

Return-Path: <miguel.p.correia@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 5B1B43A0E49 for <blockchain-interop@ietfa.amsl.com>; Mon, 12 Oct 2020 08:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, 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 i1EspvOK-cBR for <blockchain-interop@ietfa.amsl.com>; Mon, 12 Oct 2020 08:38:07 -0700 (PDT)
Received: from smtp1.tecnico.ulisboa.pt (smtp1.tecnico.ulisboa.pt [IPv6:2001:690:2100:1::15]) (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 1C8033A0E41 for <blockchain-interop@ietf.org>; Mon, 12 Oct 2020 08:38:06 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.tecnico.ulisboa.pt (Postfix) with ESMTP id 08C6F642D405; Mon, 12 Oct 2020 16:38:05 +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 OLNf2C8r4FuW; Mon, 12 Oct 2020 16:38:01 +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 CF715642D40A; Mon, 12 Oct 2020 16:38:01 +0100 (WEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tecnico.ulisboa.pt; s=mail; t=1602517081; bh=TgWbaUKdO79r+9OB/qPTXnHXsvOSqh1sYW94Gjyg2mU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Bm8Pn60ou63C7zW4dhM51LaO4lbZP3m7ODRKbMUDMrzzwvOHjkJJWQK5yjCve0dYb QL6bvtPt1unDO99VpCGO7w7uzvrrjLlhnS2+64t/iaQV9UTrTeG2EGEv1SytH5UnY/ GdnOwy8YHHDlNVZPewdtj1M7cobu3XnEuen+W3AY=
Received: from [IPv6:2001:818:d859:2000:ad37:2dbc:467d:51a4] (unknown [IPv6:2001:818:d859:2000:ad37:2dbc:467d:51a4]) (Authenticated sender: ist130598) by mail1.tecnico.ulisboa.pt (Postfix) with ESMTPSA id A7FA3360070; Mon, 12 Oct 2020 16:38:01 +0100 (WEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Miguel Correia <miguel.p.correia@tecnico.ulisboa.pt>
In-Reply-To: <CWXP123MB17517A0FE5208935FD4A2E2FFC070@CWXP123MB1751.GBRP123.PROD.OUTLOOK.COM>
Date: Mon, 12 Oct 2020 16:38:01 +0100
Cc: Thomas Hardjono <hardjono@mit.edu>, "blockchain-interop@ietf.org" <blockchain-interop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1A8833B-FC4F-4D8F-8EA4-B28D6A09D071@tecnico.ulisboa.pt>
References: <6a6b1e0074c4416dada1bfab957b8371@oc11expo23.exchange.mit.edu> <209BF1C3-ED51-4607-8255-CE806A352C6F@tecnico.ulisboa.pt> <15ec6f9f930e42e08a2a98c63407fb13@oc11expo23.exchange.mit.edu> <EE086F89-B88F-4765-A566-6074DB42728B@tecnico.ulisboa.pt> <f079dc78c68e413596bad5bfa2c06784@oc11expo23.exchange.mit.edu> <CWXP123MB17517A0FE5208935FD4A2E2FFC070@CWXP123MB1751.GBRP123.PROD.OUTLOOK.COM>
To: Martin Hargreaves <martin.hargreaves@quant.network>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/blockchain-interop/KUg-rmZPqFSn3J-1BBWTXLazsmE>
Subject: Re: [Blockchain-interop] Thoughts on unique DLT numbering/identification
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, 12 Oct 2020 15:38:10 -0000

Hi Martin,

I agree 32 bits will probably be enough, but the Internet history has also shown we can consume bits much faster than initially thought :-) If we go for 32 bits I would suggest specifying also a mechanism for updating the size later, if needed.

Best,
Miguel



> On 12 Oct 2020, at 16:20, Martin Hargreaves <martin.hargreaves@quant.network> wrote:
> 
> Hi Thomas and Miguel,
> 
> I think 32 bits should be enough unless we envisage embedded DLT gateways in IoT devices or other very widespread small systems - I think that's relatively unlikely at this point, and would probably deserve a later revision to a number of areas.
> 
> Best,
> 
> Martin
> 
> -----Original Message-----
> From: Blockchain-interop <blockchain-interop-bounces@ietf.org> On Behalf Of Thomas Hardjono
> Sent: Monday, October 12, 2020 2:04 PM
> To: Miguel Correia <miguel.p.correia@tecnico.ulisboa.pt>pt>; blockchain-interop@ietf.org
> Subject: Re: [Blockchain-interop] Thoughts on unique DLT numbering/identification
> 
> 
> Hi Miguel,
> 
> I agree with you that IETF is a good place to discuss this problem of numbering/identification of blockchain systems. Perhaps this could be a separate draft.
> 
> Something like this:
> 
> (a) Blockchain network number:  32 bits
> 
> (b) Provider (VASP) identification number:  32 bits
> 
> Would 32-bits be large enough for uniquely numbering blockchain systems in the future?  (The SWIFT number for bank identification are only 11 characters, and they seem to be working ok).
> 
> 
> 
> 
> -- thomas --
> 
> 
> ________________________________________
> From: Blockchain-interop [blockchain-interop-bounces@ietf.org] on behalf of Miguel Correia [miguel.p.correia@tecnico.ulisboa.pt]
> Sent: Monday, October 12, 2020 6:43 AM
> To: blockchain-interop@ietf.org
> Subject: Re: [Blockchain-interop] Thoughts on unique DLT numbering/identification
> 
> Hi Thomas,
> 
> I think we should discuss the relevance of this aspect because the IETF could be the right organization to handle it. I think the scope is wider than interoperability, but it is an enabler for interoperability so it might make sense to work on a proposal to solve it.
> 
> Best,
> Miguel
> 
>> On 10 Oct 2020, at 15:24, Thomas Hardjono <hardjono@mit.edu> wrote:
>> 
>> 
>> 
>> Hi Miguel,
>> 
>>>>> I think today we distinguish blockchains in two ways:
>> 
>> Agree - this is what is being used today. The client software is either configured (e.g. with IP address/port of nearest nodes), or the user needs to type in a destination system.
>> 
>> 
>>>>> One solution would be to continue using IP addresses and use DNS to
>>>>> register names for blockchains. However, for consortium blockchains
>>>>> that involve several organizations, this creates the problem of who shall register the name.
>> 
>> My understanding is that the current direction of the regulators (e.g. FATF) is to require entities handling virtual assets (i.e. VASPs or virtual asset service providers) to have some form of legal identification (e.g. LEI number) or business registration (e.g. Incorporation number in the US).
>> 
>> However, that is just numbering or identification for one entity (one VASP).  If a group VASPs form a consortium sharing a common blockchain system with many nodes, then on the protocol level there still needs to be some identification for that "system" consisting of the multiple nodes.
>> 
>> 
>>>>> Another aspect is that IDs/names are often used to help finding a resource.
>> 
>> Yes, exactly -- this what we need, some way to uniquely identify resources within a blockchain systems (independent of whether the resource is reachable, such as when within/behind private blockchains).
>> 
>> 
>> Best
>> 
>> 
>> -- thomas --
>> 
>> 
>> 
>> ________________________________________
>> From: Blockchain-interop [blockchain-interop-bounces@ietf.org] on
>> behalf of Miguel Correia [miguel.p.correia@tecnico.ulisboa.pt]
>> Sent: Saturday, October 10, 2020 8:40 AM
>> To: blockchain-interop@ietf.org
>> Subject: Re: [Blockchain-interop] Thoughts on unique DLT
>> numbering/identification
>> 
>> Hi Thomas,
>> 
>> This is a very interesting topic.
>> 
>> I think today we distinguish blockchains in two ways:
>> 
>> - the client software we use is associated to a single blockchain and
>> the identification is implicit in the software; or the client software
>> is associated to more than one  blockchain and the software provides
>> us that distinction (e.g., showing we if we are using blockchain bc1
>> or bc2)
>> 
>> - by IP address / port of (a subset of) the nodes
>> 
>> I think currently this satisfies most needs, but I also think some kind of ID scheme will be needed in the future. For example, organizations may start using many instances of the same permissioned blockchain software (e.g., Fabric), with nodes in several other organizations. Using IPs/ports might be possible but surely not practical.
>> 
>> One solution would be to continue using IP addresses and use DNS to register names for blockchains. However, for consortium blockchains that involve several organizations, this creates the problem of who shall register the name.
>> 
>> Another aspect is that IDs/names are often used to help finding a resource. Is that interesting in this context?
>> 
>> Best,
>> Miguel
>> 
>> 
>> 
>>> On 9 Oct 2020, at 19:41, Thomas Hardjono <hardjono@mit.edu> wrote:
>>> 
>>> 
>>> One of the gaps or issues with blockchain systems or DLTs today is the lack of a globally unique and uniform numbering (identification) scheme for each system.
>>> 
>>> For example, if a community in one country is running its own network of nodes (using a version of Hyperledger or Quorum), and a different community in another country is using the same software-stack on a different set of nodes, there is no way for a machine today (e.g. client) to distinguish between these communities (networks).
>>> 
>>> There has been some proposals for numbering/identification of the entities (e.g. VASP number), but this does not cover the network as a whole.
>>> 
>>> Do we need something like ARIN registry to allocate AS-numbers for blockchain networks.
>>> 
>>> 
>>> Thoughts anyone?
>>> 
>>> 
>>> 
>>> -- thomas --
>>> 
>>> 
>>> --
>>> Blockchain-interop mailing list
>>> Blockchain-interop@ietf.org
>>> https://www.ietf.org/mailman/listinfo/blockchain-interop
>> 
>> --
>> Blockchain-interop mailing list
>> Blockchain-interop@ietf.org
>> https://www.ietf.org/mailman/listinfo/blockchain-interop
>> 
>> --
>> Blockchain-interop mailing list
>> Blockchain-interop@ietf.org
>> https://www.ietf.org/mailman/listinfo/blockchain-interop
> 
> --
> Blockchain-interop mailing list
> Blockchain-interop@ietf.org
> https://www.ietf.org/mailman/listinfo/blockchain-interop
> 
> --
> Blockchain-interop mailing list
> Blockchain-interop@ietf.org
> https://www.ietf.org/mailman/listinfo/blockchain-interop
> This message is intended solely for the addressee and may contain privileged and confidential information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained in this message or in any attachment. Quant Network does not guarantee that this email has not been intercepted and amended or that it is virus free.