moq Interim Notes

21 October 2022

Chairs: Ted Hardie, Alan Frindell
Note Taker: James Gruessing

Agenda

Welcome

Logistics questions:

• Will the WG use Github and, if so, which style?
  Consensus: Nobody advocating against Github, with Github with issues
  being the preferred approach for decision tracking
• Will the WG use Slack?
  Ted: If we choose a channel it won't be used for design but for
  interop and interpretation of specification
  Ted: Strong concerns about message retention
  Ted: If design team want to use Slack unofficially, that's okay, but
  chairs will find an alternative of archiving this chat or using
  Zuilip
  Action for Chairs: Confirm position of Zuilip within the IETF, and
  find means to get archive (or digest) of a Slack channel/space
  • If so, is this a side channel for developer discussion, or a
    broader channel?

Working group document questions

• For the Use Case document, there is some adjustment to track to the
  charter--discussion on how to make progress there (a.k.a. collect
  contributors and reviewers)

  • Authors plan to update the draft
  • • will remove things that are not in charter

• Which technical questions do we want to tackle for the London
  meeting?

Consensus: Media Formats, relay support

• Who will be putting in personal drafts and on what topics?

  • Spencer and James: req & use case
  • Luke Curley: core protcol
  • Hang Shi: draft on design space
  • • how to choose name, CDN tree topology, overlay routing etc
  • • analysis of many design options

  • Maxime Sharabayko

  • • lookiking at metrics on live streaming

  • Xavier de Foy:

  • • type of relay at ingress point of wireless networks
  • • how it will deal with congestion
  • • type of metadata needed

• Moving on to Warp +Rush + Quc draft by Luke

  • nice work on bringing together common ground of all the main
    protocol drafts