Minutes interim-2022-mls-01: Thu 10:00
minutes-interim-2022-mls-01-202202031000-00

#572 - Split the Group State section into Group Context and Transcript Hashes

https://github.com/mlswg/mls-protocol/pull/572
* Small, pretty purely editorial change
* Merged


#573 - Remove endpoint_id

https://github.com/mlswg/mls-protocol/pull/573
* Some discussion confirming that we don't need endpoint_id 
* Largely based on the continuity requirements in #509
* Merged


#575 - Split LeafNode from KeyPackage

https://github.com/mlswg/mls-protocol/pull/575
* Concern about not having lifetime scoping on prepublished LeafNode signature
* General invariant: Signature always covers (a) lifetime or (b) group ID
* Note alternative architecture proposed in #539 with two types of leaves
  * Could have a helper object to capture commonality between the two types
* TODO(Richard) - Revise PR 


#523 - Move wire_format to a separate tagged-union structure MLSMessage

https://github.com/mlswg/mls-protocol/pull/523
* On the question of whether to cover all types:
  * Yes, the MLSMessage wrapper should be universal
  * ... including covering KeyPackage
* TODO(Théophile) Update PR then ready to merge


#576 - Make credential succession checking the AS's job

https://github.com/mlswg/mls-protocol/pull/576
* Depends on what the boundary of the AS is:
  * Checking credential is valid
  * Also checking (credential -> credential) transitions
* Moving this check to KP validation section would make it clearer
* TODO(Konrad) - Make a PR


#574 - Consistency between "optional that MUST contain a value when …" and selects

https://github.com/mlswg/mls-protocol/pull/574
* General agreement that selects are clearer than optionals
* TODO(Théophile) - Make a PR


#559 - Remove redundant nodes from the tree

https://github.com/mlswg/mls-protocol/pull/559
* Clarified the defition of "redundant" using some pictures
* TODO(Marta) - Make a PR


#577 - Add message/mls MIME Type

https://github.com/mlswg/mls-protocol/pull/577
* General agreement that this is a fine thing to do
* Should this be a section or a separate doc?
* How should we handle versioning?
  * Internal to the protocol, e.g., field in MLSMessage
  * Field in the MIME type
  * MIME type per version
* TODO(Rohan) - Make a PR