[Ace] Fwd: NomCom 2023 Call for Volunteers

[Daniel Migault]

Hi, 

Please consider volunteering for NomCom. It is very important to the IETF to 
have good people on the NomCom.

Yours,

Daniel 

From: NomCom Chair 2023 
mailto:nomcom-chair-2...@ietf.org>>
Subject: NomCom 2023 Call for Volunteers
Date: June 5, 2023 at 19:50:08 EDT
To: "IETF Announcement List" 
mailto:ietf-annou...@ietf.org>>
Reply-To: nomcom-chair-2...@ietf.org

The IETF Nominating Committee (NomCom) appoints people to fill the open slots 
on the IETF LLC, IETF Trust, the IAB, and the IESG.  Ten voting members for the 
NomCom are selected from a pool of volunteers.  A large pool of volunteers 
helps make the process work better.

CLICK HERE TO VOLUNTEER: https://datatracker.ietf.org/nomcom/volunteer

NomCom activity is expected to start in July and run through to November.  The 
goal is to do the bulk of the work at IETF 117 and 118, with supplemental 
conference calls between those times.  Remote participation will be supported.

The NomCom activities involve collecting requirements from the community, 
reviewing candidate responses, reviewing feedback from community members about 
candidates, interviewing candidates, and nominating a slate of candidates.

RFC 8713 details the NomCom process.  With the recent publication of RFC 9389, 
this is the first year of new qualification criteria, after a few years of 
trials.  People qualify for NomCom participation in one of three ways: 
attendance at IETF meetings (online or virtual), service as a working group 
chair or secretary, or publication of IETF RFCs.

https://datatracker.ietf.org/accounts/profile/ lists your eligibility, but you 
can still volunteer even if that says "No".  You can also volunteer by sending 
me an email.

Within the next week or two, I will add more details on the timeline and the 
selection process.

Thank you!
Martin Thomson
nomcom-chair-2...@ietf.org

___
Spasm mailing list
sp...@ietf.org
https://www.ietf.org/mailman/listinfo/spasm


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-coap-est-oscore-01.txt

[Daniel Migault]

The repo has just been created.

https://github.com/ace-wg/est-oscore.git

Yours,
Daniel

On Sat, Jun 3, 2023 at 10:00 AM Daniel Migault  wrote:

> Thanks Malisa!
>
> Yours,
> Daniel
>
> -Original Message-
> From: Ace  On Behalf Of Mališa Vucinic
> Sent: June 3, 2023 6:30 AM
> To: Ace Wg 
> Subject: Re: [Ace] I-D Action: draft-ietf-ace-coap-est-oscore-01.txt
>
> Hi all,
>
> This revision of draft-ietf-ace-coap-est-oscore addresses Marco Tiloca’s
> review. The discussions have been going on in parallel on github. We will
> discuss the latest changes at the interim on Monday.
>
> Mališa
>
>
> > On Jun 3, 2023, at 12:23, internet-dra...@ietf.org wrote:
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories. This Internet-Draft is a work item of the Authentication
> > and Authorization for Constrained Environments (ACE) WG of the IETF.
> >
> >   Title   : Protecting EST Payloads with OSCORE
> >   Authors : Göran Selander
> > Shahid Raza
> > Martin Furuhed
> > Mališa Vučinić
> > Timothy Claeys
> >   Filename: draft-ietf-ace-coap-est-oscore-01.txt
> >   Pages   : 18
> >   Date: 2023-06-03
> >
> > Abstract:
> >   This document specifies public-key certificate enrollment procedures
> >   protected with lightweight application-layer security protocols
> >   suitable for Internet of Things (IoT) deployments.  The protocols
> >   leverage payload formats defined in Enrollment over Secure Transport
> >   (EST) and existing IoT standards including the Constrained
> >   Application Protocol (CoAP), Concise Binary Object Representation
> >   (CBOR) and the CBOR Object Signing and Encryption (COSE) format.
> >
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-ace-coap-est-oscore/
> >
> > There is also an HTML version available at:
> > https://www.ietf.org/archive/id/draft-ietf-ace-coap-est-oscore-01.html
> >
> > A diff from the previous version is available at:
> > https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-coap-est-osco
> > re-01
> >
> > Internet-Drafts are also available by rsync at
> > rsync.ietf.org::internet-drafts
> >
> >
> > ___
> > Ace mailing list
> > Ace@ietf.org
> > https://www.ietf.org/mailman/listinfo/ace
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-coap-est-oscore-01.txt

[Daniel Migault]

Thanks Malisa!

Yours, 
Daniel

-Original Message-
From: Ace  On Behalf Of Mališa Vucinic
Sent: June 3, 2023 6:30 AM
To: Ace Wg 
Subject: Re: [Ace] I-D Action: draft-ietf-ace-coap-est-oscore-01.txt

Hi all,

This revision of draft-ietf-ace-coap-est-oscore addresses Marco Tiloca’s 
review. The discussions have been going on in parallel on github. We will 
discuss the latest changes at the interim on Monday.

Mališa


> On Jun 3, 2023, at 12:23, internet-dra...@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories. This Internet-Draft is a work item of the Authentication 
> and Authorization for Constrained Environments (ACE) WG of the IETF.
> 
>   Title   : Protecting EST Payloads with OSCORE
>   Authors : Göran Selander
> Shahid Raza
> Martin Furuhed
> Mališa Vučinić
> Timothy Claeys
>   Filename: draft-ietf-ace-coap-est-oscore-01.txt
>   Pages   : 18
>   Date: 2023-06-03
> 
> Abstract:
>   This document specifies public-key certificate enrollment procedures
>   protected with lightweight application-layer security protocols
>   suitable for Internet of Things (IoT) deployments.  The protocols
>   leverage payload formats defined in Enrollment over Secure Transport
>   (EST) and existing IoT standards including the Constrained
>   Application Protocol (CoAP), Concise Binary Object Representation
>   (CBOR) and the CBOR Object Signing and Encryption (COSE) format.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ace-coap-est-oscore/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-ace-coap-est-oscore-01.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-coap-est-osco
> re-01
> 
> Internet-Drafts are also available by rsync at 
> rsync.ietf.org::internet-drafts
> 
> 
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Publication has been requested for draft-ietf-ace-revoked-token-notification-06

[Daniel Migault via Datatracker]

Daniel Migault has requested publication of 
draft-ietf-ace-revoked-token-notification-06 as Proposed Standard on behalf of 
the ACE working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-ace-revoked-token-notification/


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-revoked-token-notification-06.txt

[Daniel Migault]

Thanks Goran for the revision and Marco for addressing these comments.

Yours,
Daniel


From: Ace  on behalf of Marco Tiloca 

Sent: Friday, June 2, 2023 9:59 AM
To: ace@ietf.org
Subject: Re: [Ace] I-D Action: draft-ietf-ace-revoked-token-notification-06.txt

Hello ACE,

This revision addresses the comments from the Shepherd review [1] - thanks 
Göran! - about avoiding repetitions in the instructions for the Expert review 
in the IANA considerations.

Best,
/Marco

[1] https://mailarchive.ietf.org/arch/msg/ace/mHpTsE-lDvzfMSt0cd-j_B-VknM/

On 2023-06-02 15:49, internet-dra...@ietf.org 
wrote:


A New Internet-Draft is available from the on-line Internet-Drafts
directories. This Internet-Draft is a work item of the Authentication and
Authorization for Constrained Environments (ACE) WG of the IETF.

   Title   : Notification of Revoked Access Tokens in the 
Authentication and Authorization for Constrained Environments (ACE) Framework
   Authors : Marco Tiloca
 Francesca Palombini
 Sebastian Echeverria
 Grace Lewis
   Filename: draft-ietf-ace-revoked-token-notification-06.txt
   Pages   : 59
   Date: 2023-06-02

Abstract:
   This document specifies a method of the Authentication and
   Authorization for Constrained Environments (ACE) framework, which
   allows an Authorization Server to notify Clients and Resource Servers
   (i.e., registered devices) about revoked access tokens.  As specified
   in this document, the method allows Clients and Resource Servers to
   access a Token Revocation List on the Authorization Server by using
   the Constrained Application Protocol (CoAP), with the possible
   additional use of resource observation.  Resulting (unsolicited)
   notifications of revoked access tokens complement alternative
   approaches such as token introspection, while not requiring
   additional endpoints on Clients and Resource Servers.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ace-revoked-token-notification/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-ace-revoked-token-notification-06.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-revoked-token-notification-06

Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace



--
Marco Tiloca
Ph.D., Senior Researcher

Phone: +46 (0)70 60 46 501

RISE Research Institutes of Sweden AB
Box 1263
164 29 Kista (Sweden)

Division: Digital Systems
Department: Computer Science
Unit: Cybersecurity

https://www.ri.se/

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] upcoming interim meeting

[Daniel Migault]

Just a reminder. The current expected agenda is as mentioned below:

 Agenda:
- update from AD - if present
- revoked-token-notification (waiting for shepherd write-up)
- pubsub-profile
- oscore-gm-admin
- coap-est-oscore
- edhoc-oscore-profile

Yours,
Daniel


On Thu, May 25, 2023 at 1:21 PM Loganaden Velvindron 
wrote:

> Hi Ace wg participants,
>
> Just to remind you that we have an interim meeting planned on June 05,
> so please take that opportunity to move your documents forward and
> have the appropriate discussions.
>
>
>
> Please upload your slides:
> https://datatracker.ietf.org/meeting/interim-2023-ace-05/session/ace
>
> Yours,
> Daniel and Logan.
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt

[Daniel Migault]

Thanks Paul and others for moving this document forward!

Yours,
Daniel


From: Ace  on behalf of Paul Wouters 

Sent: Friday, May 26, 2023 3:33 PM
To: Mohit Sahni
Cc: Daniel Migault; Brockhaus, Hendrik; ace@ietf.org
Subject: Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt


On Thu, May 25, 2023 at 1:15 PM Mohit Sahni 
mailto:mohit06...@gmail.com>> wrote:
Hi Paul,
I think you may be looking at the older version of the draft. (Please check 
https://datatracker.ietf.org/doc/html/draft-ietf-ace-cmpv2-coap-transport)

Odd, I was and I wasn't. Maybe a caching issue. Thanks for pointing out most of 
the ballot comments have been addressed.

I submitted the xml version and the boilerplate is auto generated from the xml. 
I am not sure how to change the boiler plate text. My guess is that it's the 
xml2rfc tool that's adding the boilerplate.

We will let the RFC Editor worry about that.

The reference of 5280 is added in the below text in the version 10 of the draft:
Section 4 bullet point 4:
An EE might not witness all of the Announcement messages when using the CoAP 
Observe option [RFC7641], since the Observe option is a "best-effort" approach 
and the server might lose its state for subscribers to its announcement 
messages. The EEs may use an alternate method described in section 2.6 to 
obtain time critical changes such as CRL [RFC5280] updates.

right.


Reference to 
draft-ietf-lamps-lightweight-cmp-profile-13<https://datatracker.ietf.org/doc/draft-ietf-lamps-lightweight-cmp-profile/13/>
 has been updated to version 21 now in the latest draft.

Indeed.

The comment "without compromising the integrity of " be better than "without 
compromising the security" (given CMP does not provide confidentiality" was not 
directed me but to the ADs (i.e. Paul) If you agree, I can make the change to 
the text.

I agree that it is a better word, however since the bullet point immediatly 
following it talks about confidentiality, I think it is fine to leave it too.
If you were to do another update, please fold it in. Otherwise perhaps we can 
change the one word during the RFC Editor phase.

I've cleared the state, so the document will proceed onwards now.

Paul


Thanks
Mohit

On Thu, May 25, 2023 at 9:07 AM Paul Wouters 
mailto:40aiven...@dmarc.ietf.org>> 
wrote:
I should probably put it in Revised ID needed, as there are a few bugs left:

- the 2119 boilerplate triggers warning (although I don't see the discrepancy)
- RFC 5280 is listed as informative reference but it is not references anywhere 
in the text
- outdated reference to 
draft-ietf-lamps-lightweight-cmp-profile-13<https://datatracker.ietf.org/doc/draft-ietf-lamps-lightweight-cmp-profile/13/>
-  "without compromising the integrity of " be better than "without 
compromising the security" (given CMP does not provide confidentiality

It seems the authors haven't gone yet through all the ballot comments at 
https://datatracker.ietf.org/doc/draft-ietf-ace-cmpv2-coap-transport/ballot/

I'll put it in revised ID needed now since at least the the above bullet points 
should be fixed.

Paul

On Thu, May 25, 2023 at 11:13 AM Daniel Migault 
mailto:mglt.i...@gmail.com>> wrote:
As far as I understand it, the document is in " Approved-announcement to be 
sent::AD Followup", which means the AD needs to approve the latest version to 
be sent to the RFC editor. Th elatest version has been published on may 15, so 
my guess is that the approval should come in the next few days.

Yours,
Daniel


On Thu, May 25, 2023 at 8:52 AM Brockhaus, Hendrik 
mailto:hendrik.brockh...@siemens.com>> wrote:
Thanks to Mohit and Saurabh for the update also from my side.
Are there any further changes planned or is anything else necessary before 
moving the draft to RFC Editor state?

Hendrik

> Von: Ace mailto:ace-boun...@ietf.org>> Im Auftrag von 
> Daniel Migault
>
> Thanks for the submission Mohit.
>
> Yours,
> Daniel
>
> 
> From: Ace mailto:ace-boun...@ietf.org>> on behalf of 
> internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>
> mailto:internet-dra...@ietf.org>>
> Sent: Monday, May 15, 2023 4:44 PM
> To: i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org>
> Cc: ace@ietf.org<mailto:ace@ietf.org>
> Subject: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the Authentication and
> Authorization for Constrained Environments (ACE) WG of the IETF.
>
>Title   : CoAP Transfer for the Certificate Management Protocol
>Authors : Mohit Sahni
>  Saurabh Tripathi
>F

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt

[Daniel Migault]

As far as I understand it, the document is in " Approved-announcement to be
sent::AD Followup", which means the AD needs to approve the latest version
to be sent to the RFC editor. Th elatest version has been published on may
15, so my guess is that the approval should come in the next few days.

Yours,
Daniel


On Thu, May 25, 2023 at 8:52 AM Brockhaus, Hendrik <
hendrik.brockh...@siemens.com> wrote:

> Thanks to Mohit and Saurabh for the update also from my side.
> Are there any further changes planned or is anything else necessary before
> moving the draft to RFC Editor state?
>
> Hendrik
>
> > Von: Ace  Im Auftrag von Daniel Migault
> >
> > Thanks for the submission Mohit.
> >
> > Yours,
> > Daniel
> >
> > 
> > From: Ace  on behalf of internet-dra...@ietf.org
> > 
> > Sent: Monday, May 15, 2023 4:44 PM
> > To: i-d-annou...@ietf.org
> > Cc: ace@ietf.org
> > Subject: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories. This Internet-Draft is a work item of the Authentication and
> > Authorization for Constrained Environments (ACE) WG of the IETF.
> >
> >Title   : CoAP Transfer for the Certificate Management
> Protocol
> >Authors : Mohit Sahni
> >  Saurabh Tripathi
> >Filename: draft-ietf-ace-cmpv2-coap-transport-10.txt
> >Pages   : 11
> >Date: 2023-05-15
> >
> > Abstract:
> >This document specifies the use of Constrained Application Protocol
> >(CoAP) as a transfer mechanism for the Certificate Management
> >Protocol (CMP).  CMP defines the interaction between various PKI
> >entities for the purpose of certificate creation and management.
> >CoAP is an HTTP-like client-server protocol used by various
> >constrained devices in the IoT space.
> >
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datatra/
> > cker.ietf.org%2Fdoc%2Fdraft-ietf-ace-cmpv2-coap-
> > transport%2F&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7Cb7
> > 45642c8925408378c508db55a8f629%7C38ae3bcd95794fd4addab42e1495d55
> > a%7C1%7C0%7C638197956407483228%7CUnknown%7CTWFpbGZsb3d8eyJ
> > WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
> > C3000%7C%7C%7C&sdata=NRMWomPpx1FbVSzl%2FLu0U0HQX3tpT9gXX2cbu
> > Tq4cro%3D&reserved=0
> >
> > There is also an htmlized version available at:
> > https://datatra/
> > cker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-ace-cmpv2-coap-transport-
> > 10&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7Cb745642c892
> > 5408378c508db55a8f629%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7
> > C0%7C638197956407483228%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
> > LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
> > %7C%7C&sdata=VlTKaJOKWtgld6rtRVKIen9ic5etr%2B3%2FXME4JIwoBG0%3D
> > &reserved=0
> >
> > A diff from the previous version is available at:
> > https://author/
> > -tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-ace-cmpv2-coap-transport-
> > 10&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7Cb745642c892
> > 5408378c508db55a8f629%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7
> > C0%7C638197956407483228%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
> > LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
> > %7C%7C&sdata=Nzg9WKRaw3P47ucvb3zEF0%2BsePKxR6Ps1oKjtdrZAXc%3D&
> > reserved=0
> >
> > Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
> >
> >
> > ___
> > Ace mailing list
> > Ace@ietf.org
> > https://www.ie/
> > tf.org%2Fmailman%2Flistinfo%2Face&data=05%7C01%7Chendrik.brockhaus%
> > 40siemens.com%7Cb745642c8925408378c508db55a8f629%7C38ae3bcd9579
> > 4fd4addab42e1495d55a%7C1%7C0%7C638197956407483228%7CUnknown%
> > 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
> > iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gHv%2FbNIlQSoDTUBx1NY6S
> > Snkc%2BtzbcFbp%2BXwInvd6Ss%3D&reserved=0
> >
> > ___
> > Ace mailing list
> > Ace@ietf.org
> > https://www.ie/
> > tf.org%2Fmailman%2Flistinfo%2Face&data=05%7C01%7Chendrik.brockhaus%
> > 40siemens.com%7Cb745642c8925408378c508db55a8f629%7C38ae3bcd9579
> > 4fd4addab42e1495d55a%7C1%7C0%7C638197956407483228%7CUnknown%
> > 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
> > iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gHv%2FbNIlQSoDTUBx1NY6S
> > Snkc%2BtzbcFbp%2BXwInvd6Ss%3D&reserved=0
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt

[Daniel Migault]

Thanks for the submission Mohit.

Yours,
Daniel


From: Ace  on behalf of internet-dra...@ietf.org 

Sent: Monday, May 15, 2023 4:44 PM
To: i-d-annou...@ietf.org
Cc: ace@ietf.org
Subject: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories. This Internet-Draft is a work item of the Authentication and
Authorization for Constrained Environments (ACE) WG of the IETF.

   Title   : CoAP Transfer for the Certificate Management Protocol
   Authors : Mohit Sahni
 Saurabh Tripathi
   Filename: draft-ietf-ace-cmpv2-coap-transport-10.txt
   Pages   : 11
   Date: 2023-05-15

Abstract:
   This document specifies the use of Constrained Application Protocol
   (CoAP) as a transfer mechanism for the Certificate Management
   Protocol (CMP).  CMP defines the interaction between various PKI
   entities for the purpose of certificate creation and management.
   CoAP is an HTTP-like client-server protocol used by various
   constrained devices in the IoT space.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ace-cmpv2-coap-transport/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-ace-cmpv2-coap-transport-10

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-cmpv2-coap-transport-10

Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] (ace) WG Interim Meeting: 2023-05-08

[Daniel Migault]

Hi,

Just a reminder, the interim meeting is this monday.Make sure you upload
your presentation before the session.

Yours,
Logan and Daniel

On Sat, Apr 29, 2023 at 9:31 AM Daniel Migault  wrote:

> Hi Acers,
>
> Just to remind you that we have an interim meeting planned on May 08, so
> please take that opportunity to move the document forward and have the
> appropriate discussions.
>
> The provisional agenda is as follows:
> https://notes.ietf.org/notes-ietf-interim-2023-ace-04-ace
>
> Agenda:
> - update from AD - if present
> - revoked-token-notification (waiting for shepherd write-up)
> - pubsub-profile
> - oscore-gm-admin
> - coap-est-oscore
> - edhoc-oscore-profile
>
> Please feel free to add any item.
>
> Please upload your slides:
> https://datatracker.ietf.org/meeting/interim-2023-ace-04/session/ace
>
> Yours,
> Logan and Daniel
>
> On Wed, Apr 19, 2023 at 2:04 PM IESG Secretary 
> wrote:
>
>> The Authentication and Authorization for Constrained Environments (ace) WG
>> will hold an interim meeting on 2023-05-08 from 09:00 to 10:00
>> America/New_York (13:00 to 14:00 UTC). Meeting Location: Montreal, CA
>>
>>
>> Agenda:
>> (No agenda submitted)
>>
>> Information about remote participation:
>>
>> https://meetings.conf.meetecho.com/interim/?short=7bd2ea10-1c42-4dda-9bc0-8776a5cb4afb
>>
>>
>>
>> --
>> A calendar subscription for all ace meetings is available at
>> https://datatracker.ietf.org/meeting/upcoming.ics?show=ace
>>
>> _______
>> IETF-Announce mailing list
>> ietf-annou...@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] (ace) WG Interim Meeting: 2023-05-08

[Daniel Migault]

Hi Acers,

Just to remind you that we have an interim meeting planned on May 08, so
please take that opportunity to move the document forward and have the
appropriate discussions.

The provisional agenda is as follows:
https://notes.ietf.org/notes-ietf-interim-2023-ace-04-ace

Agenda:
- update from AD - if present
- revoked-token-notification (waiting for shepherd write-up)
- pubsub-profile
- oscore-gm-admin
- coap-est-oscore
- edhoc-oscore-profile

Please feel free to add any item.

Please upload your slides:
https://datatracker.ietf.org/meeting/interim-2023-ace-04/session/ace

Yours,
Logan and Daniel

On Wed, Apr 19, 2023 at 2:04 PM IESG Secretary 
wrote:

> The Authentication and Authorization for Constrained Environments (ace) WG
> will hold an interim meeting on 2023-05-08 from 09:00 to 10:00
> America/New_York (13:00 to 14:00 UTC). Meeting Location: Montreal, CA
>
>
> Agenda:
> (No agenda submitted)
>
> Information about remote participation:
>
> https://meetings.conf.meetecho.com/interim/?short=7bd2ea10-1c42-4dda-9bc0-8776a5cb4afb
>
>
>
> --
> A calendar subscription for all ace meetings is available at
> https://datatracker.ietf.org/meeting/upcoming.ics?show=ace
>
> ___
> IETF-Announce mailing list
> ietf-annou...@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] interim meeting

[Daniel Migault]

Hi,

We have just set monthly meetings for May - June and July using the same
pattern as the previous meeting this year - at least that was the intent.

As far as we can tell, the remaining document in the WG are the following:
- oscore-gm-admin
- pubsub-profile
- edhoc-oscore-profile
- coap-est-oscore

Almost shipped:
- revoked-token (waiting for shepherd write)
- key-groupcom (AD review)
- key-groupcom-oscore (AD review)
- coap-eap (AD review)
- cmpv2-coap-transport (IESG)
- extended-dtls (RFC Ed)
- mqtt-tls-profile (RFC Ed)

Yours,
Logan and Daniel
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] call for adoption draft-selander-ace-coap-est-oscore

[Daniel Migault]

I think we can close the "call for adoption". We have not seen anyone opposed 
to the adoption and some people have volunteering to review. The chairs believe 
the document can be declared adopted. Please upload the document with the 
correct name.
Yours,
Daniel


From: Ace  on behalf of Rikard Höglund 

Sent: Wednesday, April 19, 2023 3:44 AM
To: Daniel Migault; Ace Wg
Subject: Re: [Ace] call for adoption draft-selander-ace-coap-est-oscore

Hello.

I support adoption of the document and would be willing to review it.

Best
Rikard Höglund

From: Ace  on behalf of Daniel Migault 

Sent: Thursday, March 30, 2023 20:52
To: Ace Wg 
Subject: [Ace] call for adoption draft-selander-ace-coap-est-oscore

Hi,

Following the IETF116 meeting we are starting a 2 week adoption call for the 
following document. Please indicate whether you would like the document to be 
adopted or if you are against its adoption. The call ends April 15 2023.

https://datatracker.ietf.org/doc/draft-selander-ace-coap-est-oscore/

Yours,
Daniel
--
Daniel Migault
Ericsson

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] WGLC draft-ietf-ace-revoked-token-notification-04.txt

[Daniel Migault]

