All Proposals - Table View

This document does not contain any technical proposals. It is a Change Request (CR) document that proposes adding a missing cancelled property to the ServiceScheduleDescription schema in the OpenAPI YAML for 3GPP TS 26.517, but it does not contain any explicitly marked "Proposal" sections.

This document does not contain any proposals. It is a Change Request (CR) document that adds a missing cancellation property to the OpenAPI YAML schema in 3GPP TR 26.517, but no text is explicitly marked as a "Proposal" anywhere in the document.

This document does not contain any proposals. It is a Change Request (CR) document that contains only a technical specification change (adding a missing cancellation property to an OpenAPI YAML schema), with no sections explicitly marked as "Proposal" in any of the formats described.

Proposal 1: Define Conformance profiles parameter for an MBS Distribution Session.

Proposal 2: Clarify that the Transport security protection flag for an MBS Distribution Session is provisioned by the MBS Application Provider or (in the special case of a User Service Announcement Channel) by the MBSF.

Proposal 3: Define optional MIME media type accompanying Object acquisition identifiers for an MBS Distribution Session that are mandatory in the case of Application Service Entry Point documents.

Proposal 4: Define Object repair back-off parameters for an MBS Distribution Session and clarify that the Object Repair feature is not provisioned by the MBS Application Provider.

Proposal 5: Define new reference point MBS‑1 used by MBS Application Provider to retrieve User Service Announcement bundles from the MBSF.

Proposal 6: Clarify that the full User Service Announcement exposed in the User Service advertisement notification is the User Service Announcement bundle.

Proposal 1: Define Conformance profiles parameter for an MBS Distribution Session.

Proposal 2: Clarify that the Transport security protection flag for an MBS Distribution Session is provisioned by the MBS Application Provider or (in the special case of a User Service Announcement Channel) by the MBSF.

Proposal 3: Define optional MIME media type accompanying Object acquisition identifiers for an MBS Distribution Session that are mandatory in the case of Application Service Entry Point documents.

Proposal 4: Define Object repair back-off parameters for an MBS Distribution Session and clarify that the Object Repair feature is not provisioned by the MBS Application Provider.

Proposal 5: Define new reference point MBS‑1 used by MBS Application Provider to retrieve User Service Announcement bundles from the MBSF.

Proposal 6: Clarify that the full User Service Announcement exposed in the User Service advertisement notification is the User Service Announcement bundle.

This document does not contain any explicitly marked proposals (i.e., no text formatted as "Proposal X:", "Proposal:", "Proposal.", or similar variants). It is a Change Request (CR) document that describes technical changes and clarifications to 3GPP TR 26.502, but does not include any sections explicitly labeled as proposals.

Change to:

[77] ETSI TS 103 973: "Coded Multisource Media Format (CMMF) for Content Distribution and Delivery".

This document contains no technical proposals. It is a Change Request (CR) document that proposes an editorial/correction update to a reference entry in 3GPP TS 26.512, specifically removing "V1.1.3 (Stable Draft)" from reference [77] to align with the latest published version of ETSI TS 103 973. There are no explicitly marked proposals in this document.