From nobody Fri Aug 18 01:41:34 2017 Return-Path: X-Original-To: cose@ietfa.amsl.com Delivered-To: cose@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D91521326E8 for ; Fri, 18 Aug 2017 01:41:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=erdtman-se.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19c5SkytGdVn for ; Fri, 18 Aug 2017 01:41:30 -0700 (PDT) Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6693713280F for ; Fri, 18 Aug 2017 01:41:30 -0700 (PDT) Received: by mail-pg0-x22c.google.com with SMTP id u185so59962250pgb.1 for ; Fri, 18 Aug 2017 01:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erdtman-se.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=YwYDDhD24stWBSoe3YvZQpCsq4VwvJgsN9KKWLSJNSM=; b=ifVXJCGgcYdf0GB6jgnZytsbCFjb9Seu/F1Ym/PutwI56uYdnsik2SaqrjhFGX0beN uxpzoKU6dP59X7V9qgJLretQGXFfvWvavGo8LYcRT9n34DlEQjOWopglPoj/+6vDi4+L HYiZMrHApje9+JHFnL0iUx34ftScX+T+ixcfjw5NwkRepXynA3ymvw8m/nCqWWcd1bwo 9hQaoqPo6Zs/quRGDxLbxWr3bE9QZW0+zXnn5+HDA5AwaLIh/yPEHFOvWO6IBS9s/mB3 1salHYKZwaE1fu22VJkVuhKGB+hBdvRgr74ee7EFULTr25GvBRayu7N/IKAzei/snrxS Ck9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=YwYDDhD24stWBSoe3YvZQpCsq4VwvJgsN9KKWLSJNSM=; b=GkHq5DHWuTehrA2wX2a5Nj5lHf/7IOKaICaIgAF4nmdW2UQ97yenevCd4Ax9TWH+aV NkLtJINB313sc15h9aaad8k8+WGpVqnp+nM0+sV3wsqrqXOt3qbtIhPBRfOuiQIr4VCl Zg6ly0h8TOp78Cd9sUMC+/R6SGw+NuJRzOdQOuwMvNNLNkHOimD19kHhpoHDTTYk1jxJ f0kEefY8XZDgQuBrkbVpzoy+KxIfKoNHmqcuF8K8R2n1z6uEve6E6oo4R1fKvisLP3HL 1/EpgdWRiIQUg0gwEpWPJ+p/1Da/zjlwjxZsP8T37124PUtxunkC0hb7E5C8gT0JeSG2 nxKQ== X-Gm-Message-State: AHYfb5ixFBFx0B0YlIPTrnlrIxgRG7nEOa4sfGRXYC/+eIhf8+bMplF6 Yan2wQvPa+gJFhKrUk9sKDsVsS09XxmF+luFBQ== X-Received: by 10.84.224.198 with SMTP id k6mr9059596pln.239.1503045689604; Fri, 18 Aug 2017 01:41:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.151.67 with HTTP; Fri, 18 Aug 2017 01:41:29 -0700 (PDT) In-Reply-To: References: <20170705181605.29A05B81904@rfc-editor.org> <70635E3E-53E9-41B8-89E5-2BBAA9B97C3C@mit.edu> From: Samuel Erdtman Date: Fri, 18 Aug 2017 10:41:29 +0200 Message-ID: To: cose Content-Type: multipart/alternative; boundary="f40304362194690ed50557031835" Archived-At: Subject: Re: [COSE] RFC 8152 on CBOR Object Signing and Encryption (COSE) X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Aug 2017 08:41:33 -0000 --f40304362194690ed50557031835 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable A bit late, but congratulations, Jim and others involved! I think this is a great document, lets implement and deploy stuff. Cheers //Samuel On Thu, Jul 6, 2017 at 3:14 AM, Kepeng Li wrote: > Congratulation! > > Well done, everybody! > > Kepeng > > > =E5=9C=A8 06/07/2017, 2:57 AM=EF=BC=8C "COSE on behalf of Justin Richer" > =E5=86=99=E5=85=A5: > > >Congratulations to the working group! It=E2=80=99s wonderful seeing some= thing > >finally cross the finish line. > > > >Your formerly COSE chair, > > =E2=80=94 Justin > > > >> On Jul 5, 2017, at 2:16 PM, rfc-editor@rfc-editor.org wrote: > >> > >> A new Request for Comments is now available in online RFC libraries. > >> > >> > >> RFC 8152 > >> > >> Title: CBOR Object Signing and Encryption (COSE) > >> Author: J. Schaad > >> Status: Standards Track > >> Stream: IETF > >> Date: July 2017 > >> Mailbox: ietf@augustcellars.com > >> Pages: 121 > >> Characters: 256190 > >> Updates/Obsoletes/SeeAlso: None > >> > >> I-D Tag: draft-ietf-cose-msg-24.txt > >> > >> URL: https://www.rfc-editor.org/info/rfc8152 > >> > >> DOI: 10.17487/RFC8152 > >> > >> Concise Binary Object Representation (CBOR) is a data format designed > >> for small code size and small message size. There is a need for the > >> ability to have basic security services defined for this data format. > >> This document defines the CBOR Object Signing and Encryption (COSE) > >> protocol. This specification describes how to create and process > >> signatures, message authentication codes, and encryption using CBOR > >> for serialization. This specification additionally describes how to > >> represent cryptographic keys using CBOR. > >> > >> This document is a product of the CBOR Object Signing and Encryption > >>Working Group of the IETF. > >> > >> This is now a Proposed Standard. > >> > >> STANDARDS TRACK: This document specifies an Internet Standards Track > >> protocol for the Internet community, and requests discussion and > >>suggestions > >> for improvements. Please refer to the current edition of the Official > >> Internet Protocol Standards (https://www.rfc-editor.org/standards) for > >>the > >> standardization state and status of this protocol. Distribution of > >>this > >> memo is unlimited. > >> > >> This announcement is sent to the IETF-Announce and rfc-dist lists. > >> To subscribe or unsubscribe, see > >> https://www.ietf.org/mailman/listinfo/ietf-announce > >> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > >> > >> For searching the RFC series, see https://www.rfc-editor.org/search > >> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk > >> > >> Requests for special distribution should be addressed to either the > >> author of the RFC in question, or to rfc-editor@rfc-editor.org. Unles= s > >> specifically noted otherwise on the RFC itself, all RFCs are for > >> unlimited distribution. > >> > >> > >> The RFC Editor Team > >> Association Management Solutions, LLC > >> > >> > >> _______________________________________________ > >> COSE mailing list > >> COSE@ietf.org > >> https://www.ietf.org/mailman/listinfo/cose > > > >_______________________________________________ > >COSE mailing list > >COSE@ietf.org > >https://www.ietf.org/mailman/listinfo/cose > > > _______________________________________________ > COSE mailing list > COSE@ietf.org > https://www.ietf.org/mailman/listinfo/cose > --f40304362194690ed50557031835 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
A bit late, but congratulations, Jim and others = involved!