d that parameter if it doesn't support the 'cursor' extension.
>
>
> [Section 10.1]
>
> *"A response from the TRL endpoint indicating that t1 has expired."
>
> Could be good to clarify this sentence to say that this indication is
> about th1 having been removed from the TRL.
>
>
> *"If expunging or not accepting t2 yields the deletion of th2 as per the
> two conditions specified above"
>
> Suggested rephrasing:
> "If receiving t2 yields the deletion of th2 as per the two conditions
> specified above"
> It is the "receiving and seeing" that is criteria 1. "Expunging" or "not
> accepting" is not part of critera 1 or 2.
>
>
> *"iii) has the sequence number encoded in the 'cti' claim not greater than
> the highest sequence number among the expired Access Tokens specifying the
> 'exi' claim"
>
> Should this say "is greater" rather than "not greater"? If for instance
> the sequence number is lower, then should not the procedure in 5.10.3 of
> RFC9200 make such an Access Token be rejected in the first place?
>
>
> [Section 13.4]
>
> s/Client migth/Client might
>
> s/the Autherization Server/the Authorization Server
>
>
> [Appendix B]
>
> The table states that MAX_DIFF_BATCH is not a single instance parameter,
> and in Section 9 it states that a registered device may receive
> MAX_DIFF_BATCH from the AS during registration. Why is MAX_DIFF_BATCH not a
> single instance parameter, but MAX_N is? Or rather, why are they not both
> single instance, or not single instance?
>
> --
> *From:* Ace  on behalf of Daniel Migault <
> mglt.i...@gmail.com>
> *Sent:* Monday, March 13, 2023 18:36
> *To:* Ace Wg 
> *Subject:* [Ace] WGLC draft-ietf-ace-revoked-token-notification-04.txt
>
> Hi everyone,
>
> This email starts a WGLC for draft-ietf-ace-revoked-token-notification
> which ends on March 27. Please provide your support and feed backs by that
> time. We will take advantage of the IETF116 session to solve any remaining
> discussions on that draft.
>
> I am also looking for someone interested in being the document shepherd:
> Please volunteer!
>
> To the co-authors I am looking at:
> - 1) a heads-up regarding the implementations.
> - 2) a confirmation that they are or not aware of any IPR
> - 3)  a confirmation that they are willing to co-author the document.
>
> Yours,
> Logan and Daniel
>
>
> On Mon, Mar 13, 2023 at 11:36 AM  wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the Authentication and
> Authorization for Constrained Environments (ACE) WG of the IETF.
>
>Title   : Notification of Revoked Access Tokens in the
> Authentication and Authorization for Constrained Environments (ACE)
> Framework
>Authors : Marco Tiloca
>  Ludwig Seitz
>  Francesca Palombini
>  Sebastian Echeverria
>  Grace Lewis
>Filename: draft-ietf-ace-revoked-token-notification-04.txt
>Pages   : 59
>Date: 2023-03-13
>
> Abstract:
>This document specifies a method of the Authentication and
>Authorization for Constrained Environments (ACE) framework, which
>allows an Authorization Server to notify Clients and Resource Servers
>(i.e., registered devices) about revoked Access Tokens.  The method
>allows Clients and Resource Servers to access a Token Revocation List
>on the Authorization Server, with the possible additional use of
>resource observation for the Constrained Application Protocol (CoAP).
>Resulting (unsolicited) notifications of revoked Access Tokens
>complement alternative approaches such as token introspection, while
>not requiring additional endpoints on Clients and Resource Servers.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ace-revoked-token-notification/
> <https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-ace-revoked-token-notification%2F&data=05%7C01%7Crikard.hoglund%40ri.se%7C6e109d1b535245f2de8c08db23e98fd8%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638143258281785774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ScSk98oxn17GGIh5VtkZxePUAxKw43vsnf57Ga7PT1M%3D&reserved=0>
>
> There is also an HTML version available at:
>
> https://www.ietf.org/archive/id

[Ace] call for adoption draft-selander-ace-coap-est-oscore

[Daniel Migault]

Hi,

Following the IETF116 meeting we are starting a 2 week adoption call for
the following document. Please indicate whether you would like the document
to be adopted or if you are against its adoption. The call ends April 15
2023.

https://datatracker.ietf.org/doc/draft-selander-ace-coap-est-oscore/

Yours,
Daniel
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-07

[Daniel Migault]

Thanks!
Yours,
Daniel

From: Ace  On Behalf Of Mohit Sahni
Sent: March 30, 2023 2:22 PM
To: Paul Wouters 
Cc: Mohit Sahni ; ace@ietf.org; 
draft-ietf-ace-cmpv2-coap-transp...@ietf.org
Subject: Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-07

Thanks Paul, I will upload a new version today.


On Wed, Mar 29, 2023 at 9:33 PM Paul Wouters 
mailto:40aiven...@dmarc.ietf.org>> 
wrote:



On Fri, Mar 10, 2023 at 4:12 AM Mohit Sahni 
mailto:msa...@paloaltonetworks.com>> wrote:

[ proposed changes / confirmations in the xml file ]

I have read the xml diff and I agree with all changes made.


Just noticed an incomplete response for this comment, responding again to it.

>The next bullet I just do not understand:
>
>In order to to reduce the risks imposed by DoS attacks, the
>implementations SHOULD optimally use the available datagram size
>i.e. avoid small datagrams containing partial CMP PKIMessage data.
>
>Please explain what is meant here and/or rephrase it.

The intent here is to instruct clients to send CMP messages in as few 
packets as possible. Fragmentation of CMP messages may cause the server to 
buffer packets which will consume resources on the server. With clients 
instructed to send CMP messages in as few packets as possible, servers can 
choose to ignore fragmented CMP messages to mitigate such DOS attacks.


So maybe:

Implementations SHOULD use the available datagram size and avoid small 
datagrams containing partial CMP PKIMessage data in order to reduce memory 
usage for packet buffering.

Please submit a new version to the datatracker with these changes, so we can 
start the IETF Last Call.

Paul
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE agenda / presentation

[Daniel Migault]

hi,

Please make sure you have uploaded your slides.

Yours,
Daniel

On Tue, Mar 14, 2023 at 12:40 PM Daniel Migault  wrote:

> Hi,
>
> I think this is the ACE agenda Stephen and Malisa can consider. I am
> assuming it will be uploaded with the LAKE agenda.
>
> - words from chairs / AD (5 minutes)
> - pubsub-profile (10 minutes) Cigdem
> - revoked-token WGLC discussions (10 minutes) Marco
> - oscore-gm-admin (10 minutes) Marco
> - follow-up activities (5-10 minutes) Marco
> - edhoc-oscore-profile ( 10 minutes) Goran
> - selander-ace-coap-est-oscore (10 minutes ) Malissa
>
> I would like to thank ACE folks for providing the necessary inputs so we
> can provide the agenda on time and Malisa to remind me of the March 15
> deadline for the agenda last Friday ;-).
> Please upload your presentation as soon as you can and make it clear the
> presentation is related to ace (not lake):
> https://datatracker.ietf.org/meeting/116/session/lake
>
> I wish you a happy IETF 116 ACE session!
>
> Yours,
> Daniel
>
>
> On Mon, Mar 13, 2023 at 11:20 PM Daniel Migault 
> wrote:
>
>> This sounds to be the final agenda. Please shout if there is anything we
>> need to change.
>>
>> We are a bit over time, so please:
>> 1. make sure you have the presentation uploaded in the lake session.
>> 2. try to be as short as possible. If no issue needs to be discussed for
>> revoked-token we may skim the slot to 5 minutes. If we are too short the
>> follow-up activities may also be skimmed to 5 minutes.
>>
>> - words from chairs / AD (5 minutes)
>> - pubsub-profile (10 minutes) Cigdem
>> - revoked-token WGLC discussions (10 minutes) Marco
>> - oscore-gm-admin (10 minutes) Marco
>> - follow-up activities (5-10 minutes) Marco
>> - edhoc-oscore-profile ( 10 minutes) Goran
>> - selander-ace-coap-est-oscore (10 minutes )
>>
>> Yours,
>> Logan and Daniel
>>
>> On Mon, Mar 13, 2023 at 9:58 PM Göran Selander <
>> goran.selan...@ericsson.com> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> Just confirming the need for a slot for edhoc-oscore-profile, 5-10
>>> minutes. In particular it would be good to discuss a proposal to take out
>>> the use of EDHOC_KeyUpdate, sketched here:
>>>
>>> https://github.com/ace-wg/ace-edhoc-oscore-profile/pull/1
>>>
>>>
>>>
>>> Göran
>>>
>>>
>>>
>>> *From: *Ace  on behalf of Daniel Migault <
>>> mglt.i...@gmail.com>
>>> *Date: *Monday, 13 March 2023 at 23:14
>>> *To: *Ace Wg 
>>> *Cc: *lake-cha...@ietf.org 
>>> *Subject: *Re: [Ace] ACE agenda / presentation
>>>
>>> Please find the current draft agenda that considers the received inputs
>>> so far. Feel free to comment, we will share it with lake chairs so they can
>>> upload it on time (march 15).
>>>
>>>
>>>
>>> - words from chairs / AD (5 minutes)
>>>
>>> - pubsub-profile (10 minutes) Cigdem
>>>
>>> - revoked-token WGLC discussions (10 minutes) Marco
>>>
>>> - oscore-gm-admin (10 minutes) Marco
>>>
>>> - follow-up activities (5-10 minutes) Marco
>>>
>>> - selander-ace-coap-est-oscore (10 minutes )
>>>
>>> - edhoc-oscore-profile ?
>>>
>>>
>>>
>>> Yours,
>>>
>>> Logan and Daniel
>>>
>>>
>>>
>>> On Mon, Mar 13, 2023 at 12:20 PM Daniel Migault 
>>> wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>> Please do not forget to provide feed backs regarding the current agenda
>>> by today if possible  - and confirm your slot.
>>>
>>> - words from AD
>>>
>>> - revoked-token WGLC discussions if needed)
>>>
>>> - oscore-gm-admin
>>>
>>> - pubsub-profile
>>>
>>> - edhoc-oscore-profile
>>>
>>> - group-oscore-profile
>>>
>>> - selander- -ace-coap-est-oscore (10 minutes )
>>>
>>>
>>>
>>> Yours,
>>>
>>> Logan and daniel
>>>
>>>
>>>
>>> On Fri, Mar 10, 2023 at 2:37 PM Daniel Migault 
>>> wrote:
>>>
>>> Hi all,
>>>
>>>
>>>
>>> As we are sharing the session with the lake, we need to be a bit more
>>> organized than we usual are. If you intend to request a session please
>>> provide by Monday 13 (end of your day) a time slot request.
>>>
>>>

Re: [Ace] Status of draft-ietf-ace-cmpv2-coap-transport

[Daniel Migault]

Great thanks!
Yours, 
Daniel

-Original Message-
From: Mohit Sahni  
Sent: March 15, 2023 2:53 PM
To: Daniel Migault 
Cc: Paul Wouters ; Mohit Sahni 
; Brockhaus, Hendrik 
; stripa...@paloaltonetworks.com; 
draft-ietf-ace-cmpv2-coap-transport@ietf.org; ace@ietf.org
Subject: Re: [Ace] Status of draft-ietf-ace-cmpv2-coap-transport

Hi Daniel
I have shared the new version with Paul in a separate email.

-Mohit

On Wed, Mar 15, 2023 at 6:34 AM Daniel Migault  wrote:
>
> Hi,
>
> I am just checking if the new version has been shared. I do not necessarily 
> need to be in the loop, but I just want to make sure the document to progress 
> over the last needed micro bit that remains to be fixed.
>
> Yours,
> Daniel
>
> On Tue, Mar 14, 2023 at 5:22 PM Daniel Migault  wrote:
>>
>> Thanks for the response. I confirm no active discussion in the WG.
>> Yours,
>> Daniel
>>
>> On Tue, Mar 14, 2023 at 5:18 PM Paul Wouters  wrote:
>>>
>>>
>>>
>>> On Tue, Mar 14, 2023 at 2:54 PM Daniel Migault  wrote:
>>>>
>>>> Hi Mohit,
>>>>
>>>> I am just wondering if there is any version you can share with us that 
>>>> solves Paul's comment. The draft cut off has passed so you won't be able 
>>>> to publish the draft yourself. I suggest you shar eit there and if that 
>>>> addresses all comments either Paul can request a publication or you will 
>>>> be able to publish it the monday the IETF starts - whichever Paul thinks 
>>>> is easier.
>>>
>>>
>>> We don't have to wait for the Monday, as the changes aren't changing 
>>> core aspects of the document and I don't think it is currently actively 
>>> discussed in the WG, as it waiting for a change for me to start IETF Last 
>>> Call.
>>>
>>> Paul
>>>
>>>
>>>>
>>>> Yours,
>>>> Daniel
>>>>
>>>> On Fri, Mar 3, 2023 at 2:12 PM Mohit Sahni  
>>>> wrote:
>>>>>
>>>>> Hi Hendrik
>>>>> I am working on resolving Paul's comments. Hopefully I will resolve and 
>>>>> publish the next version by Monday March 6th.
>>>>>
>>>>> -Mohit
>>>>>
>>>>> On Thu, Mar 2, 2023 at 10:31 PM Brockhaus, Hendrik 
>>>>>  wrote:
>>>>>>
>>>>>> Dear Mohit
>>>>>>
>>>>>> Dear Saurabh
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks’ a lot, for writing the document 
>>>>>> draft-ietf-ace-cmpv2-coap-transport. I really appreciate your 
>>>>>> work and use it in my documents that update the Certificate 
>>>>>> Management Protocol. In the meantime, all three documents 
>>>>>> (draft-ietf-lamps-cmp-algorithms, draft-ietf-lamps-cmp-updates, 
>>>>>> and draft-ietf-lamps-lightweight-cmp-profile) are in RFC Editor 
>>>>>> queue. https://www.rfc-editor.org/cluster_info.php?cid=C458
>>>>>>
>>>>>> The publication of these documents requires also 
>>>>>> draft-ietf-ace-cmpv2-coap-transport to reach that state.
>>>>>>
>>>>>> I feel like little work is required tackling the comments from the ADs 
>>>>>> during the final reviews. From my experience, quick response and timely 
>>>>>> updates of the draft ease the review and approval process a lot and also 
>>>>>> reduce the time you have to invest on this work.
>>>>>>
>>>>>> Saying this, I would appreciate seeing more activity on this draft. If 
>>>>>> you need support from my side, I am welcome to help, please feel free to 
>>>>>> contact me.
>>>>>>
>>>>>>
>>>>>>
>>>>>> With best regards,
>>>>>>
>>>>>> Hendrik
>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Migault
>>>> Ericsson
>>
>>
>>
>> --
>> Daniel Migault
>> Ericsson
>
>
>
> --
> Daniel Migault
> Ericsson
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] Status of draft-ietf-ace-cmpv2-coap-transport

[Daniel Migault]

Hi,

I am just checking if the new version has been shared. I do not necessarily
need to be in the loop, but I just want to make sure the document to
progress over the last needed micro bit that remains to be fixed.

Yours,
Daniel

On Tue, Mar 14, 2023 at 5:22 PM Daniel Migault  wrote:

> Thanks for the response. I confirm no active discussion in the WG.
> Yours,
> Daniel
>
> On Tue, Mar 14, 2023 at 5:18 PM Paul Wouters 
> wrote:
>
>>
>>
>> On Tue, Mar 14, 2023 at 2:54 PM Daniel Migault 
>> wrote:
>>
>>> Hi Mohit,
>>>
>>> I am just wondering if there is any version you can share with us that
>>> solves Paul's comment. The draft cut off has passed so you won't be able to
>>> publish the draft yourself. I suggest you shar eit there and if that
>>> addresses all comments either Paul can request a publication or you will be
>>> able to publish it the monday the IETF starts - whichever Paul thinks is
>>> easier.
>>>
>>
>> We don't have to wait for the Monday, as the changes aren't changing core
>> aspects of the document and I don't think it is currently actively
>> discussed in the WG,
>> as it waiting for a change for me to start IETF Last Call.
>>
>> Paul
>>
>>
>>
>>> Yours,
>>> Daniel
>>>
>>> On Fri, Mar 3, 2023 at 2:12 PM Mohit Sahni 
>>> wrote:
>>>
>>>> Hi Hendrik
>>>> I am working on resolving Paul's comments. Hopefully I will resolve and
>>>> publish the next version by Monday March 6th.
>>>>
>>>> -Mohit
>>>>
>>>> On Thu, Mar 2, 2023 at 10:31 PM Brockhaus, Hendrik <
>>>> hendrik.brockh...@siemens.com> wrote:
>>>>
>>>>> Dear Mohit
>>>>>
>>>>> Dear Saurabh
>>>>>
>>>>>
>>>>>
>>>>> Thanks’ a lot, for writing the document
>>>>> draft-ietf-ace-cmpv2-coap-transport. I really appreciate your work and use
>>>>> it in my documents that update the Certificate Management Protocol. In the
>>>>> meantime, all three documents (draft-ietf-lamps-cmp-algorithms,
>>>>> draft-ietf-lamps-cmp-updates, and 
>>>>> draft-ietf-lamps-lightweight-cmp-profile)
>>>>> are in RFC Editor queue.
>>>>> https://www.rfc-editor.org/cluster_info.php?cid=C458
>>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_cluster-5Finfo.php-3Fcid-3DC458&d=DwMFAg&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=J7DgfMyeL26OZuy8d3qTy_h24Ff1NatxSKMgDUj2Kxg&m=g73vpLN1d8vop4qNIObfQrZU9dURHLU-mPZXmUGSYpvVENKqDwPaQ9TIa2E41iGG&s=a0Mo2DY4roTHbfGVxO7KE-ZA_xbzMWVzL7VlQTGh8jc&e=>
>>>>>
>>>>> The publication of these documents requires also
>>>>> draft-ietf-ace-cmpv2-coap-transport to reach that state.
>>>>>
>>>>> I feel like little work is required tackling the comments from the ADs
>>>>> during the final reviews. From my experience, quick response and timely
>>>>> updates of the draft ease the review and approval process a lot and also
>>>>> reduce the time you have to invest on this work.
>>>>>
>>>>> Saying this, I would appreciate seeing more activity on this draft. If
>>>>> you need support from my side, I am welcome to help, please feel free to
>>>>> contact me.
>>>>>
>>>>>
>>>>>
>>>>> With best regards,
>>>>>
>>>>> Hendrik
>>>>>
>>>>
>>>
>>> --
>>> Daniel Migault
>>> Ericsson
>>>
>>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] Status of draft-ietf-ace-cmpv2-coap-transport

[Daniel Migault]

Thanks for the response. I confirm no active discussion in the WG.
Yours,
Daniel

On Tue, Mar 14, 2023 at 5:18 PM Paul Wouters  wrote:

>
>
> On Tue, Mar 14, 2023 at 2:54 PM Daniel Migault 
> wrote:
>
>> Hi Mohit,
>>
>> I am just wondering if there is any version you can share with us that
>> solves Paul's comment. The draft cut off has passed so you won't be able to
>> publish the draft yourself. I suggest you shar eit there and if that
>> addresses all comments either Paul can request a publication or you will be
>> able to publish it the monday the IETF starts - whichever Paul thinks is
>> easier.
>>
>
> We don't have to wait for the Monday, as the changes aren't changing core
> aspects of the document and I don't think it is currently actively
> discussed in the WG,
> as it waiting for a change for me to start IETF Last Call.
>
> Paul
>
>
>
>> Yours,
>> Daniel
>>
>> On Fri, Mar 3, 2023 at 2:12 PM Mohit Sahni 
>> wrote:
>>
>>> Hi Hendrik
>>> I am working on resolving Paul's comments. Hopefully I will resolve and
>>> publish the next version by Monday March 6th.
>>>
>>> -Mohit
>>>
>>> On Thu, Mar 2, 2023 at 10:31 PM Brockhaus, Hendrik <
>>> hendrik.brockh...@siemens.com> wrote:
>>>
>>>> Dear Mohit
>>>>
>>>> Dear Saurabh
>>>>
>>>>
>>>>
>>>> Thanks’ a lot, for writing the document
>>>> draft-ietf-ace-cmpv2-coap-transport. I really appreciate your work and use
>>>> it in my documents that update the Certificate Management Protocol. In the
>>>> meantime, all three documents (draft-ietf-lamps-cmp-algorithms,
>>>> draft-ietf-lamps-cmp-updates, and draft-ietf-lamps-lightweight-cmp-profile)
>>>> are in RFC Editor queue.
>>>> https://www.rfc-editor.org/cluster_info.php?cid=C458
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_cluster-5Finfo.php-3Fcid-3DC458&d=DwMFAg&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=J7DgfMyeL26OZuy8d3qTy_h24Ff1NatxSKMgDUj2Kxg&m=g73vpLN1d8vop4qNIObfQrZU9dURHLU-mPZXmUGSYpvVENKqDwPaQ9TIa2E41iGG&s=a0Mo2DY4roTHbfGVxO7KE-ZA_xbzMWVzL7VlQTGh8jc&e=>
>>>>
>>>> The publication of these documents requires also
>>>> draft-ietf-ace-cmpv2-coap-transport to reach that state.
>>>>
>>>> I feel like little work is required tackling the comments from the ADs
>>>> during the final reviews. From my experience, quick response and timely
>>>> updates of the draft ease the review and approval process a lot and also
>>>> reduce the time you have to invest on this work.
>>>>
>>>> Saying this, I would appreciate seeing more activity on this draft. If
>>>> you need support from my side, I am welcome to help, please feel free to
>>>> contact me.
>>>>
>>>>
>>>>
>>>> With best regards,
>>>>
>>>> Hendrik
>>>>
>>>
>>
>> --
>> Daniel Migault
>> Ericsson
>>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] Status of draft-ietf-ace-cmpv2-coap-transport

[Daniel Migault]

Please send the version by email and let Paul confirm it addresses its
concerns so we can have the draft being sent to the IESG before this IETF.
Yours,
Daniel

On Tue, Mar 14, 2023 at 3:00 PM Mohit Sahni 
wrote:

> Daniel, I was waiting for Paul's reply. I can push a new version by today
> evening PST.
>
> On Tue, Mar 14, 2023 at 11:54 AM Daniel Migault 
> wrote:
>
>> Hi Mohit,
>>
>> I am just wondering if there is any version you can share with us that
>> solves Paul's comment. The draft cut off has passed so you won't be able to
>> publish the draft yourself. I suggest you shar eit there and if that
>> addresses all comments either Paul can request a publication or you will be
>> able to publish it the monday the IETF starts - whichever Paul thinks is
>> easier.
>>
>> Yours,
>> Daniel
>>
>> On Fri, Mar 3, 2023 at 2:12 PM Mohit Sahni 
>> wrote:
>>
>>> Hi Hendrik
>>> I am working on resolving Paul's comments. Hopefully I will resolve and
>>> publish the next version by Monday March 6th.
>>>
>>> -Mohit
>>>
>>> On Thu, Mar 2, 2023 at 10:31 PM Brockhaus, Hendrik <
>>> hendrik.brockh...@siemens.com> wrote:
>>>
>>>> Dear Mohit
>>>>
>>>> Dear Saurabh
>>>>
>>>>
>>>>
>>>> Thanks’ a lot, for writing the document
>>>> draft-ietf-ace-cmpv2-coap-transport. I really appreciate your work and use
>>>> it in my documents that update the Certificate Management Protocol. In the
>>>> meantime, all three documents (draft-ietf-lamps-cmp-algorithms,
>>>> draft-ietf-lamps-cmp-updates, and draft-ietf-lamps-lightweight-cmp-profile)
>>>> are in RFC Editor queue.
>>>> https://www.rfc-editor.org/cluster_info.php?cid=C458
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_cluster-5Finfo.php-3Fcid-3DC458&d=DwMFAg&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=J7DgfMyeL26OZuy8d3qTy_h24Ff1NatxSKMgDUj2Kxg&m=g73vpLN1d8vop4qNIObfQrZU9dURHLU-mPZXmUGSYpvVENKqDwPaQ9TIa2E41iGG&s=a0Mo2DY4roTHbfGVxO7KE-ZA_xbzMWVzL7VlQTGh8jc&e=>
>>>>
>>>> The publication of these documents requires also
>>>> draft-ietf-ace-cmpv2-coap-transport to reach that state.
>>>>
>>>> I feel like little work is required tackling the comments from the ADs
>>>> during the final reviews. From my experience, quick response and timely
>>>> updates of the draft ease the review and approval process a lot and also
>>>> reduce the time you have to invest on this work.
>>>>
>>>> Saying this, I would appreciate seeing more activity on this draft. If
>>>> you need support from my side, I am welcome to help, please feel free to
>>>> contact me.
>>>>
>>>>
>>>>
>>>> With best regards,
>>>>
>>>> Hendrik
>>>>
>>>
>>
>> --
>> Daniel Migault
>> Ericsson
>>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] Status of draft-ietf-ace-cmpv2-coap-transport

[Daniel Migault]

Hi Mohit,

I am just wondering if there is any version you can share with us that
solves Paul's comment. The draft cut off has passed so you won't be able to
publish the draft yourself. I suggest you shar eit there and if that
addresses all comments either Paul can request a publication or you will be
able to publish it the monday the IETF starts - whichever Paul thinks is
easier.

Yours,
Daniel

On Fri, Mar 3, 2023 at 2:12 PM Mohit Sahni 
wrote:

