[Sat] Question about asset-identifiers

Thomas Hardjono <hardjono@mit.edu> Thu, 21 March 2024 13:19 UTC

Return-Path: <hardjono@mit.edu>
X-Original-To: sat@ietfa.amsl.com
Delivered-To: sat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FEFC14F5F2 for <sat@ietfa.amsl.com>; Thu, 21 Mar 2024 06:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mit.edu
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 953Wzv60g0Mt for <sat@ietfa.amsl.com>; Thu, 21 Mar 2024 06:19:12 -0700 (PDT)
Received: from NAM02-DM3-obe.outbound.protection.outlook.com (mail-dm3nam02on2095.outbound.protection.outlook.com [40.107.95.95]) (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 35903C15155E for <sat@ietf.org>; Thu, 21 Mar 2024 06:19:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Mrd/nM+O7Fe0VGv+ONYgEWHEvhwi4rnfE1/cuIFopUfaL4AyAd2AZmTTVb37yFhDjdduHJ0iJgxfiBTWNdrXakGcmAeG5elbY/UJoZrRFX5ORpYesy26VdTGHr2Xk2MtNi0grSkkq1HRY9TjRx2USh/og3/0CZQbVoD4zeY/etyUj2qPu+1hW4BuHH/Zhld6wH1pTn7fDiXQKT34IuR2KOKO7FJupDFCqWzfvIuy/Wpi0iobLu45CMqN3ZJUwi7yYdboqdTLZtB6qN1fFr6PmWd48E/5KDB64ljP3d1o9unxpFphQSn49LmiNTcaa9y1eWeLDqbo34XsvBSzGUqIfg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=7xtLzb/hF8Z2XmGw0cJF7k+rI0Nu9/nEX6y8r6m3dkk=; b=ShpqIGAe41ScbTs1ATM0ZVwKECEf2QGJtiUi+ogOQ2zl6f7mJjslxlajUBI4JfNy2L3xsR2A8nNVtD581LITQzNTs4Kt0uW9R+j5Mu+rBehSdcawgIrgIp+f46FJBDm3ozuPVyZZvo205PqqV4tewdSqQ1K+4sPncQYuo8q3lsJSNmAh0lAo8cGG8kBnSiPI3F5pk6pfHjrukL2NTDf6bm+LiHlOdJafYOBYfqfe7WDj9PAXgHOHipXkRK6BbV0mmS4yYZXXhFSTYIpaGspRKN3Ue9a6aU6GgrkpFuz2+HBM/HDclLW3cbV/+RWHfX1hCn4Rrmo7KqO7HUUtmh/mrQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=mit.edu; dmarc=pass action=none header.from=mit.edu; dkim=pass header.d=mit.edu; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7xtLzb/hF8Z2XmGw0cJF7k+rI0Nu9/nEX6y8r6m3dkk=; b=tJlQyLCUbi0HmGWv7E1vV9bCEb6xFlVx/70oEHyMO8E89WY3SiBPnejtjXxSpYqfPts2ttEqtTWoNPi3KEWBRTHE+nkSUg93iQkGnLnpUUk/sG/hkZmRyUgceZhzWOQSE6cZSWAUmCYbXjbOMv/zWbhL9c9KqZ6y5VYtIEqkWDc=
Received: from DM6PR01MB4395.prod.exchangelabs.com (2603:10b6:5:7a::16) by BN0PR01MB7007.prod.exchangelabs.com (2603:10b6:408:164::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.15; Thu, 21 Mar 2024 13:19:09 +0000
Received: from DM6PR01MB4395.prod.exchangelabs.com ([fe80::e4f9:514d:5169:6582]) by DM6PR01MB4395.prod.exchangelabs.com ([fe80::e4f9:514d:5169:6582%5]) with mapi id 15.20.7386.025; Thu, 21 Mar 2024 13:19:03 +0000
From: Thomas Hardjono <hardjono@mit.edu>
To: "sat@ietf.org" <sat@ietf.org>
Thread-Topic: Question about asset-identifiers
Thread-Index: AQHae5E/9oDxzqk1B0i9Gh+RYpfq4w==
Date: Thu, 21 Mar 2024 13:19:03 +0000
Message-ID: <DM6PR01MB4395DA2EFF962C980F92B220CB322@DM6PR01MB4395.prod.exchangelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=mit.edu;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DM6PR01MB4395:EE_|BN0PR01MB7007:EE_
x-ms-office365-filtering-correlation-id: 9274c46c-3c73-4639-0bf2-08dc49a97a59
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: IeE9asFmeKMstwQhjGL+pSsAayCXEMSh9U86PIgke1LhavZUjK6C2ZTmpr066QcCRyP88lfl/s8OcStuBGjarNC1YmUbdrZtpu2+1H07nPE+jwsfwkRcN9l9kzA45OI+duifm2YCbHkwSjFJYpfY4V8X2xJ/yJmUKKvUU97a4EQ7XqLm/WfZh95Nyxmw0R5l8E2rMDkYCM3AZD+flr6XAO7qv3ZRjlcAqFj1UiC90ZuPpUJqwxX7k0kxFf08TN6RijSDgXgYjac+dmlgQEgwil++fiGPlK/w4ejZ/rD/joV2rFNKRojAM7B4TW/hlKCgMOFHaPbWVWRza49zmXTe51+XdxK22UBdas9RMYwkjWoMdTD11Wgby9klIZGkTSWfYaCkxyWa3ahi1I4ipw2OyurM8199fYtJuWdYBz88Fz1mez+z/XHs0Bw6fXK3ud5dmECTD7E8Lg2a6VgEjaxn2i+71LcwDaFITOErq/kXAdV3pZAh3IpRjNm1uv2Fc/pkolq43Vqz5KreuqUyXgqwkJByAExQbjz8QV8x/QKwSN4LAm87Rp7aNEbUN//Poo/F7sFfSr8uE8zvXgrE2YBdfNLCrusxhzFpEvJtZZdPhksx/TbaCrncRyo0yYo12C34RZuQit9h5FTU+8d3ewDQAt7Faxr8fkizQ8wcoHockNrW3DVFsutu++Tmm76O2QZIJhUnjBQ2IAuNK54xEgxE3IzqybQVDjFxkwRyorLaL+A=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR01MB4395.prod.exchangelabs.com; PTR:; CAT:NONE; SFS:(13230031)(1800799015)(376005)(366007)(38070700009); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 6mEscBlcWcl4RBEni7CfooCsi9MOafmU1WCQWCiDlvse+SUvlq8KvSH30sUcVEDEZyaj4qq6fA0smxyX+kNsLuUAR4wYWcyUDyV6f2i4oIksClHe8A+u+JUR+wFaNqjQJ9P1/+3zyJgX4/XcRvpo/ShBxNMZezsNbksz02tTZ5oQKcfW08JeDZgzauWekNPvOMpzXt0ybbSqpZ3rlxGY2ekL3zH+y8fxiR8O2ZqwpHK8F7Tvsl+59dBY/9timANR9cbqHivZ9x5Ba/08jeDxtLD+ZEFuZTK5lPofinhwva51ItWJdH5jIwHopN1S9FO3ll2e9b3pXtbB6sGZ9MBPAWPGk4etI7vldvgVyaWVbo722lSzjLoV53fG27xw2Wcdtl6cM9JB8jUc5b3ZUQG7sG75zfCLH1QmvYnbJ8c+vOgF8ish6d690Qey4Pkxk73giuXaFenIfVIYUndvm1kzcFdVEXo1L2cZpJTT4/aD/4gxf5SvxKpTXpd6RgMQOOopmzcs0i2g9DyCfBmAa4frWPJ14YqDJjFmbJW54Ohxmq6JGqJ30ERf9wYWnQj5LlUnCiWv8utqaAqHJ0x5lW6NYjiQ6p4GV4jw9t7JamiAu3r9kxIxvmH/lbO1cFT8aYPS+AIDTmHTcB/e1fLz9RORbBFyKxyaA4dZ41mqDLWHD/Bn4Ouyg2TypC1opdoubZsRFQvtNoPjjFUYoLt4AbbBL6CSc7dPNCZ5KPdcp7JD3Pe+CsxTsqzE9mp1oSHl8CzUwC6+MnpIawrMzdh1UYkj134vOl4juegvXB/aFW8zHd2fHTr4HtHfoliFn07AI71fV9CtyFczRHoEyGD5zPMDsYcH9DysCwsQKsfBuHjeV0M2TodR6OqntBDkZZ30NPvSgFbEuX4UqWA4r4/VpNdfrJrgTXZtmNWnO2JE8FAcv2+oysmHPFI45Gew7ngzsPg5mXxCXyVCSjCo+z/3F1oQl8X77rm0pU8BsetE2Tdd90WhM7k2LWMOKtGdUBavXqcvhES/zB1j79l0dAQhG/rAYGx4oIueN9XuyhphCwPi7mVklkejyWmz/+2TXEGADeV94MhYDojCr0EVWrGijAC46u3H3DpV79k+23U+hUmJHBpUntrnuOZhqwbQRgpIOb+TeFHaF11BOO3mo+12IOK0roAyPVYCYKsa/6oBup/Sad4qL7hPeQESmRNxCpthHMaWVA3XIDl+NdQ/UupcZfa8svFxtZbvjTp5ji0w/ysjs5CPzPQPEvnBwW1BlugBR54HmLf+Px+iH4/HJyE9LlvDTqPjn63VxTbKhZSgekdqQza9cak377pKLQH7k3GaMh93eB8t+3voUSM+hSB4Pm4oT5+hcQS7f7magQEgifaV7DQ1E+CdnCnB5pjW/7OzVsl/myHNaMbocSsEn1SkxykjwvDoy4eNTazZdgWOvGFL5HrItRHClcW+tg1JWtAaJqJZQii4/hoLJDVQNOrN479kH5TRjwNNbsb67GlY5fuSWNtXIdfN9YEZLnOSnKv4f6Zj4JpblU36+bFxQuMvLn4DMTNs25jBg3q7TU/3FjG5siwepn5xNU1faW2bepoNUfnQXKAD6TOcp1EGLXoRJm2TnJ/jQ0Zz8lfm/+scNc7wniQlvIFqBrdG1K2LPQbRH7k0
Content-Type: multipart/alternative; boundary="_000_DM6PR01MB4395DA2EFF962C980F92B220CB322DM6PR01MB4395prod_"
MIME-Version: 1.0
X-OriginatorOrg: mit.edu
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR01MB4395.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9274c46c-3c73-4639-0bf2-08dc49a97a59
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2024 13:19:03.0392 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 64afd9ba-0ecf-4acf-bc36-935f6235ba8b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qxe5u1P2OCM2NbZP2XfYEAqT9gAsBhmVG6jGT488DbyREcwflVnwTFmVCkGJS996wyHxVYtQeDQwB9bCR+y5sg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN0PR01MB7007
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/INCfwRnbbVseHh_z6aD_gJ8AITs>
Subject: [Sat] Question about asset-identifiers
X-BeenThere: sat@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "The purpose of this mailing-list is to discuss the secure asset transfer \(SAT\) protocol and related aspects." <sat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sat>, <mailto:sat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sat/>
List-Post: <mailto:sat@ietf.org>
List-Help: <mailto:sat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sat>, <mailto:sat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2024 13:19:16 -0000

Folks,

Earlier this week I received a question about SATP-core, specifically about digital asset identifiers in the origin network (NW1) and in the destination network (NW2).

The digital asset identifier (DAI) is described very briefly in Section 5.2.3 of draft-core-03 as a UUID.

The question looks simple, but has some twists related to traceability of asset transfers (i.e. regulated assets and taxation) and privacy:

-- Assume the digital-asset is recorded in NW1 (i.e. in the ledger or database) as having an identifier DAI01.  After a successful transfer to NW2, the asset is assigned a new identifier DAI02 in NW2.

-- Question: should NW1 be aware of the new identifier DAI02 in NW2?   (for example, the new identifier DAI02 is reported back from gateway G2 to gateway G1 within the ACK-Final-Receipt message (message 3.7 of draft-core-03)).

-- The implication concerns privacy:  if the new identifier DAI02 is also copied (recorded as plaintext data) in NW1, this may permit other participants (other asset holders) in NW1 to know the new owner of the asset in NW2.


My response was that only the hash-of-DAI02 should be recorded in NW1.

So, the ACK-Final-Receipt message sent from gateway G2 to G1 should have the following parameters (where these will be recorded as data onto NW1 by G1):

Identifier of G1 and G2 (who handled the transfer instance).
The network identifier NW2 (to where the asset was transferred).
The asset identifier DAI01 (which is already known in NW1).
The hash of the asset identifier DAI02 (as it is known in NW2).
Date/timestamp.


As a corollary, when gateway G2 mints and assigns the new asset in NW2 (i.e. assign asset to Bob in NW2 immediately following the Commit-Final-Assertion message 3.5), gateway G2 should also record the hash of identifier DAI01 to NW2:

Identifier of G1 and G2 (who handled the transfer instance).
The network identifier NW1 (where the asset originated from).
The asset identifier DAI02 (the new identifier in NW2).
The hash of the asset identifier DAI01 (as it was known in NW1)
Date/timestamp.


Any thoughts?


--thomas