Simple Time Over MoQ Protocol (STOMP)
draft-shamim-moq-time-00

Network Working Group                                         S. Pirzada
Internet-Draft                                                     Cisco
Intended status: Informational                           21 October 2024
Expires: 24 April 2025

                 Simple Time Over MoQ Protocol (STOMP)
                         draft-shamim-moq-time-00

Abstract

   This document describes Simple Time Over MoQ Protocol (STOMP), a
   protocol for sending the local time and, optionally, location
   information via Media Over QUIC Transport (MOQT) protocol
   [I-D.ietf-moq-transport].

   Such information enables observing endpoints to measure latencies and
   monitor health of MOQT delivery network from different geographical
   locations.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 24 April 2025.

Copyright Notice

   Copyright (c) 2024 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Pirzada                   Expires 24 April 2025                 [Page 1]
Internet-Draft                    stomp                     October 2024

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Notation and Conventions . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Naming  . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Data Objects  . . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  STOMP Servers Discovery . . . . . . . . . . . . . . . . . . .   3
     6.1.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   4
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   When sending media over the internet, it is often useful to measure
   latency.  This applies to both streaming media (for example Netflix)
   or real time interactive media (for example Webex or Zoom).

   The goal of this specification is to allow a set of time servers to
   periodically report timing and other optional metadata, over Media
   Over QUIC Transport (MOQT).  This allows clients to connect to
   several of these STOMP servers to measure latencies across the relay
   networks from different geographical locations.  This also enables
   monitoring the health of a relay network.

2.  Requirements Notation and Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD","SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   {{!RFC2119}}.

3.  Terminology

   TODO

Pirzada                   Expires 24 April 2025                 [Page 2]
Internet-Draft                    stomp                     October 2024

4.  Naming

   The value of <moq://stomp.moq.arpa/v1/> is defined in this
   specification as the first entry into the Track Namespace tuple.  The
   track name identifies the device (i.e.  STOMP server) reporting the
   data objects {{data}}. The track name is identified with <deviceID>.

   When sending data over one or more QUIC streams, an additional tuple
   entry, "stream", is specified, with the full track name having the
   following components:

   ("moq://stomp.moq.arpa/v1","stream",<deviceID>)

   When sending data over QUIC datagrams, the track namespace tuple has
   following 2 entries:

   ("moq://stomp.moq.arpa/v1","datagram")

   and the full track name for the same has the following components:

   ("moq://stomp.moq.arpa/v1","datagram",<deviceID>)

   The MOQT GroupID is a randomly generated 62 bit number that is
   updated every minute.  Within a MOQT group, a new stomp data object
   {{data}} is generated periodically over a randomized range between
   0.8 and 1.2 seconds.  MOQT ObjectID starts with 0 and is incremented
   by 1 for every object published within a given group.

5.  Data Objects

   STOMP data objects are JSON [RFC8259] objects with the following
   fields:

   1.  The timestamp as UNIX Epoch time in microseconds since 00:00:00
       UTC on 1 January 1970.

   2.  Optional fields capturing the longitude and latitude, represented
       as signed integer.  If omitted, these values correspond to the
       most recent object 0 that had any these values.

6.  STOMP Servers Discovery

   Endpoints can learn about STOMP servers available within a given
   relay network.  They do so by sending SUBSCRIBE_ANNOUNCE message to
   with Track Namespace Prefix set to <moq://stomp.moq.arpa/v1/>.

Pirzada                   Expires 24 April 2025                 [Page 3]
Internet-Draft                    stomp                     October 2024

6.1.  Examples

   Here is an example of Object ID 0 data, represented in JSON format
   [RFC8259].

   Group 10135, Object ID 0
   {
     "timestamp": 1729538287,
     "latitude" : 18.25,
     "longitude" : -63.1667
   }

   Below is another example that shows data as continuation from the
   previous example, where the redundant information is omitted.

   Group 18902, Object ID 0
   {
     "timestamp": 1729539981
   }

7.  Normative References

   [I-D.ietf-moq-transport]
              Curley, L., Pugin, K., Nandakumar, S., Vasiliev, V., and
              I. Swett, "Media over QUIC Transport", Work in Progress,
              Internet-Draft, draft-ietf-moq-transport-07, 21 October
              2024, <https://datatracker.ietf.org/doc/html/draft-ietf-
              moq-transport-07>.

8.  Informative References

   [RFC8259]  Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
              Interchange Format", STD 90, RFC 8259,
              DOI 10.17487/RFC8259, December 2017,
              <https://www.rfc-editor.org/info/rfc8259>.

Appendix A.  Acknowledgments

   Thanks to Cullen Jennings and Suhas Nandakumar for contributions and
   suggestions to this specification.

Author's Address

   Shamim Pirzada
   Cisco
   United States of America
   Email: spirzada@cisco.com

Pirzada                   Expires 24 April 2025                 [Page 4]