> Hi Hendrik
> I am working on resolving Paul's comments. Hopefully I will resolve and
> publish the next version by Monday March 6th.
>
> -Mohit
>
> On Thu, Mar 2, 2023 at 10:31 PM Brockhaus, Hendrik <
> hendrik.brockh...@siemens.com> wrote:
>
>> Dear Mohit
>>
>> Dear Saurabh
>>
>>
>>
>> Thanks’ a lot, for writing the document
>> draft-ietf-ace-cmpv2-coap-transport. I really appreciate your work and use
>> it in my documents that update the Certificate Management Protocol. In the
>> meantime, all three documents (draft-ietf-lamps-cmp-algorithms,
>> draft-ietf-lamps-cmp-updates, and draft-ietf-lamps-lightweight-cmp-profile)
>> are in RFC Editor queue.
>> https://www.rfc-editor.org/cluster_info.php?cid=C458
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_cluster-5Finfo.php-3Fcid-3DC458&d=DwMFAg&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=J7DgfMyeL26OZuy8d3qTy_h24Ff1NatxSKMgDUj2Kxg&m=g73vpLN1d8vop4qNIObfQrZU9dURHLU-mPZXmUGSYpvVENKqDwPaQ9TIa2E41iGG&s=a0Mo2DY4roTHbfGVxO7KE-ZA_xbzMWVzL7VlQTGh8jc&e=>
>>
>> The publication of these documents requires also
>> draft-ietf-ace-cmpv2-coap-transport to reach that state.
>>
>> I feel like little work is required tackling the comments from the ADs
>> during the final reviews. From my experience, quick response and timely
>> updates of the draft ease the review and approval process a lot and also
>> reduce the time you have to invest on this work.
>>
>> Saying this, I would appreciate seeing more activity on this draft. If
>> you need support from my side, I am welcome to help, please feel free to
>> contact me.
>>
>>
>>
>> With best regards,
>>
>> Hendrik
>>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE agenda / presentation

[Daniel Migault]

Hi,

I think this is the ACE agenda Stephen and Malisa can consider. I am
assuming it will be uploaded with the LAKE agenda.

- words from chairs / AD (5 minutes)
- pubsub-profile (10 minutes) Cigdem
- revoked-token WGLC discussions (10 minutes) Marco
- oscore-gm-admin (10 minutes) Marco
- follow-up activities (5-10 minutes) Marco
- edhoc-oscore-profile ( 10 minutes) Goran
- selander-ace-coap-est-oscore (10 minutes ) Malissa

I would like to thank ACE folks for providing the necessary inputs so we
can provide the agenda on time and Malisa to remind me of the March 15
deadline for the agenda last Friday ;-).
Please upload your presentation as soon as you can and make it clear the
presentation is related to ace (not lake):
https://datatracker.ietf.org/meeting/116/session/lake

I wish you a happy IETF 116 ACE session!

Yours,
Daniel


On Mon, Mar 13, 2023 at 11:20 PM Daniel Migault  wrote:

> This sounds to be the final agenda. Please shout if there is anything we
> need to change.
>
> We are a bit over time, so please:
> 1. make sure you have the presentation uploaded in the lake session.
> 2. try to be as short as possible. If no issue needs to be discussed for
> revoked-token we may skim the slot to 5 minutes. If we are too short the
> follow-up activities may also be skimmed to 5 minutes.
>
> - words from chairs / AD (5 minutes)
> - pubsub-profile (10 minutes) Cigdem
> - revoked-token WGLC discussions (10 minutes) Marco
> - oscore-gm-admin (10 minutes) Marco
> - follow-up activities (5-10 minutes) Marco
> - edhoc-oscore-profile ( 10 minutes) Goran
> - selander-ace-coap-est-oscore (10 minutes )
>
> Yours,
> Logan and Daniel
>
> On Mon, Mar 13, 2023 at 9:58 PM Göran Selander <
> goran.selan...@ericsson.com> wrote:
>
>> Hi,
>>
>>
>>
>> Just confirming the need for a slot for edhoc-oscore-profile, 5-10
>> minutes. In particular it would be good to discuss a proposal to take out
>> the use of EDHOC_KeyUpdate, sketched here:
>>
>> https://github.com/ace-wg/ace-edhoc-oscore-profile/pull/1
>>
>>
>>
>> Göran
>>
>>
>>
>> *From: *Ace  on behalf of Daniel Migault <
>> mglt.i...@gmail.com>
>> *Date: *Monday, 13 March 2023 at 23:14
>> *To: *Ace Wg 
>> *Cc: *lake-cha...@ietf.org 
>> *Subject: *Re: [Ace] ACE agenda / presentation
>>
>> Please find the current draft agenda that considers the received inputs
>> so far. Feel free to comment, we will share it with lake chairs so they can
>> upload it on time (march 15).
>>
>>
>>
>> - words from chairs / AD (5 minutes)
>>
>> - pubsub-profile (10 minutes) Cigdem
>>
>> - revoked-token WGLC discussions (10 minutes) Marco
>>
>> - oscore-gm-admin (10 minutes) Marco
>>
>> - follow-up activities (5-10 minutes) Marco
>>
>> - selander-ace-coap-est-oscore (10 minutes )
>>
>> - edhoc-oscore-profile ?
>>
>>
>>
>> Yours,
>>
>> Logan and Daniel
>>
>>
>>
>> On Mon, Mar 13, 2023 at 12:20 PM Daniel Migault 
>> wrote:
>>
>> Hi,
>>
>>
>>
>> Please do not forget to provide feed backs regarding the current agenda
>> by today if possible  - and confirm your slot.
>>
>> - words from AD
>>
>> - revoked-token WGLC discussions if needed)
>>
>> - oscore-gm-admin
>>
>> - pubsub-profile
>>
>> - edhoc-oscore-profile
>>
>> - group-oscore-profile
>>
>> - selander- -ace-coap-est-oscore (10 minutes )
>>
>>
>>
>> Yours,
>>
>> Logan and daniel
>>
>>
>>
>> On Fri, Mar 10, 2023 at 2:37 PM Daniel Migault 
>> wrote:
>>
>> Hi all,
>>
>>
>>
>> As we are sharing the session with the lake, we need to be a bit more
>> organized than we usual are. If you intend to request a session please
>> provide by Monday 13 (end of your day) a time slot request.
>>
>>
>>
>> current agenda could be, but please confirm.
>>
>> - words from AD
>>
>> - revoked-token WGLC discussions if needed)
>>
>> - oscore-gm-admin
>>
>> - pubsub-profile
>>
>> - edhoc-oscore-profile
>>
>> - group-oscore-profile
>>
>>
>>
>> Yours,
>> Daniel
>>
>>
>>
>> On Sat, Feb 25, 2023 at 10:04 AM Daniel Migault 
>> wrote:
>>
>> Hi,
>>
>>
>>
>> Please do not forget to update the agenda:
>>
>> https://notes.ietf.org/notes-ietf-116-ace
>>
>>
>>
>> and upload your presentations by 2023-03-26 (Yokhoama time)
>>
>> https://datatracker.ietf.org/meeting/116/session/ace
>>
>>
>>
>> Yours,
>>
>> Logan and Daniel
>>
>>
>>
>> --
>>
>> Daniel Migault
>>
>> Ericsson
>>
>>
>>
>>
>> --
>>
>> Daniel Migault
>>
>> Ericsson
>>
>>
>>
>>
>> --
>>
>> Daniel Migault
>>
>> Ericsson
>>
>>
>>
>>
>> --
>>
>> Daniel Migault
>>
>> Ericsson
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE agenda / presentation

[Daniel Migault]

This sounds to be the final agenda. Please shout if there is anything we
need to change.

We are a bit over time, so please:
1. make sure you have the presentation uploaded in the lake session.
2. try to be as short as possible. If no issue needs to be discussed for
revoked-token we may skim the slot to 5 minutes. If we are too short the
follow-up activities may also be skimmed to 5 minutes.

- words from chairs / AD (5 minutes)
- pubsub-profile (10 minutes) Cigdem
- revoked-token WGLC discussions (10 minutes) Marco
- oscore-gm-admin (10 minutes) Marco
- follow-up activities (5-10 minutes) Marco
- edhoc-oscore-profile ( 10 minutes) Goran
- selander-ace-coap-est-oscore (10 minutes )

Yours,
Logan and Daniel

On Mon, Mar 13, 2023 at 9:58 PM Göran Selander 
wrote:

> Hi,
>
>
>
> Just confirming the need for a slot for edhoc-oscore-profile, 5-10
> minutes. In particular it would be good to discuss a proposal to take out
> the use of EDHOC_KeyUpdate, sketched here:
>
> https://github.com/ace-wg/ace-edhoc-oscore-profile/pull/1
>
>
>
> Göran
>
>
>
> *From: *Ace  on behalf of Daniel Migault <
> mglt.i...@gmail.com>
> *Date: *Monday, 13 March 2023 at 23:14
> *To: *Ace Wg 
> *Cc: *lake-cha...@ietf.org 
> *Subject: *Re: [Ace] ACE agenda / presentation
>
> Please find the current draft agenda that considers the received inputs
> so far. Feel free to comment, we will share it with lake chairs so they can
> upload it on time (march 15).
>
>
>
> - words from chairs / AD (5 minutes)
>
> - pubsub-profile (10 minutes) Cigdem
>
> - revoked-token WGLC discussions (10 minutes) Marco
>
> - oscore-gm-admin (10 minutes) Marco
>
> - follow-up activities (5-10 minutes) Marco
>
> - selander-ace-coap-est-oscore (10 minutes )
>
> - edhoc-oscore-profile ?
>
>
>
> Yours,
>
> Logan and Daniel
>
>
>
> On Mon, Mar 13, 2023 at 12:20 PM Daniel Migault 
> wrote:
>
> Hi,
>
>
>
> Please do not forget to provide feed backs regarding the current agenda
> by today if possible  - and confirm your slot.
>
> - words from AD
>
> - revoked-token WGLC discussions if needed)
>
> - oscore-gm-admin
>
> - pubsub-profile
>
> - edhoc-oscore-profile
>
> - group-oscore-profile
>
> - selander- -ace-coap-est-oscore (10 minutes )
>
>
>
> Yours,
>
> Logan and daniel
>
>
>
> On Fri, Mar 10, 2023 at 2:37 PM Daniel Migault 
> wrote:
>
> Hi all,
>
>
>
> As we are sharing the session with the lake, we need to be a bit more
> organized than we usual are. If you intend to request a session please
> provide by Monday 13 (end of your day) a time slot request.
>
>
>
> current agenda could be, but please confirm.
>
> - words from AD
>
> - revoked-token WGLC discussions if needed)
>
> - oscore-gm-admin
>
> - pubsub-profile
>
> - edhoc-oscore-profile
>
> - group-oscore-profile
>
>
>
> Yours,
> Daniel
>
>
>
> On Sat, Feb 25, 2023 at 10:04 AM Daniel Migault 
> wrote:
>
> Hi,
>
>
>
> Please do not forget to update the agenda:
>
> https://notes.ietf.org/notes-ietf-116-ace
>
>
>
> and upload your presentations by 2023-03-26 (Yokhoama time)
>
> https://datatracker.ietf.org/meeting/116/session/ace
>
>
>
> Yours,
>
> Logan and Daniel
>
>
>
> --
>
> Daniel Migault
>
> Ericsson
>
>
>
>
> --
>
> Daniel Migault
>
> Ericsson
>
>
>
>
> --
>
> Daniel Migault
>
> Ericsson
>
>
>
>
> --
>
> Daniel Migault
>
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE agenda / presentation

[Daniel Migault]

Please find the current draft agenda that considers the received inputs
so far. Feel free to comment, we will share it with lake chairs so they can
upload it on time (march 15).

- words from chairs / AD (5 minutes)
- pubsub-profile (10 minutes) Cigdem
- revoked-token WGLC discussions (10 minutes) Marco
- oscore-gm-admin (10 minutes) Marco
- follow-up activities (5-10 minutes) Marco
- selander-ace-coap-est-oscore (10 minutes )
- edhoc-oscore-profile ?

Yours,
Logan and Daniel

On Mon, Mar 13, 2023 at 12:20 PM Daniel Migault  wrote:

> Hi,
>
> Please do not forget to provide feed backs regarding the current agenda
> by today if possible  - and confirm your slot.
> - words from AD
> - revoked-token WGLC discussions if needed)
> - oscore-gm-admin
> - pubsub-profile
> - edhoc-oscore-profile
> - group-oscore-profile
> - selander- -ace-coap-est-oscore (10 minutes )
>
> Yours,
> Logan and daniel
>
> On Fri, Mar 10, 2023 at 2:37 PM Daniel Migault 
> wrote:
>
>> Hi all,
>>
>> As we are sharing the session with the lake, we need to be a bit more
>> organized than we usual are. If you intend to request a session please
>> provide by Monday 13 (end of your day) a time slot request.
>>
>> current agenda could be, but please confirm.
>> - words from AD
>> - revoked-token WGLC discussions if needed)
>> - oscore-gm-admin
>> - pubsub-profile
>> - edhoc-oscore-profile
>> - group-oscore-profile
>>
>> Yours,
>> Daniel
>>
>> On Sat, Feb 25, 2023 at 10:04 AM Daniel Migault 
>> wrote:
>>
>>> Hi,
>>>
>>> Please do not forget to update the agenda:
>>> https://notes.ietf.org/notes-ietf-116-ace
>>>
>>> and upload your presentations by 2023-03-26 (Yokhoama time)
>>> https://datatracker.ietf.org/meeting/116/session/ace
>>>
>>> Yours,
>>> Logan and Daniel
>>>
>>> --
>>> Daniel Migault
>>> Ericsson
>>>
>>
>>
>> --
>> Daniel Migault
>> Ericsson
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] WGLC draft-ietf-ace-revoked-token-notification-04.txt

[Daniel Migault]

Hi everyone,

This email starts a WGLC for draft-ietf-ace-revoked-token-notification
which ends on March 27. Please provide your support and feed backs by that
time. We will take advantage of the IETF116 session to solve any remaining
discussions on that draft.

I am also looking for someone interested in being the document shepherd:
Please volunteer!

To the co-authors I am looking at:
- 1) a heads-up regarding the implementations.
- 2) a confirmation that they are or not aware of any IPR
- 3)  a confirmation that they are willing to co-author the document.

Yours,
Logan and Daniel


On Mon, Mar 13, 2023 at 11:36 AM  wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the Authentication and
> Authorization for Constrained Environments (ACE) WG of the IETF.
>
>Title   : Notification of Revoked Access Tokens in the
> Authentication and Authorization for Constrained Environments (ACE)
> Framework
>Authors : Marco Tiloca
>  Ludwig Seitz
>  Francesca Palombini
>  Sebastian Echeverria
>  Grace Lewis
>Filename: draft-ietf-ace-revoked-token-notification-04.txt
>Pages   : 59
>Date: 2023-03-13
>
> Abstract:
>This document specifies a method of the Authentication and
>Authorization for Constrained Environments (ACE) framework, which
>allows an Authorization Server to notify Clients and Resource Servers
>(i.e., registered devices) about revoked Access Tokens.  The method
>allows Clients and Resource Servers to access a Token Revocation List
>on the Authorization Server, with the possible additional use of
>resource observation for the Constrained Application Protocol (CoAP).
>Resulting (unsolicited) notifications of revoked Access Tokens
>complement alternative approaches such as token introspection, while
>not requiring additional endpoints on Clients and Resource Servers.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ace-revoked-token-notification/
>
> There is also an HTML version available at:
>
> https://www.ietf.org/archive/id/draft-ietf-ace-revoked-token-notification-04.html
>
> A diff from the previous version is available at:
>
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-revoked-token-notification-04
>
> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
>
>
> _______
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE agenda / presentation

[Daniel Migault]

Hi,

Please do not forget to provide feed backs regarding the current agenda
by today if possible  - and confirm your slot.
- words from AD
- revoked-token WGLC discussions if needed)
- oscore-gm-admin
- pubsub-profile
- edhoc-oscore-profile
- group-oscore-profile
- selander- -ace-coap-est-oscore (10 minutes )

Yours,
Logan and daniel

On Fri, Mar 10, 2023 at 2:37 PM Daniel Migault  wrote:

> Hi all,
>
> As we are sharing the session with the lake, we need to be a bit more
> organized than we usual are. If you intend to request a session please
> provide by Monday 13 (end of your day) a time slot request.
>
> current agenda could be, but please confirm.
> - words from AD
> - revoked-token WGLC discussions if needed)
> - oscore-gm-admin
> - pubsub-profile
> - edhoc-oscore-profile
> - group-oscore-profile
>
> Yours,
> Daniel
>
> On Sat, Feb 25, 2023 at 10:04 AM Daniel Migault 
> wrote:
>
>> Hi,
>>
>> Please do not forget to update the agenda:
>> https://notes.ietf.org/notes-ietf-116-ace
>>
>> and upload your presentations by 2023-03-26 (Yokhoama time)
>> https://datatracker.ietf.org/meeting/116/session/ace
>>
>> Yours,
>> Logan and Daniel
>>
>> --
>> Daniel Migault
>> Ericsson
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE agenda / presentation

[Daniel Migault]

Hi all,

As we are sharing the session with the lake, we need to be a bit more
organized than we usual are. If you intend to request a session please
provide by Monday 13 (end of your day) a time slot request.

current agenda could be, but please confirm.
- words from AD
- revoked-token WGLC discussions if needed)
- oscore-gm-admin
- pubsub-profile
- edhoc-oscore-profile
- group-oscore-profile

Yours,
Daniel

On Sat, Feb 25, 2023 at 10:04 AM Daniel Migault  wrote:

> Hi,
>
> Please do not forget to update the agenda:
> https://notes.ietf.org/notes-ietf-116-ace
>
> and upload your presentations by 2023-03-26 (Yokhoama time)
> https://datatracker.ietf.org/meeting/116/session/ace
>
> Yours,
> Logan and Daniel
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Publication has been requested for draft-ietf-ace-key-groupcomm-oscore-16

[Daniel Migault via Datatracker]

Daniel Migault has requested publication of 
draft-ietf-ace-key-groupcomm-oscore-16 as Proposed Standard on behalf of the 
ACE working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm-oscore/


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] ACE agenda / presentation

[Daniel Migault]

Hi,

Please do not forget to update the agenda:
https://notes.ietf.org/notes-ietf-116-ace

and upload your presentations by 2023-03-26 (Yokhoama time)
https://datatracker.ietf.org/meeting/116/session/ace

Yours,
Logan and Daniel

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] interim meeting (corrected date) Monday 2023-02-20 09:00 EST (14:00 UTC)

[Daniel Migault]

Hi,

Just to remind you we do have an interim meeting on Monday. Please upload
your presentation if you want to present.

Yours,
Daniel


On Mon, Feb 6, 2023 at 9:17 AM Daniel Migault  wrote:

> Hi all,
>
> My bad, the next interim meeting is in February - not March..
> Please note that we do have an interim meeting on Monday Monday 2023-02-20
> 09:00 EST (14:00 UTC).
>
> Feel free to let us know if you intend to present and upload your
> presentation:
> https://datatracker.ietf.org/meeting/interim-2023-ace-02/session/ace
>
> The current ongoing drafts are:
> 0. -key-groupcomm-oscore
> 1. -pubsub-profile
> 2. -revoked-token-notification
> 3. -oscore-gm-admin
> 4. -edhoc-oscore-profile
>
> Let's see if we can make a WGLC right after the interim!
>
> Yours,
> Daniel.
>
>
> On Mon, Feb 6, 2023 at 9:15 AM Daniel Migault  wrote:
>
>> Hi all,
>>
>> My bad, the next interim meeting is in February - not March..
>> Please note that we do have an interim meeting on Monday Monday
>> 2023-02-20 09:00 EST (14:00 UTC).
>>
>> Feel free to let us know if you intend to present and upload your
>> presentation:
>> https://datatracker.ietf.org/meeting/interim-2023-ace-02/session/ace
>>
>> The current ongoing drafts are:
>> 0. -key-groupcomm-oscore
>> 1. -pubsub-profile
>> 2. -revoked-token-notification
>> 3. -oscore-gm-admin
>> 4. -edhoc-oscore-profile
>>
>> Let's see if we can make a WGLC right after the interim!
>>
>> Yours,
>> Daniel.
>>
>> On Sun, Feb 5, 2023 at 8:44 PM Daniel Migault 
>> wrote:
>>
>>> Please note that we do have an interim meeting on Monday 2023-03-20
>>> 09:00 EDT (13:00 UTC).
>>>
>>> Feel free to let us know if you intend to present and upload your
>>> presentation:
>>> https://datatracker.ietf.org/meeting/interim-2023-ace-03/session/ace
>>>
>>>
>>> The current ongoing drafts are:
>>> 0. -key-groupcomm-oscore
>>> 1. -pubsub-profile
>>> 2. -revoked-token-notification
>>> 3. -oscore-gm-admin
>>> 4. -edhoc-oscore-profile
>>>
>>> Let's see if we can make a WGLC right after the interim!
>>>
>>> Yours,
>>> Daniel
>>> --
>>> Daniel Migault
>>> Ericsson
>>>
>>
>>
>> --
>> Daniel Migault
>> Ericsson
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] interim meeting (corrected date) Monday 2023-02-20 09:00 EST (14:00 UTC)

[Daniel Migault]

Hi all,

My bad, the next interim meeting is in February - not March..
Please note that we do have an interim meeting on Monday Monday 2023-02-20
09:00 EST (14:00 UTC).

Feel free to let us know if you intend to present and upload your
presentation:
https://datatracker.ietf.org/meeting/interim-2023-ace-02/session/ace

The current ongoing drafts are:
0. -key-groupcomm-oscore
1. -pubsub-profile
2. -revoked-token-notification
3. -oscore-gm-admin
4. -edhoc-oscore-profile

Let's see if we can make a WGLC right after the interim!

Yours,
Daniel.


On Mon, Feb 6, 2023 at 9:15 AM Daniel Migault  wrote:

> Hi all,
>
> My bad, the next interim meeting is in February - not March..
> Please note that we do have an interim meeting on Monday Monday 2023-02-20
> 09:00 EST (14:00 UTC).
>
> Feel free to let us know if you intend to present and upload your
> presentation:
> https://datatracker.ietf.org/meeting/interim-2023-ace-02/session/ace
>
> The current ongoing drafts are:
> 0. -key-groupcomm-oscore
> 1. -pubsub-profile
> 2. -revoked-token-notification
> 3. -oscore-gm-admin
> 4. -edhoc-oscore-profile
>
> Let's see if we can make a WGLC right after the interim!
>
> Yours,
> Daniel.
>
> On Sun, Feb 5, 2023 at 8:44 PM Daniel Migault  wrote:
>
>> Please note that we do have an interim meeting on Monday 2023-03-20 09:00
>> EDT (13:00 UTC).
>>
>> Feel free to let us know if you intend to present and upload your
>> presentation:
>> https://datatracker.ietf.org/meeting/interim-2023-ace-03/session/ace
>>
>>
>> The current ongoing drafts are:
>> 0. -key-groupcomm-oscore
>> 1. -pubsub-profile
>> 2. -revoked-token-notification
>> 3. -oscore-gm-admin
>> 4. -edhoc-oscore-profile
>>
>> Let's see if we can make a WGLC right after the interim!
>>
>> Yours,
>> Daniel
>> --
>> Daniel Migault
>> Ericsson
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Monday 2023-02-20 09:00 EST (14:00 UTC)

[Daniel Migault]

Hi all,

My bad, the next interim meeting is in February - not March..
Please note that we do have an interim meeting on Monday 2023-03-20 09:00
EDT (13:00 UTC).

Feel free to let us know if you intend to present and upload your
presentation:
https://datatracker.ietf.org/meeting/interim-2023-ace-02/session/ace

The current ongoing drafts are:
0. -key-groupcomm-oscore
1. -pubsub-profile
2. -revoked-token-notification
3. -oscore-gm-admin
4. -edhoc-oscore-profile

Let's see if we can make a WGLC right after the interim!

Yours,
Daniel.

On Sun, Feb 5, 2023 at 8:44 PM Daniel Migault  wrote:

> Please note that we do have an interim meeting on Monday 2023-03-20 09:00
> EDT (13:00 UTC).
>
> Feel free to let us know if you intend to present and upload your
> presentation:
> https://datatracker.ietf.org/meeting/interim-2023-ace-03/session/ace
>
>
> The current ongoing drafts are:
> 0. -key-groupcomm-oscore
> 1. -pubsub-profile
> 2. -revoked-token-notification
> 3. -oscore-gm-admin
> 4. -edhoc-oscore-profile
>
> Let's see if we can make a WGLC right after the interim!
>
> Yours,
> Daniel
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] interim meeting Monday 2023-03-20 09:00 EDT (13:00 UTC)

[Daniel Migault]

Please note that we do have an interim meeting on Monday 2023-03-20 09:00
EDT (13:00 UTC).

Feel free to let us know if you intend to present and upload your
presentation:
https://datatracker.ietf.org/meeting/interim-2023-ace-03/session/ace


The current ongoing drafts are:
0. -key-groupcomm-oscore
1. -pubsub-profile
2. -revoked-token-notification
3. -oscore-gm-admin
4. -edhoc-oscore-profile

Let's see if we can make a WGLC right after the interim!

Yours,
Daniel
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-07.txt

[Daniel Migault]

Thanks Mohit.

Yours,
Daniel

On Fri, Jan 27, 2023 at 12:36 PM Mohit Sahni  wrote:

