From nobody Thu Mar 2 17:22:50 2023 Return-Path: X-Original-To: cbor@ietfa.amsl.com Delivered-To: cbor@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6EC5C151AF2 for ; Thu, 2 Mar 2023 17:22:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=lifewithalacrity-com.20210112.gappssmtp.com 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 K-VRQfZzCN5f for ; Thu, 2 Mar 2023 17:22:45 -0800 (PST) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 D62E9C151AF1 for ; Thu, 2 Mar 2023 17:22:45 -0800 (PST) Received: by mail-ed1-x532.google.com with SMTP id cy23so4251277edb.12 for ; Thu, 02 Mar 2023 17:22:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lifewithalacrity-com.20210112.gappssmtp.com; s=20210112; t=1677806563; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ajmz5oG1ulG2mvzfl/uAh25ZQWopSdDxO0AowlYriT0=; b=QQXupKK/5p3VkNliuHzg64LSWDgzk17t6dnRWLmUwrW23FzhoqCvc51HujQTZDMCfk Lotr7SCKuXY4yXcGb91WrHC7EJFG46Z989v/OksoXeWI+o3KBJFFRZYJlmxw1U1yZI11 IOrBxXNKRMYaC/KBOForWEIx5NnswsgQzDFmTRpZJAh5IgjYtk38HJKOombFG5AHsUIx xmsYkC1UGx/zZzMJa1dblwjJQ3F1gSrGlfpfr6/szza4Q1s28ivQGvdslHL8hHtdnRXx avGLOMhLGdXcg5ApIUZYAi7DcTKBjQw4RnkozZ2fpEKxTs8P2APabgtVaylXsfmQSL1J OQiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677806563; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ajmz5oG1ulG2mvzfl/uAh25ZQWopSdDxO0AowlYriT0=; b=uQrxfC0Td22EwMRSY/2BLqmneMfQB7MBx0XM1g14W1m7uSX2phczGZ0QjPc0B0LjAg DmwrIMf7TtA6Q8XlyH+WOrBlYqYc62pHtEZQ8bHQ7lOGoKVU6kvitqOTgDF4Zbua1eNi WYGjaBZro57LIOsxqOcVTRrJXmo+Wd4gM7pQu0GpAeuWb44eq8+tP3aYmtQVW26zVThc jH4frlclID8Un5iwg3NI42EWRwb6DiNrKRqmN4o91ERrTBtyNs7p7oD2IxjiE+1vXeyO 0zvzw4jpkmOWONg6wSeK+3e2ST4thAK7lqJ3KryFThRNs0PgfuRezJxs1X/869Xgy62y osRg== X-Gm-Message-State: AO0yUKVvipzZB0apG5iJxrKoDmxfceA3Uk7Skr7dhd8EFmjF1p+VcyOI aYpWAADjpODkGT+oYeRttbLCRrLDV90wE+MwqvKtesKbYZnbJmZLVnQ= X-Google-Smtp-Source: AK7set84wDbdGECGYi1s9da90YszgszEVeXzYbqSKO30NajZBRRIETaBMOeb6KWv1lHaEqi+HM9NPEIS7v4JzhfJfTg= X-Received: by 2002:a17:906:af6a:b0:87d:ce4:eb7a with SMTP id os10-20020a170906af6a00b0087d0ce4eb7amr5928403ejb.13.1677806563336; Thu, 02 Mar 2023 17:22:43 -0800 (PST) MIME-Version: 1.0 From: Christopher Allen Date: Thu, 2 Mar 2023 17:22:32 -0800 Message-ID: To: cbor@ietf.org Cc: wolf@wolfmcnally.com, Shannon.Appelcline@gmail.com, Anders Rundgren Content-Type: multipart/alternative; boundary="00000000000035bacb05f5f4c84f" Archived-At: Subject: Re: [Cbor] Fwd: New deterministic CBOR Libraries (Rust & Swift) from Blockchain Commons X-BeenThere: cbor@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "Concise Binary Object Representation \(CBOR\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2023 01:22:50 -0000 --00000000000035bacb05f5f4c84f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 16 February 2023 19:26 UTC Anders Rundgren < anders.rundgren.net@gmail.com> wrote: > On 2023-02-16 19:13, Laurence Lundblade wrote: > > Is there a further detailed definition of determinism, such as what to do with floats? > > I started with that a while ago, We have more detail on the specific choices that we've made in our dCBOR libraries, excerpted from Wednesday's meeting of the Gordian Developer Community. In particular, we have a lot of detail about how we handle floats and maps: * YouTube Video Archive: https://www.youtube.com/watch?v=3DNlJE8oF1B5M * MP3 Audio Archive: https://github.com/BlockchainCommons/Gordian-Developer-Community/blob/maste= r/meetings/dCBOR%20(Deterministic%20CBOR)%20Library%20from%20Blockchain%20C= ommons.mp3 * Presentation PDF: https://github.com/BlockchainCommons/Gordian-Developer-Community/blob/maste= r/meetings/2023-03-01-dCBOR-presentation.pdf * Text Transcript: TBD See also "Why CBOR": * Article: https://www.blockchaincommons.com/introduction/Why-CBOR/ * Video: https://www.youtube.com/watch?v=3DuoD5_Vr6qzw dCBOR Source & Documentation: * dCBOR Library for Rust: https://github.com/BlockchainCommons/bc-dcbor-rus= t * dCBOR Library for Swift: https://github.com/BlockchainCommons/BCSwiftDCBO= R * dCBOR-CLI Reference App: https://github.com/BlockchainCommons/dcbor-cli Blockchain Commons has embraced deterministic CBOR (dCBOR), as a the foundation for Gordian Envelope: * Intro Article: https://www.blockchaincommons.com/introduction/Envelope-Intro/ * YouTube Video: https://www.blockchaincommons.com/introduction/Envelope-Intro/ We also presented Gordian Envelope in the W3C Credentials Community Group last January. Transcript and OGG audio at https://w3c-ccg.github.io/meetings/2023-01-31/ On Thu, 16 February 2023 19:26 UTC Anders Rundgren < anders.rundgren.net@gmail.com> wrote: > but now it may be time to unify the different solutions. We are currently in what we call the "Community Review" phase for our dCBOR libraries before we submit them for a third-party security review. We welcome participation in any discussions to "unify the different solutions" =E2=80=94 this is a perfect time for this. We currently are expecting to be scheduled to present virtually at the Japan IETF about both dCBOR and Gordian Envelope during the hours dedicated for the Dispatch group, but if you would also like to schedule some time with us either then, or another date virtually, we would be glad to share. We also are hoping to schedule a BOF at IETF San Francisco and plan to be there F2F. We are open to other collaborations, either at the dCBOR level, Gordian Envelope level, or the next generation of PKI. -- Christopher Allen --00000000000035bacb05f5f4c84f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, 16 February 2023 19:26 UTC=C2=A0Anders Rundgr= en <anders.rundgren.net= @gmail.com> wrote:
> On 2023-02-16 19:13, Laurence Lundb= lade wrote:
> > Is there a further detailed definition of determin= ism, such as what to do with floats?
>=C2=A0
> I started with = that a while ago,=C2=A0

