**Session Date/Time:** 06 Nov 2023 16:30

```markdown
# lake

## Summary

The Lake working group session at IETF 118 covered the status of several drafts, including ad-hoc, traces, and odds. Implementer feedback was presented on the odds draft. Additionally, two new individual submissions were discussed: one on implementation considerations and another on application process coordination. A draft on grease was also introduced.

## Key Discussion Points

*   **Ad-hoc and Traces Drafts:** Status update on ad-hoc and traces drafts currently in the RFC editor queue. A temporary setback with ad-hoc due to an overlap in IANA registrations regarding cozy header maps was discussed and resolved. Test vector updates and invalid trace inclusions were highlighted for the traces draft.
*   **Lake Odds Draft:** Implementer feedback on the Lake Odds draft (zero-touch authorization) was presented, focusing on credential handling (by value vs. by reference), voucher validation, and EAD item processing. Questions were raised about the need for an EAD3 item and the trust model related to ID credentials.
*   **Implementation Considerations Draft:** Discussion on an individual submission outlining implementation considerations for ad-hoc, covering invalidation of sessions and keys, trust models for authentication credentials learned on the fly, and side processing steps for credential validation and EAD item processing. The terminology used for trust levels was questioned.
*   **Application Process Coordination Draft:** Presentation of a draft focused on defining identifiers for application profiles, examples of usage, a canonical representation of profiles in CBOR, and the potential definition of well-known application profiles. Open questions remain regarding the attributes that an application profile should cover.
*   **Grease Draft:** Introduction of a draft proposing the use of "grease" (adding dummy extensions) for ad-hoc to ensure that extension points (EAD items, surface weights) are properly handled by implementations and middleboxes.

## Decisions and Action Items

*   **Ad-hoc Draft:** Paul will send a mail to the RFC editor to put the ad-hoc draft back in the queue.
*   **Lake Odds Draft:**  Create an issue tracker entry to document the discussion point on the trust of device credentials.
*   **Implementation Considerations Draft:**  Explore additional updates, then do a call for adoption. The terminology used for trust levels in the draft will be reviewed.
*   **Interim Meeting:** Chairs will send a mail to the list to determine preferences for an interim meeting.

## Next Steps

*   The ad-hoc and traces drafts are expected to return to the RFC editor queue shortly.
*   Authors will incorporate feedback into the Lake Odds draft.
*   The chairs will send a mail to the mailing list soliciting feedback on all presented drafts and determining the interest in an interim meeting.
*   Continue discussion on the mailing list for the application process coordination and grease drafts.