> Removed the text to resolve following comment:
>
> 3. Section 5. I think that the sentence
>
>The CoAP is vulnerable due to the connectionless characteristics of UDP
>itself.
>
> should either be expanded of what particular vulnerabilities are meant
> (because
> not all CoAP vulnerabilities are concerned with using UDP) or deleted.
>
> On Fri, Jan 27, 2023 at 9:34 AM  wrote:
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Authentication and Authorization for
> Constrained Environments WG of the IETF.
> >
> > Title   : CoAP Transfer for the Certificate Management
> Protocol
> > Authors : Mohit Sahni
> >   Saurabh Tripathi
> >   Filename: draft-ietf-ace-cmpv2-coap-transport-07.txt
> >   Pages   : 11
> >   Date: 2023-01-27
> >
> > Abstract:
> >This document specifies the use of Constrained Application Protocol
> >(CoAP) as a transfer mechanism for the Certificate Management
> >Protocol (CMP).  CMP defines the interaction between various PKI
> >entities for the purpose of certificate creation and management.
> >CoAP is an HTTP-like client-server protocol used by various
> >constrained devices in the IoT space.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-ace-cmpv2-coap-transport/
> >
> > There is also an htmlized version available at:
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-ace-cmpv2-coap-transport-07
> >
> > A diff from the previous version is available at:
> >
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-cmpv2-coap-transport-07
> >
> >
> > Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
> >
> >
> > ___________
> > Ace mailing list
> > Ace@ietf.org
> > https://www.ietf.org/mailman/listinfo/ace
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] draft-ietf-ace-oscore-gm-admin split

[Daniel Migault]

Hi,

To avoid delaying the publication of the work by waiting
draft-ietf-core-coral, there has been a consensus within the WG
that draft-ietf-ace-oscore-gm-admin will be split into:
– Doc 1: current document minus the CoRAL-related content (use, special
features, examples , …)
– Doc 2: new WG document, with revised CoRAL-related content taken out of
this ACE document

Unless someone opposes the split, we will create a new WG document for doc
2 when it will be ready. The current plan is to have the WG document
created shortly after -oscore-gm-admin is in WGLC and stay dormant until it
is being re-activated.

If you oppose to such plan, please indicate it by February 6.

Yours,
Daniel

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE interim meeting: 2023-01-23 14:00 UTC.

[Daniel Migault]

That is great!

Yours,
Daniel


From: Ace  on behalf of Marco Tiloca 

Sent: Friday, January 20, 2023 3:40 AM
To: Daniel Migault; Ace Wg
Subject: Re: [Ace] ACE interim meeting: 2023-01-23 14:00 UTC.

Hello Daniel and all,

As time did not allow at the previous interim meeting, I would like to present 
the current status and next steps for draft-ietf-ace-oscore-gm-admin [1].

Best,
/Marco

[1] https://datatracker.ietf.org/doc/draft-ietf-ace-oscore-gm-admin/

On 2023-01-18 04:15, Daniel Migault wrote:
Hi,

This is just a reminder of our next interim meeting. If you would like to 
present feel free to let the WG know.

Yours,
Logan and Daniel

On Wed, Jan 4, 2023 at 9:13 PM Daniel Migault 
mailto:mglt.i...@gmail.com>> wrote:
Hi,

This is just a reminder that we have an ACE interim meeting this month on 
2023-01-23 14:00 UTC.

Meeting informations are available here:
https://datatracker.ietf.org/meeting/interim-2023-ace-01/session/ace<https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-891cf2739e97d2dc&q=1&e=d92153c4-8a5c-41e9-bb04-4fe62a0331b8&u=https%3A%2F%2Feur05.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdatatracker.ietf.org%252Fmeeting%252Finterim-2023-ace-01%252Fsession%252Face%26data%3D05%257C01%257Cmarco.tiloca%2540ri.se%257C6441d2e309f44a40a21208daf9025cc8%257C5a9809cf0bcb413a838a09ecc40cc9e8%257C0%257C0%257C638096085940054832%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C2000%257C%257C%257C%26sdata%3D0VKtEbtlcEMYrW7weIi1kiOKtvBj2XdwgmZ7LS%252Fo9qk%253D%26reserved%3D0>

Current documents we expect to make progress and discuss are:
1. -pubsub-profile
2. -revoked-token-notification
3. -oscore-gm-admin
4. -edhoc-oscore-profile (first presentation)
5. (key-groupcomm-oscore) if not already shipped to the IESG.

Yours,
Logan and Daniel

--
Daniel Migault
Ericsson


--
Daniel Migault
Ericsson



___
Ace mailing list
Ace@ietf.org<mailto:Ace@ietf.org>
https://www.ietf.org/mailman/listinfo/ace



--
Marco Tiloca
Ph.D., Senior Researcher

Phone: +46 (0)70 60 46 501

RISE Research Institutes of Sweden AB
Box 1263
164 29 Kista (Sweden)

Division: Digital Systems
Department: Computer Science
Unit: Cybersecurity

https://www.ri.se<https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-3d296ae5721cac2b&q=1&e=d92153c4-8a5c-41e9-bb04-4fe62a0331b8&u=https%3A%2F%2Fwww.ri.se%2F>

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE interim meeting: 2023-01-23 14:00 UTC.

[Daniel Migault]

Hi,

This is just a reminder of our next interim meeting. If you would like to
present feel free to let the WG know.

Yours,
Logan and Daniel

On Wed, Jan 4, 2023 at 9:13 PM Daniel Migault  wrote:

> Hi,
>
> This is just a reminder that we have an ACE interim meeting this month on
> 2023-01-23 14:00 UTC.
>
> Meeting informations are available here:
> https://datatracker.ietf.org/meeting/interim-2023-ace-01/session/ace
>
> Current documents we expect to make progress and discuss are:
> 1. -pubsub-profile
> 2. -revoked-token-notification
> 3. -oscore-gm-admin
> 4. -edhoc-oscore-profile (first presentation)
> 5. (key-groupcomm-oscore) if not already shipped to the IESG.
>
> Yours,
> Logan and Daniel
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04

[Daniel Migault]

Great!

Yours,
Daniel

On Mon, Jan 16, 2023 at 9:59 AM Paul Wouters  wrote:

>
> On Mon, Jan 16, 2023 at 9:46 AM Daniel Migault 
> wrote:
>
>> We had a reviview from the Security Directorate and the
>> General Directorate. What I think you are saying is that there are some
>> updates to be done to address the Security Directorate comments. If so, yes
>> Mohit, please update the document accordingly and respond to Valery. If you
>> can do that today that would be great.
>> I do not see this as a serious issue, and unless there are other issues,
>> maybe Paul can try to push the draft to the IESG ?
>>
>
> Sorry about dropping the ball on this one. Yes, it was waiting on
> resolving Valery's comments in the secdir mail exchange:
> https://mailarchive.ietf.org/arch/msg/ace/IcJbf2stWcktjIoepyxT0ePq_pI/
>
> If we can get a document update for that, we can move it onwards.
>
> Paul
>
>
>
>> Yours,
>> Daniel
>>
>>
>> On Mon, Jan 16, 2023 at 8:16 AM Brockhaus, Hendrik <
>> hendrik.brockh...@siemens.com> wrote:
>>
>>> If I am correct, the SecDir review is not complete.
>>> https://mailarchive.ietf.org/arch/msg/secdir/vZJDmEsWxvhKcjGVOOTj8QnZ3ns/
>>>
>>> Hendrik
>>>
>>> > -Ursprüngliche Nachricht-
>>> > Von: Daniel Migault 
>>> > Gesendet: Montag, 16. Januar 2023 14:02
>>> > An: Brockhaus, Hendrik (T CST SEA-DE) ;
>>> > Mohit Sahni 
>>> > Cc: draft-ietf-ace-cmpv2-coap-transport@ietf.org; ace@ietf.org;
>>> > paul.wout...@aiven.io; Benjamin Kaduk ; Fries, Steffen
>>> (T
>>> > CST) ; von Oheimb, David (T CST SEA-DE)
>>> > ; Saurabh Tripathi
>>> > 
>>> > Betreff: Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04
>>> >
>>> > Hi,
>>> >
>>> > From my perspective it is in the hands of our ADs. Can you please
>>> clarify the
>>> > status as well as if there is anything we are expected to do.
>>> >
>>> > In the history I can see:
>>> > 2022-10-12 05   Paul WoutersIESG state changed to Last Call
>>> Requested from
>>> > AD Evaluation
>>> >
>>> > So I suppose, this is pretty much baked. The last note is the
>>> following one:
>>> >
>>> > 2022-10-27 05   (System)IESG state changed to Waiting for
>>> Writeup from In
>>> > Last Call
>>> >
>>> > We I interpret as considering the comments received from the LC.
>>> >
>>> > Yours,
>>> > Daniel
>>> >
>>> > 
>>> > From: Brockhaus, Hendrik 
>>> > Sent: Monday, January 16, 2023 7:49 AM
>>> > To: Mohit Sahni; Daniel Migault
>>> > Cc: draft-ietf-ace-cmpv2-coap-transport@ietf.org; ace@ietf.org;
>>> > paul.wout...@aiven.io; Benjamin Kaduk; Fries, Steffen; von Oheimb,
>>> David;
>>> > Saurabh Tripathi
>>> > Subject: AW: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04
>>> >
>>> > Mohit, Daniel
>>> >
>>> > In the meantime, the Lightweight CMP Profile passed the IESG review
>>> and is on
>>> > its way for publication.
>>> > Also, the BRSKI-AE draft is in the last review rounds.
>>> > Both drafts and also CMP Algorithms and CMP Updates require
>>> publication of
>>> > CMPoverCoAP.
>>> > What is the status of this draft and when do you think it it is ready
>>> for
>>> > publication?
>>> >
>>> > Hendrik
>>> >
>>> > > > Von: Ace  Im Auftrag von Mohit Sahni
>>> > > >
>>> > > > Hi Ben and Hello Paul,
>>> > > > I have published a new version for the draft that incorporates
>>> Ben's
>>> > > > Comments, I am sorry for the long delay that happened due to some
>>> > > > personal reasons. I want to thank Hendrik for his help and support
>>> in
>>> > > > resolving these comments.
>>> > > >
>>> > > > In summary, I have accepted all the comments suggested by Ben
>>> except this
>>> > > > one:
>>> > > [...]
>>>
>>
>>
>> --
>> Daniel Migault
>> Ericsson
>>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04

[Daniel Migault]

We had a reviview from the Security Directorate and the
General Directorate. What I think you are saying is that there are some
updates to be done to address the Security Directorate comments. If so, yes
Mohit, please update the document accordingly and respond to Valery. If you
can do that today that would be great.
I do not see this as a serious issue, and unless there are other issues,
maybe Paul can try to push the draft to the IESG ?

Yours,
Daniel


On Mon, Jan 16, 2023 at 8:16 AM Brockhaus, Hendrik <
hendrik.brockh...@siemens.com> wrote:

> If I am correct, the SecDir review is not complete.
> https://mailarchive.ietf.org/arch/msg/secdir/vZJDmEsWxvhKcjGVOOTj8QnZ3ns/
>
> Hendrik
>
> > -Ursprüngliche Nachricht-----
> > Von: Daniel Migault 
> > Gesendet: Montag, 16. Januar 2023 14:02
> > An: Brockhaus, Hendrik (T CST SEA-DE) ;
> > Mohit Sahni 
> > Cc: draft-ietf-ace-cmpv2-coap-transport@ietf.org; ace@ietf.org;
> > paul.wout...@aiven.io; Benjamin Kaduk ; Fries, Steffen (T
> > CST) ; von Oheimb, David (T CST SEA-DE)
> > ; Saurabh Tripathi
> > 
> > Betreff: Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04
> >
> > Hi,
> >
> > From my perspective it is in the hands of our ADs. Can you please
> clarify the
> > status as well as if there is anything we are expected to do.
> >
> > In the history I can see:
> > 2022-10-12 05   Paul WoutersIESG state changed to Last Call
> Requested from
> > AD Evaluation
> >
> > So I suppose, this is pretty much baked. The last note is the following
> one:
> >
> > 2022-10-27 05   (System)IESG state changed to Waiting for
> Writeup from In
> > Last Call
> >
> > We I interpret as considering the comments received from the LC.
> >
> > Yours,
> > Daniel
> >
> > 
> > From: Brockhaus, Hendrik 
> > Sent: Monday, January 16, 2023 7:49 AM
> > To: Mohit Sahni; Daniel Migault
> > Cc: draft-ietf-ace-cmpv2-coap-transport@ietf.org; ace@ietf.org;
> > paul.wout...@aiven.io; Benjamin Kaduk; Fries, Steffen; von Oheimb,
> David;
> > Saurabh Tripathi
> > Subject: AW: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04
> >
> > Mohit, Daniel
> >
> > In the meantime, the Lightweight CMP Profile passed the IESG review and
> is on
> > its way for publication.
> > Also, the BRSKI-AE draft is in the last review rounds.
> > Both drafts and also CMP Algorithms and CMP Updates require publication
> of
> > CMPoverCoAP.
> > What is the status of this draft and when do you think it it is ready for
> > publication?
> >
> > Hendrik
> >
> > > > Von: Ace  Im Auftrag von Mohit Sahni
> > > >
> > > > Hi Ben and Hello Paul,
> > > > I have published a new version for the draft that incorporates Ben's
> > > > Comments, I am sorry for the long delay that happened due to some
> > > > personal reasons. I want to thank Hendrik for his help and support in
> > > > resolving these comments.
> > > >
> > > > In summary, I have accepted all the comments suggested by Ben except
> this
> > > > one:
> > > [...]
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04

[Daniel Migault]

Hi,

>From my perspective it is in the hands of our ADs. Can you please clarify the 
>status as well as if there is anything we are expected to do.

In the history I can see:
2022-10-12 05   Paul WoutersIESG state changed to Last Call Requested from 
AD Evaluation

So I suppose, this is pretty much baked. The last note is the following one:

2022-10-27 05   (System)IESG state changed to Waiting for Writeup from 
In Last Call

We I interpret as considering the comments received from the LC.

Yours,
Daniel


From: Brockhaus, Hendrik 
Sent: Monday, January 16, 2023 7:49 AM
To: Mohit Sahni; Daniel Migault
Cc: draft-ietf-ace-cmpv2-coap-transport@ietf.org; ace@ietf.org; 
paul.wout...@aiven.io; Benjamin Kaduk; Fries, Steffen; von Oheimb, David; 
Saurabh Tripathi
Subject: AW: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04

Mohit, Daniel

In the meantime, the Lightweight CMP Profile passed the IESG review and is on 
its way for publication.
Also, the BRSKI-AE draft is in the last review rounds.
Both drafts and also CMP Algorithms and CMP Updates require publication of 
CMPoverCoAP.
What is the status of this draft and when do you think it it is ready for 
publication?

Hendrik

> > Von: Ace  Im Auftrag von Mohit Sahni
> >
> > Hi Ben and Hello Paul,
> > I have published a new version for the draft that incorporates Ben's
> > Comments, I am sorry for the long delay that happened due to some
> > personal reasons. I want to thank Hendrik for his help and support in
> > resolving these comments.
> >
> > In summary, I have accepted all the comments suggested by Ben except this
> > one:
> [...]

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Fw: ACE WG wiki migration

[Daniel Migault]

To wiki users, 

Please have a look at the wiki  and let Liz know if you see anything missing. 

https://wiki.ietf.org/group/ace



Yours, 
Daniel

From: Liz Flynn 
Sent: Wednesday, January 11, 2023 8:18 PM
To: ace-cha...@ietf.org
Subject: ACE WG wiki migration

Hi ACE WG chairs!

As you have probably seen, we are transitioning community wiki content to 
wiki.ietf.org and decommissioning Trac-based wikis.

As part of that, we’ve undertaken an initial move of ACE's wiki to:

https://wiki.ietf.org/group/ace

from:

https://trac.ietf.org/trac/ace/wiki

Please take a moment to review this content to see if anything is missing on 
wiki.ietf.org, and let me know if it's ready to go or if it needs more work.

The current plan is to decommission all Trac based wikis before March 2023. An 
archive of all Trac wikis will be retained, though it will not be 
Web-accessible.


Let me know if you have any questions or concerns!

Thanks,

Liz
IETF Secretariat

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] ACE interim meeting: 2023-01-23 14:00 UTC.

[Daniel Migault]

Hi,

This is just a reminder that we have an ACE interim meeting this month on
2023-01-23 14:00 UTC.

Meeting informations are available here:
https://datatracker.ietf.org/meeting/interim-2023-ace-01/session/ace

Current documents we expect to make progress and discuss are:
1. -pubsub-profile
2. -revoked-token-notification
3. -oscore-gm-admin
4. -edhoc-oscore-profile (first presentation)
5. (key-groupcomm-oscore) if not already shipped to the IESG.

Yours,
Logan and Daniel

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] interim-2022-ace-02 interim approved

[Daniel Migault]

Hi,

We have an interim meeting planned on:
Monday 2022-12-19 09:00 EST (14:00 UTC)

To join the meeting:
https://ws.conf.meetecho.com/conference/?short=5e0b91f9-04ca-40e7-b67a-62d7361adcc2

Please find the draft agenda below, Feel free to let us know if you have a
specific item to present.
https://notes.ietf.org/notes-ietf-interim-2022-ace-02-ace

Current documents we expect to be discussed are:
1. -pubsub-profile
2. -revoked-token-notification
3. -oscore-gm-admin
4. -edhoc-oscore-profile

Please upload your presentation to:
https://datatracker.ietf.org/meeting/interim-2022-ace-02/session/ace

We also look for a minute taker, anyone volunteering is appreciated

Yours,
Daniel



On Fri, Dec 2, 2022 at 10:21 PM IETF Meeting Session Request Tool <
session-requ...@ietf.org> wrote:

>
> An interim meeting for ace has been approved or does not require
> additional approval.
> A message has been sent to the secretariat requesting the interim be
> announced.
>
>
> -
> Working Group Name: Authentication and Authorization for Constrained
> Environments
> Area Name: Security Area
> Session Requester: Daniel Migault
>
> City: Montreal
> Country: CA
>
>
> Session 1:
>
> Date: 2022-12-19
> Start Time: 09:00 America/New_York
> Duration: 01:00
> Remote Participation Information:
> Agenda Note:
>
> -
>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Meeting in Yokhohama ?

[Daniel Migault]

Hi,

We would like to consider meeting in the IETF 116 in Yokohama. To confirm
the meeting request, we would like to get an idea of:
1-  who is planning to attend the session remotely or face to face as well
as
2 - what should be discussed that cannot be discussed during interim
meetings

Yours,
Daniel



-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Ace interim meeting December - March

[Daniel Migault]

Hi,

We are planning to have the following interim meeting to ensure the
documents move forward and these are potential time slots we foresee.
Please let us know if there are any concerns.

1) Monday 19 December - 9:00 UTC/GMT -5 hours
2) Monday 23 January - 9:00 UTC/GMT -5 hours
3) Monday 20 February - 9:00 UTC/GMT -5 hours
4) Monday 20 March - 9:00 UTC/GMT -5 hours

Yours,
Daniel

WG doc
-revoked-token-notification - WGLC last call January ?
-oscore-gm-admin - WGLC February ?
-edhoc-oscore-profile - WGLC January ?
-pubsub-profile - WGLC January ?

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] Call for adoption: draft-selander-ace-edhoc-oscore-profile-00

[Daniel Migault]

Thanks Malisa, We do have some support, none opposed, I guess we can close
the call for adoption.
Authors, please upload the draft as a WG document.

Yours,
Daniel

On Thu, Nov 10, 2022 at 12:43 PM Mališa Vučinić 
wrote:

> Hello ACE,
>
> I have previously implemented the OSCORE profile for ACE in the
> OpenWSN-6TiSCH environment and find this document a natural extension to
> it. I think that this document is already in a very good shape for this
> stage. I therefore support it being adopted and further improved in ACE.
>
> Mališa
>
> On Sep 12, 2022, at 16:26, Daniel Migault  wrote:
>
> Hi,
>
> This work stats a Call for adoption of the following document:
> Ephemeral Diffie-Hellman Over COSE (EDHOC) and Object Security for
> Constrained Environments (OSCORE) Profile for Authentication and
> Authorization for Constrained Environments (ACE) [1].
>
> Please indicate if you support or not the adoption of the document by
> September 26.
>
> Yours,
> Logan and Daniel
>
> [1]
> https://datatracker.ietf.org/doc/draft-selander-ace-edhoc-oscore-profile/
> --
> Daniel Migault
> Ericsson
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>
>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-extend-dtls-authorize-03.txt

[Daniel Migault]

Many thanks Olaf! The draft has sent to the IESG now.

Yours,
Daniel

On Wed, Sep 21, 2022 at 7:35 AM Olaf Bergmann  wrote:

> Hi Daniel,
>
> On 2022-09-19, Daniel Migault  wrote:
>
> > You are correct, it might be clearer to keep it.
>
> Thanks. I have now submitted -04 that removes the reference to RFC
> 9202 from the abstract.
>
> Grüße
> Olaf
>
> > On Mon, Sep 19, 2022 at 10:29 AM Olaf Bergmann  wrote:
> >
> >  Hi Daniel,
> >
> >  Thanks for pushing this document forward.
> >
> >  On 2022-09-16, Daniel Migault  wrote:
> >
> >  > There two nits to address before the draft can be moved forward .
> >  >
> >  >   ** The abstract seems to contain references ([RFC9202]), which it
> >  >  shouldn't.  Please replace those with straight textual mentions
> of the
> >  >  documents in question.
> >
> >  Okay, I will fix this.
> >
> >  >  ** Obsolete normative reference: RFC 6347 (Obsoleted by RFC 9147)
> >
> >  The full text reads:
> >
> > [RFC9202] only specifies the use of DTLS [RFC6347] [RFC9147] but
> > works equally well for TLS [RFC8446].
> >
> >  The reference to DTLS version 1.2 is explicitly included because RFC
> >  9202 specifies the use of DTLS version 1.2 (and mentions that DTLS
> >  version 1.3 can be used instead).
> >
> >  I am happy to delete the reference to DTLS 1.2 but I am wondering if
> >  this could lead to confusion?
> >
> >  Grüße
> >  Olaf
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Publication has been requested for draft-ietf-ace-extend-dtls-authorize-04

[Daniel Migault via Datatracker]

Daniel Migault has requested publication of 
draft-ietf-ace-extend-dtls-authorize-04 as Proposed Standard on behalf of the 
ACE working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] AD review of draft-ietf-ace-cmpv2-coap-transport-04

[Daniel Migault]

Thanks Mohit, that is well appreciated.
Yours,
Daniel

On Mon, Sep 19, 2022 at 11:25 AM Brockhaus, Hendrik <
hendrik.brockh...@siemens.com> wrote:

> Mohit
>
> Thank you very much for performing all these updates.
>
> Hendrik
>
> > Von: Ace  Im Auftrag von Mohit Sahni
> >
> > Hi Ben and Hello Paul,
> > I have published a new version for the draft that incorporates Ben's
> > Comments, I am sorry for the long delay that happened due to some
> > personal reasons. I want to thank Hendrik for his help and support in
> > resolving these comments.
> >
> > In summary, I have accepted all the comments suggested by Ben except this
> > one:
> [...]
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-extend-dtls-authorize-03.txt

[Daniel Migault]

You are correct, it might be clearer to keep it.

Yours,
Daniel

On Mon, Sep 19, 2022 at 10:29 AM Olaf Bergmann  wrote:

> Hi Daniel,
>
> Thanks for pushing this document forward.
>
> On 2022-09-16, Daniel Migault  wrote:
>
> > There two nits to address before the draft can be moved forward .
> >
> >   ** The abstract seems to contain references ([RFC9202]), which it
> >  shouldn't.  Please replace those with straight textual mentions of
> the
> >  documents in question.
>
> Okay, I will fix this.
>
> >  ** Obsolete normative reference: RFC 6347 (Obsoleted by RFC 9147)
>
> The full text reads:
>
>[RFC9202] only specifies the use of DTLS [RFC6347] [RFC9147] but
>works equally well for TLS [RFC8446].
>
> The reference to DTLS version 1.2 is explicitly included because RFC
> 9202 specifies the use of DTLS version 1.2 (and mentions that DTLS
> version 1.3 can be used instead).
>
> I am happy to delete the reference to DTLS 1.2 but I am wondering if
> this could lead to confusion?
>
> Grüße
> Olaf
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-extend-dtls-authorize-03.txt

[Daniel Migault]

Hi all,

Please find the shepherd write-up. Feel free to provide any comments before
we move the document forward.
https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/shepherdwriteup/
Yours,
Daniel

On Fri, Sep 16, 2022 at 12:05 PM Daniel Migault  wrote:

