Return-Path: X-Original-To: auth48archive@mail2.ietf.org Delivered-To: auth48archive@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id EB417FACEFA0 for ; Thu, 4 Jun 2026 05:56:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780577809; bh=E3tVcW47tDDbQ8Q+Iq5ixsecmvMiFvUIKIBZXlKlD98=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=BneYLS8qkDzDy9BHuWvcS4BYqHKQH+dGj8O4xAXP7ExOOQfaXB7B1mozE/I7cn992 AnDlsTHQhoesfx5ebycB1ubxJMvVdKDZFXYNQkCUc6ywnEQc1YCi2YdX6CuwqaAA1j fio47lfVBMPozDz8Ox68jA4XvGWzERpX5RBfHtKk= 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=or13.io 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 OnyAlAdZ5TqF for ; Thu, 4 Jun 2026 05:56:47 -0700 (PDT) Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (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 83DACFACEE92 for ; Thu, 4 Jun 2026 05:55:47 -0700 (PDT) Received: by mail-vk1-xa2d.google.com with SMTP id 71dfb90a1353d-59ebb89109aso539342e0c.1 for ; Thu, 04 Jun 2026 05:55:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1780577741; cv=none; d=google.com; s=arc-20240605; b=ZB52eCbRWiCvpfAknNscLvqMSSh3kU2BSlYa8GoSe6YE2reIjOKicQnfz+oQZKxnki E3meICeVLLa0lEA82ikiU9EzTKnMYP3TuhyyLbySjiNCfLYOMiAr0/7TZllhErLtSuhp SO90jqZCA8JbF8gy0OCTSMFwtdAodYISytJiXIY1xkBHHeiLUBP0hTVqDZKVk04ofMPf NPJNL8kRhRZW2jn2FsQ+j69NmGLdMSpYTRjLiyoY6rja4iaXuYeVTppNgeuEwtx1Ds+J ehE4yJHYgrAcdedLf4lSVdllOexiThoSh1HFKHnCiDej1Y/OxD21RL+JjCH+rkuxm/NL auuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=dy57vf/zaEe5C5k7pflMdHu+ilqx8dxm2SD+qSnrCoU=; fh=hklrrz2lynJyuhD+LPtG4vycnGgiZKDyV7HeEFZ4t2g=; b=XDBMIhvEYaPF5R0S827rhGN82pCV7YlhqQ4pKEF89u3MfcYQWzt8dwf4AcQASc91nE dhDIMiogxqOYymX//L0GX6VZaN9ktrtGCJ3csODS7tE28NDP9o3xjonKAzkgea8vrOLl JtfOwXG2AbRrtPFiYdAPQruJXAY7jz7boA3qpumBl3kdgPPC3FBuqWVJBpYBfN/Ez/pZ kwAGYH+94yVky1yzmVDLDJD7DoA6m3Q6HHcNNei3wM2AlNLqhj6N9T2PKR1JJJ1zphfc AbAMxv+5l84qwbvlfHx+BkarP04FqbAP3PQ+5FM5CZn0/lhnrs+nsWfWKd6bhsL8l9O1 MrKw==; darn=rfc-editor.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=or13.io; s=google; t=1780577741; x=1781182541; darn=rfc-editor.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dy57vf/zaEe5C5k7pflMdHu+ilqx8dxm2SD+qSnrCoU=; b=K+Ro+gteNJeg+g3NSekDeJDniTbMuBxH2k8IrKke9cjUJWGVqeqJ6rhLNWUYXy4k21 r4VyDJn2O95KiIR0+vcpOaz5aRm/F1mbOhl0eTE7ev0XiSkhOzCpbENWjzcvAfSeoVDq EBOrm415CDAAkVbK6AzGe6yxXGQ1rzpiklFUl3trvzlbRP5WZEsYsQhwLTyEFKeSK0QD G4nlQTGcaiGW33A8isvJL7eEeD9mhvbDMcdYPxlUnU2IKGlNW6hvpg6cIkUrU/8CRlk5 VI9zy2UwmPE365rfnRDM5hmjUxtTKTvIY1C8CVXlSYkGlNgkPI/nZTCO2Z5Ol7p43cfT qfRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1780577741; x=1781182541; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=dy57vf/zaEe5C5k7pflMdHu+ilqx8dxm2SD+qSnrCoU=; b=NtlMZTQF8A6b95qqpvlmzTiPHWd1HOFrfQn6Fyc+iZKSaaq2oTjxYhHotE7h3+cdyi DotqCuj85mJajtbkXtPnfxZTcmXWOLXj0ZO64VznY2VF155dgJeOjU2LkCMF+gh1h5Zw uUgDlXLcRaFo61YWkk3/vAOzxXAncnyeW9g1J7dOxvUuiZo2dTcPfH7iJR3mv0qbXt7o Z96R3TdHbO9QnuFw0rJ8HCRvUCDpL8o2egXMWZSdYBnP6lF4qGA1GY7RX3jmlnwJ6n49 RYVTrpIlwotSfEMA10VsBmFLTbF8e9rryXU0FqFjjJUxawGRO5qmHZIKo4EcqPEQ6reI JM4w== X-Forwarded-Encrypted: i=1; AFNElJ8CLY0o9U+Z1Y5zD4NywkpJLJVz+z3xeCySqV8gL8u3wbv+F/tlXC6FxLyg7HdvCW8YGEVT/4pIbt9FK+Kt@rfc-editor.org X-Gm-Message-State: AOJu0YzP13aHhUDhnf537cI87TYjBD61qy/fVjaDNe7dws/YopIvDBGM muW5aTjpxVH2BAT3atjtObsKvw5oEHqFMSHsXNuhDMS7z0q2k+bhUOLSMP/HLPTC/UY/kvPHfXh xDr7k9HTmHCMJ7nzgl7HrB8PqtthnOtiOwDS+44TAPQ== X-Gm-Gg: Acq92OEdSnq7GJNUI6KMn5s7NglOHXaHMneW92z/QkKA3yzHtL0fcJYLQeP9z1aPDig ahRgtiKheeHESYhY3ivRZbickPJMgh8OoPmpKPVnxQu0uE0sF5O3Hojs38Q+eGl0ZmCQ+aIvS2H cxKhbNS0tc8fGfCyiMGQatipki6izu559vjrD+zwnMB6/uvdoucGiuwUErVAkRMclad6UBqVtd5 Fg+tRxMDSHD3qwmLef4znboEnghzQUM8wobvDOPdBTXjQtJCAdLimjRFGtj4KrtaaXpGbD9H9+1 BwmpVChQ5hXIZU9VOKxhKBmWlh3Isbgrb462b6Yus7ciJ249IBJM X-Received: by 2002:a05:6122:3788:b0:56f:6b46:28be with SMTP id 71dfb90a1353d-5a6e61c91cdmr4678026e0c.8.1780577741423; Thu, 04 Jun 2026 05:55:41 -0700 (PDT) MIME-Version: 1.0 References: <177933119520.10.8108173421221401387@rfc-editor.org> <64AEC0B7-82F5-420F-8226-80E8363163EE@staff.rfc-editor.org> <89d21ea2-00e4-3159-6199-5aac513b26ac@ietf.contact> In-Reply-To: <89d21ea2-00e4-3159-6199-5aac513b26ac@ietf.contact> From: Orie Date: Thu, 4 Jun 2026 07:55:30 -0500 X-Gm-Features: AVVi8Cf5nWd0egnW75wJG6T0BIcBJNu29Nc35ossZ2njdi5Ot_AfieTDVQ-ZYmc Message-ID: To: Henk Birkholz Content-Type: multipart/alternative; boundary="000000000000c5d19406536d0f79" Message-ID-Hash: 6VEAPAJYLO5MCLVJVV25WZWN2YKAD65Z X-Message-ID-Hash: 6VEAPAJYLO5MCLVJVV25WZWN2YKAD65Z X-MailFrom: orie@or13.io X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Megan Ferguson , Steve Lasker , auth48archive@rfc-editor.org, jon.geater@gmail.com, debcooley1@gmail.com, stndrds-inacio@andrew.cmu.edu, sec-ads@ietf.org, cose-chairs@ietf.org, rfc-editor@rfc-editor.org X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Bauth48=5D_Re=3A_Final_review_in_markdown=3A_RFC-to-be_9995_draf?= =?utf-8?q?t-ietf-cose-hash-envelope_for_your_review?= List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000c5d19406536d0f79 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Lets go with Henk's reply regarding commas. OS On Thu, Jun 4, 2026 at 7:54=E2=80=AFAM Henk Birkholz wrote: > Hi! > > Sorry, maybe my reply never made it out. I have to disagree with Orie on > (3) here and I thought that I stated that before (but cannot find a > corresponding reply in my Sent box, so here it is "again"): > > For consistency over all CDDL, I would propose: > > > Hash_Envelope_Protected_Header =3D { > > ? &(alg: 1) =3D> int, > > &(payload_hash_alg: 258) =3D> int, > > ? &(payload_preimage_content_type: 259) =3D> uint / tstr, > > ? &(payload_location: 260) =3D> tstr, > > * (int / tstr) =3D> any > > } > > which would be consistent with the previous CDDL block: > > > Hash_Envelope_as_COSE_Sign1 =3D [ > > protected: bstr .cbor Hash_Envelope_Protected_Header, > > unprotected: Hash_Envelope_Unprotected_Header, > > payload: bstr / nil, > > signature: bstr > > ] > > All of the variants are correct. This proposal is purely optical and > target towards consistency. > > > Viele Gr=C3=BC=C3=9Fe, > > Henk > > > > > On 04.06.26 14:41, Orie wrote: > > Hi, > > > > Addressing 3 and 11: > > > > 3. keep the comma. > > 11. use " for values, not `. > > > > Regards, > > > > OS > > > > On Wed, May 27, 2026 at 12:30=E2=80=AFPM Megan Ferguson > > = > > > > wrote: > > > > Hi Orie, > > > > Thanks for the reply and guidance! > > > > We have updated as requested. We believe questions #3 and #11 > > remain unresolved for now. > > > > We have posted the updated files below. Please review carefully as > > we do not make changes once a document is published as an RFC. > > > > The files are available here (please refresh): > > https://www.rfc-editor.org/authors/rfc9995.md > > > > https://www.rfc-editor.org/authors/rfc9995.html > > > > https://www.rfc-editor.org/authors/rfc9995.pdf > > > > https://www.rfc-editor.org/authors/rfc9995.txt > > > > > > The diff files are available here (please refresh): > > https://www.rfc-editor.org/authors/rfc9995-diff.html > > > (comprehensive) > > https://www.rfc-editor.org/authors/rfc9995-rfcdiff.html > > (side by > side) > > > > https://www.rfc-editor.org/authors/rfc9995-auth48diff.html > > (AUTH4= 8 > > changes only) > > https://www.rfc-editor.org/authors/rfc9995-auth48rfcdiff.html > > > > (side by side) > > > > The details of the AUTH48 status of your document are here: > > https://www.rfc-editor.org/auth48/rfc9995 > > > > > > Thank you. > > > > Megan Ferguson > > RFC Production Center > > > > > > > On May 27, 2026, at 7:15=E2=80=AFAM, Orie > > wrote: > > > > > > > > > Hi, > > > > > > Thank you for the work on this document! > > > Inline for the rest: > > > > > > > > > On Tue, May 26, 2026 at 11:56=E2=80=AFAM Megan Ferguson > > > > wrote: > > > Just resending to add Steve=E2=80=99s preferred email to the thr= ead. > > > > > > > On May 20, 2026, at 8:39=E2=80=AFPM, rfc-editor@rfc-editor.org > > wrote: > > > > > > > > Authors, > > > > > > > > While reviewing this document during AUTH48, please resolve (a= s > > necessary) the following questions, which are also in the source > file. > > > > > > > > 1) > > > > > > > > > > > > 2) > > > > > > > > > > I prefer your edit to the original here. > > > > > > > > > > > 3) > > > > > > > > > > I prefer the comma, though I will admit I have lost track of CDD= L > > best practices for this... @Henk Birkholz ? > > > > > > > > > > > 4) > > > > > > > > > > > > 5) > > > > > > > > > > Thanks for correcting! > > > > > > > > > > > 6) > > > > > > > > > > "the" could be removed here I think. > > > > > > > > > > > 7) > > > > > > I think it can remain lower case here. > > > > > > > > > > > > 8) > > > > > > Looks good to me. > > > > > > > > > > > > 9) > > > > > > It must be "COSE_Mac" and "SHA-256". > > > > > > > > > > > > > > > 10) > > > > > > > > > > No, but expanded as "Software Package Data Exchange" seems like = a > > good idea: > > https://en.wikipedia.org/wiki/Software_Package_Data_Exchange > > > > > > > > > > > > > > > > 11) > > > > > > > > > > Lets address this at the end, to avoid chatter, I'm not attached > > to making any changes here, just called it out during intake. > > > > > > > > > > > Thank you. > > > > Megan Ferguson and Sandy Ginoza > > > > RFC Production Center > > > > > > > > > > > > > > > > > > > > On May 20, 2026, at 4:20=E2=80=AFPM, rfc-editor@rfc-editor.org > > wrote: > > > > > > > > RFC Author(s): > > > > > > > > Your document is now ready for Final Review (previously AUTH48= ). > > > > > > > > The document was edited in kramdown-rfc as part of the RPC > > pilot test (see > > > > > > > https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_kramdown_rfc= < > https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_kramdown_rfc= >). > > > > > > > > Please review the procedures for your review using kramdown-rf= c: > > > > > > > > > > > https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_instructions= _completing_auth48_using_kramdown > < > https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_instructions= _completing_auth48_using_kramdown > > > > > > > > > > Once the review is complete, it will be published as an RFC. > > > > > > > > > > > > Files > > > > ----- > > > > > > > > The files are available here: > > > > https://www.rfc-editor.org/authors/rfc9995.md > > > > > > https://www.rfc-editor.org/authors/rfc9995.html > > > > > > https://www.rfc-editor.org/authors/rfc9995.pdf > > > > > > https://www.rfc-editor.org/authors/rfc9995.txt > > > > > > > > > > Diff file of the text: > > > > https://www.rfc-editor.org/authors/rfc9995-diff.html > > > > > > https://www.rfc-editor.org/authors/rfc9995-rfcdiff.html > > (side by > side) > > > > > > > > Diff of the kramdown: > > > > https://www.rfc-editor.org/authors/rfc9995-md-diff.html > > > > > > https://www.rfc-editor.org/authors/rfc9995-md-rfcdiff.html > > (side > > by side) > > > > > > > > > > > > Tracking progress > > > > ----------------- > > > > > > > > The details of the AUTH48 status of your document are here: > > > > https://www.rfc-editor.org/auth48/rfc9995 > > > > > > > > > > > > > > Please let us know if you have any questions. > > > > > > > > Thank you for your cooperation, > > > > > > > > RFC Editor > > > > > > > > -------------------------------------- > > > > RFC 9995 (draft-ietf-cose-hash-envelope) > > > > > > > > Title : COSE Hash Envelope > > > > Author(s) : O. Steele, > > > > S. Lasker, > > > > H. Birkholz > > > > WG Chair(s) : Ivaylo Petrov, Michael Jones > > > > Area Director(s) : Deb Cooley, Christopher Inacio > > > > > > > > > > --000000000000c5d19406536d0f79 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Lets go with Henk's reply regarding commas.

OS<= /div>
On Thu, Jun 4, 2026 at 7:54=E2=80=AFAM Henk Birkholz &= lt;henk.birkholz@ietf.contact> wrote:
Hi!

Sorry, maybe my reply never made it out. I have to disagree with Orie on (3) here and I thought that I stated that before (but cannot find a
corresponding reply in my Sent box, so here it is "again"):

For consistency over all CDDL, I would propose:

>=C2=A0 =C2=A0 Hash_Envelope_Protected_Header =3D {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 ? &(alg: 1) =3D> int,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &(payload_hash_alg: 258) =3D> int, >=C2=A0 =C2=A0 =C2=A0 =C2=A0 ? &(payload_preimage_content_type: 259)= =3D> uint / tstr,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 ? &(payload_location: 260) =3D> tstr= ,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 * (int / tstr) =3D> any
>=C2=A0 =C2=A0 }

which would be consistent with the previous CDDL block:

>=C2=A0 =C2=A0 Hash_Envelope_as_COSE_Sign1 =3D [
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 protected: bstr .cbor Hash_Envelope_Protect= ed_Header,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 unprotected: Hash_Envelope_Unprotected_Head= er,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 payload: bstr / nil,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 signature: bstr
>=C2=A0 =C2=A0 ]

All of the variants are correct. This proposal is purely optical and
target towards consistency.


Viele Gr=C3=BC=C3=9Fe,

Henk




On 04.06.26 14:41, Orie wrote:
> Hi,
>
> Addressing 3 and 11:
>
> 3. keep the comma.
> 11. use " for values, not `.
>
> Regards,
>
> OS
>
> On Wed, May 27, 2026 at 12:30=E2=80=AFPM Megan Ferguson
> <mferguson@staff.rfc-editor.org <mailto:mferguson@staff.rfc-editor.org= >>
> wrote:
>
>=C2=A0 =C2=A0 =C2=A0Hi Orie,
>
>=C2=A0 =C2=A0 =C2=A0Thanks for the reply and guidance!
>
>=C2=A0 =C2=A0 =C2=A0We have updated as requested.=C2=A0 We believe ques= tions #3 and #11
>=C2=A0 =C2=A0 =C2=A0remain unresolved for now.
>
>=C2=A0 =C2=A0 =C2=A0We have posted the updated files below.=C2=A0 Pleas= e review carefully as
>=C2=A0 =C2=A0 =C2=A0we do not make changes once a document is published= as an RFC.
>
>=C2=A0 =C2=A0 =C2=A0The files are available here (please refresh):
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-editor.org/auth= ors/rfc9995.md
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org/= authors/rfc9995.md>
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-editor.org/au= thors/rfc9995.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.or= g/authors/rfc9995.html>
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-editor.org/aut= hors/rfc9995.pdf
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org= /authors/rfc9995.pdf>
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-editor.org/aut= hors/rfc9995.txt
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org= /authors/rfc9995.txt>
>
>=C2=A0 =C2=A0 =C2=A0The diff files are available here (please refresh):=
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-editor.o= rg/authors/rfc9995-diff.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-edit= or.org/authors/rfc9995-diff.html> (comprehensive)
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-edito= r.org/authors/rfc9995-rfcdiff.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-e= ditor.org/authors/rfc9995-rfcdiff.html> (side by side)
>
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-ed= itor.org/authors/rfc9995-auth48diff.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rf= c-editor.org/authors/rfc9995-auth48diff.html> (AUTH48
>=C2=A0 =C2=A0 =C2=A0changes only)
>=C2=A0 =C2=A0 =C2=A0https://www.rfc= -editor.org/authors/rfc9995-auth48rfcdiff.html
>=C2=A0 =C2=A0 =C2=A0<https://www= .rfc-editor.org/authors/rfc9995-auth48rfcdiff.html>
>=C2=A0 =C2=A0 =C2=A0(side by side)
>
>=C2=A0 =C2=A0 =C2=A0The details of the AUTH48 status of your document a= re here:
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-editor.org/auth48/r= fc9995
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org/auth= 48/rfc9995>
>
>=C2=A0 =C2=A0 =C2=A0Thank you.
>
>=C2=A0 =C2=A0 =C2=A0Megan Ferguson
>=C2=A0 =C2=A0 =C2=A0RFC Production Center
>
>
>=C2=A0 =C2=A0 =C2=A0 > On May 27, 2026, at 7:15=E2=80=AFAM, Orie <= ;orie@or13.io
>=C2=A0 =C2=A0 =C2=A0<mailto:orie@or13.io>> wrote:
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > Hi,
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > Thank you for the work on this document!
>=C2=A0 =C2=A0 =C2=A0 > Inline for the rest:
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > On Tue, May 26, 2026 at 11:56=E2=80=AFAM Mega= n Ferguson
>=C2=A0 =C2=A0 =C2=A0<mferguson@staff.rfc-editor.org
>=C2=A0 =C2=A0 =C2=A0<mailto:mferguson@staff.rfc-editor.org>> wrot= e:
>=C2=A0 =C2=A0 =C2=A0 > Just resending to add Steve=E2=80=99s preferr= ed email to the thread.
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > > On May 20, 2026, at 8:39=E2=80=AFPM, rfc-editor@rfc-= editor.org
>=C2=A0 =C2=A0 =C2=A0<mailto:rfc-editor@rfc-editor.org> wrote:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Authors,
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > While reviewing this document during AUT= H48, please resolve (as
>=C2=A0 =C2=A0 =C2=A0necessary) the following questions, which are also = in the source file.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 1) <!-- [rfced] Please insert any key= words (beyond those that
>=C2=A0 =C2=A0 =C2=A0appear in
>=C2=A0 =C2=A0 =C2=A0 > > the title) for use on https://ww= w.rfc-editor.org/search
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org/search&g= t;. -->
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 2) <!--[rfced] Please review and conf= irm this suggested update
>=C2=A0 =C2=A0 =C2=A0maintains
>=C2=A0 =C2=A0 =C2=A0 > > your intended meaning:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Original:
>=C2=A0 =C2=A0 =C2=A0 > > COSE defined detached payloads in Sectio= n 2 of [RFC9052], using
>=C2=A0 =C2=A0 =C2=A0nil as
>=C2=A0 =C2=A0 =C2=A0 > > the payload.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Perhaps:
>=C2=A0 =C2=A0 =C2=A0 > > Section 2 of [RFC9052] defines detached = payloads for COSE,
>=C2=A0 =C2=A0 =C2=A0using nil
>=C2=A0 =C2=A0 =C2=A0 > > as the payload.=C2=A0 -->
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > I prefer your edit to the original here.
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 3) <!--[rfced] Please review our upda= te to add a comma at the
>=C2=A0 =C2=A0 =C2=A0end of a line in the CDDL:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Original:
>=C2=A0 =C2=A0 =C2=A0 > > &(payload_hash_alg: 258) =3D> int=
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Current:
>=C2=A0 =C2=A0 =C2=A0 > > &(payload_hash_alg: 258) =3D> int= ,
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > -->
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > I prefer the comma, though I will admit I hav= e lost track of CDDL
>=C2=A0 =C2=A0 =C2=A0best practices for this... @Henk Birkholz ?
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 4) <!--[rfced] Please review our upda= tes to the following text
>=C2=A0 =C2=A0 =C2=A0to ensure
>=C2=A0 =C2=A0 =C2=A0 > > we have maintained your intended meaning= :
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Original:
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0For example, when the actual= content is a bstr, a Verifier
>=C2=A0 =C2=A0 =C2=A0appraising
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0a content-type bstr has to d= ecide if that bstr describes the
>=C2=A0 =C2=A0 =C2=A0digest
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0bytes or the preimage bytes.= =C2=A0 Setting preimage-content-type
>=C2=A0 =C2=A0 =C2=A0to bstr,
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0makes it clear that the prei= mage bytes themselves were a bstr.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Current:
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0For example, when the actual= content is a byte string (bstr), a
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0verifier appraising the payl= oad has to decide whether that bstr
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0represents the digest bytes = or the preimage bytes.=C2=A0 Setting
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0payload_preimage_content_typ= e to bstr makes it clear that the
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0preimage bytes themselves we= re a bstr.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > Current looks good to me.
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > > -->
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 5) <!-- [rfced] We updated the URL fo= r application/spdx+json as
>=C2=A0 =C2=A0 =C2=A0shown below, as the original was 404. Please review= and let us know
>=C2=A0 =C2=A0 =C2=A0if any corrections are needed.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Original:
>=C2=A0 =C2=A0 =C2=A0https://www.ia= na.org/assignments/media-types/application/spdx+
>=C2=A0 =C2=A0 =C2=A0<https://ww= w.iana.org/assignments/media-types/application/spdx+>
>=C2=A0 =C2=A0 =C2=A0 > > current:
>=C2=A0 =C2=A0 =C2=A0https://ww= w.iana.org/assignments/media-types/application/spdx+json
>=C2=A0 =C2=A0 =C2=A0<https:= //www.iana.org/assignments/media-types/application/spdx+json>
>=C2=A0 =C2=A0 =C2=A0 > > -->
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > Thanks for correcting!
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 6) <!--[rfced] Using "the" = before manifest.spdx.json makes it
>=C2=A0 =C2=A0 =C2=A0feel like a
>=C2=A0 =C2=A0 =C2=A0 > > label is missing.=C2=A0 Please review. >=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Original:
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0The payload of this COSE_Sig= n1 is the SHA256 hash of the
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0manifest.spdx.json.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > -->
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > "the" could be removed here I think= .
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 7) <!--[rfced] Please review if inter= net should be Internet here:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Original:
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0Verifiers that do not have a= ccess to the internet and obtain the
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0preimage via other means wil= l not be able to perform that
>=C2=A0 =C2=A0 =C2=A0check, nor
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0to derive utility from it. >=C2=A0 =C2=A0 =C2=A0 > > -->
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > I think it can remain lower case here.
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 8) <!-- [rfced] We updated the "= Value Registry" column of table
>=C2=A0 =C2=A0 =C2=A01 to include references to "CoAP Content-Forma= ts" and "COSE
>=C2=A0 =C2=A0 =C2=A0Algorithms".=C2=A0 Please review and let us kn= ow any concerns.=C2=A0 The
>=C2=A0 =C2=A0 =C2=A0references have been added as informative reference= s.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Because we added a reference to the COSE= Algorithms registry,
>=C2=A0 =C2=A0 =C2=A0we also replaced the URL below with an in text cita= tion.=C2=A0 Please
>=C2=A0 =C2=A0 =C2=A0review.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Original:
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0Note that when using a pre-h= ash
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0algorithm, the algorithm MUS= T be registered in the IANA COSE
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0Algorithms registry (https://www.iana.org/assignments/cose/
>=C2=A0 =C2=A0 =C2=A0<https://www.iana.org/assignments/c= ose/>
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0cose.xhtml#algorithms), and = MUST be distinguishable from
>=C2=A0 =C2=A0 =C2=A0non-pre hash
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0variants that may also be pr= esent.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Current:
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0Note that, when using a pre-= hash algorithm,
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0the algorithm MUST be regist= ered in the IANA "COSE Algorithms"
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0registry [COSE-Algorithms] a= nd MUST be distinguishable from
>=C2=A0 =C2=A0 =C2=A0non-pre-
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0hash variants that may also = be present.
>=C2=A0 =C2=A0 =C2=A0 > > -->
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > Looks good to me.
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 9) <!--[rfced] Please review the foll= owing possible
>=C2=A0 =C2=A0 =C2=A0inconsistencies with regard to terminology:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > COSE_MAC vs. COSE_Mac
>=C2=A0 =C2=A0 =C2=A0 > > SHA-256 vs. SHA256
>=C2=A0 =C2=A0 =C2=A0 > > SHA-384 vs. SHA384
>=C2=A0 =C2=A0 =C2=A0 > > -->
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > It must be "COSE_Mac" and=C2=A0 &qu= ot;SHA-256".
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 10) <!--[rfced] We had the following = questions related to
>=C2=A0 =C2=A0 =C2=A0abbreviation use in the document:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > a) Please note that we have expanded abb= reviations on first use.
>=C2=A0 =C2=A0 =C2=A0 > > Please review for accuracy.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > b) Would you like to expand SPDX as &quo= t;System Package Data
>=C2=A0 =C2=A0 =C2=A0Exchange" on
>=C2=A0 =C2=A0 =C2=A0 > > first use?=C2=A0 -->
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > No, but expanded as "Software Package Da= ta Exchange" seems like a
>=C2=A0 =C2=A0 =C2=A0good idea:
>=C2=A0 =C2=A0 =C2=A0https://en.wikip= edia.org/wiki/Software_Package_Data_Exchange
>=C2=A0 =C2=A0 =C2=A0<https://en.w= ikipedia.org/wiki/Software_Package_Data_Exchange>
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > 11) <!--[rfced] In the response to ou= r intake form, we saw:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > We only use ` ... I suspect we might be = better off using " for
>=C2=A0 =C2=A0 =C2=A0a few
>=C2=A0 =C2=A0 =C2=A0 > > values instead of `, and reserve ` for h= ighlighting code points and
>=C2=A0 =C2=A0 =C2=A0 > > not examples.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Please let us know if/how updates should= be made using Old/New
>=C2=A0 =C2=A0 =C2=A0and/or
>=C2=A0 =C2=A0 =C2=A0 > > by updating the edited file directly. --= >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > Lets address this at the end, to avoid chatte= r, I'm not attached
>=C2=A0 =C2=A0 =C2=A0to making any changes here, just called it out duri= ng intake.
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Thank you.
>=C2=A0 =C2=A0 =C2=A0 > > Megan Ferguson and Sandy Ginoza
>=C2=A0 =C2=A0 =C2=A0 > > RFC Production Center
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > On May 20, 2026, at 4:20=E2=80=AFPM, rfc-editor@rfc-= editor.org
>=C2=A0 =C2=A0 =C2=A0<mailto:rfc-editor@rfc-editor.org> wrote:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > RFC Author(s):
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Your document is now ready for Final Rev= iew (previously AUTH48).
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > The document was edited in kramdown-rfc = as part of the RPC
>=C2=A0 =C2=A0 =C2=A0pilot test (see
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0htt= ps://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_kramdown_rfc = <https://www.rfc-editor.= org/rpc/wiki/doku.php?id=3Dpilot_test_kramdown_rfc>).
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Please review the procedures for your re= view using kramdown-rfc:
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0https://www.rfc-editor.org/rpc/wiki/doku.php?= id=3Dpilot_test_instructions_completing_auth48_using_kramdown <https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_instructions_= completing_auth48_using_kramdown>
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Once the review is complete, it will be = published as an RFC.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Files
>=C2=A0 =C2=A0 =C2=A0 > > -----
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > The files are available here:
>=C2=A0 =C2=A0 =C2=A0 > > https://www.rfc-edit= or.org/authors/rfc9995.md
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org/= authors/rfc9995.md>
>=C2=A0 =C2=A0 =C2=A0 > > https://www.rfc-ed= itor.org/authors/rfc9995.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.or= g/authors/rfc9995.html>
>=C2=A0 =C2=A0 =C2=A0 > > https://www.rfc-edi= tor.org/authors/rfc9995.pdf
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org= /authors/rfc9995.pdf>
>=C2=A0 =C2=A0 =C2=A0 > > https://www.rfc-edi= tor.org/authors/rfc9995.txt
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org= /authors/rfc9995.txt>
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Diff file of the text:
>=C2=A0 =C2=A0 =C2=A0 > > https://www.r= fc-editor.org/authors/rfc9995-diff.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-edit= or.org/authors/rfc9995-diff.html>
>=C2=A0 =C2=A0 =C2=A0 > > https://ww= w.rfc-editor.org/authors/rfc9995-rfcdiff.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-e= ditor.org/authors/rfc9995-rfcdiff.html> (side by side)
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Diff of the kramdown:
>=C2=A0 =C2=A0 =C2=A0 > > https://ww= w.rfc-editor.org/authors/rfc9995-md-diff.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-e= ditor.org/authors/rfc9995-md-diff.html>
>=C2=A0 =C2=A0 =C2=A0 > > https:/= /www.rfc-editor.org/authors/rfc9995-md-rfcdiff.html
>=C2=A0 =C2=A0 =C2=A0<https://www.rf= c-editor.org/authors/rfc9995-md-rfcdiff.html> (side
>=C2=A0 =C2=A0 =C2=A0by side)
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Tracking progress
>=C2=A0 =C2=A0 =C2=A0 > > -----------------
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > The details of the AUTH48 status of your= document are here:
>=C2=A0 =C2=A0 =C2=A0 > > https://www.rfc-editor.o= rg/auth48/rfc9995
>=C2=A0 =C2=A0 =C2=A0<https://www.rfc-editor.org/auth= 48/rfc9995>
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Please let us know if you have any quest= ions.
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Thank you for your cooperation,
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > RFC Editor
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > -------------------------------------- >=C2=A0 =C2=A0 =C2=A0 > > RFC 9995 (draft-ietf-cose-hash-envelope)=
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 > > Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 : COSE Hash Envelope
>=C2=A0 =C2=A0 =C2=A0 > > Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 : O= . Steele,
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 S. Lasker,
>=C2=A0 =C2=A0 =C2=A0 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 H. Birkholz
>=C2=A0 =C2=A0 =C2=A0 > > WG Chair(s)=C2=A0 =C2=A0 =C2=A0 : Ivaylo= Petrov, Michael Jones
>=C2=A0 =C2=A0 =C2=A0 > > Area Director(s) : Deb Cooley, Christoph= er Inacio
>=C2=A0 =C2=A0 =C2=A0 > >
>=C2=A0 =C2=A0 =C2=A0 >
>
--000000000000c5d19406536d0f79--