Re: [Sat] stage0 message exchange diagram

Thomas Hardjono <hardjono@mit.edu> Tue, 21 March 2023 14:38 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 2305DC14CF0C for <sat@ietfa.amsl.com>; Tue, 21 Mar 2023 07:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.099 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-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 ZXLB-Fmjr7o8 for <sat@ietfa.amsl.com>; Tue, 21 Mar 2023 07:38:38 -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 36B52C1CAB2E for <sat@ietf.org>; Tue, 21 Mar 2023 07:38:29 -0700 (PDT)
Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 32LEc5PS026404; Tue, 21 Mar 2023 10:38:27 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1679409508; bh=rt58PA+UGtmYZEDU/uiSIh3OPKT90vkcGBikNSx11Ko=; h=From:To:Subject:Date:References:In-Reply-To; b=CQAEZjLowbKRmOOjId/qgGVqnVJFMA14Dw+JkaygqGk00k04dpqfb4JgM2vW2cngZ d0bmKo5jOR6JrZNTvs3GWWp3/1xazpeb2fe7cffKy0mDWu+3a/LxGgE9NAMhoc1vvX 1EAlxB3hv51Gnj1MUizbPOaJlsbCKoZ4rgIy90IyoaZm6M/vAytG4Oz2UAwntMaOza EhTbZCNA+C7zjcpuudkTXVGEIybj6NwjfaIgSBhk+DzQ239AG/fkwKf2dcbjzCdW8+ 7dm9vLBFG96ZIaGbNHtclAiYj/JFAgxGB17W0E6ouXvVw7jEn8HrkdOfoTqk1PqTII VYqJXOLRfALZQ==
Received: from w92expo23.exchange.mit.edu (18.7.74.77) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.48; Tue, 21 Mar 2023 10:37:25 -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.42; Tue, 21 Mar 2023 10:37:30 -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.042; Tue, 21 Mar 2023 10:37:30 -0400
From: Thomas Hardjono <hardjono@mit.edu>
To: Venkatraman Ramakrishna <vramakr2@in.ibm.com>, "ladler2@bellatlantic.net" <ladler2@bellatlantic.net>, "sat@ietf.org" <sat@ietf.org>
Thread-Topic: [Sat] stage0 message exchange diagram
Thread-Index: AdlZwznEwQF1tB0WQJeXK00S5nbekACICizAAAd9tbo=
Date: Tue, 21 Mar 2023 14:37:30 +0000
Message-ID: <a172d76b3a5e48f3a8dc518714356e73@oc11expo23.exchange.mit.edu>
References: <006901d959c7$21121f20$63365d60$.ref@bellatlantic.net> <006901d959c7$21121f20$63365d60$@bellatlantic.net>, <BYAPR15MB2277BD627F3EF65DCB9C2531B8819@BYAPR15MB2277.namprd15.prod.outlook.com>
In-Reply-To: <BYAPR15MB2277BD627F3EF65DCB9C2531B8819@BYAPR15MB2277.namprd15.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.100.88.16]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/guCFxv22vo8Sj_H09eizEn61fEA>
Subject: Re: [Sat] stage0 message exchange diagram
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: Tue, 21 Mar 2023 14:38:45 -0000

Hi David,

What's interesting to me in Denis' applications-interaction diagram is that the gateway selection/election occurs (already completed) between Line-4 and Line-5 in Denis' diagram.

So by the time we start the SATP flow (the grey area) with a Transfer-Commence message 2.1, gateway G1 and G2 already "know" each other via Line-8.

(ps. I'm using the word "Line" for Denis's applications interaction diagram, and "Message" for our message flow)


Although this applications-interaction is out of scope for SATP, it answers one of the questions we received last year (about showing a complete end-to-end flow).



--thomas



________________________________________
From: sat [sat-bounces@ietf.org] on behalf of Venkatraman Ramakrishna [vramakr2@in.ibm.com]
Sent: Tuesday, March 21, 2023 6:59 AM
To: ladler2@bellatlantic.net; sat@ietf.org
Subject: Re: [Sat] stage0 message exchange diagram

My answers:

  1.  Yes, they refer to the same things. We should use consistent terminology here; I prefer either Ledger or State DB and not “system”, which we use interchangeably with “network” in the charter and in the drafts.
  2.  Step 4 is supposed to be oblivious to the gateway. I don’t think we need to prescribe a standard transport mechanism, since it is out of scope for the current SATP, but I imagine we can use HTTP or GRPC.

Rama

From: sat <sat-bounces@ietf.org> On Behalf Of ladler2@bellatlantic.net
Sent: 18 March 2023 23:56
To: sat@ietf.org
Subject: [EXTERNAL] [Sat] stage0 message exchange diagram

Hi: I have some questions on the Stage 0 message exchange: Are system1 and system2 the same as State Data DB1 and DB2 given in the SATP Message Flow Diagram? How is the step 4 message “propagateTransferContext” sent from client1App
ZjQcmQRYFpfptBannerStart
This Message Is From an Untrusted Sender

You have not previously corresponded with this sender.



ZjQcmQRYFpfptBannerEnd
Hi:
   I have some questions on the Stage 0 message exchange:


  1.  Are system1 and system2 the same as State  Data DB1 and DB2 given in the SATP Message Flow Diagram?
  2.  How is the step 4 message “propagateTransferContext” sent from client1App to client2App?

Does the message pass through gateway1 and gateway2?  If not what is   the underlying transport mechanism?

David Millman