> Hi Olaf,
>
> There two nits to address before the draft can be moved forward .
>
>   ** The abstract seems to contain references ([RFC9202]), which it
>  shouldn't.  Please replace those with straight textual mentions of the
>  documents in question.
>  ** Obsolete normative reference: RFC 6347 (Obsoleted by RFC 9147)
>
> Yours,
> Daniel
>
>
> On Fri, Sep 2, 2022 at 5:33 AM Olaf Bergmann  wrote:
>
>> Dear all,
>>
>> to celebrate the publication of this WG's recent RFCs, I have
>> updated the references to the ACE OAuth framework and profiles in
>> the ace-extend-dtls document.
>>
>> Another small change is referencing RFC9147 in alignment with the
>> finalized wording of RFC9202.
>>
>> Grüße
>> Olaf
>>
>>
>> On 2022-09-02, internet-dra...@ietf.org wrote:
>>
>> > A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> > This draft is a work item of the Authentication and Authorization for
>> Constrained Environments WG of the IETF.
>> >
>> > Title   : Extension of the CoAP-DTLS Profile for ACE to
>> TLS
>> > Authors : Olaf Bergmann
>> >   John Preuß Mattsson
>> >   Göran Selander
>> >   Filename: draft-ietf-ace-extend-dtls-authorize-03.txt
>> >   Pages   : 6
>> >   Date: 2022-09-02
>> >
>> > Abstract:
>> >This document updates the CoAP-DTLS profile for ACE [RFC9202] by
>> >specifying that the profile applies to TLS as well as DTLS.
>> >
>> > Discussion Venues
>> >
>> >This note is to be removed before publishing as an RFC.
>> >
>> >Discussion of this document takes place on the Authentication and
>> >Authorization for Constrained Environments Working Group mailing list
>> >(ace@ietf.org), which is archived at
>> >https://mailarchive.ietf.org/arch/browse/ace/.
>> >
>> >Source for this draft and an issue tracker can be found at
>> >https://github.com/ace-wg/ace-extend-dtls-authorize.
>> >
>> >
>> > The IETF datatracker status page for this draft is:
>> > https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/
>> >
>> > There is also an HTML version available at:
>> >
>> https://www.ietf.org/archive/id/draft-ietf-ace-extend-dtls-authorize-03.html
>> >
>> > A diff from the previous version is available at:
>> >
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-extend-dtls-authorize-03
>> >
>> >
>> > Internet-Drafts are also available by rsync at rsync.ietf.org:
>> :internet-drafts
>> >
>> >
>> > ___
>> > Ace mailing list
>> > Ace@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ace
>>
>> ___
>> Ace mailing list
>> Ace@ietf.org
>> https://www.ietf.org/mailman/listinfo/ace
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-extend-dtls-authorize-03.txt

[Daniel Migault]

Hi Olaf,

There two nits to address before the draft can be moved forward .

  ** The abstract seems to contain references ([RFC9202]), which it
 shouldn't.  Please replace those with straight textual mentions of the
 documents in question.
 ** Obsolete normative reference: RFC 6347 (Obsoleted by RFC 9147)

Yours,
Daniel


On Fri, Sep 2, 2022 at 5:33 AM Olaf Bergmann  wrote:

> Dear all,
>
> to celebrate the publication of this WG's recent RFCs, I have
> updated the references to the ACE OAuth framework and profiles in
> the ace-extend-dtls document.
>
> Another small change is referencing RFC9147 in alignment with the
> finalized wording of RFC9202.
>
> Grüße
> Olaf
>
>
> On 2022-09-02, internet-dra...@ietf.org wrote:
>
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Authentication and Authorization for
> Constrained Environments WG of the IETF.
> >
> > Title   : Extension of the CoAP-DTLS Profile for ACE to
> TLS
> > Authors : Olaf Bergmann
> >   John Preuß Mattsson
> >   Göran Selander
> >   Filename: draft-ietf-ace-extend-dtls-authorize-03.txt
> >   Pages   : 6
> >   Date: 2022-09-02
> >
> > Abstract:
> >This document updates the CoAP-DTLS profile for ACE [RFC9202] by
> >specifying that the profile applies to TLS as well as DTLS.
> >
> > Discussion Venues
> >
> >This note is to be removed before publishing as an RFC.
> >
> >Discussion of this document takes place on the Authentication and
> >Authorization for Constrained Environments Working Group mailing list
> >(ace@ietf.org), which is archived at
> >https://mailarchive.ietf.org/arch/browse/ace/.
> >
> >Source for this draft and an issue tracker can be found at
> >https://github.com/ace-wg/ace-extend-dtls-authorize.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/
> >
> > There is also an HTML version available at:
> >
> https://www.ietf.org/archive/id/draft-ietf-ace-extend-dtls-authorize-03.html
> >
> > A diff from the previous version is available at:
> >
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-extend-dtls-authorize-03
> >
> >
> > Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
> >
> >
> > ___
> > Ace mailing list
> > Ace@ietf.org
> > https://www.ietf.org/mailman/listinfo/ace
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Call for adoption: draft-selander-ace-edhoc-oscore-profile-00

[Daniel Migault]

Hi,

This work stats a Call for adoption of the following document:
Ephemeral Diffie-Hellman Over COSE (EDHOC) and Object Security for
Constrained Environments (OSCORE) Profile for Authentication and
Authorization for Constrained Environments (ACE) [1].

Please indicate if you support or not the adoption of the document by
September 26.

Yours,
Logan and Daniel

[1]
https://datatracker.ietf.org/doc/draft-selander-ace-edhoc-oscore-profile/
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] interim-2022-ace-01 interim approved

[Daniel Migault]

Hi,

For those willing to present slides, please upload them here:
https://datatracker.ietf.org/meeting/interim-2022-ace-01/session/ace

We also need a minute taker - if one could volunteer. The current agenda
has been posted:
https://notes.ietf.org/aVNaImlCSpeHq7vht9588w?edit

Yours,
Daniel

On Thu, Sep 8, 2022 at 11:03 AM Göran Selander 
wrote:

> Hi Daniel,
>
>
>
> We would like to present the new EDHOC-OSCORE profile of ACE that was
> submitted for IETF 114:
>
>
>
>
> https://datatracker.ietf.org/doc/html/draft-selander-ace-edhoc-oscore-profile
>
>
>
> In brief, the idea is the following: Whereas in the OSCORE profile the
> access token is bound to a symmetric key used with OSCORE, in
>
> this profile the access token is bound to a public key credential used to
> authenticate with EDHOC and establish a shared symmetric key which is used
> with OSCORE.
>
>
>
> Best regards
>
> Göran
>
>
>
>
>
> *From: *Ace  on behalf of Daniel Migault <
> mglt.i...@gmail.com>
> *Date: *Thursday, 8 September 2022 at 15:13
> *To: *Ace Wg 
> *Subject: *Re: [Ace] interim-2022-ace-01 interim approved
>
> Hi,
>
>
>
> As of today, we do not have received any agenda item. Let us know by the
> end of the day if you are willing to present.
>
>
>
> As a reminder, here is  where we think we are with the various documents.
> Please take the necessary actions to ensure the documents make consequent
> progress.
>
> https://mailarchive.ietf.org/arch/msg/ace/4i2kmdJ7owsXfrhbse8UP1CSMhA/
>
>
>
> Yours,
>
> Daniel
>
>
>
>
>
> On Mon, Aug 29, 2022 at 8:57 AM Daniel Migault 
> wrote:
>
> Hi,
>
>
>
> Please find the virtual meeting information. Let us know if you are
> planning to present.
>
>
>
> Yours,
>
> Daniel
>
> -- Forwarded message -
> From: *IETF Meeting Session Request Tool* 
> Date: Mon, Aug 29, 2022 at 8:53 AM
> Subject: interim-2022-ace-01 interim approved
> To: , 
>
>
>
>
> An interim meeting for ace has been approved or does not require
> additional approval.
> A message has been sent to the secretariat requesting the interim be
> announced.
>
>
> -
> Working Group Name: Authentication and Authorization for Constrained
> Environments
> Area Name: Security Area
> Session Requester: Daniel Migault
>
> Meeting Type: Virtual Meeting
>
> Session 1:
>
> Date: 2022-09-12
> Start Time: 10:00 America/New_York
> Duration: 01:00
> Remote Participation Information:
> https://meetings.conf.meetecho.com/interim/?short=24c81a1f-7240-4990-a8ae-8b46a94e8b1b
> <https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-59f1d5873c51c981&q=1&e=1cb785a7-7540-4fb6-b067-10b011a865d3&u=https%3A%2F%2Fmeetings.conf.meetecho.com%2Finterim%2F%3Fshort%3D24c81a1f-7240-4990-a8ae-8b46a94e8b1b>
> Agenda Note:
>
> -
>
>
>
>
> --
>
> Daniel Migault
>
> Ericsson
>
>
>
>
> --
>
> Daniel Migault
>
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] interim-2022-ace-01 interim approved

[Daniel Migault]

Hi, 

Thank for the reply. Just to clarify the meeting is on Monday. If you believe 
that some of the issues need to be discussed feel free to take your time during 
the meeting. I think that providing a head-up to the wg on the mailing list on 
what issues you would like input on might be helpful so people can be prepared 
and actually provide the feed back - during the meeting or on the mailing list.

Yours, 
Daniel


From: Ace  on behalf of Cigdem Sengul 

Sent: Thursday, September 8, 2022 10:07 AM
To: Daniel Migault
Cc: Ace Wg
Subject: Re: [Ace] interim-2022-ace-01 interim approved


Hello Daniel,
I can give a verbal update on pub-sub without slides tomorrow but in short I am 
revising the document to align with the latest key-groupcomm and with the goal 
of closing as many issues as possible. There are some open points about the 
cose object which are documented in the wg emails reviewing the document and on 
github issues.

I will submit a new version soon but some todos will remain in the document, 
which will need to be resolved with Francesca and I am not knowledgeable about 
some earlier design decisions.
Kind regards,




On Thu, 8 Sep 2022 at 14:08, Daniel Migault 
mailto:mglt.i...@gmail.com>> wrote:
Hi,

As of today, we do not have received any agenda item. Let us know by the end of 
the day if you are willing to present.

As a reminder, here is  where we think we are with the various documents. 
Please take the necessary actions to ensure the documents make consequent 
progress.
https://mailarchive.ietf.org/arch/msg/ace/4i2kmdJ7owsXfrhbse8UP1CSMhA/

Yours,
Daniel


On Mon, Aug 29, 2022 at 8:57 AM Daniel Migault 
mailto:mglt.i...@gmail.com>> wrote:
Hi,

Please find the virtual meeting information. Let us know if you are planning to 
present.

Yours,
Daniel

-- Forwarded message -
From: IETF Meeting Session Request Tool 
mailto:session-requ...@ietf.org>>
Date: Mon, Aug 29, 2022 at 8:53 AM
Subject: interim-2022-ace-01 interim approved
To: mailto:ace-cha...@ietf.org>>, 
mailto:mglt.i...@gmail.com>>



An interim meeting for ace has been approved or does not require additional 
approval.
A message has been sent to the secretariat requesting the interim be announced.


-
Working Group Name: Authentication and Authorization for Constrained 
Environments
Area Name: Security Area
Session Requester: Daniel Migault

Meeting Type: Virtual Meeting

Session 1:

Date: 2022-09-12
Start Time: 10:00 America/New_York
Duration: 01:00
Remote Participation Information: 
https://meetings.conf.meetecho.com/interim/?short=24c81a1f-7240-4990-a8ae-8b46a94e8b1b<https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-59f1d5873c51c981&q=1&e=e4039ce7-0f58-45fd-b7b5-b7219c7317ce&u=https%3A%2F%2Fmeetings.conf.meetecho.com%2Finterim%2F%3Fshort%3D24c81a1f-7240-4990-a8ae-8b46a94e8b1b>
Agenda Note:

-------------



--
Daniel Migault
Ericsson


--
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org<mailto:Ace@ietf.org>
https://www.ietf.org/mailman/listinfo/ace
--
Dr Cigdem Sengul
Reader
ACM-W Communications Co-Chair
E cigdem.sen...@brunel.ac.uk<mailto:cigdem.sen...@brunel.ac.uk>
Brunel University London
Dept of Computer Science
Brunel University London, Uxbridge, UB8 3PH, United Kingdom
T +44(0)1895 274000
www.brunel.ac.uk<http://www.brunel.ac.uk/>


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] interim-2022-ace-01 interim approved

[Daniel Migault]

Hi,

As of today, we do not have received any agenda item. Let us know by the
end of the day if you are willing to present.

As a reminder, here is  where we think we are with the various documents.
Please take the necessary actions to ensure the documents make consequent
progress.
https://mailarchive.ietf.org/arch/msg/ace/4i2kmdJ7owsXfrhbse8UP1CSMhA/

Yours,
Daniel


On Mon, Aug 29, 2022 at 8:57 AM Daniel Migault  wrote:

> Hi,
>
> Please find the virtual meeting information. Let us know if you are
> planning to present.
>
> Yours,
> Daniel
>
> -- Forwarded message -
> From: IETF Meeting Session Request Tool 
> Date: Mon, Aug 29, 2022 at 8:53 AM
> Subject: interim-2022-ace-01 interim approved
> To: , 
>
>
>
> An interim meeting for ace has been approved or does not require
> additional approval.
> A message has been sent to the secretariat requesting the interim be
> announced.
>
>
> -
> Working Group Name: Authentication and Authorization for Constrained
> Environments
> Area Name: Security Area
> Session Requester: Daniel Migault
>
> Meeting Type: Virtual Meeting
>
> Session 1:
>
> Date: 2022-09-12
> Start Time: 10:00 America/New_York
> Duration: 01:00
> Remote Participation Information:
> https://meetings.conf.meetecho.com/interim/?short=24c81a1f-7240-4990-a8ae-8b46a94e8b1b
> Agenda Note:
>
> -
>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] new ACE rfcs!

[Daniel Migault]

Hi all, 

The chairs would like to congratulate the authors for their these new rfcs 9200 
- 9201 - 9202 - 9003 and 9237! 

Please check the WG status so many of the document currently on hold can 
progress!

Yours, 
Daniel 

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Fwd: interim-2022-ace-01 interim approved

[Daniel Migault]

Hi,

Please find the virtual meeting information. Let us know if you are
planning to present.

Yours,
Daniel

-- Forwarded message -
From: IETF Meeting Session Request Tool 
Date: Mon, Aug 29, 2022 at 8:53 AM
Subject: interim-2022-ace-01 interim approved
To: , 



An interim meeting for ace has been approved or does not require additional
approval.
A message has been sent to the secretariat requesting the interim be
announced.


-
Working Group Name: Authentication and Authorization for Constrained
Environments
Area Name: Security Area
Session Requester: Daniel Migault

Meeting Type: Virtual Meeting

Session 1:

Date: 2022-09-12
Start Time: 10:00 America/New_York
Duration: 01:00
Remote Participation Information:
https://meetings.conf.meetecho.com/interim/?short=24c81a1f-7240-4990-a8ae-8b46a94e8b1b
Agenda Note:

-



-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] Planned updates to draft-ace-key-groupcomm

[Daniel Migault]

Thanks for the very details - please ship it! To the WG, please state your 
opinion by the end of August.

Yours,
Daniel


From: Ace  on behalf of Marco Tiloca 

Sent: Friday, July 29, 2022 12:20 PM
To: ace@ietf.org
Subject: [Ace] Planned updates to draft-ace-key-groupcomm

Hello ACE,

Following some discussions in the past months, I was planning to make
two non-invasive changes to draft-ace-key-groupcomm-15 [ACE-KG], which
is currently in AD Review.

After giving a heads-up to Daniel and Paul at IETF 114, this mail is to
check with the Working Group if there are objections to make the changes.

---

UPDATE 1

Following IETF 113, there was a proposal from Christian about updating
Section 7 "Extended Scope Format" of [ACE-KG]. The defined approach is
optional to use, it signals the semantics of a binary encoded "scope"
claim of an access token, and is referred to in the documents
[ACE-KGO][ACE-ADMIN].

The result of the change, also proposed in [GH-ISSUE], would be a
simpler and more efficient signaling of the scope semantics. In turn, it
automatically takes advantage of the work done in CBOR at [CBOR-FM].

Question: is there any objection to update Section 7 of [ACE-KG], based
on the proposal at [GH-ISSUE]?

---

UPDATE 2

At IETF 113, it was discussed that the "scope" claim of a same access
token could specify, at the same time, both: i) scope entries related to
roles of members in an OSCORE group, as per [ACE-KGO]; and ii) scope
entries related to admin permissions for Administrators of OSCORE groups
as per [ACE-ADMIN].

Following that discussion and in order to make things simpler, a single
AIF data model "AIF-OSCORE-GROUPCOMM" is now defined in Section 3 of
[ACE-KGO]. This still builds on the general requirements from Section
3.1 of [ACE-KG], and primarily serves what is specified in [ACE-KGO].

Then, the same AIF data model is extended in Section 3 of [ACE-ADMIN] to
serve what is specified therein. That is, in each Administrator scope
entry , Toid indicates a pattern of group names, while
Tperm indicates admin permissions on groups whose name matches the
pattern. In particular, Toid can be: i) the CBOR Simple Value "true"
used as wildcard, also part of a suggestion from Ben at IETF 113
[ACE-113]; ii) a CBOR text string specifying a literal group name; iii)
a tagged CBOR item specifying a complex pattern of group names, with the
CBOR tag indicating the pattern semantics (e.g., a regular expression
provided by a text string).

With the above background in mind, the small update for [ACE-KG] would
be in its Section 3.1, about having consistent general requirements when
using AIF. The requirements are currently mandating "Toid" to always be
a CBOR text string, while in fact "Toid" is only _often_ a CBOR text
string (also highlighted by Ben at IETF 113 [ACE-113]). The change can
simply mandate the use of exactly a CBOR text string only for scope
entries related to group members, i.e.:

OLD:
If the AIF format is used, each scope entry is encoded as specified in
[I-D.ietf-ace-aif]. The object identifier "Toid" corresponds to the
group name and MUST be encoded as a CBOR text string. The permission set
"Tperm" indicates the roles that the Client wishes to take in the group.

NEW:
If the AIF format is used, each scope entry is encoded as per
[I-D.ietf-ace-aif], according to the used AIF specific data model. If a
scope entry expresses a set of roles to take in a group as per this
document, the object identifier "Toid" specifies the group name and MUST
be encoded as a CBOR text string, while the permission set "Tperm"
specifies the roles that the Client wishes to take in the group.

Question: is there any objection to update Section 3.1 of [ACE-KG] as above?

---

Reminder: there are also some minor, editorial changes that are pending,
as already mentioned at point 1 of [MAIL] and during the IETF 113
presentation of [KGO]. These updates are about consistently aligning
terminology and parameter names, as triggered by the WGLC review of
[ACE-KGO] at [REVIEW] and by the latest updates to the CoRE document
[GROUP-OSCORE].

I can certainly process these small pending changes together with the
two main ones above.


Thanks,
/Marco


[ACE-KG]
https://datatracker.ietf.org/doc/html/draft-ietf-ace-key-groupcomm-15

[ACE-KGO]
https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm-oscore/

[ACE-ADMIN] https://datatracker.ietf.org/doc/draft-ietf-ace-oscore-gm-admin/

[GH-ISSUE] 
https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-a993cf57d4eb0424&q=1&e=f7c78eb1-ef42-4a78-b159-4fd24b9b965e&u=https%3A%2F%2Fgithub.com%2Face-wg%2Face-key-groupcomm%2Fissues%2F144

[CBOR-FM] https://datatracker.ietf.org/doc/draft-ietf-cbor-file-magic/

[ACE-113] https://notes.ietf.org/notes-ietf-113-ace?both

[MAIL]
https://mailarchive.ietf.org/arch/msg/ace/wBpceZW1qT1YYICzECnKqvdwQb8/

[REVIEW]
https://mailarchive.ietf.org/arch/msg/ace/SIB_rte0orqkvDEtTAw-1F7Cdzo/

[GROUP-OSC

Re: [Ace] I-D Action: draft-ietf-ace-key-groupcomm-oscore-14.txt

[Daniel Migault]

Hi all,

We are planning this document to be ready by the end of September. If you
have any comments regarding this document please provide them by the end of
august.

Yours,
Daniel

On Thu, Apr 28, 2022 at 11:38 AM  wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Authentication and Authorization for
> Constrained Environments WG of the IETF.
>
> Title   : Key Management for OSCORE Groups in ACE
> Authors : Marco Tiloca
>   Jiye Park
>   Francesca Palombini
> Filename: draft-ietf-ace-key-groupcomm-oscore-14.txt
> Pages   : 103
> Date: 2022-04-28
>
> Abstract:
>This document defines an application profile of the ACE framework for
>Authentication and Authorization, to request and provision keying
>material in group communication scenarios that are based on CoAP and
>are secured with Group Object Security for Constrained RESTful
>Environments (Group OSCORE).  This application profile delegates the
>authentication and authorization of Clients, that join an OSCORE
>group through a Resource Server acting as Group Manager for that
>group.  This application profile leverages protocol-specific
>transport profiles of ACE to achieve communication security, server
>authentication and proof-of-possession for a key owned by the Client
>and bound to an OAuth 2.0 Access Token.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm-oscore/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-ace-key-groupcomm-oscore-14.html
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-key-groupcomm-oscore-14
>
>
> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
>
>
> _______
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Fwd: Full list of volunteers so far

[Daniel Migault]

Hi all,

If you have not done it yet, please volunteer for the nomcom [1]. The IETF
is better if a wider range of folks help select the leadership.

Yours,
[1] https://datatracker.ietf.org/nomcom/volunteer

-- Forwarded message -
From: NomCom Chair 2022 
Date: Fri, Jul 15, 2022 at 1:53 PM
Subject: Full list of volunteers so far
To: IETF Announcement List 
Cc: 


With help from Robert Sparks of the tools team, and Ryan Cross of AMS, here
is the full list of people who have volunteered to be on NomCom. This is
both those who signed up via the link [1] and those who checked the box
when they registered for the upcoming meeting.

There are 284 volunteers, and FYI all but six qualified under at least the
"path 1" option.  I am posting the interim list because multiple people
suggested it might give others incentive to volunteer. The final call will
be issued next week, and closes next Friday. Early next week I will
announce the random seeds. Choices will be made during IETF week, and the
challenge period will then begin.

[1] https://datatracker.ietf.org/nomcom/volunteer

Plain Name,Affiliation,Qualifications
Aaron Ding,TU Delft,1
Aaron Falk,Akamai Technologies,1+2
Adam W. Montville,Center for Internet Security,1
Adnan Rashid,University of Florence,1
Afzal Ali S,Hrblock,1
Ahmed Abdelsalam,Cisco,1
Aihua Liu,Shenzhen Zhongxing Software Company Limited,1
Aijun Wang,China Telecom,1+3
Akira Tsukamoto,AIST (The National Institute of Advanced Industrial Science
and Technology Japan),1
AlbertoRodriguezNatal,Cisco,1
Alexander Clemm,Futurewei,1+3
Alissa Cooper,Cisco,1
Allison Mankin,Salesforce,1+2+3
Ameya Deshpande,NITK Surathkal,1
Andrew Campling,419 Consulting Ltd,1
Ani Arya,,1
Annajiat_Alim Rasel,Brac University,1
Anthony Nadalin,Pacific Northwest University,3
Anuj Budhiraja,Cisco,1
Ari Keranen,Ericsson,1+2+3
Barry Leiba,Futurewei Technologies,1+2+3
Behcet Sarikaya,None,1+3
Benjamin Kaduk,Akamai Technologies,1+2
Benjamin M. Schwartz,Google / Jigsaw,1+2
Benno Overeinder,NLnet Labs,1+2
Bernard Aboba,Microsoft Corporation,1+2
Bill Woodcock,Packet Clearing House,1
Bingyang Liu,Huawei,1
Bo Wu,Huawei Technologies,1
Bob Briscoe,Independent (bobbriscoe.net Ltd),1
Brian Rosen,,1+2+3
Bron Gondwana,Fastmail,1+2+3
Bruno Teixeira,,1
Cedric Westphal,Futurewei USA,1
Charles Eckel,Cisco,1+2
Cheng Li,Huawei,1+3
Chi-Yuan Chen,National Ilan University,1
Ching-Heng Ku,Taiwan Network Information Center,1
Chonggang Wang,InterDigital,1
Chris Box,BT,1+2
Chris Lemmons,Comcast,1
Christian Hopps,"LabN Consulting, LLC",1+2+3
Christian Huitema,Private Octopus Inc.,1+3
Christopher Inacio,Carnegie Mellon,1
Colin Whorlow,NCSC,1
Corinna Schmitt,"Universitaet der Bundeswehr Muenchen, RI CODE",1
Daniel Havey,Microsoft,1
Daniel Huang,Nanjing Zhongxing Software Company Limited,1
Daniel King,Lancaster University,1+3
Daniel Migault,Ericsson,1+2+3
Daniele Ceccarelli,Ericsson AB,1+2+3
Darren Dukes,Cisco Systems,1
David Guzman,Technische Universitaet Muenchen,1
David Lake,DELL Technologies,1
David Sinicrope,Ericsson,1+2
Dawei Fan,Huawei,1
Dean Bogdanovic,"Alef Edge, Inc.",1+3
Dhruv Dhody,Huawei Technologies India Pvt. Ltd.,1+2+3
Dieter Beller,Nokia,1
Dimitris Maroulidis,Technical University of Crete,1
Donald E. Eastlake 3rd,Futurewei Technologies,1+2+3
eanas,no,1
Eberhard Lisse,Namibian Network Information Center (Pty) Ltd,1
Ehsan Rezaaifar,Nokia,1
Eliot Lear,Cisco,1+3
Emiliano Spinella,Syndeno,1
Eric Brunner-Williams,none,1
Eric Rescorla,Mozilla,1+3
Fady,,1
Fan Yang,Huawei Technologies,1
Fanghong Duan,Huawei,1
Fernando Gont,SI6 Networks,3
Francois Clad,Cisco Systems,1
Frank Anati,Ghana Health Service,1
Fred Baker,ISC,1+2+3
Gabriel Montenegro,Samsung Research America (consultant),1
Geoff Huston,APN IC,1+3
George G. Michaelson,APNIC P/L,1+3
Georgios Karagiannis,Huawei,1
Giuseppe Fioccola,Huawei Technologies,1+3
GNANAJEYARAMAN RAJARAM,SBM COLLEGE OF ENGINEERING AND TECHNOLOGY,1
Goeran Selander,Ericsson,1+3
Gonzalo Salgueiro,Cisco,1+2+3
Greg Mirsky,Ericsson,1+3
Greg Shepherd,,1+2
Guangpeng Li,Huawei,1
Haibo Wang,Huawei,1
Haiyang Su,"Huawei Technologies Co.,Ltd",1
Hannes Tschofenig,Arm Limited,1+2+3
Hannu Flinck,Nokia,1
Haomian Zheng,"Huawei Technologies Co., Ltd.",1+3
Haoyu Song,Futurewei Technologies,1
Henk Birkholz,Fraunhofer SIT,1+2+3
Herman Ramos,Inaglobe,1
Hooman Bidgoli,Nokia,1
Huaimo Chen,Futurewei,1+3
Ian Swett,Google,1+2
Ignas Bagdonas,Equinix,1
Ines Robles,,1+2
Italo Busi,Huawei,1
Jaehoon Paul Jeong,Sungkyunkwan University,1+3
Jaime Jimenez,Ericsson,1+2
James Cumming,Nokia,1
James Gruessing,Nederlandse Publiek Omroep,1+2
Jason Sterne,Nokia,1
Jeff Tantsura,Microsoft,1+2+3
Jeffrey Haas,Juniper Networks,1+2+3
Jeffrey Yasskin,Google Chrome,1
Jenny Bui,AMSL,1
Jianfei(Jeffrey) HE,City University of Hong Kong,1
Jie Dong,Huawei Technologies,1+2+3
Jim Guichard,,1+2
Jim Reid,,1
Jingrong Xie,Huawei,1
Joel Jaeggli,fastly,1+2
Joey Salazar,n/a,1+2
John Drake,Juniper Networks,1+3
John Preuss

Re: [Ace] ace - Not having a session at IETF 114

[Daniel Migault]

Hi,

We had a discussion between the chairs and believe that ACE does not need
to meet for this IETF meeting. If the WG believes that an interim meeting
in June will help, let us know, we are happy to plan such a meeting.

Yours,
Daniel

On Tue, May 10, 2022 at 1:08 PM IETF Meeting Session Request Tool <
session-requ...@ietf.org> wrote:

>
>
> Daniel Migault, a chair of the ace working group, indicated that the ace
> working group does not plan to hold a session at IETF 114.
>
> This message was generated and sent by the IETF Meeting Session Request
> Tool.
>
>
>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] WGLC draft-ietf-ace-extend-dtls-authorize

