├── LICENSE ├── README.md ├── bof-request.md └── charter.md /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2022 moq-wg 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # moq-charter 2 | Charter related work for MOQ 3 | -------------------------------------------------------------------------------- /bof-request.md: -------------------------------------------------------------------------------- 1 | # Name: Media over QUIC 2 | ## Description 3 | 4 | This is merely a placeholder for the BOF request, the details of the charter are currently being developed, so please consider this as heads up for the 5 | Media Over QUIC BOF request. 6 | 7 | Media over QUIC (moq) will work on solution for a simple low-latency 8 | media delivery protocol for ingest and distribution. 9 | This work may address use cases including live streaming, gaming, and 10 | media conferencing and allows efficient scaling. The solution supports 11 | both web browsers and simple devices that don’t contain embedded browsers. 12 | 13 | 14 | ## Required Details 15 | - Status: WG Forming 16 | - Responsible AD: TBD ART AD 17 | - BOF proponents: TBD 18 | - BOF chairs: TBD 19 | - Number of people expected to attend: 70 20 | - Length of session (1 or 2 hours): 2 hours 21 | - Conflicts (whole Areas and/or WGs) 22 | - Chair Conflicts: TBD 23 | - Technology Overlap: TBD 24 | - Key Participant Conflict: TBD 25 | 26 | ## Information for IAB/IESG 27 | 28 | At IETF 113 a non WG forming BOF was held to discuss the idea of delivering media over QUIC which had participations from 58 pariticipants across realtime conferencing and streaming industries. Since then 29 | we have had 2 follow up meetings to work on the charter, each bringing in contributions from around 30 participants. There has been consistent interest and participation in this work from developers associated with widely deployed applications including Twitter, Facebook, Webex, Haivison. 30 | 31 | 32 | ## Agenda 33 | - TBD 34 | 35 | ## Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc. 36 | - Mailing List: https://www.ietf.org/mailman/listinfo/moq 37 | - Draft charter: https://github.com/moq-wg/moq-charter 38 | - Relevant drafts: Following drafts were submitted as part of Non WG forming BOF at IETF113 39 | - https://datatracker.ietf.org/doc/draft-gruessing-moq-requirements/ 40 | - https://datatracker.ietf.org/doc/draft-jennings-moq-quicr-proto/ 41 | - https://www.ietf.org/archive/id/draft-lcurley-warp-00.html 42 | - https://www.ietf.org/archive/id/draft-kpugin-rush-01.html 43 | - https://www.ietf.org/archive/id/draft-jennings-moq-quicr-arch-00.html -------------------------------------------------------------------------------- /charter.md: -------------------------------------------------------------------------------- 1 | #Charter for Media over QUIC 2 | 3 | Media over QUIC (moq) will develop a simple low-latency media delivery solution 4 | for ingest and distribution of media. This solution addresses use cases including live 5 | streaming, gaming, and media conferencing and will scale efficiently. The 6 | solution will be implementable in both browser and non-browser endpoints. 7 | 8 | The work focuses on building protocol mechanisms for publication of media 9 | and means to identify and receive the media. 10 | 11 | The media publication protocol will enable sending 12 | media including audio, video, and timed metadata, such as closed captions and 13 | cue points. 14 | The common protocol for publishing media for ingest and distribution 15 | will support: 16 | 17 | * one or more media formats, 18 | * an interoperable way to indicate the media and the media format being sent, 19 | * rate adaptation strategies based on changing codec rates, changing chosen media 20 | encoding/qualities, or other mechanisms 21 | * cache friendly media mechanisms 22 | 23 | The mechanism to name and receive media will enable: 24 | 25 | * Requesting the server start sending media related to given point in the stream 26 | * Selection of desired encoding (choosing language, bit rate, etc) 27 | 28 | Media will be mapped onto underlying QUIC mechanisms (QUIC streams and/or 29 | QUIC datagrams) and can be used over raw QUIC or WebTransport. 30 | 31 | The proposed solution will provide extensibility for supporting different media 32 | formats and will support multiple media types and media encodings. 33 | 34 | 35 | The working group will define MoQ so that the media publication protocol 36 | can leverage coordinating relays, caches, or replication points wherever applicable 37 | to improve the delivery performance. 38 | 39 | The solution will specify a simple method for clients to authenticate 40 | to the relay or server to transmit or receive media. 41 | Media will be encrypted at the transport layer using the standard QUIC 42 | mechanisms. Media content may be end-to-end encrypted in certain use cases, 43 | where the "end-to-end" keys are available to media sources and consumers, but 44 | not relays. Even when media is content end-to-end encrypted, the relays can access 45 | metadata needed for caching (such as timestamp), making media forwarding 46 | decisions (such as drop or delay under congestion), and so on. Such media 47 | metadata will be authenticated and integrity-protected end-to-end. Mechanisms 48 | for establishing keys for these end-to-end protections are outside the scope of 49 | this group. 50 | 51 | This working group will not propose changes to the underlying QUIC transport, but 52 | may propose requirements for QUIC extensions to the QUIC WG. This working group 53 | will not define signaling mechanisms for discovery of relay or media producers 54 | or consumers. 55 | 56 | This working group will coordinate with the QUIC, WebTransport, and MOPS working 57 | groups as needed. It will liaise with MPEG Systems WG, DASH Industry Forum, and 58 | W3C WebTransport as appropriate. 59 | 60 | ## Milestones 61 | 62 | * WG adoption of Protocol Specification for Common Media Publication Protocol 63 | over QUIC 64 | * WG adoption of Protocol Specification for the use of the Datagram Extension for Media 65 | Publication Protocol over QUIC 66 | * WG adoption of Protocol Specification for Media Subscription Protocol over 67 | QUIC 68 | * WG adoption of Architecture Specification for a Common Media Delivery 69 | Protocol over QUIC 70 | * WG adoption of Usecases and Requirements document for Media Delivery over QUIC 71 | - decision about whether to forward to IESG for publication to be made later, by 72 | WG consensus 73 | * Forward Protocol Specification for Common Media Publication Protocol over QUIC 74 | draft to IESG 75 | * Forward Protocol Specification for the use of the Datagram Extension for Media Publication 76 | Protocol over QUIC draft to IESG 77 | * Forward Protocol Specification for Media Subscription Protocol over QUIC draft 78 | to IESG 79 | * Forward Architecture Specification for a Common Media Delivery Protocol over 80 | QUIC draft to IESG 81 | --------------------------------------------------------------------------------