[Blockchain-interop] Summary Notes from IETF Gateway Interop meeting (4 January 2022)

Thomas Hardjono <hardjono@mit.edu> Tue, 04 January 2022 16: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 6D8703A1E09 for <blockchain-interop@ietfa.amsl.com>; Tue, 4 Jan 2022 08:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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] 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 zh1f5TCwDKC5 for <blockchain-interop@ietfa.amsl.com>; Tue, 4 Jan 2022 08:27:37 -0800 (PST)
Received: from outgoing-exchange-3.mit.edu (outgoing-exchange-3.mit.edu [18.9.28.13]) (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 D6B203A1E01 for <blockchain-interop@ietf.org>; Tue, 4 Jan 2022 08:27:36 -0800 (PST)
Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 204GRVh6027214 for <blockchain-interop@ietf.org>; Tue, 4 Jan 2022 11:27:35 -0500
Received: from oc11expo23.exchange.mit.edu (18.9.4.88) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1497.26; Tue, 4 Jan 2022 11:26:03 -0500
Received: from oc11expo23.exchange.mit.edu (18.9.4.88) by oc11expo23.exchange.mit.edu (18.9.4.88) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Tue, 4 Jan 2022 11:27:07 -0500
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.023; Tue, 4 Jan 2022 11:27:07 -0500
From: Thomas Hardjono <hardjono@mit.edu>
To: "blockchain-interop@ietf.org" <blockchain-interop@ietf.org>
Thread-Topic: Summary Notes from IETF Gateway Interop meeting (4 January 2022)
Thread-Index: AQHYAYJSb8D4Z6Pb706MfncMTdqmqw==
Date: Tue, 04 Jan 2022 16:27:07 +0000
Message-ID: <a8d87b754779440d838840ede74726f8@oc11expo23.exchange.mit.edu>
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.100.88.16]
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/pe3dENMJ7UMeBA5a_NziNgRwEW4>
Subject: [Blockchain-interop] Summary Notes from IETF Gateway Interop meeting (4 January 2022)
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: Tue, 04 Jan 2022 16:27:44 -0000

Folks,

Here is the summary notes from our meeting today (4 Jan 2022)

Please feel free to add/correct.


-- thomas --


----------------------------------------------
Summary Notes from IETF Gateway Interoperability group meeting

Date: Tuesday 4 January 2022

(a) Attendees:

Venkatraman Ramakrishna
Dhinakaran Vinayagamurthy
Rafael Belchior
Andre Augusto
Tom McGarry
Denis Avrilionis
Martin Hargreaves
Claire Facer
Thomas Hardjono


(b) IETF Note Well slide

-- This group meeting operates under IETF IP Rules as described in RFC5378 and RFC8179.


(c) Discussion regarding BOF at IETF113 or IETF114:

-- The IETF has posted an update regarding the coming IETF113 meeting (March 2022), which will now be in Vienna/Austria and Online.

-- As we have seen from other IETF events this past 2 years, conducting a BOF Session over Zoom/Online is difficult (unsatisfactory). So ideally we should aim for a BOF at an IETF meeting that has a reasonable F2F attendee population (i.e. enough people attending in-person).

-- For IETF113 Vienna, there is concern regarding travel restriction and difficulties (over Omicron). So we will need to wait until closer to March 2022.

-- The other option is to wait for IETF114 in Philadelphia in July 2022 on the East Coast of the USA.


(d) Discussion regarding Charter:

-- Looking at other WGs in the IETF, the charter needs to be specific regarding the scope of work and few deliverables within a specified timeline.

-- The input received from our Side Meeting at IETF112 in November 2021 was that the charter needs to focus specifically on (i) secure asset transfers, and (ii) it needs to be general enough to cover various ranges of "digital assets"

-- For example, could we define a secure asset transfer protocol that permit the proper transfer of domain-names (including the change to the DNS-related configurations). Today some would consider domain-names to be an "asset" which can be bought/sold on the Internet.  Another example would be the transfer of mobile phone number from one carrier (operator) to another.

-- The plan is for the group to be working on a draft charter for a Secure Asset Transfer working group that address these challenges. We should aim to get the draft charter done before IETF113 in March (independent of when we ask for a BOF).


(e) Discussion regarding asset identifiers:

-- Denis brought up a related question of how we identify digital assets, in a globally unique manner. This is a challenging question, and also related to the problem of the identification of DLT networks, where today there has not been any serious engineering considerations regarding this problem.

-- Martin mentioned that we had started a draft on the digital asset profile that sought o answer some of these questions.

 

(f) Future meetings:

-- January 18th, 2022

-- February 1st, 2022




----------------------------------------------------------