[Daniel Migault]

Just reminding other co-authors
.
Yours,
Daniel

On Tue, Mar 15, 2022 at 11:00 AM Olaf Bergmann  wrote:

> Hi Logan and Daniel,
>
> On 2022-02-28, Daniel Migault  wrote:
>
> > For all co-authors, please provide an IPR statement and let us
> > know of any known implementations.
>
> I am not aware of any IPR related to this document.
>
> Our implementation (WIP) at [1] supports CoAP transport over DTLS
> and TLS using libcoap [2]. The client-side retry with different
> transport layer security is not yet implemented, though.
>
> [1] https://gitlab.informatik.uni-bremen.de/DCAF/dcaf
> [2] https://libcoap.net
>
> Grüße
> Olaf
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] draft-ietf-ace-key-groupcomm-oscore-13

[Daniel Migault]

Thanks Goran for the review!
Yours,
Daniel


From: Ace  on behalf of Göran Selander 

Sent: Sunday, March 20, 2022 5:18 PM
To: ace@ietf.org
Subject: [Ace] draft-ietf-ace-key-groupcomm-oscore-13


All,

I have taken a look at ace-key-groupcomm-oscore-13. The intent was to make a 
complete review but I think it would be easier to do that if the draft was 
somewhat restructured first - a concrete proposal is the main content of this 
mail. A lot of good thinking has been put into this draft and there are traces 
from re-writes due to changes in the documents it depends on, which may be the 
reason for the current structure. In any case I would like to come back with 
more detailed comments once we discussed the structure.

Dependencies:

The main "parent" of this draft is ace-key-groupcomm, of which it is a profile. 
Another parent is core-oscore-groupcomm, for which it provides key management. 
Both are pre-requisite reading and therefore this draft uses content from these 
drafts directly without much introduction. While this is a reasonable 
assumption, I think the reading would be simplified by a slight rearrangement 
of the content.


Restructure proposal summary:

* Follow more closely the order of content in ace-key-groupcomm. More below.

* Start with the main cases and what happens first, wait with exceptions and 
what comes later. Some sections start with listing error codes and come to 
normal operations later. Of course, this is a matter of style, but I was 
surprised, for example, to find group *re-keying* in section 2.2 - essentially 
the first content of the draft - basically before any keying procedures have 
been described.

* Group some of the later sections into subsections, to allow a reader of the 
table-of-contents an overview. The draft has 26 sections excluding appendices. 
For example, sections 8-17 are all about sharing information about groups and 
nodes, which could be made into subsections of one or more sections.

* There are a large number of parameters discussed in the document. It would be 
good if they could be grouped into tables for easier overview and to see which 
belong together and for what purpose. Section 21 provides a list which is a 
good starting point.


I made a sketch as PR #50 to illustrate the comments above (except tables). It 
may be difficult to read the diff since I rearranged sections, made some into 
subsections, and also rearranged some content within sections to make the point 
about my preferred order of things. Again, this is just a proposal and it may 
be that we happen to have quite opposite preferences here.


More details:

ace-key-groupcomm has the following content:

Sec. 3.  authorization req/resp & token transfer req/resp
Sec. 4.  RS REST interface / KDC functionality

Then sections about changes in the group.

Sec. 5. removing member
Sec. 6. rekeying

Then formats, parameters, error identifiers in Secs. 7-9.

This is something like a top-down structure, starting with the main cases and 
what happens first, waiting with exceptions and what comes later.

Now looking at ace-key-groupcomm-oscore, Section 2.1 is essentially a pointer 
to sections 4 and 6  corresponding to section 3 in ace-key-groupcomm). I 
propose to delete section 2.1 and let sections 4 and 6 follow suite, rather 
than point to them.

The next section in  would then be 5 corresponding to section 4 in 
ace-key-groupcomm.

Section 2.2 is about re-keying and stale IDs corresponding to sections 5-6 in 
ace-key-groupcomm. I think that makes more sense to speak about after the 
normal procedure has been described.

Section 3 is about format but is quite independent. This could come before or 
after the main procedures, I put it before. Section 7 is about the public keys 
is also quite independent and actually provides high level understanding of the 
trust model, so I put that before too, but is not critical.


So the order of the first sections would become something like this:

1
3
7
2.0
4
6
5
2.2
...

There are individual paragraphs moved around the PR to make the text flow 
better. Have a look and let's discuss.


A few nits already now:


Nit 1.

> Group OSCORE is
   used to protect CoAP group communication over IP multicast
[I-D.ietf-core-groupcomm-bis]

Not necessarily IP multicast. This is mentioned in multiple occasions. Use the 
general formulation “to protect CoAP group communication.” and mention IP 
multicast as occasional example where needed


Nit 2.

The identification of the HKDF algorithm by using an algorithm value for a 
direct method in COSE (COSE algorithms -11, -10) is somehow violating the 
intent, as there is in this case no COSE object for which the direct method is 
used. The OSCORE profile of ACE (RFC-to-be 9203 
https://www.rfc-editor.org/authors/rfc9203.html

[Ace] Please upload your slides!

[Daniel Migault]

Hi,

Here is the current agenda:
https://notes.ietf.org/notes-ietf-113-ace

Please upload your presentation by 21/03.
https://datatracker.ietf.org/meeting/113/session/ace

Yours,
Daniel
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] WGLC draft-ietf-ace-extend-dtls-authorize

[Daniel Migault]

This email closes the WGLC.

If anyone is willing to shepherd the document please let us know. For all
co-authors, please provide an IPR statement and let us know of any known
implementations.

Yours,
Logan and Daniel

On Fri, Feb 18, 2022 at 9:22 AM Olaf Bergmann  wrote:

> Marco,
>
> Thanks. I have removed the reference to DTLS1.3 and will propose
> text to address the interoperability issues asap.
>
> Grüße
> Olaf
>
> On 2022-02-18, Marco Tiloca  wrote:
>
> > Please, see my replies inline (trimming the solved points)
> >
> >
> > On 2022-02-18 13:42, Olaf Bergmann wrote:
> >> Hi Marco,
> >>
> >> thanks for the thorough review. I have done most of the suggested
> >> updates (see Editor's copy [1]).
> >>
> >> Just a few comments and questions inline.
> >>
> >> [1]
> >>
> https://ace-wg.github.io/ace-extend-dtls-authorize/draft-ietf-ace-extend-dtls-authorize.html
> >>
> >> On 2022-02-18, Marco Tiloca 
> >> wrote:
> >>
> >>> [Section 1]
> >>>
> >>> * For consistency with draft-ietf-ace-dtls-authorize , I think
> >>> here it would be better to refer to RFC 6347 when mentioning
> >>> DTLS. The original profile only mentions DTLS 1.3 as a possible
> >>> later version, without pointing to the specification.
> >> Done.
> >>
> >> DTLS1.3 now is not referenced anymore. Do you think a normative
> >> dependency for DTLS1.3 is required?
> >
> > ==>MT
> > I think you can remove the DTLS 1.3 entry from the list of normative
> > references. That reference is not present among those in
> > draft-ietf-ace-dtls-authorize either (where DTLS 1.3 is at least named
> > once), so it feels even more unnecessary here.
> > <==
> >>> * "The same access rights are valid in case transport layer
> >>> security is either DTLS or TLS, and the same access token can be
> >>> used."
> >>>
> >>> This implies that the "ace_profile" claim in the access token
> >>> and the corresponding "ace_profile" parameter in the AS-to-Client
> >>> response still indicate the profile name "coap_dtls", even though
> >>> TLS might be used between C and RS. I think it's better to
> >>> highlight it.
> >> Yes, good point.
> >>
> >> I have added the following sentence at the end:
> >>
> >>Therefore, the value `coap_dtls` in the `ace_profile` parameter of
> >>an AS-to-Client response or in the `ace_profile` claim of an
> >>access token indicates that either DTLS or TLS can be used for
> >>transport layer security.
> >
> > ==>MT
> > Looks good.
> > <==
> >
> >>> * Building on the previous point, there's probably something more
> >>> worth clarifying. Let's say that the client receives an
> >>> AS-to-Client response specifying "ace_profile" with value
> >>> "coap_dtls". Presumably, the following applies:
> >>> - The client can feel free to go ahead with TLS or DTLS as
> >>> it
> >>> sees fit, if it does not know in advance which the RS prefers or
> >>> exclusively supports.
> >>> - Then, if the RS does not show support for DTLS (TLS), the
> >>> client may want to try again with TLS (DTLS) if supporting it.
> >>> On the other hand, a client or RS that has been registered
> >>> to
> >>> the AS as supporting the "coap_dtls" profile is supposed to
> >>> support at least one among TLS or DTLS.
> >> You are raising an interesting point. It might happen that the
> >> client supports either DTLS or TLS, and the resource server has only
> >> support for the other transport layer security, they might not be
> >> able to talk to each other at all. The same might happen for other
> >> values of 'ace_profile' but for different profiles, the
> >> AS-to-clientn response would make this transparent.
> >>
> >> Do you feel that we should elaborate on the case where ace_profile:
> >> coap_dtls is returned in the AS-to-Client response but client and
> >> resource server still will not be able to setup a (D)TLS connection?
> >
> > ==>MT
> > Yes, it would help to elaborate on that. As you say, there is a
> > possibility of no commonly supported transport security protocol,
> > although within the commonly supported profile.
> >
> > In that case, and assuming that neither of the two parties can be
> > (promptly) updated to broaden its support, the client would just have
> > to give up after failing to establish a channel with the only
> > transport security protocol it supports.
> >
> >
> > Thanks,
> > /Marco
> > <==
> >
> >> Done
> >>
> >> Grüße
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-mqtt-tls-profile-14.txt

[Daniel Migault]

Thanks for the update! I am happy this document is in LC!
Yours,
Daniel

On Thu, Feb 17, 2022 at 4:31 AM Cigdem Sengul 
wrote:

> Dear Ace,
> This version updates the document as required for the AD review, mainly
> aligning the descriptions to DTLS-profile when TLS is used for client
> authentication.
>
> Kind regards,
> --Cigdem
>
> On Thu, 17 Feb 2022 at 09:29,  wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Authentication and Authorization for
>> Constrained Environments WG of the IETF.
>>
>> Title   : Message Queuing Telemetry Transport (MQTT)-TLS
>> profile of Authentication and Authorization for Constrained Environments
>> (ACE) Framework
>> Authors : Cigdem Sengul
>>   Anthony Kirby
>> Filename: draft-ietf-ace-mqtt-tls-profile-14.txt
>> Pages   : 43
>> Date: 2022-02-17
>>
>> Abstract:
>>This document specifies a profile for the ACE (Authentication and
>>Authorization for Constrained Environments) framework to enable
>>authorization in a Message Queuing Telemetry Transport (MQTT)-based
>>publish-subscribe messaging system.  Proof-of-possession keys, bound
>>to OAuth2.0 access tokens, are used to authenticate and authorize
>>MQTT Clients.  The protocol relies on TLS for confidentiality and
>>MQTT server (broker) authentication.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-ace-mqtt-tls-profile/
>>
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-ace-mqtt-tls-profile-14
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-mqtt-tls-profile-14
>>
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org:
>> :internet-drafts
>>
>>
>> _______
>> Ace mailing list
>> Ace@ietf.org
>> https://www.ietf.org/mailman/listinfo/ace
>>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] WGLC draft-ietf-ace-extend-dtls-authorize

[Daniel Migault]

Thanks for the review and fast response.

Yours,
Daniel

On Fri, Feb 18, 2022 at 7:42 AM Olaf Bergmann  wrote:

> Hi Marco,
>
> thanks for the thorough review. I have done most of the suggested
> updates (see Editor's copy [1]).
>
> Just a few comments and questions inline.
>
> [1]
> https://ace-wg.github.io/ace-extend-dtls-authorize/draft-ietf-ace-extend-dtls-authorize.html
>
> On 2022-02-18, Marco Tiloca  wrote:
>
> > [General]
> >
> > * In the document header, "Network Working Group" should be
> > replaced by "ACE Working Group".
>
> Done
>
> > * Looking at the phrasing in Section 2 of
> > draft-ietf-ace-dtls-authorize, it would be more consistent to use
> > "Extension of the CoAP-DTLS Profile for ACE to TLS", as document
> > title and in the abstract.
>
> Done
>
> > [Abstract]
> >
> > * Also as a feedback from the ID nit checker, the abstract should
> > explicitly mention the updated document
> > draft-ietf-ace-dtls-authorize.
>
> Done
>
> > [Section 1]
> >
> > * For consistency with draft-ietf-ace-dtls-authorize , I think
> > here it would be better to refer to RFC 6347 when mentioning
> > DTLS. The original profile only mentions DTLS 1.3 as a possible
> > later version, without pointing to the specification.
>
> Done.
>
> DTLS1.3 now is not referenced anymore. Do you think a normative
> dependency for DTLS1.3 is required?
>
> > * Please, add a reference to RFC 8446 for TLS.
>
> Done.
>
> > * "The same access rights are valid in case transport layer
> > security is either DTLS or TLS, and the same access token can be
> > used."
> >
> >This implies that the "ace_profile" claim in the access token
> > and the corresponding "ace_profile" parameter in the AS-to-Client
> > response still indicate the profile name "coap_dtls", even though
> > TLS might be used between C and RS. I think it's better to
> > highlight it.
>
> Yes, good point.
>
> I have added the following sentence at the end:
>
>   Therefore, the value `coap_dtls` in the `ace_profile` parameter of
>   an AS-to-Client response or in the `ace_profile` claim of an
>   access token indicates that either DTLS or TLS can be used for
>   transport layer security.
>
> > * Building on the previous point, there's probably something more
> > worth clarifying. Let's say that the client receives an
> > AS-to-Client response specifying "ace_profile" with value
> > "coap_dtls". Presumably, the following applies:
> >
> >- The client can feel free to go ahead with TLS or DTLS as it
> > sees fit, if it does not know in advance which the RS prefers or
> > exclusively supports.
> >
> >- Then, if the RS does not show support for DTLS (TLS), the
> > client may want to try again with TLS (DTLS) if supporting it.
> >
> >On the other hand, a client or RS that has been registered to
> > the AS as supporting the "coap_dtls" profile is supposed to
> > support at least one among TLS or DTLS.
>
> You are raising an interesting point. It might happen that the
> client supports either DTLS or TLS, and the resource server has only
> support for the other transport layer security, they might not be
> able to talk to each other at all. The same might happen for other
> values of 'ace_profile' but for different profiles, the
> AS-to-clientn response would make this transparent.
>
> Do you feel that we should elaborate on the case where ace_profile:
> coap_dtls is returned in the AS-to-Client response but client and
> resource server still will not be able to setup a (D)TLS connection?
>
> > [Section 2]
> >
> > * Shouldn't this section update the IANA considerations from
> > Section 9 of draft-ietf-ace-dtls-authorize ? The "Profile
> > Description" column of the "coap_dtls" entry in the ACE OAuth
> > Profile registry should become:
> >
> >"Profile for delegating client authentication and authorization
> > in a constrained environment by establishing a Datagram Transport
> > Layer Security (DTLS) or Transport Layer Security (TLS) channel
> > between resource-constrained nodes."
>
> Done
>
> >
> > [Nits]
> >
> > * Section 1
> > --- s/specifies use/specifies the use
> > --- s/lacking from the/lacking in the
> > --- s/is either DTLS/is provided by either DTLS
>
> Done
>
> Grüße
> Olaf
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] WGLC draft-ietf-ace-extend-dtls-authorize

[Daniel Migault]

Hi all,

This email starts a WGLC for Extension of the ACE CoAP-DTLS Profile to TLS.
If you think the document is ready or have any comments please indicate it
by Feb 22 on the mailing list.

The document is available here:
https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/

Yours,
Daniel

-- Forwarded message -
From: 
Date: Fri, Feb 4, 2022 at 3:54 AM
Subject: [Ace] I-D Action: draft-ietf-ace-extend-dtls-authorize-01.txt
To: 
Cc: 



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Authentication and Authorization for
Constrained Environments WG of the IETF.

Title   : Extension of the ACE CoAP-DTLS Profile to TLS
Authors : Olaf Bergmann
  John Preuß Mattsson
  Göran Selander
Filename: draft-ietf-ace-extend-dtls-authorize-01.txt
Pages   : 4
Date: 2022-02-04

Abstract:
   This document updates the ACE CoAP-DTLS profile by specifying that
   the profile applies to TLS as well as DTLS.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the Authentication and
   Authorization for Constrained Environments Working Group mailing list
   (ace@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/ace/.

   Source for this draft and an issue tracker can be found at
   https://github.com/ace-wg/ace-extend-dtls-authorize.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-ace-extend-dtls-authorize-01.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-extend-dtls-authorize-01


Internet-Drafts are also available by rsync at rsync.ietf.org:
:internet-drafts


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] AD review of draft-ietf-ace-aif-04

[Daniel Migault]

Thank you very much Carsten!
Yours,
Daniel


From: Carsten Bormann 
Sent: Friday, February 11, 2022 12:48 PM
To: Benjamin Kaduk
Cc: draft-ietf-ace-aif@ietf.org; Ace Wg
Subject: Re: AD review of draft-ietf-ace-aif-04

Hi Ben,

thank you for this in-depth review.

I have prepared a pull request with resulting changes at

https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-17c8a7970d4c9863&q=1&e=c984e08c-d5a2-4479-9691-1a868bfc976f&u=https%3A%2F%2Fgithub.com%2Fcabo%2Face-aif%2Fpull%2F1

Depending on further feedback from you and from the WG, I plan to submit the 
resulting updated I-D on Monday.

> On 2022-02-11, at 05:20, Benjamin Kaduk  wrote:
>
> Hi all,
>
> There's enough that will be changing yet that I'll mark this as "Revised
> I-D needed" in the datatracker rather than starting an IETF Last Call
> directly.
>
> We'll also need to change the "Intended RFC Status" field in the
> datatracker to match the Proposed Standard target.

Chairs: please do make this change.

> Without further ado...
>
> Abstract, Introduction
>
> Seeing ~identical abstract and introduction always makes me wonder if
> there's a way to pare down the abstract and/or flesh out the introduction
> further.  (I didn't get very far in my wonderment today, to be clear.)

I don’t see immediate opportunities for such changes, so I haven’t tried.

> Also, in the first sentence we say "Constrained Devices [...] need
> security."  I see that we go on to focus on the authorization aspect of such
> security functionality, but I think it would be good to have some more
> adjectives qualifying "security", which in isolation can mean very different
> things to different readers.

Hmm, the whole point of the rest of the first paragraph is to specify what kind 
of security is addressed here.

>   need to ascertain
>   that the authorization to request the operation does apply to the
>   actual requester, [...]
>
> nit: maybe "actual authenticated requester"?

Good idea; I made it “actual requester as authenticated”.

>
> and need to ascertain that other devices they place
>   requests on are the ones they intended.
>
> nit: maybe s/place requests on/make requests of/?

“make requests of” is not a phrase I would have come up with, but I’ll defer to 
the native speaker here.

>
>  This document provides a suggestion for such a
>   format, the Authorization Information Format (AIF).  [...]
>
> If we're going for Proposed Standard, we should say something stronger than
> just "a suggestion for" such a format.

Right.  s/provides a suggestion for/defines/

(It is too easy to forget making such changes as a draft progresses from straw 
man to solid specification…)

>AIF is defined
>   both as a general structure that can be used for many different
>   applications and as a specific refinement that describes REST
>   resources (potentially dynamically created) and the permissions on
>   them.
>
> (editorial) I might consider a framing more like "defined both as [...] and
> as a specific instantiation tailored to REST resources and the permissions
> on them, including some provision for dynamically created resources."

Nice!  Adopted.

> Section 1.1
>
>   The shape of data is specified in CDDL [RFC8610].  Terminology for
>   Constrained Devices is defined in [RFC7228].
>
> I expect that some readers will find "the shape of data" to be too informal
> for their liking.  I'm willing to let it go through to IETF LC, myself, but
> am not going to push hard for it to remain if there is pushback.

“Data shape” is a technical term that we actually use a lot to describe the 
qualities that a structural (as opposed to semantic) data definition describes.
Googling, I get about 257.000 results, e.g., 
https://www.w3.org/2014/data-shapes/wiki/Main_Page

>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>   "OPTIONAL" in this document are to be interpreted as described in
>   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
>   capitals, as shown here.  These words may also appear in this
>   document in lower case as plain English words, absent their normative
>   meanings.
>
> I expect multiple future reviewers to ask you to use the BCP 14 boilerplate
> exactly as it appears in RFC 8174.

Indeed, with Standards Track, this can now be normalized.

>   (Note that this document is itself informational, but it is
>   discussing normative statements that MUST be put into concrete terms
>   in each specification that makes use of this document.)
>
> This is stale now that we're not going for Informational anymore.

Ditto.

> Section 2
>
>   We do not concern the AIF format with the subject for which the AIF
>   data item is issued, so we are focusing the AIF data item on a single
>   row in the access

[Ace] Publication has been requested for draft-ietf-ace-key-groupcomm-15

[Daniel Migault via Datatracker]

Daniel Migault has requested publication of draft-ietf-ace-key-groupcomm-15 as 
Proposed Standard on behalf of the ACE working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm/


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-aif-04.txt

[Daniel Migault]

Hi,

Please find an update of the aif draft that is resulting from post WGLC
discussion with co-author and our AD. The only (real) change is the change
of the status from informational to standard. What raised our attention is
that it led to downgraded reference in other drafts and reconsidering the
status and standard status seemed to us more appropriate.

If anyone has any issue with that please let us know  by Feb. 4.

Yours,
Daniel

On Fri, Jan 28, 2022 at 9:29 AM  wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Authentication and Authorization for
> Constrained Environments WG of the IETF.
>
> Title   : An Authorization Information Format (AIF) for ACE
> Author  : Carsten Bormann
> Filename: draft-ietf-ace-aif-04.txt
> Pages   : 14
> Date: 2022-01-28
>
> Abstract:
>Constrained Devices as they are used in the "Internet of Things" need
>security.  One important element of this security is that devices in
>the Internet of Things need to be able to decide which operations
>requested of them should be considered authorized, need to ascertain
>that the authorization to request the operation does apply to the
>actual requester, and need to ascertain that other devices they place
>requests on are the ones they intended.
>
>To transfer detailed authorization information from an authorization
>manager (such as an ACE-OAuth Authorization Server) to a device, a
>compact representation format is needed.  This document provides a
>suggestion for such a format, the Authorization Information Format
>(AIF).  AIF is defined both as a general structure that can be used
>for many different applications and as a specific refinement that
>describes REST resources (potentially dynamically created) and the
>permissions on them.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ace-aif/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-ace-aif-04.html
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-aif-04
>
>
> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
>
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Fwd: [saag] Interested in chairing a WG?

[Daniel Migault]

Hi everyone!

If you are interested in chairing a WG. Feel free to contact Ben and Roman
directly or Logan Med or myself if you have any questions and want to have
a discussion.

Yours,
Daniel

-- Forwarded message -
From: Roman Danyliw 
Date: Wed, Jan 19, 2022 at 12:09 PM
Subject: [saag] Interested in chairing a WG?
To: saag 


Hi!

The IETF functions best when there is a robust and diverse pipeline of
candidates in WG leadership positions.  Ben and I would like to have a pool
of candidates to select from when any WG chair positions need to be
filled.  Such a pool lets us tailor a match between the position, and the
skills and potential of the candidates in question.

We're sending this note to make sure we've got the broadest pool available
for future WG chair assignments.  If you are interested in chairing, or
know someone interested in chairing, please email us privately.  Chairs
with previous experience are great.  No prior experience is also fine as we
often pair experienced chairs with those new to the role.  If you
previously responded to calls such as this [1] [2], we would still like to
hear from you again to confirm your interest.

Thanks, and looking forward to talking to you.

Regards,
Roman and Ben

[1] https://mailarchive.ietf.org/arch/msg/saag/_lXbKOo5r6IaOz6PTtZ7Qn6DWp4/
[2] https://mailarchive.ietf.org/arch/msg/saag/0mfa1LhPnox6MtzhG76N_kVTMsY/

___
saag mailing list
s...@ietf.org
https://www.ietf.org/mailman/listinfo/saag


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] ACE status

