Minutes interim-2021-ace-08: Tue 10:00
minutes-interim-2021-ace-08-202105111000-00

ACE Interim Meeting
2021-05-11 14:00 - 15:00 UTC
---

* datatracker
https://datatracker.ietf.org/meeting/interim-2021-ace-08/session/ace * webex 
https://ietf.webex.com/ietf/j.php?MTID=m4d4b02389fc6f862663a7ac103a9d9ce *
codimd https://codimd.ietf.org/notes-ietf-interim-2021-ace-08-ace

## Agenda
* [Note
Well](https://docs.google.com/presentation/d/1YuUzfZMbMijvpJJkBoOkppOaec4u2S_TMBowo1EqQVY/edit#slide=id.g9edff33b62_0_0),
 agenda bashing
  * minute taker, blue sheet
* Agenda Bashing
* Adressing comments from the IESG review:
  * draft-ietf-ace-dtls-authorize
  * draft-ietf-ace-oauth-authz
  * draft-ietf-ace-oscore-profile

* WGLC
  * draft-ietf-ace-key-groupcomm
  * draft-ietf-ace-aif
  * draft-ietf-ace-cmpv2-coap-transport

* Ongoing Work
  * draft-ietf-ace-wg-coap-eap
  * draft-ietf-ace-mqtt-tls-profile
  * draft-ietf-ace-pubsub-profile

# WG Status:
In IESG:
* draft-ietf-ace-coap-est (RFC Ed)
* draft-ietf-ace-oauth-params (Approved)
* draft-ietf-ace-dtls-authorize (IESG review)
  * 1 question to Francesca: clarification of comment.
  * 1 question to Murray: access token is updated and replaced or replace.
  Discussion regarding MUST or SHOULD.
* draft-ietf-ace-oauth-authz (IESG review)
  * 1 DISCUSS from Francesca: one issue remains to be disccussed. One major
  comment regarding combination of the profiles. * bitstring in the draft is
  expressed in base64 -> need Ludwig final's say. * Table 8 is great. Francesca
  requests an equivalent Table for acceptable parameters for the request.
  Discussion between Francesca and Ludwig. No strong opinion. * Combination of
  profiles: The last paragraph mentions profiles can be combined. The current
  document does not mention how the combination is occurring. Francesca
  recommends removing the sentences. Cigdem, Carsten argue that the document
  cannot describe how the combination can occur with non existent profiles.
  MQTT is not an exact combination, but is the closest example we have. There
  are 3 sentences regarding the combination. The 1st needs to explain the term
  "combination" and that a profile needs to specify how the combination is
  made. The 3rd sentence may be removed.
* draft-ietf-ace-oscore-profile (IESG review)
  * Comments addressed. Waiting for approval from Ben. Daniel: Any confirmation
  from ADs which made the comment? Francesca: Still waiting for Roman to lift
  the DISCUSS.

In WGLC
* draft-ietf-ace-key-groupcomm
  * GS committed to review for WGLC. Cigdem offers to review next month. Marco
  will submit an updated version soon (-12). See slide meeting slide deck.
* draft-ietf-ace-aif
  * one comment to review a new version is expected.
* draft-ietf-ace-cmpv2-coap-transport
  * one review has been made.

AD evaluation:
* draft-ietf-ace-mqtt-tls-profile
  * registration of application/ace+json media type

Ongoing work:
* draft-ietf-ace-wg-coap-eap
  * Carsten: The server should be allowed to use any URI they want. No
  requirement to enumerate the steps. Each time new state, there is a location
  of the resource in the response. The current procedure should just be an
  example. * Carsten: Make clear to make a distinction between what CoAP is
  performing and what is part of the CoAP-EAP protocol.

 * draft-ietf-ace-pubsub-profile
   * Cigdem: No new updates since the latest interim meeting.