We have more detail on= the specific choices that we've made in our dCBOR libraries, excerpted= from Wednesday's meeting of the Gordian Developer Community. In partic= ular, we have a lot of detail about how we handle floats and maps:

=
* Text Transcript: TBD


Blockchain Commons has embraced determi= nistic CBOR (dCBOR), as a the foundation for Gordian Envelope:
* Intro Article:=C2=A0https://www.blockchaincommons.com/introduction/Enve= lope-Intro/

We also pr= esented Gordian Envelope in the W3C Credentials Community Group last Januar= y. Transcript and OGG audio at=C2=A0https://w3c-ccg.github.io/meetings/2023-01-31/

On Thu, 16 February 2023 19:26 UTC=C2=A0Anders Ru= ndgren <anders.rundgren= .net@gmail.com> wrote:
> but now it may be time to = unify the different solutions.

We are currently in what we call the "Community = Review" phase=C2=A0for our dCBOR libraries before=C2=A0we submit them = for a third-party security review. We welcome participation in any discussi= ons to "unify the different solutions" =E2=80=94 this is a perfec= t time for this.

We currently are expecting to be = scheduled to present virtually at the Japan IETF about both dCBOR and Gordi= an Envelope during the hours dedicated for the Dispatch group, but if you w= ould also like to schedule some time with us either then, or another date v= irtually, we would be glad to share.=C2=A0

We also= are hoping to schedule a BOF at IETF San Francisco and plan to be there F2= F.

We are open to other collaborations, either at = the dCBOR level, Gordian Envelope level, or the next generation of PKI.

-- Christopher Allen



--00000000000035bacb05f5f4c84f--