IETF Logo Mail Archive

Re: [Sat] Small correction to draft-avrilionis-satp-asset-schema-architecture-00.txt

Martin Gfeller <mgf@acm.org> Sun, 28 January 2024 14:30 UTC

Return-Path: <m.c.gfeller@gmail.com>
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 F2F5CC1516F8 for <sat@ietfa.amsl.com>; Sun, 28 Jan 2024 06:30:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.407
X-Spam-Level:
X-Spam-Status: No, score=-1.407 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 zHUo_6HZLH2o for <sat@ietfa.amsl.com>; Sun, 28 Jan 2024 06:30:23 -0800 (PST)
Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (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 2A63FC1516EB for <sat@ietf.org>; Sun, 28 Jan 2024 06:30:23 -0800 (PST)
Received: by mail-lj1-f172.google.com with SMTP id 38308e7fff4ca-2cf0390eddbso20741691fa.3 for <sat@ietf.org>; Sun, 28 Jan 2024 06:30:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706452221; x=1707057021; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Y7RQNDI2F3OK91Q9RHNJ4iEMwOpNtMFOQG63nupoZaE=; b=B3lb4eOknfKV9dX7qqWz3wsLLTrFyHAWNajKMlCFAD9ehcQasAWv7hxc1JXA7SrTC8 KYeqv6eMJS5EiQ+tsWD9kcR5HB1h6ggpQwXfx5ecI6goUkOC67coKHRethGJguUlaUJ8 NUJ4PQk9zf8r2ZRZRMGZnpFZ98/PkDMFrnM19b4MjaNvksBnYdhxGMjVeK+H951Qe/k5 Zz1M8IYAFClH+TjkIs2tdYgAqVDCyGEB4tYk9fw5HUTyKbYGEZT8cQtAxYQNQgg6XZHs dpBJu8l35sCRFuRwEy8bPyv59P35+/xqxWVjhUENotfBQb1qpazLbD/Sedt1/s4wqSeb V0Cg==
X-Gm-Message-State: AOJu0YzoWRDtS170XLpQsDSQC4QYAJuYnh67JkDm9l45XBYEWGSJ7ZDr jrC5NjCmvd/rjeq1axjCyt+NrxDPsJGHC3U9SNCJtLNZDXS7pHLFGXHtB9f0fxuYtzXFleM+fYY qXaWvcjT97RvazJ/I1X4JIkB0cg==
X-Google-Smtp-Source: AGHT+IHatwWa3+D1HHc/svYs1TtGlI07UK8Ip5cw3KFKAS3p9M2G0/HyoGIyZqS2T5UFOC2LU0ct7f4e1QN2VOnoO+Q=
X-Received: by 2002:a2e:9f54:0:b0:2cc:eeea:9e8f with SMTP id v20-20020a2e9f54000000b002cceeea9e8fmr2234219ljk.13.1706452220954; Sun, 28 Jan 2024 06:30:20 -0800 (PST)
MIME-Version: 1.0
References: <170636765495.44674.8032416098392214097@ietfa.amsl.com> <DM5PR0101MB295663EA14DE88132B282C4ECB782@DM5PR0101MB2956.prod.exchangelabs.com>
In-Reply-To: <DM5PR0101MB295663EA14DE88132B282C4ECB782@DM5PR0101MB2956.prod.exchangelabs.com>
From: Martin Gfeller <mgf@acm.org>
Date: Sun, 28 Jan 2024 15:30:08 +0100
Message-ID: <CAOYrHJPAHgp1eGD0ZFm_Quf-4ueJfhHKxaa33GKbRKTouX4Kqw@mail.gmail.com>
To: Thomas Hardjono <hardjono@mit.edu>
Cc: "sat@ietf.org" <sat@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000074cb9d0610025e22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/Zy2Y1k5so63GRN7OoGTEr0xp6oU>
Subject: Re: [Sat] Small correction to draft-avrilionis-satp-asset-schema-architecture-00.txt
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: Sun, 28 Jan 2024 14:30:27 -0000

Dear Denis and Thomas

A small remark:

In 2. Terminology, "Asset Metadata Artifacts" has the wrong entry. It
duplicates the definition of "Asset Provider".

Best regards
Martin

On Sat, Jan 27, 2024 at 4:02 PM Thomas Hardjono <hardjono@mit.edu> wrote:

>
> ------------------------------
> *From:* internet-drafts@ietf.org <internet-drafts@ietf.org>
> *Sent:* Saturday, January 27, 2024 10:00 AM
> *To:* Denis Avrilionis <denis@compell.io>; Thomas Hardjono <
> hardjono@mit.edu>
> *Subject:* New Version Notification for
> draft-avrilionis-satp-asset-schema-architecture-00.txt
>
> A new version of Internet-Draft
> draft-avrilionis-satp-asset-schema-architecture-00.txt has been
> successfully
> submitted by Thomas Hardjono and posted to the
> IETF repository.
>
> Name:     draft-avrilionis-satp-asset-schema-architecture
> Revision: 00
> Title:    Asset Schema Architecture for Asset Exchange
> Date:     2024-01-27
> Group:    Individual Submission
> Pages:    12
> URL:
> https://www.ietf.org/archive/id/draft-avrilionis-satp-asset-schema-architecture-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-avrilionis-satp-asset-schema-architecture/
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-avrilionis-satp-asset-schema-architecture
>
>
> Abstract:
>
>    A management architecture for asset schemas and profiles is needed to
>    enable entities in the tokenized assets ecosystem to instantiate
>    tokens within one or more asset networks.  An asset network may be
>    constrained to support only a select class or type of token to be
>    present in the network.  In the SATP protocol, the receiving gateway
>    at the destination network is assumed in its preparatory stages to
>    evaluate the transfer request of a tokenized asset from the sending
>    gateway at the origin network.  In order to evaluate the proposed
>    transfer, the receiving gateway must have access to the asset
>    definition schema upon which the token was based in the origin
>    network.  The current document discusses the management architecture
>    for the asset definition schema and the schema-profiles derived from
>    the definition schema.
>
>
>
> The IETF Secretariat
>
>
> --
> sat mailing list
> sat@ietf.org
> https://www.ietf.org/mailman/listinfo/sat
>

v2.23.0 | Report a Bug | By Email