I think this is a great document, lets implement and= deploy stuff.

Cheers
//Samuel

=

On Thu, Jul 6, 2017 at 3:14 AM, Kepeng Li <kepeng.lkp@alibab= a-inc.com> wrote:
Congratu= lation!

Well done, everybody!

Kepeng


=E5=9C=A8 06/07/2017, 2:57 AM=EF=BC=8C "COSE on behalf of Justin Riche= r"
<cose-bounces@ietf.org on b= ehalf of jricher@mit.edu> =E5=86= =99=E5=85=A5:

>Congratulations to the working group! It=E2=80=99s wonderful seeing som= ething
>finally cross the finish line.
>
>Your formerly COSE chair,
>=C2=A0 =E2=80=94 Justin
>
>> On Jul 5, 2017, at 2:16 PM, rfc-editor@rfc-editor.org wrote:
>>
>> A new Request for Comments is now available in online RFC librarie= s.
>>
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 RFC 8152
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 CBOR Object = Signing and Encryption (COSE)
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author:=C2=A0 =C2=A0 =C2=A0J. Schaad >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0Standards Tr= ack
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stream:=C2=A0 =C2=A0 =C2=A0IETF
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date:=C2=A0 =C2=A0 =C2=A0 =C2=A0July 20= 17
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Mailbox:=C2=A0 =C2=A0 ietf@augustcellars.com
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 121
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Characters: 256190
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Updates/Obsoletes/SeeAlso:=C2=A0 =C2=A0= None
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 I-D Tag:=C2=A0 =C2=A0 draft-ietf-cose-m= sg-24.txt
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.rfc-editor.org/info/rfc8152
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 DOI:=C2=A0 =C2=A0 =C2=A0 =C2=A0 10.1748= 7/RFC8152
>>
>> Concise Binary Object Representation (CBOR) is a data format desig= ned
>> for small code size and small message size.=C2=A0 There is a need = for the
>> ability to have basic security services defined for this data form= at.
>> This document defines the CBOR Object Signing and Encryption (COSE= )
>> protocol.=C2=A0 This specification describes how to create and pro= cess
>> signatures, message authentication codes, and encryption using CBO= R
>> for serialization.=C2=A0 This specification additionally describes= how to
>> represent cryptographic keys using CBOR.
>>
>> This document is a product of the CBOR Object Signing and Encrypti= on
>>Working Group of the IETF.
>>
>> This is now a Proposed Standard.
>>
>> STANDARDS TRACK: This document specifies an Internet Standards Tra= ck
>> protocol for the Internet community, and requests discussion and >>suggestions
>> for improvements.=C2=A0 Please refer to the current edition of the= Official
>> Internet Protocol Standards (https://www.rfc-editor.org= /standards) for
>>the
>> standardization state and status of this protocol.=C2=A0 Distribut= ion of
>>this
>> memo is unlimited.
>>
>> This announcement is sent to the IETF-Announce and rfc-dist lists.=
>> To subscribe or unsubscribe, see
>>=C2=A0 https://www.ietf.org/mailman/= listinfo/ietf-announce
>>=C2=A0 https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>
>> For searching the RFC series, see https://www.rfc-editor.o= rg/search
>> For downloading RFCs, see https://www.rfc-editor.or= g/retrieve/bulk
>>
>> Requests for special distribution should be addressed to either th= e
>> author of the RFC in question, or to rfc-editor@rfc-editor.org.=C2=A0 Unless
>> specifically noted otherwise on the RFC itself, all RFCs are for >> unlimited distribution.
>>
>>
>> The RFC Editor Team
>> Association Management Solutions, LLC
>>
>>
>> _______________________________________________
>> COSE mailing list
>> COSE@ietf.org
>> https://www.ietf.org/mailman/listinfo/cose
>
>_______________________________________________
>COSE mailing list
>COSE@ietf.org
>https://www.ietf.org/mailman/listinfo/cose

_______________________________________________
COSE mailing list
COSE@ietf.org
https://www.ietf.org/mailman/listinfo/cose

--f40304362194690ed50557031835--