> For the complete documentation index, see [llms.txt](https://changes.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changes.ishare.eu/cab-and-deepdive-meetings/cab-meetings/2026/2026-01-28.md).

# 2026-01-28

This CAB meeting will be held on January 28, 2026 at 10:00 CET. If you would like to be invited for this meeting, or if you would like to add a topic to the agenda, please reach out to us through available channels.

### Agenda

1. Welcome + introduce new participants
2. Update on the implementation of RFCs on the [RFC board](https://gitlab.com/ishare-foundation/cab/rfc/-/boards)
   1. Walk through of the [Release 3.0](https://framework.ishare.eu/)
   2. Walk through of the Releases [2.1.1](https://framework.ishare.eu/version-2.1.1) and [2.2](https://framework.ishare.eu/version-2.2) updates
3. Work Items 
   1. [RFC032](https://gitlab.com/ishare-foundation/cab/rfc/-/issues/14): Framework legal changes
   2. [RFC049](https://gitlab.com/ishare-foundation/cab/rfc/-/issues/16): Signing the HTTP payload
   3. [RFC063](https://gitlab.com/ishare-foundation/cab/rfc/-/issues/31): Remove JSON wrapper in API request and response
   4. [RFC048](https://gitlab.com/ishare-foundation/cab/rfc/-/issues/17): Improve change and release management process
   5. [RFC044](https://gitlab.com/ishare-foundation/cab/rfc/-/issues/2): Accommodate iSHARE Satellite without distributed ledger
4. Advice on newly incoming (Proposed) RFCs
   1. RFC073: iSHARE framework flavours
   2. RFC070: Using WWW-Authenticate header as an access token endpoint discovery mechanism
   3. RFC068: Non-repudiation improvements
   4. RFC071: DSGO proposals to improve roles and authorisations
   5. RFC072: Authentication Assurance Levels
5. RFC prioritisation: discuss priority on the [RFC board](https://gitlab.com/ishare-foundation/cab/rfc/-/boards)
6. Wrap up and outlook to next quarter


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://changes.ishare.eu/cab-and-deepdive-meetings/cab-meetings/2026/2026-01-28.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.