gt;
Yes, the intention is to move COSE to Internet Standard.
- m
Matthew A. Miller
signature.asc
Description: OpenPGP digital signature
___
COSE mailing list
COSE@ietf.org
https://www.ietf.org/mailman/listinfo/cose
[ dons hat ]
Gentle reminder that the call for adoption of these documents ends soon.
[ doffs hat ]
I support adopting both documents.
- m
Matthew A. Miller
On 19/01/07 19:39, Matthew A. Miller wrote:
> Welcome back COSE Working Group! Let's get started!
>
> This message begins
[ doffs hat ]
I support adoption of this document.
- m
Matthew A. Miller
On 19/01/16 08:48, ivaylo petrov wrote:
> Dear WG,
>
> This message begins the call for adoption of the following draft:
>
> * draft-schaad-cose-x509-03
> - https://tools.ietf.org/html/draft-s
Welcome back COSE Working Group! Let's get started!
This message begins the call for adoption of the following drafts:
* draft-schaad-cose-rfc8152bis-struct-01
- https://tools.ietf.org/html/draft-schaad-cose-rfc8152bis-struct-01
* draft-schaad-cose-rfc8152bis-algs-01
-
The Call for Adoption has concluded, with a good show of support to
adopt and no objections noted.
Mike, at your convenience please submit `draft-ietf-cose-webauthn-algs`
(or -algorithms), replacing `draft-jones-cose-additional-algorithms`.
In the meeting session, it was determined (with consent
This messages starts a call for consensus to separate the COSE hash
algorithms into a separate document, ending on 2018-03-10.
In the virtual interim on 02-15, it was proposed to separate them from
draft-ietf-cose-x509, to allow the hash algorithm registrations to
stabilize more quickly than the
Thank you all who participating in the various rounds, either in-person
on on-list.
From the comments, it does not appear we have consensus to make the
change. The existing context "CounterSignature0" will remain.
- Ivaylo and Matthew
COSE WG Chairs
On 19/03/29 06:06, Matthew A. Mi
Hello Jean-Marc,
Two reviewers have approved of the header parameters, so I believe the
value 33 should be safe.
I will follow up with IANA to see when that will be reflected in the
registry.
- m
Matthew A. Miller
one each of Expert Reviewers and COSE chairs
On 19/08/20 10:29, DESPERRIER Jean
As a Chair, I approve of this early assignment.
- m
Matthew A. Miller
On 19/07/31 09:51, Sabrina Tanamal via RT wrote:
> Hi Jim, all,
>
> Before we can make RFC 7120 early allocations for the registrations listed
> below, we need approval from a chair and an AD.
Hello WG,
The draft minutes from our session at IETF 106 are in Datatracker:
<
https://datatracker.ietf.org/meeting/106/materials/minutes-106-cose-00.txt >
Please send any corrections to the chairs or this list.
Thank you,
- Ivaylo and Matthew
COSE WG Chairs
Hello All,
There's a couple days left on comments regarding rechartering. So far
we have:
* no objections to rechartering
* no additional proposed work on non-algorithms (beyond cert compression)
If you have objections to rechartering, or have additional non-algorithm
work items that should be
With no hat ...
Being a little less specific on the profile details in the charter seems
worthwhile to me. I don't want it to be an open invitation to come up
with a third profile, though.
- m
Matthew A. Miller
On 20/04/17 01:30, Joel Höglund wrote:
> Hi all,
>
> I support th
Hello All,
This message is to confirm the in-meeting consensus to recharter the
COSE Working Group. Given the strong consensus in the meeting, we are
most concerned with objections to rechartering.
With all of the chartered work effectively complete, the question is
raised about what to do
Apologies for the extreme delay here. The WGLC for
draft-ietf-cose-rfc8152bis drafts (-struct[1] and -algs[2]) has been
bespoke closed for a while now.
Thank you all that provided review and feedback. The chairs read that
we have consensus to publish, and the latest revisions address the
I believe I can do this still, and will do so, and update the shepherd
write-up.
- m
Matthew A. Miller
On 20/03/31 12:41, Benjamin Kaduk wrote:
> I can change it in the datatracker as needed, too.
>
> -Ben
>
> On Tue, Mar 31, 2020 at 11:40:26AM -0700, Jim Schaad wrote:
>>
A reminder that our session is tomorrow at 17:00 UTC (10:00 PDT, 18:00
CEST) over Webex:
URL:
https://ietf.webex.com/ietf/j.php?MTID=m65dc99c8fcf80c2ad60c4bcc24f22477
Meeting Number: 318 487 000
Meeting Password: DkuJ2VDMK79
Our Agenda (with more details):
1. Administrivia (Chairs) - 5 minutes
> On Aug 26, 2020, at 13:58, Matthew A. Miller
> wrote:
>
> Hello COSE WG,
>
> The interim meeting today focused on countersignatures, and there was
> rough consensus on a proposed plan. The chairs are seeking any
> objections for a proposed breakdown to move forward c
The recording for last week's session can be found here: <
https://ietf.webex.com/ietf/ldr.php?RCID=ce4a477b56724b0ea5873646358c7e7b >
The minutes have been uploaded to datatracker: <
https://www.ietf.org/proceedings/interim-2020-cose-02/minutes/minutes-interim-2020-cose-02-202008261600-00
>
Hello all,
We have an interim meeting Wednesday, 26 August 2020 at 16:00 UTC. The
agenda is to progress a new CounterSignature mechanism that addresses
the discovered defects.
This interim will be conducted via Webex <
https://ietf.webex.com/ietf/j.php?MTID=m5528e10375ba600e61b9133f1f8bcfa7 >.
Hello COSE WG,
The interim meeting today focused on countersignatures, and there was
rough consensus on a proposed plan. The chairs are seeking any
objections for a proposed breakdown to move forward countersignatures.
1) The working group will have two documents: rfc8152bis-struct for the
deprecation in -struct.
- m
Matthew A. Miller
On 20/08/24 10:17, Jim Schaad wrote:
> At the virtual IETF meeting where had a long discussion on how the structure
> document should progress without getting any type of final conclusions.
> Since that time I have come up with a new optio
Hello Linda,
Thanks for the review. Speaking on the author's behalf, SHA-2 is
defined as the collection of hash algorithms, including all of those
cited (SHA-256, SHA-384, SHA-512). Do you believe it is critical to
call this out explicitly?
- m
Matthew A. Miller
On 20/05/26 17:51, Linda
This message is to confirm consensus to deprecate the current
CounterSignature feature and replace it with one that best accounts for
all COSE message types.
At the synchronous WG meeting on July 29, the issue with
countersignatures was heavily discussed. In summary, the
currently-defined
If you participated in last weeks festivities and have not filled out
the meeting survey, please consider doing so.
The survey is at: < https://www.surveymonkey.com/r/T3SL7JF >
Thanks!
- Ivaylo and Matthew
COSE WG Chairs
On 20/08/05 04:30, IETF Executive Director wrote:
> Thank you very much
As you may have noticed, the schedule is a little tight. To help get
going more quickly, we are soliciting volunteers now for:
* taking notes/minutes (grab action items)
* scribing to Jabber (relay "MIC" comments from Jabber to meetecho,
Please message < cose-cha...@ietf.org > if you can help.
Hello COSE WG,
A reminder the session is Wednesday (tomorrow)!
Where: Meetecho
When: 2020-07-29 @ 13:00-13:50 UTC
* Notes: https://codimd.ietf.org/notes-ietf-108-cose
* Jabber: xmpp:c...@jabber.ietf.org?join
* Meetecho:
https://meetings.conf.meetecho.com/ietf108/?group=cose==1
The updated
Minutes from the COSE WG @ IETF-108 session are uploaded to datatracker.
Please send any corrections and the minutes will be updated.
* Minutes: <
https://www.ietf.org/proceedings/108/minutes/minutes-108-cose-01.txt >
A big thank you to Francesca Palombini for taking minutes.
-- Ivaylo and
This is well overdue, but here is a preliminary agenda based on
activities. If anyone has more to discuss, please alert the chairs.
The COSE WG session is scheduled for 50 minutes on Wednesday, 20 July at
11:00 UTC. Note this is quite early for those of located in western
North America
28 matches
Mail list logo
