[COSE] Re: Subject: Feedback Request: REM Protocol Draft (DOI + Blockchain Proofs)
Robin Bryce <robinbryce@gmail.com> Tue, 23 September 2025 14:21 UTC
Return-Path: <robinbryce@gmail.com>
X-Original-To: cose@mail2.ietf.org
Delivered-To: cose@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 12FC36793330 for <cose@mail2.ietf.org>; Tue, 23 Sep 2025 07:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L_GxXkhsqJyY for <cose@mail2.ietf.org>; Tue, 23 Sep 2025 07:21:52 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 835E86793114 for <cose@ietf.org>; Tue, 23 Sep 2025 07:20:52 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-32df5cae0b1so6440726a91.2 for <cose@ietf.org>; Tue, 23 Sep 2025 07:20:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758637251; x=1759242051; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=5XSvlzFU8sQNncn1uVYppUBQ83/3h5qqUOHZVyXRiok=; b=bOU/2IQ4NgezQSkkvdfLDbl8jZAMapfRFBGSRoUilkIQsqqHcECZThyHd+CUeZkzEY 2yKKyGbKQSPtKQ2egEXPFoHsAy28no7+2tmuPZdDGwrxRAketsa54YP6uUU5y1rk1/Nd aEkDqgONfE4H+3PWO4zpBGjE/eiYfm+VX40NlZpTNQSqGo38jiz1xeVzlK+ai6Ssgcab QQrTFebfNR4ZhlNQ+jU5gAHcAjQPpG4Ndyz3BlHGbwiIUfn6s0MvvMlWDg2IdxibzW9w c7W2+jFxvCEETdMJ5bL5NcQ9JRYdT/yg7QM86DgEx7Yj+cb1qz23EBuLd2ZxVH3lb2iN vZIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758637251; x=1759242051; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=5XSvlzFU8sQNncn1uVYppUBQ83/3h5qqUOHZVyXRiok=; b=lU/HzBH363cH7SK/rCH2AmCs3UG7ax/PtuOST1qrWehDS60LF0n4WZo+rtB4ke/lws nD+PGtMfaZq0UdxSUetk/bNXJuprJ8QzKdD9lvqumsffDBB00vBykB3IUbaXwOC26nY6 63TIStJAtx+gf/xIbeHcQbUjoghc0eIyPfCNUANPztzGXQ/BMWsB5IIDb2uJGdQfEYvr gLi7Ds0dMtEwpbMxWrsSrfweMHIk/A4N/VD7B412TgXELRsBKr5oezuVgJKNOCN+5+75 7Ow/ZhtXn6YWHoOoWv3IdQfcZ2/WTCvY0tMnhLST0W3Enqp6+I9XHFEGQ9HCBV2SJKpE DEZg==
X-Forwarded-Encrypted: i=1; AJvYcCWv3kUez44O5SFG/EXPm5VWrmmRRRQgbk71eHe5RJI0NrrLPRxsZ1I9bpSxWeg8cEoNM9Yq@ietf.org
X-Gm-Message-State: AOJu0YxS+DHp4vNfs31SeaECSxlFcdY6HAQa2hymdvqQ7Wxu1TRR2WEH ZUtxhL1whm1l2oQAgLCf5uG90T0qCiVGFIOKvLxC1MTpxsVZhXLCkSA6UvgYKPqNPmsYlRGD1Cl 4NhHN/6yIP4+EjpzoPWQSsxDGOS+hVkI=
X-Gm-Gg: ASbGncvTRJuBpcJb9o3y5ZXktE9A5qw7Z4x/5gxZrFDxhnlITj1HLMrY4U+1yDSsjz+ WODSVpmNKCM47sfceBQ3scbw3pnu2WEN7gJsn5ibmzrUOSf5FfiiRq5KK68NcVcTqE+tObHXRPz pAxrcZLsg0p0aEhf7l9FVrM+PL3fVZYWHX+Wr5V1HgznxqNnO4SUqvdt8ZDRkls+9HA3hRGyLiU xGvKLKFi1HTcw8ahW9UJddjhJ627+WU4YnNPg==
X-Google-Smtp-Source: AGHT+IEAYK62mX5Pthp/UHie+McNw3/aZuG4V7+U5JxdLJ++jfRXC9L2IsCbLs1ktJFMWEErgMWOeLRkhQFiPLSwJiQ=
X-Received: by 2002:a17:90b:3508:b0:32e:e3af:45f6 with SMTP id 98e67ed59e1d1-332a9502f78mr3386043a91.10.1758637251313; Tue, 23 Sep 2025 07:20:51 -0700 (PDT)
MIME-Version: 1.0
References: <CAHAdb+ijsOCGRThCFtDrtwjFfKFtX8A3v1MBLrE01To9VsE7YA@mail.gmail.com> <19545.1758560069@obiwan.sandelman.ca> <CAHAdb+gzy055qtYm6ceEo-nTaNgAWH4ouZDepM6_H6FUbQ-LxQ@mail.gmail.com> <29406.1758562249@obiwan.sandelman.ca> <CAHAdb+gpTsWXaJnZ+yd5vB72BkqU_VwTRTkB58w+9=uSFMXWGw@mail.gmail.com>
In-Reply-To: <CAHAdb+gpTsWXaJnZ+yd5vB72BkqU_VwTRTkB58w+9=uSFMXWGw@mail.gmail.com>
From: Robin Bryce <robinbryce@gmail.com>
Date: Tue, 23 Sep 2025 15:20:40 +0100
X-Gm-Features: AS18NWABXeha-h0paPc7ZTgmydrUbX4jAp622cs9qCBNVlqAPIsEI6wylZ7-2Qo
Message-ID: <CAE8YuVx6CuMbtaRNaYvPRRcr-iM4zV_ejOE_Nc3M=e-BoTqfUw@mail.gmail.com>
To: lawrence reilly <lawrencejohnreilly@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: HCOPT6UELECNSBIBVNUXVMNN2FQBYYUF
X-Message-ID-Hash: HCOPT6UELECNSBIBVNUXVMNN2FQBYYUF
X-MailFrom: robinbryce@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cose.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Michael Richardson <mcr+ietf@sandelman.ca>, cose@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: robinbryce@gmail.com
Subject: [COSE] Re: Subject: Feedback Request: REM Protocol Draft (DOI + Blockchain Proofs)
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/0xx5stoJRFLtRaj1RCd8yy9ebmQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Owner: <mailto:cose-owner@ietf.org>
List-Post: <mailto:cose@ietf.org>
List-Subscribe: <mailto:cose-join@ietf.org>
List-Unsubscribe: <mailto:cose-leave@ietf.org>
Hi Lawrence, If you haven't found them already, these ID's are pretty active and you will likely find some common interest with at least some of the collaborators: * https://datatracker.ietf.org/doc/draft-ietf-cose-merkle-tree-proofs/ And two draft profiles * https://datatracker.ietf.org/doc/draft-birkholz-cose-receipts-ccf-profile/ * https://datatracker.ietf.org/doc/draft-bryce-cose-receipts-mmr-profile/ On Mon, 22 Sept 2025 at 18:37, lawrence reilly <lawrencejohnreilly@gmail.com> wrote: > > Hi Michael, > > Thank you for taking the time to share such detailed feedback and references. I appreciate the context on LTANS, SCITT WG, and the existing IEC/ISO work around time-stamping services. I’ll review those links more closely to better understand the prior art and fit. > > My motivation with the REM Protocol is not to portray blockchain as “magical,” but rather to explore how existing constructs (DOIs, hashes, TXIDs) can be formally packaged and archived with long-term verifiability. I see blockchain timestamping as one component, alongside notaries and receipts, rather than a wholesale replacement for established trust models. > > Your point about CPU cycles and practical verification is well-taken. That’s why I’m experimenting with layered proofs (DOI + hash + TXID) to minimize reliance on any single ledger or entity. My aim is to complement, not duplicate, existing timestamping solutions, while leaving an open door for interoperability via COSE/CBOR formats. > > I’ll dig further into LTANS and SCITT, but your note helps me clarify the scope: REM may have a role in bridging scholarly/archival artifacts with trusted time-stamping models already in play. > > Thanks again for pointing me in the right direction. Any additional guidance on where discussions of archival permanence + receipts would be most welcome would be greatly appreciated. > > Thanks again, > Lawrence Reilly > > > On Mon, Sep 22, 2025, 1:30 PM Michael Richardson <mcr+ietf@sandelman.ca> wrote: >> >> >> lawrence reilly <lawrencejohnreilly@gmail.com> wrote: >> > Would you suggest an alternative working group or area within IETF that >> > might be a better fit for this draft? I’d like to make sure I’m >> > engaging with the right forum for further discussion and refinement. >> >> I think you should find an organization who believes proof-of-work blockchain >> has some ethical purpose. >> >> Even if changed to a shared-ledger (like Hyperledger), time-stamp services >> do not generally involve mutually suspicious entities with sufficient >> interest to spend the cpu cycles to verify the ledger. I don't think anyone >> wouldr spend the cpu cycles to download gigabytes of data, and verify >> a block chain in order to be sure some code-signature was time-stamped >> correctly before applying the patch. >> >> So it reduces to an entity running the time-stamping service, which singly >> rooted systems such as described 20 years ago at >> https://datatracker.ietf.org/wg/ltans/documents/ >> would apply. Such services exist today (I see Entrust, Sectigo, Adacom with >> a trivial search). IEC/ISO did some work more recently. >> So, you want COSE/CBOR format for receipts, then I'd start from LTANS, >> and you'll need at least two notaries to partipate. >> Here at the IETF, the SCITT WG might be interested, but I seem to think that >> they already have a solution. >> >> I understand that many people think that blockchain is magical, without cost, >> and will "free" you from having to make busiess relationships. >> I also want a unicorn. >> >> -- >> Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) >> Sandelman Software Works Inc, Ottawa and Worldwide > > _______________________________________________ > COSE mailing list -- cose@ietf.org > To unsubscribe send an email to cose-leave@ietf.org
- [COSE] Subject: Feedback Request: REM Protocol Dr… lawrence reilly
- [COSE] Re: Subject: Feedback Request: REM Protoco… Michael Richardson
- [COSE] Re: Subject: Feedback Request: REM Protoco… lawrence reilly
- [COSE] Re: Subject: Feedback Request: REM Protoco… Michael Richardson
- [COSE] Re: Subject: Feedback Request: REM Protoco… lawrence reilly
- [COSE] Re: Subject: Feedback Request: REM Protoco… Robin Bryce
- [COSE] Re: Subject: Feedback Request: REM Protoco… lawrence reilly
- [COSE] Re: Subject: Feedback Request: REM Protoco… Robin Bryce
- [COSE] Re: Subject: Feedback Request: REM Protoco… lawrence reilly