| Type | Name | Scope | Specification |
|---|---|---|---|
| 0x02 | OBJECT_DELIVERY_TIMEOUT | Track, Object | Section 12.2 |
| 0x04 | MAX_CACHE_DURATION | Track | Section 12.3 |
| 0x06 | SUBGROUP_DELIVERY_TIMEOUT | Track, Object | Section 12.1 |
| 0x0B | IMMUTABLE_PROPERTIES | Track, Object | Section 12.7 |
| 0x0E | DEFAULT_PUBLISHER_PRIORITY | Track | Section 12.4 |
| 0x22 | DEFAULT_PUBLISHER_GROUP_ORDER | Track | Section 12.5 |
| 0x30 | DYNAMIC_GROUPS | Track | Section 12.6 |
| 0x3C | PRIOR_GROUP_ID_GAP | Object | Section 12.8 |
| 0x3E | PRIOR_OBJECT_ID_GAP | Object | Section 12.9 |
| 0x7f * N + 0x9D | Reserved for greasing | Any | Section 14 |
The following table contains provisional registrations for other active drafts in the moq wg. These entries share the same Property Type space as the table above.
| Type | Name | Scope | Specification |
|---|---|---|---|
| 0x06 | TIMESTAMP | Object | draft-ietf-moq-loc |
| 0x08 | TIMESCALE | Track, Object | draft-ietf-moq-loc |
| 0x0A | VIDEO_FRAME_MARKING | Object | draft-ietf-moq-loc |
| 0x0C | AUDIO_LEVEL | Object | draft-ietf-moq-loc |
| 0x0D | VIDEO_CONFIG | Object | draft-ietf-moq-loc |
Endpoints MUST ignore unknown Property types, skipping them according to the Key-Value-Pair encoding; odd types use their length field, even types are skipped by parsing a varint value.
-
MOQ Properties - we wish to define the following registration policies:
-
0x00 to 0x77: Standards Action or IESG Approval (1-byte encoding)
-
0x78 to 0x7F: Reserved for application-specific use (1-byte encoding, no registration permitted)
-
0x80 to 0x37FF: Specification Required (2-byte encoding)
-
0x3800 to 0x3FFF: Reserved for application-specific use (2-byte encoding, no registration permitted)
-
0x4000 to 0x7FFF: Reserved for Mandatory Track Properties (see Section 2.5.1). Properties registered in this range MUST have Track scope; Object scope properties MUST NOT be registered in this range.
-
0x8000 and above: First Come First Served
Code points reserved for application-specific use will never be allocated by IANA. Applications using these values do not need to coordinate with IANA. Note that applications consuming tracks from uncoordinated sources may encounter different semantics for the same code points, creating potential collision risks.
-