[Sat] stage0 v2 - message exchange diagram / SATP pre-conditions

Denis Avrilionis <denis@compell.io> Tue, 21 March 2023 17:09 UTC

Return-Path: <denis@compell.io>
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 D4437C14CF15 for <sat@ietfa.amsl.com>; Tue, 21 Mar 2023 10:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=compell.io
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 OJn-JSTGeEWq for <sat@ietfa.amsl.com>; Tue, 21 Mar 2023 10:09:43 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DCE8C14CF12 for <sat@ietf.org>; Tue, 21 Mar 2023 10:09:42 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id r11so62500449edd.5 for <sat@ietf.org>; Tue, 21 Mar 2023 10:09:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=compell.io; s=google; t=1679418580; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=ST0zlKEHFY344xGm5RtZ26R72NlDS5UoTAEqGUs3OmA=; b=HV4QSxXLilaUy97imk1L9RmWQzCErjUq+O+NecFaPIOk1J9ENitilXXNxTG2hoAEZ0 ciFZQqbdfSJiZhN5OpteK1y/ojwhFCpHItwZ+a1ugPZk/mLK+ve0Y9BMrjNRkpcNjMu1 w/I6kDpeSLasgep1ROIlcOdTutzNSMJhV3w5jrpG2iBS++QUcKvLi/JM7o8jUahqV736 z03q0R1gPNXLJwDg5FztWC8QegQG2WRJN70f53eMEUBtCVi2DubRal/f6/IT1gWv47kD kI3hsPBe4LrHeUtOqSCBFor44Zfnr61cKC4zH9HnZkRsSiZ837BvcPlH67r+Cyt+LyuB qAaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679418580; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ST0zlKEHFY344xGm5RtZ26R72NlDS5UoTAEqGUs3OmA=; b=jMFht068uY7b16ymrkSuWQRn3Mlpcw7dcojbNZ535W7P5XCeCLFYfJ+vVvwKPDzVLk /pk1CRb723QDA98sqgfB2gvK4R3EUzvFIdk0pMmKfqFO/2+gisAZjpvLg/JvzR2LWIif 0sbNwWEnB4m3qnTYM5nXq2SvtYr2gEeniLmeI31igAPRqRSjhNo3Z3jqYQvSZSu8XFgz YTLlF6KsV2f5sXccvqVt6f/m3gcrk5MSS3ZnWCONHledywT6q10Yjre4fPqa7qAjMrJI osDyf6DD8aAAQjNRvBzlH5w5MBoG1P1QpRz4Kt0xJSakgkMvKnT4B6c7pLqSCWBTxkNr Ajdg==
X-Gm-Message-State: AO0yUKVQsMP2wJnY9tEKOLV8/rWTiMDGk+iZUaIF/aNzvEO811VrV9BA zKAWrmRT7xVW9Jfjutwb0BVEqw==
X-Google-Smtp-Source: AK7set/JT2E+uHIMank5p84jXDE4R5AKvXtlqH+p/pPixhM/YSY5OHLj1yIsUKKKFp8JATbZHMnSvQ==
X-Received: by 2002:a05:6402:12c3:b0:4ac:b687:f57e with SMTP id k3-20020a05640212c300b004acb687f57emr3983220edx.1.1679418579779; Tue, 21 Mar 2023 10:09:39 -0700 (PDT)
Received: from smtpclient.apple (ppp005055110128.access.hol.gr. [5.55.110.128]) by smtp.gmail.com with ESMTPSA id t22-20020a50d716000000b004af6163f845sm6576005edi.28.2023.03.21.10.09.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Mar 2023 10:09:39 -0700 (PDT)
From: Denis Avrilionis <denis@compell.io>
Message-Id: <270344AD-3AB7-4C2B-A24A-1AFD3D6CE064@compell.io>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9C35BB89-C114-41AC-818F-D55F523DA87A"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Date: Tue, 21 Mar 2023 19:09:29 +0200
In-Reply-To: <01ab01d95c10$828fe200$87afa600$@bellatlantic.net>
Cc: sat@ietf.org
To: ladler2@bellatlantic.net, Thomas Hardjono <hardjono@mit.edu>, Venkatraman Ramakrishna <vramakr2@in.ibm.com>
References: <006901d959c7$21121f20$63365d60$.ref@bellatlantic.net> <006901d959c7$21121f20$63365d60$@bellatlantic.net> <BYAPR15MB2277BD627F3EF65DCB9C2531B8819@BYAPR15MB2277.namprd15.prod.outlook.com> <a172d76b3a5e48f3a8dc518714356e73@oc11expo23.exchange.mit.edu> <01ab01d95c10$828fe200$87afa600$@bellatlantic.net>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/PQR4dSJYkViiaJ5xfkK5h5jadXo>
Subject: [Sat] stage0 v2 - message exchange diagram / SATP pre-conditions
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 17:09:47 -0000

Attached is a revision of the Stage 0 diagram where I aligned the flow to the swimlanes of the core SAT message flow (thank you for your input!).


Answering to (Claire’s I think) question on how we can translate this to a set of pre-conditions to initiate SATP I think we can state them as follows:

- The Originator Application (a.k.a. Client App A1, a.k.a. Alice) has obtained a “transfer context”, i.e. information that unambiguously defines a specific asset transfer instance related to sending a well-defined set of assets from a given Originator to a given Beneficiary

- Network 1 (a.k.a. State Data DB1) is aware that this well-defined set of managed assets (owned by the originator) is going to be transferred for the given transfer context, and this at any moment in the future, based on Gateway 1 own initiative.   

- Gateway 1 is bound to Gateway 2 for the given transfer context

- The Beneficiary Application (a.k.a. Client App A2, a.k.a. Bob) knows that it will receive a well-defined set of assets for the given transfer context

- Network 2 (a.k.a. State Data DB2) is aware that assets will be received for a given beneficiary for the given transfer context

- Gateway is bound to Gateway 1 for the given transfer context  


Only if all the above conditions are met then the SATP transfer instance can be completed (note: completion can be either commit or rollback).

   


> On 21 Mar 2023, at 18:16, <ladler2@bellatlantic.net> <ladler2@bellatlantic.net> wrote:
> 
> Hi:
>   Yes it is progress that the stage0 message exchange defines a startup and
> a conclusion to the SATP process.
> 
> The problem with step 4 is that there appears to be no feedback to
> client1App from client2App after receipt of the message.
> If step 4 is not received by client2App steps 6,7, and 8 will not be
> executed. This would block the entire SATP process.
> Also when would client1App initiate step 5?
> 
> Also, if client1App and client2App are running on computers internal to a
> corporate network I don't see how network
> security  would allow anything except an email to go from the client1App
> computer to the client2App computer.
> 
> David Millman
> 
> -----Original Message-----
> From: sat <sat-bounces@ietf.org> On Behalf Of Thomas Hardjono
> Sent: Tuesday, March 21, 2023 10:38 AM
> To: Venkatraman Ramakrishna <vramakr2@in.ibm.com>; ladler2@bellatlantic.net;
> sat@ietf.org
> Subject: Re: [Sat] stage0 message exchange diagram
> 
> 
> 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
> 
> --
> sat mailing list
> sat@ietf.org
> https://www.ietf.org/mailman/listinfo/sat
> 
> -- 
> sat mailing list
> sat@ietf.org
> https://www.ietf.org/mailman/listinfo/sat