[Daniel Migault]

Hi,

After discussing it with Logan, we are planning to have a short 1h session
during the next IETF. We are also wondering if the WG is willing to have an
interim meeting. If you have any opinion, please let us know.
We are expecting 1. 2. to be resolved this month with the addition to
change aif from informational to standard. 3. is expected to be done in
february or at least before the IETF meeting. Feel free to let us know if
you have a different schedule in mind.

Yours,
Daniel


On Wed, Dec 22, 2021 at 8:09 PM Daniel Migault  wrote:

> Hi all,
>
> Just to remind everyone of the current status of the WG:
> 1. ongoing shepherd writeup for -coap-eap and -key-groupcomm.
> 2. WGLC for -key-groupcomm-oscore (waiting for reviews)
> 3. -extended-dtls-authorize / -pubsub-profile are expected to be soon in
> WGLC
> 4. revoked-token-notification and oscore-gm-admin are in progress.
>
> Yours,
> Logan and Daniel
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-key-groupcomm-14.txt

[Daniel Migault]

Hi,

In case it has missed,  I am just following up with IPR disclosure.

Yours,
Daniel

On Wed, Dec 22, 2021 at 7:55 PM Daniel Migault  wrote:

> Hi,
>
> In order to complete the shepherd I would like the co-author to confirm
> that any and all appropriate IPR disclosures required for full conformance
> with the provisions of BCP 78 and BCP 79 have already been filed.
>
> Please have also a look at the nits
>
> https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-ace-key-groupcomm-14.txt
>
> There is a MAY NOT that causes an issue as well as unused references.
>
> Yours,
> Daniel
>
> On Mon, Oct 25, 2021 at 12:48 PM Marco Tiloca  40ri...@dmarc.ietf.org> wrote:
>
>> Hello ACE,
>>
>> This new version should have addressed all the WGLC comments from Göran
>> [1] and Cigdem [2], as well as further points from follow-up discussions
>> on the thread throughout the draft revision.
>>
>> Thank you very much for the good comments!
>>
>> Best,
>> /Marco
>>
>> [1]
>> https://mailarchive.ietf.org/arch/msg/ace/pr2gBhvqy9j8AfUdQVTZLwamXac/
>>
>> [2]
>> https://mailarchive.ietf.org/arch/msg/ace/gv_uRo2Y45jqOLJghVSbAARWky0/
>>
>> On 2021-10-25 15:57, internet-dra...@ietf.org wrote:
>> > A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> > This draft is a work item of the Authentication and Authorization for
>> Constrained Environments WG of the IETF.
>> >
>> >  Title   : Key Provisioning for Group Communication
>> using ACE
>> >  Authors : Francesca Palombini
>> >Marco Tiloca
>> >   Filename: draft-ietf-ace-key-groupcomm-14.txt
>> >   Pages   : 106
>> >   Date: 2021-10-25
>> >
>> > Abstract:
>> > This document defines how to use the Authentication and
>> Authorization
>> > for Constrained Environments (ACE) framework to distribute keying
>> > material and configuration parameters for secure group
>> communication.
>> > Candidate group members acting as Clients and authorized to join a
>> > group can do so by interacting with a Key Distribution Center (KDC)
>> > acting as Resource Server, from which they obtain the keying
>> material
>> > to communicate with other group members.  While defining general
>> > message formats as well as the interface and operations available at
>> > the KDC, this document supports different approaches and protocols
>> > for secure group communication.  Therefore, details are delegated to
>> > separate application profiles of this document, as specialized
>> > instances that target a particular group communication approach and
>> > define how communications in the group are protected.  Compliance
>> > requirements for such application profiles are also specified.
>> >
>> >
>> > The IETF datatracker status page for this draft is:
>> >
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-ace-key-groupcomm%2F&data=04%7C01%7Cmarco.tiloca%40ri.se%7Ca638ee397ced4fc372ff08d997bf79b5%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637707672366321795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=MUGHcPBWXrsBtP%2BEJ0PdmTxTlrfQ9jb3IZCzVopwCB4%3D&reserved=0
>> >
>> > There is also an HTML version available at:
>> >
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-ace-key-groupcomm-14.html&data=04%7C01%7Cmarco.tiloca%40ri.se%7Ca638ee397ced4fc372ff08d997bf79b5%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637707672366321795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=y6LdDfymSDIs5cDuPgmhOciO%2BEahcrSXGvW3LfR98j8%3D&reserved=0
>> >
>> > A diff from the previous version is available at:
>> >
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-ace-key-groupcomm-14&data=04%7C01%7Cmarco.tiloca%40ri.se%7Ca638ee397ced4fc372ff08d997bf79b5%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637707672366321795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=kmEdmD6senkWyvdWMwx5OzdzOq0OavECCx4yKI0g4Ds%3D&reserved=0
>> >
>> >
>> > Internet-Drafts are also available by anonymous FTP at

Re: [Ace] ACE status

[Daniel Migault]

Thanks Carsten for the response. I understand we have never been so close to 
get them published, but it is hard for me to have an estimation of the 
publication date.

Yours,
Daniel


From: Ace  on behalf of Carsten Bormann 
Sent: Thursday, December 23, 2021 11:12 AM
To: Ludwig Seitz
Cc: Daniel Migault; Ace Wg
Subject: Re: [Ace] ACE status

On 2021-12-23, at 16:46, Ludwig Seitz  wrote:
>
> Could you also give us an update on draft-ietf-ace-oauth-authz and the 
> related profile drafts?
> (I have only noticed they are sitting in the RFC-Editor’s queue for some 
> time).

I’m not Daniel, but these drafts are sitting in the RFC-Editor’s queue in a 
cluster:

https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-ec2464718dfbc91f&q=1&e=de33d636-a74c-4b91-82e4-5f31aca056e6&u=https%3A%2F%2Fwww.rfc-editor.org%2Fcluster_info.php%3Fcid%3DC442

The good news is that none of the drafts in this cluster has a MISSREF, so we 
are not waiting for anything.  The other good news is that the drafts have 
already passed the EDIT stage and are now in RFC-EDITOR stage.  The somewhat 
more low-key news is that quite a few drafts are in that stage, as this 
requires a review of the work done in EDIT; we are 3.4 weeks into that stage, 
while other drafts (including monsters such as C430) have 6 weeks or more and 
aren’t done yet.

So I would expect we’ll get into AUTH48 state in January.  How long we need to 
get that done depends foremost on the responsiveness of the authors.  With 
luck, we’ll be published in February, but if there is a show-stopper, we might 
miss IETF 113.

Grüße, Carsten

___
Ace mailing list
Ace@ietf.org
https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-1496721336ed3e31&q=1&e=de33d636-a74c-4b91-82e4-5f31aca056e6&u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Face

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-key-groupcomm-14.txt

[Daniel Migault]

Thanks Marco!

Yours,
Daniel

On Thu, Dec 23, 2021 at 8:05 AM Marco Tiloca  wrote:

> Hello Daniel,
>
> I do not have and I am not aware of any IPR on this document.
>
> I have just submitted version -15, with the two requested fixes.
>
>
> * In Section 3.3
>
> OLD:
> the KDC MAY NOT include 'sign_info' parameter
>
> NEW:
> the KDC MAY omit the 'sign_info' parameter
>
>
> * The apparently unused reference "I-D.ietf-cose-rfc8152bis-struct" was
> actually used in Section 1.1. However, it was spread over two lines, hence
> probably missed by the nit checker. It's fixed now.
>
>
> Best,
> /Marco
>
> On 2021-12-23 01:55, Daniel Migault wrote:
>
> Hi,
>
> In order to complete the shepherd I would like the co-author to confirm
> that any and all appropriate IPR disclosures required for full conformance
> with the provisions of BCP 78 and BCP 79 have already been filed.
>
> Please have also a look at the nits
>
> https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-ace-key-groupcomm-14.txt
> <https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww6.ietf.org%2Ftools%2Fidnits%3Furl%3Dhttps%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-ace-key-groupcomm-14.txt&data=04%7C01%7Cmarco.tiloca%40ri.se%7C7370a0447e6940f4515a08d9c5aef774%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637758178729531544%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=9MzRKSbpg3bMwDcX6a3jjnn88H1d9j8rWVmGpX5VOQ4%3D&reserved=0>
>
> There is a MAY NOT that causes an issue as well as unused references.
>
> Yours,
> Daniel
>
> On Mon, Oct 25, 2021 at 12:48 PM Marco Tiloca  40ri...@dmarc.ietf.org> wrote:
>
>> Hello ACE,
>>
>> This new version should have addressed all the WGLC comments from Göran
>> [1] and Cigdem [2], as well as further points from follow-up discussions
>> on the thread throughout the draft revision.
>>
>> Thank you very much for the good comments!
>>
>> Best,
>> /Marco
>>
>> [1]
>> https://mailarchive.ietf.org/arch/msg/ace/pr2gBhvqy9j8AfUdQVTZLwamXac/
>> <https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Face%2Fpr2gBhvqy9j8AfUdQVTZLwamXac%2F&data=04%7C01%7Cmarco.tiloca%40ri.se%7C7370a0447e6940f4515a08d9c5aef774%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637758178729687782%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=TGGln2GwsahjKNoqmEnJfGCvlIyHkD2l7gzVoDxSqjc%3D&reserved=0>
>>
>> [2]
>> https://mailarchive.ietf.org/arch/msg/ace/gv_uRo2Y45jqOLJghVSbAARWky0/
>> <https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Face%2Fgv_uRo2Y45jqOLJghVSbAARWky0%2F&data=04%7C01%7Cmarco.tiloca%40ri.se%7C7370a0447e6940f4515a08d9c5aef774%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637758178729687782%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=ieY4jgh2uJM1%2FlfupW0w6b2WScTlLuKcr1zVqMMGjF8%3D&reserved=0>
>>
>> On 2021-10-25 15:57, internet-dra...@ietf.org wrote:
>> > A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> > This draft is a work item of the Authentication and Authorization for
>> Constrained Environments WG of the IETF.
>> >
>> >  Title   : Key Provisioning for Group Communication
>> using ACE
>> >  Authors : Francesca Palombini
>> >Marco Tiloca
>> >   Filename: draft-ietf-ace-key-groupcomm-14.txt
>> >   Pages   : 106
>> >   Date: 2021-10-25
>> >
>> > Abstract:
>> > This document defines how to use the Authentication and
>> Authorization
>> > for Constrained Environments (ACE) framework to distribute keying
>> > material and configuration parameters for secure group
>> communication.
>> > Candidate group members acting as Clients and authorized to join a
>> > group can do so by interacting with a Key Distribution Center (KDC)
>> > acting as Resource Server, from which they obtain the keying
>> material
>> > to communicate with other group members.  While defining general
>> > message formats as well as the interface and operations available at
>> > the KDC, this document supports different approaches and protocols
>> > for secure group communication.  Therefore, details are delegated to

[Ace] ACE status

[Daniel Migault]

Hi all,

Just to remind everyone of the current status of the WG:
1. ongoing shepherd writeup for -coap-eap and -key-groupcomm.
2. WGLC for -key-groupcomm-oscore (waiting for reviews)
3. -extended-dtls-authorize / -pubsub-profile are expected to be soon in
WGLC
4. revoked-token-notification and oscore-gm-admin are in progress.

Yours,
Logan and Daniel

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-key-groupcomm-14.txt

[Daniel Migault]

ng list
> > Ace@ietf.org
> >
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Face&data=04%7C01%7Cmarco.tiloca%40ri.se%7Ca638ee397ced4fc372ff08d997bf79b5%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C637707672366321795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ALG3Ogjc4qxYzMyjQMd%2FnJNcenvEiMGb8X97ZP0dS7E%3D&reserved=0
>
> --
> Marco Tiloca
> Ph.D., Senior Researcher
>
> Division: Digital System
> Department: Computer Science
> Unit: Cybersecurity
>
> RISE Research Institutes of Sweden
> https://www.ri.se
>
> Phone: +46 (0)70 60 46 501
> Isafjordsgatan 22 / Kistagången 16
> SE-164 40 Kista (Sweden)
>
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] WG Last Call for -key-groupcomm-oscore

[Daniel Migault]

Hi,

Please keep in mind -key-groupcomm-oscore is in WGLC. We will update the
datatracker.

Yours,
Daniel

On Tue, Nov 9, 2021 at 11:34 AM Daniel Migault  wrote:

> Hi,
>
> This email starts a 2 week Working Group Last Call for
> -key-groupcomm-oscore [1]. Please provide your feedback by November 23.
>
> Yours,
> Logan and Daniel
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm-oscore/
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] [Emu] New Version Notification for draft-ietf-ace-wg-coap-eap-04.txt

[Daniel Migault]

 (here or in a security consideration) that in case of an error
> message containing a cipher suite, the exchange of cipher suites between
> EAP authenticator and EAP peer cannot be verified. For example, a
> man-in-the-middle could replace cipher suites in either message which would
> not be noticed if the protocol is ended after step 2.
>
>
>
> [authors] That’s right. However, after your comments, we believe this
> could be improved. The reason is that by default we can assume that at
> least cipher suite 0. AES-CCM-16-64-128, SHA-256 is implemented in both
> entities. As such, if the controller includes option 0 in the list of
> cipher suites, the controller will not receive a bad request since at least
> the IoT device can select cipher suite 0 and therefore the authentication
> will follow until the end cipher suite negotiation can be verified.  We
> think it is simpler and we can get rid of a bad request. Does it sound
> reasonable?
>
> [GS] Sounds OK to me.
>
>
>
>
>
>
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] [Emu] New Version Notification for draft-ietf-ace-wg-coap-eap-04.txt

[Daniel Migault]

>   The authentication can be successful before EAP-SUCCES.
>
>
>
> - In section 3.3. it might be good to state that "Reauthentication" might
> be needed to rekey MSK/EMSK and to increase protection against key leakage.
>
>
>
> (An important mitigation of pervasive monitoring is to force attackers to
> do dynamic key exfiltration instead of static key exfiltration. Dynamic key
> exfiltration increases the risk of discovery for the attacker [RFC7624].
> While OSCORE will soon be augmented with a rekeying mechanism with forward
> secrecy, attackers can still get away with doing static key exfiltration.
> This is similar to TLS 1.3 with KeyUpdate, after leakage of
> application_traffic_secret_N, a passive attacker can passively eavesdrop on
> all future application data sent on the connection including application
> data encrypted with application_traffic_secret_N+1,
> application_traffic_secret_N+2, etc.)
>
>
>
> - "4.  The values from 65000 to 65535 are reserved for experimentation"
>
>
>
>what does "The values" refer to? Lifetime? In that case it would fit
> better under 3.
>
>
>
> - In addition to AES-CCM-16-64-128, only ciphersuites only cipher suites
> with AES-GCM is included. My feeling was that most IoT people are more
> interested in ChaCha20-Poly1305 than AES-GCM. I don't have a strong
> personal opinion.
>
>
>
> - "which is considered fresh key material"
>
>
>
>“considered fresh”? Maybe "uniformally random"?
>
>
>
> - With normal use of DTLS, Appendix A violates “The CoAP-EAP operation is
> intended to be compatible with the use of intermediary entities between the
> IoT device and the Controller”. This limitation should be clearly stated.
>
>
>
> - Probably good if the labels have “CoAP-EAP” in all the labels to
> guarantee that they do not collide with anything else.
>
>
>
> Cheers,
>
> John
>
>
>
> *From: *Emu  on behalf of Dan Garcia Carrillo <
> garcia...@uniovi.es>
> *Date: *Monday, 25 October 2021 at 13:27
> *To: *ace@ietf.org , EMU WG 
> *Subject: *Re: [Emu] New Version Notification for
> draft-ietf-ace-wg-coap-eap-04.txt
>
> Dear ACE and EMU WG,
>
> We have submitted a new version of the draft (draft-ietf-ace-wg-coap-eap)
>
> This version provides information on the different comments, from the
> reviews and interim meetings.
>
> Best Regards.
>
>
> El 10/25/2021 a las 1:23 PM, internet-dra...@ietf.org escribió:
> > A new version of I-D, draft-ietf-ace-wg-coap-eap-04.txt
> > has been successfully submitted by Dan Garcia-Carrillo and posted to the
> > IETF repository.
> >
> > Name: draft-ietf-ace-wg-coap-eap
> > Revision: 04
> > Title:EAP-based Authentication Service for CoAP
> > Document date:2021-10-25
> > Group:ace
> > Pages:29
> > URL:
> https://www.ietf.org/archive/id/draft-ietf-ace-wg-coap-eap-04.txt
> > Status:
> https://datatracker.ietf.org/doc/draft-ietf-ace-wg-coap-eap/
> > Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-ace-wg-coap-eap
> > Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-wg-coap-eap-04
> >
> > Abstract:
> > This document specifies an authentication service that uses the
> > Extensible Authentication Protocol (EAP) transported employing
> > Constrained Application Protocol (CoAP) messages.  As such, it
> > defines an EAP lower layer based on CoAP called CoAP-EAP.  One of the
> > primer goals is to authenticate a CoAP-enabled IoT device (EAP peer)
> > that intends to join a security domain managed by a Controller (EAP
> > authenticator).  Secondly, it allows deriving key material to protect
> > CoAP messages exchanged between them based on Object Security for
> > Constrained RESTful Environments (OSCORE), enabling the establishment
> > of a security association between them.
> >
> >
>
> >
> >
> > The IETF Secretariat
> >
> >
>
> ___
> Emu mailing list
> e...@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
> ___
> Emu mailing list
> e...@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] WG Adoption Call for tiloca-ace-revoked-token-notification

[Daniel Migault]

Thanks! I suppose implicitly you are volunteering to review and provide
feedbacks.
Yours,
Daniel

On Tue, Nov 16, 2021 at 11:09 AM Marco Rasori 
wrote:

> Hi everyone,
>
> I'm a researcher at CNR in Italy, and I'm currently implementing this
> draft for Eclipse Californium.
>
> I believe that this mechanism is useful and innovative, and I'm interested
> in its success.
>
> +1 for adoption
>
> Il giorno mar 9 nov 2021 alle ore 17:35 Daniel Migault <
> mglt.i...@gmail.com> ha scritto:
>
>> Hi,
>>
>> This email starts a 2 week Working Group Adoption Call for
>> -tiloca-ace-revoked-token-notification [1]. Please provide your feedback by
>> November 23.
>>
>> Yours,
>> Logan and Daniel
>>
>> [1]
>> https://datatracker.ietf.org/doc/draft-tiloca-ace-revoked-token-notification/
>> --
>> Daniel Migault
>> Ericsson
>> ___
>> Ace mailing list
>> Ace@ietf.org
>> https://www.ietf.org/mailman/listinfo/ace
>>
>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] WG Adoption Call for bergmann-ace-extend-dtls-authorize

[Daniel Migault]

Hi,

This email starts a 2 week Working Group Adoption Call for
-bergmann-ace-extend-dtls-authorize [1]. Please provide your feedback by
November 23.

Yours,
Logan and Daniel

[1]
https://datatracker.ietf.org/doc/draft-bergmann-ace-extend-dtls-authorize/
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] WG Adoption Call for tiloca-ace-revoked-token-notification

[Daniel Migault]

Hi,

This email starts a 2 week Working Group Adoption Call for
-tiloca-ace-revoked-token-notification [1]. Please provide your feedback by
November 23.

Yours,
Logan and Daniel

[1]
https://datatracker.ietf.org/doc/draft-tiloca-ace-revoked-token-notification/
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] WG Last Call for -key-groupcomm-oscore

[Daniel Migault]

Hi,

This email starts a 2 week Working Group Last Call for
-key-groupcomm-oscore [1]. Please provide your feedback by November 23.

Yours,
Logan and Daniel

[1] https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm-oscore/
-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] minute taker for the IETF 112 ace session

[Daniel Migault]

Hi,

We do have a busy agenda today, and it would be good to have multiple
volunteers to take the minutes. So please be ready to show up.

Yours,
Logan and Daniel

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Publication has been requested for draft-ietf-ace-cmpv2-coap-transport-04

[Daniel Migault via Datatracker]

Daniel Migault has requested publication of 
draft-ietf-ace-cmpv2-coap-transport-04 as Proposed Standard on behalf of the 
ACE working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-ace-cmpv2-coap-transport/


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Fwd: NomCom 2021-2022 Call for Community Feedback

[Daniel Migault]

Please consider giving the nomcom your input.

Yours,
Daniel

-- Forwarded message -
From: NomCom Chair 2021 
Date: Tue, Oct 19, 2021 at 10:28 AM
Subject: NomCom 2021-2022 Call for Community Feedback
To: IETF Announcement List 


Hi IETF,

The deadline for nominee acceptance and questionnaire submission was
yesterday,
Oct 18.

As of today, Oct 19, NomCom is accepting feedback on nominees for
IAB, IESG Area Directors, IETF Trust and LLC Board. NomCom is also
accepting
feedback on other topics (more on this below).

You can see the list of nominees for the 2021 nomination cycle at
https://datatracker.ietf.org/nomcom/2021/feedback/
[If you are a nominee and submitted a questionnaire your name should appear
on that page,
otherwise, please let me know.]

You may provide feedback using the web form. Any submitted feedback is
encrypted with a key I created and gave only to NomCom members.
Without this key, your feedback cannot be seen by the secretariat, the
tools people, or any of the management.

Your feedback through the web form is not anonymous when shown to
NomCom members as you need an IETF login to provide it.

You may also send feedback directly to the NomCom via nomcom-2021 at
ietf.org

If you want to give more anonymous feedback, please contact one
of the NomCom members that you trust directly, and ask that person to
relay the feedback anonymously to the NomCom.

You can also submit feedback via email to nomcom-chair-2021 at
ietf.org and I will enter it in the datatracker (one email per
candidate, please). Please indicate if I should share your identity
with the full NomCom.

The positions to be filled and the desired expertise are listed at:
https://datatracker.ietf.org/nomcom/2021/

Some of you may be aware of the "360-degree reviews" of the current IESG
ADs:
https://mailarchive.ietf.org/arch/msg/ietf-announce/DecFofU9c-svf_yiCPQDi6nLOQg/

I encourage you to provide that feedback as well. I wish to clarify that
personnel feedback to
NomCom should be limited to nominees (some of which may also be IESG
incumbents).
This should clarify the difference of NomCom feedback with the "360-degree
reviews".

NomCom also welcomes feedback on topics related to the nomination process.
Please submit via email as suggested above, although some topics may start
showing up in the above feedback web form at
https://datatracker.ietf.org/nomcom/2021/feedback/.


Thanks in advance for your feedback - we really value it and
appreciate your time taken to submit it.

Gabriel

Gabriel Montenegro
IETF NomCom Chair 2021-22
nomcom-chair-2021 at ietf dot org

___
IETF-Announce mailing list
ietf-annou...@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

[Daniel Migault]

sure. Just submit when the submission re-opens.

Yours,
Daniel

From: Mohit Sahni 
Sent: Tuesday, October 26, 2021 2:39 PM
To: Daniel Migault 
Cc: Brockhaus, Hendrik ; Saurabh Tripathi 
; Russ Housley ; 
david.von.ohe...@siemens.com ; Daniel Migault 
; Ace Wg 
Subject: Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

Hi Daniel,
I have the changes ready, but I cannot publish the new draft because draft 
submission is blocked currently till 11/06. Here is the message that I see on 
the submission page.

"The I-D submission tool will be reopened after 2021-11-06 23:59 UTC 
(IETF-meeting local time)."

Thanks
Mohit

On Tue, Oct 26, 2021 at 7:59 AM Daniel Migault 
mailto:daniel.miga...@ericsson.com>> wrote:
looks good to me.
Yours,
Daniel

From: Ace mailto:ace-boun...@ietf.org>> on behalf of 
Mohit Sahni mailto:mohit06...@gmail.com>>
Sent: Tuesday, October 26, 2021 10:57 AM
To: Brockhaus, Hendrik 
mailto:hendrik.brockh...@siemens.com>>
Cc: Saurabh Tripathi 
mailto:stripa...@paloaltonetworks.com>>; Russ 
Housley mailto:hous...@vigilsec.com>>; 
david.von.ohe...@siemens.com<mailto:david.von.ohe...@siemens.com> 
mailto:david.von.ohe...@siemens.com>>; Daniel 
Migault mailto:mglt.i...@gmail.com>>; Ace Wg 
mailto:ace@ietf.org>>
Subject: Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

Hi Daniel,
Does this text look good to you?

   This document references the cmp, a temporary entry, in the Well-
   Known URIs [1] IANA registry.  This document is expected to be
   published together with [I-D.ietf-lamps-cmp-updates] that makes
   the cmp registry entry permanent. Please add a reference of this
   document to the Well-Known URIs [1] IANA registry for that entry.


8.3.  URIs

   [1] https://www.iana.org/assignments/well-known-uris/well-known-
   uris.xhtml


Thanks
Mohit

On Tue, Oct 26, 2021 at 7:51 AM Brockhaus, Hendrik 
mailto:hendrik.brockh...@siemens.com>> wrote:

Thank you for the suggestion. I am fine with it.

Hendrik



Von: Daniel Migault mailto:mglt.i...@gmail.com>>
Gesendet: Dienstag, 26. Oktober 2021 16:29


Thanks for the follow-up Handrik. I will put that into the shepherd. Given that 
draft submission is closed, the drafts will be roughly sent at the same time to 
our ADs, so the timing looks fine.



Then, I am wondering what we should put into the IANA section. I am tempted to 
put instead the text below. I am happy with any other alternatives.



This Internet draft references the .well-known/cmp temporary IANA registry 
[Link to: 
https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml<https://protect2.fireeye.com/v1/url?k=fe0a6103-a1915805-fe0a2198-86ee86bd5107-981714ff6a88f6b0&q=1&e=085826df-8b5b-4acc-9251-32e8a7cc6efe&u=https%3A%2F%2Feur01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.iana.org%252Fassignments%252Fwell-known-uris%252Fwell-known-uris.xhtml%26data%3D04%257C01%257Chendrik.brockhaus%2540siemens.com%257C36a90282ef44486bac4708d9988cfe0c%257C38ae3bcd95794fd4addab42e1495d55a%257C1%257C0%257C637708554252515691%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%26sdata%3DO%252Fd1DH4xsH5%252F%252FkzqUmFzhTjOK92PqSoMNBVsjyixOJE%253D%26reserved%3D0>].
 This document is expected to be published together with 
[I-D.ietf-lamps-cmp-updates] that makes .well-known/cmp registry permanent.



Yours,
Daniel



On Tue, Oct 26, 2021 at 2:15 AM Brockhaus, Hendrik 
mailto:hendrik.brockh...@siemens.com>> wrote:





Von: Daniel Migault mailto:mglt.i...@gmail.com>>
Gesendet: Dienstag, 26. Oktober 2021 02:22



On Mon, Oct 25, 2021 at 5:18 PM Mohit Sahni 
mailto:mohit06...@gmail.com>> wrote:





D) I will add a note for IANA mentioning this. Can you please review if this 
note looks good?



This Internet draft references the .well-known/cmp temporary IANA registry 
[Link to: 
https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml<https://protect2.fireeye.com/v1/url?k=2af65ff7-756d66f1-2af61f6c-86ee86bd5107-4da7b38d59847a6c&q=1&e=085826df-8b5b-4acc-9251-32e8a7cc6efe&u=https%3A%2F%2Feur01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.iana.org%252Fassignments%252Fwell-known-uris%252Fwell-known-uris.xhtml%26data%3D04%257C01%257Chendrik.brockhaus%2540siemens.com%257C36a90282ef44486bac4708d9988cfe0c%257C38ae3bcd95794fd4addab42e1495d55a%257C1%257C0%257C637708554252525686%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%26sdata%3DNgaodceiFq5QSaEz%252B%252FydswbVU7kuWtt7rIVlYAtAzfs%253D%26reserved%3D0>].
 Please add a reference of this draft to the .well-known/cmp registry and if 
this draft is published before [I-D.ietf-lamps-cmp-updates] please make the 
.well-known/cmp registry permanent

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

[Daniel Migault]

looks good to me.
Yours,
Daniel

From: Ace  on behalf of Mohit Sahni 
Sent: Tuesday, October 26, 2021 10:57 AM
To: Brockhaus, Hendrik 
Cc: Saurabh Tripathi ; Russ Housley 
; david.von.ohe...@siemens.com 
; Daniel Migault ; Ace Wg 

Subject: Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

Hi Daniel,
Does this text look good to you?

   This document references the cmp, a temporary entry, in the Well-
   Known URIs [1] IANA registry.  This document is expected to be
   published together with [I-D.ietf-lamps-cmp-updates] that makes
   the cmp registry entry permanent. Please add a reference of this
   document to the Well-Known URIs [1] IANA registry for that entry.


8.3.  URIs

   [1] https://www.iana.org/assignments/well-known-uris/well-known-
   uris.xhtml


Thanks
Mohit

On Tue, Oct 26, 2021 at 7:51 AM Brockhaus, Hendrik 
mailto:hendrik.brockh...@siemens.com>> wrote:

Thank you for the suggestion. I am fine with it.

Hendrik



Von: Daniel Migault mailto:mglt.i...@gmail.com>>
Gesendet: Dienstag, 26. Oktober 2021 16:29


Thanks for the follow-up Handrik. I will put that into the shepherd. Given that 
draft submission is closed, the drafts will be roughly sent at the same time to 
our ADs, so the timing looks fine.



Then, I am wondering what we should put into the IANA section. I am tempted to 
put instead the text below. I am happy with any other alternatives.



This Internet draft references the .well-known/cmp temporary IANA registry 
[Link to: 
https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml<https://protect2.fireeye.com/v1/url?k=fe0a6103-a1915805-fe0a2198-86ee86bd5107-981714ff6a88f6b0&q=1&e=085826df-8b5b-4acc-9251-32e8a7cc6efe&u=https%3A%2F%2Feur01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.iana.org%252Fassignments%252Fwell-known-uris%252Fwell-known-uris.xhtml%26data%3D04%257C01%257Chendrik.brockhaus%2540siemens.com%257C36a90282ef44486bac4708d9988cfe0c%257C38ae3bcd95794fd4addab42e1495d55a%257C1%257C0%257C637708554252515691%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%26sdata%3DO%252Fd1DH4xsH5%252F%252FkzqUmFzhTjOK92PqSoMNBVsjyixOJE%253D%26reserved%3D0>].
 This document is expected to be published together with 
[I-D.ietf-lamps-cmp-updates] that makes .well-known/cmp registry permanent.



Yours,
Daniel



On Tue, Oct 26, 2021 at 2:15 AM Brockhaus, Hendrik 
mailto:hendrik.brockh...@siemens.com>> wrote:





Von: Daniel Migault mailto:mglt.i...@gmail.com>>
Gesendet: Dienstag, 26. Oktober 2021 02:22



On Mon, Oct 25, 2021 at 5:18 PM Mohit Sahni 
mailto:mohit06...@gmail.com>> wrote:





D) I will add a note for IANA mentioning this. Can you please review if this 
note looks good?



This Internet draft references the .well-known/cmp temporary IANA registry 
[Link to: 
https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml<https://protect2.fireeye.com/v1/url?k=2af65ff7-756d66f1-2af61f6c-86ee86bd5107-4da7b38d59847a6c&q=1&e=085826df-8b5b-4acc-9251-32e8a7cc6efe&u=https%3A%2F%2Feur01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.iana.org%252Fassignments%252Fwell-known-uris%252Fwell-known-uris.xhtml%26data%3D04%257C01%257Chendrik.brockhaus%2540siemens.com%257C36a90282ef44486bac4708d9988cfe0c%257C38ae3bcd95794fd4addab42e1495d55a%257C1%257C0%257C637708554252525686%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%26sdata%3DNgaodceiFq5QSaEz%252B%252FydswbVU7kuWtt7rIVlYAtAzfs%253D%26reserved%3D0>].
 Please add a reference of this draft to the .well-known/cmp registry and if 
this draft is published before [I-D.ietf-lamps-cmp-updates] please make the 
.well-known/cmp registry permanent based on this draft's publication.



That seems fine to me. They will probably ask for something else or remove the 
text, but we have avoided running through the cracks.



[Bro] I updated the CMP Updates and the Lightweight CMP Profile drafts 
yesterday and asked the LAMPS chairs for WGLC. The CMP Algorithms draft already 
passed WGLC.

BTW, I discussed with Russ, that we would like to publish the three CMP related 
drafts with consecutive RFC numbers.



Hendrik




--

Daniel Migault

Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

[Daniel Migault]

Thanks for the follow-up Handrik. I will put that into the shepherd. Given
that draft submission is closed, the drafts will be roughly sent at the
same time to our ADs, so the timing looks fine.

Then, I am wondering what we should put into the IANA section. I am tempted
to put instead the text below. I am happy with any other alternatives.

This Internet draft references the .well-known/cmp temporary IANA registry
[Link to:
https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml
<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fwell-known-uris%2Fwell-known-uris.xhtml&data=04%7C01%7Chendrik.brockhaus%40siemens.com%7C2bbd6c1b1f314c91356608d99816ab79%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637708046625686656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=EE1ke%2FeqXN5RpTikRqMsgMz%2BPv8w0sgOxPiqN5JywTY%3D&reserved=0>].
This document is expected to be published together with
[I-D.ietf-lamps-cmp-updates]
that makes .well-known/cmp registry permanent.

Yours,
Daniel

On Tue, Oct 26, 2021 at 2:15 AM Brockhaus, Hendrik <
hendrik.brockh...@siemens.com> wrote:

>
>
>
>
> *Von:* Daniel Migault 
> *Gesendet:* Dienstag, 26. Oktober 2021 02:22
>
>
>
> On Mon, Oct 25, 2021 at 5:18 PM Mohit Sahni  wrote:
>
>
>
>
>
> D) I will add a note for IANA mentioning this. Can you please review if
> this note looks good?
>
>
>
> This Internet draft references the .well-known/cmp temporary IANA registry
> [Link to:
> https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fwell-known-uris%2Fwell-known-uris.xhtml&data=04%7C01%7Chendrik.brockhaus%40siemens.com%7C2bbd6c1b1f314c91356608d99816ab79%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637708046625686656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=EE1ke%2FeqXN5RpTikRqMsgMz%2BPv8w0sgOxPiqN5JywTY%3D&reserved=0>].
> Please add a reference of this draft to the .well-known/cmp registry and if
> this draft is published before [I-D.ietf-lamps-cmp-updates] please make the
> .well-known/cmp registry permanent based on this draft's publication.
>
>
>
> That seems fine to me. They will probably ask for something else or remove
> the text, but we have avoided running through the cracks.
>
>
>
> [Bro] I updated the CMP Updates and the Lightweight CMP Profile drafts
> yesterday and asked the LAMPS chairs for WGLC. The CMP Algorithms draft
> already passed WGLC.
>
> BTW, I discussed with Russ, that we would like to publish the three CMP
> related drafts with consecutive RFC numbers.
>
>
>
> Hendrik
>


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

[Daniel Migault]

Thanks. I am ready to push the next version to the IESG.

Thank you all for moving this document.

Yours
Daniel

On Mon, Oct 25, 2021 at 5:30 PM Saurabh Tripathi <
stripa...@paloaltonetworks.com> wrote:

> Hi Mohit,
>
> I am not aware of any IPR.
>
> --Saurabh
>
> On Mon, Oct 25, 2021 at 2:18 PM Mohit Sahni  wrote:
>
>> Hi Daniel,
>>
>> Please find answers to your questions:
>> A) Currently there is an open source implementation to support CMP over
>> CoAP maintained by @David von Oheimb . I
>> believe these do not follow the draft exactly but are based on this draft.
>> Here are github links:
>>
>>- https://github.com/siemens/LightweightCmpRa
>>
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_siemens_LightweightCmpRa&d=DwMFaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=ZOdGf2OQ8EYofyZRMf0bHltv3S89_8OfM7ykqC8-cvA&m=HYATU_g3NfOO8cMsDWF7hUXVleiwuE4kv8hH17Mzk5c&s=Ck7iZwTTMXwZp5qhZJ5UPta4b3n6MeQg97vmgl0nVnE&e=>
>>- https://github.com/siemens/embeddedCMP
>>
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_siemens_embeddedCMP&d=DwMFaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=ZOdGf2OQ8EYofyZRMf0bHltv3S89_8OfM7ykqC8-cvA&m=HYATU_g3NfOO8cMsDWF7hUXVleiwuE4kv8hH17Mzk5c&s=T4mI0MvZMWr3puXUJ9sEy2izdpL1g1cGFeBx5GYJyB4&e=>
>>
>> B) I can confirm that I am not aware of any IPR. Adding @Saurabh Tripathi
>>  to confirm on this side also.
>>
>> C) I generated the document using the xml2rfc v3 tool. The boilerplate is
>> generated by the xml2rfc tool based on xml tags. It could be an issue with
>> the NITS tool or XML2RFC tool, I will try to generate another txt version
>> based on latest version of the tool or fix the issue manually.
>>
>> D) I will add a note for IANA mentioning this. Can you please review if
>> this note looks good?
>>
>> This Internet draft references the .well-known/cmp temporary IANA
>> registry [Link to:
>> https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_assignments_well-2Dknown-2Duris_well-2Dknown-2Duris.xhtml&d=DwMFaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=ZOdGf2OQ8EYofyZRMf0bHltv3S89_8OfM7ykqC8-cvA&m=HYATU_g3NfOO8cMsDWF7hUXVleiwuE4kv8hH17Mzk5c&s=a2BlPpzMwKPT5yrPzFc731SADo9AVmndkKmo_sIKas4&e=>].
>> Please add a reference of this draft to the .well-known/cmp registry and if
>> this draft is published before [I-D.ietf-lamps-cmp-updates] please make the
>> .well-known/cmp registry permanent based on this draft's publication.
>>
>> E) Can you confirm if this change looks good to you?
>> OLD:
>>This document requires a new entry to the CoAP Content-Formats
>>Registry code for the content-type "application/pkixcmp" for
>>transfering CMP transactions over CoAP.
>>
>>Type name: application
>>
>>Subtype name: pkixcmp
>>
>> NEW:
>>This document requires a new entry to the CoAP Content-Formats
>>Registry code for the content-type "application/pkixcmp" for
>>transfering CMP transactions over CoAP from the identifier
>>range 256- reserved for IETF specifications.
>>
>>Type name: application
>>
>>Subtype name: pkixcmp
>>
>>Encoding: Content may contain arbitrary octet
>>values. The octet values are the ASN.1 DER
>>encoding of a PKI message, as defined in the
>>[RFC4210] specifications.
>>
>>Reference: This internet draft and RFC4210
>>
>> Thanks a lot for your help moving this forward.
>>
>> Regards
>> Mohit
>>
>>
>> On Mon, Oct 25, 2021 at 12:37 PM Daniel Migault 
>> wrote:
>>
>>> Hi,
>>>
>>> Here are some information I need to complete the shepherd:
>>>
>>> A.  Do we have existing implementation or intention to implement it.
>>>
>>> B. Can both co-authors confirm they are not aware of any IPR.
>>>
>>> C. The document seems to lack the recommended RFC 2119 boilerplate,
>>> even if
>>>
>>>  it appears to use RFC 2119 keywords -- however, there's a paragraph 
>>> with
>>>  a matching beginning. Boilerplate error?
>>>
>>> D.  .The draft uses .well-known/cmp. .well-known/cmp is indicated as
>>> temporary [iana] and cmp-updates is still a draft. I am not sure we need to
>>> wait for cmp-updates to be published, but if the draft is abandoned we may
>>

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

[Daniel Migault]

On Mon, Oct 25, 2021 at 5:18 PM Mohit Sahni  wrote:

> Hi Daniel,
>
> Please find answers to your questions:
> A) Currently there is an open source implementation to support CMP over
> CoAP maintained by @David von Oheimb . I
> believe these do not follow the draft exactly but are based on this draft.
> Here are github links:
>
>- https://github.com/siemens/LightweightCmpRa
>- https://github.com/siemens/embeddedCMP
>
> great. That is helpful for the shepherd

>
>-
>
> B) I can confirm that I am not aware of any IPR. Adding @Saurabh Tripathi
>  to confirm on this side also.
>
> thanks.

C) I generated the document using the xml2rfc v3 tool. The boilerplate is
> generated by the xml2rfc tool based on xml tags. It could be an issue with
> the NITS tool or XML2RFC tool, I will try to generate another txt version
> based on latest version of the tool or fix the issue manually.
>
> you did good. I was looking at the wrong place. The nits was misleading to
me.


> D) I will add a note for IANA mentioning this. Can you please review if
> this note looks good?
>
> This Internet draft references the .well-known/cmp temporary IANA registry
> [Link to:
> https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml].
> Please add a reference of this draft to the .well-known/cmp registry and if
> this draft is published before [I-D.ietf-lamps-cmp-updates] please make the
> .well-known/cmp registry permanent based on this draft's publication.
>
> That seems fine to me. They will probably ask for something else or remove
the text, but we have avoided running through the cracks.


> E) Can you confirm if this change looks good to you?
> OLD:
>This document requires a new entry to the CoAP Content-Formats
>Registry code for the content-type "application/pkixcmp" for
>transfering CMP transactions over CoAP.
>
>Type name: application
>
>Subtype name: pkixcmp
>
> NEW:
>This document requires a new entry to the CoAP Content-Formats
>Registry code for the content-type "application/pkixcmp" for
>transfering CMP transactions over CoAP from the identifier
>range 256- reserved for IETF specifications.
>
>Type name: application
>
>Subtype name: pkixcmp
>
>Encoding: Content may contain arbitrary octet
>values. The octet values are the ASN.1 DER
>encoding of a PKI message, as defined in the
>[RFC4210] specifications.
>
>Reference: This internet draft and RFC4210
>
> Looks good!

> Thanks a lot for your help moving this forward.
>
> Regards
> Mohit
>
>
> On Mon, Oct 25, 2021 at 12:37 PM Daniel Migault 
> wrote:
>
>> Hi,
>>
>> Here are some information I need to complete the shepherd:
>>
>> A.  Do we have existing implementation or intention to implement it.
>>
>> B. Can both co-authors confirm they are not aware of any IPR.
>>
>> C. The document seems to lack the recommended RFC 2119 boilerplate, even
>> if
>>
>>  it appears to use RFC 2119 keywords -- however, there's a paragraph with
>>  a matching beginning. Boilerplate error?
>>
>> D.  .The draft uses .well-known/cmp. .well-known/cmp is indicated as
>> temporary [iana] and cmp-updates is still a draft. I am not sure we need to
>> wait for cmp-updates to be published, but if the draft is abandoned we may
>> need to indicate IANA that the cmp needs to be moved to permanent after
>> 2022-05-20  - or may be at the publication of this draft. I suggest we add
>> a note in the IANA section which could be removed by IANA or the RFC
>> editor.
>>
>> E. I am not sure the registration of pkiccmp does not need more
>> information. More especially, I see
>>
>> https://www.iana.org/assignments/core-parameters/core-parameters.xhtml#content-formats
>> https://www.rfc-editor.org/rfc/rfc7252.html#section-12.3
>>
>> Please check what is needed and make sure the IANA is correct.
>>
>> Yours,
>> Daniel
>>
>>

-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

[Daniel Migault]

Hi,

Here are some information I need to complete the shepherd:

A.  Do we have existing implementation or intention to implement it.

B. Can both co-authors confirm they are not aware of any IPR.

C. The document seems to lack the recommended RFC 2119 boilerplate, even if

 it appears to use RFC 2119 keywords -- however, there's a paragraph with
 a matching beginning. Boilerplate error?

D.  .The draft uses .well-known/cmp. .well-known/cmp is indicated as
temporary [iana] and cmp-updates is still a draft. I am not sure we need to
wait for cmp-updates to be published, but if the draft is abandoned we may
need to indicate IANA that the cmp needs to be moved to permanent after
2022-05-20  - or may be at the publication of this draft. I suggest we add
a note in the IANA section which could be removed by IANA or the RFC
editor.

E. I am not sure the registration of pkiccmp does not need more
information. More especially, I see
https://www.iana.org/assignments/core-parameters/core-parameters.xhtml#content-formats
https://www.rfc-editor.org/rfc/rfc7252.html#section-12.3

Please check what is needed and make sure the IANA is correct.

Yours,
Daniel
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] interim-2021-ace-13 : ace

[Daniel Migault]

Hi all,

Just a heads-up that we have a interim meeting planned next week. Please
feel free to propose agenda item and upload your presentations.
https://datatracker.ietf.org/meeting/interim-2021-ace-13/session/ace

In my mind, this meeting should enable us to finalize the ongoing WGLCs.
* coap-eap
* cmpv2-coap-transport
* key-groupcomm

as well as progress on the current WG items:
* key-groupcom-oscore
* pusub-profile
* oscore-gm-admin

Yours,
Daniel



-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Publication has been requested for draft-ietf-ace-aif-03

[Daniel Migault via Datatracker]

Daniel Migault has requested publication of draft-ietf-ace-aif-03 as 
Informational on behalf of the ACE working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-ace-aif/


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

[Ace] Fwd: Second Call for Nominations

[Daniel Migault]

Hi,

Please consider helping the nomcom!

Yours,
Daniel

-- Forwarded message -
From: NomCom Chair 2021 
Date: Tue, Oct 5, 2021 at 1:51 PM
Subject: Second Call for Nominations
To: IETF Announcement List 
Cc: 


Hello IETF Community!

Only one week to go and we need everyone's HELP with nominations.

If you go to https://datatracker.ietf.org/nomcom/2021/nominate/
you will notice that:

  -INT, TSV, OPS, and ART have only ONE accepted nomination so far
  -Other positions are not that much better: 2 or 3 accepted
nominations is
   not a lot (TRUST, LLC, Routing, Security)
  -Neither are 10 accepted nominations for 6 open IAB positions

Oh, and nominations close in one week: Monday October 11.

Please take some 10 minutes today (or make it a fun weekend assignment) to
think about
someone who would be a good candidate and nominate them using the above
link. Of course,
self-nominations are encouraged!

For full information, please refer to the previous Call for Nominations
here:
https://datatracker.ietf.org/nomcom/ann/350147/


Thanks,

Gabriel Montenegro
IETF NomCom Chair 2021-22
nomcom-chair-2021 at ietf dot org

___
IETF-Announce mailing list
ietf-annou...@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


-- 
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Re: [Ace] Tuesday 2021-09-14 14:00 UTC

[Daniel Migault]

Great thanks for the feed back!
Yours,
Daniel

From: Ace  on behalf of Cigdem Sengul 

Sent: Tuesday, September 14, 2021 5:28 AM
To: Daniel Migault 
Cc: Ace Wg 
Subject: Re: [Ace] Tuesday 2021-09-14 14:00 UTC

Hello Daniel,
I have a conflict for this meeting tomorrow - I will do my best to join, but I 
will not be able to present any updates from the IETF meeting.
My summary update is: I have received AD-review for the MQTT-TLS profile, and 
received a pub-sub review from Marco. I am working towards addressing both, 
prioritising the MQTT-TLS profile to make sure that it can progress.

Kind regards,
--Cigdem

On Tue, Sep 14, 2021 at 4:02 AM Daniel Migault 
mailto:mglt.i...@gmail.com>> wrote:
Hi,

This is just a heads-up on tomorrow's meeting, so far I only see the groupcomm 
slides;-)

Yours,
Daniel

On Mon, Aug 30, 2021 at 9:39 AM Daniel Migault 
mailto:mglt.i...@gmail.com>> wrote:
Hi,

Please note that we do have an interim meeting on September 14. A potential 
agenda could be:

## Agenda
* Note Well,  agenda bashing
  * minute taker, blue sheet
* Agenda Bashing
* WGLC
  * key-groupcomm
  * cmpv2-coap-transport
  * wg-coap-eap
* Ongoing Work
  * pubsub-profile
  * gm-admin
  * groupcomm-oscore

Feel free to propose any additional topic here:
https://notes.ietf.org/notes-ietf-interim-2021-ace-12-ace
and upload you material here:
https://datatracker.ietf.org/meeting/interim-2021-ace-12/session/ace

Yours,
Logan and Daniel

--
Daniel Migault
Ericsson


--
Daniel Migault
Ericsson
___
Ace mailing list
Ace@ietf.org<mailto:Ace@ietf.org>
https://www.ietf.org/mailman/listinfo/ace
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace