Meeting: TSGS4_135_India | Agenda Item: 10.8
7 documents found
[FS_DCE_MED] Key Issue Description for Interworking with MTSI
Observation 1) In TS 23.228, IMS AS modifies the endpoint type of the application data channel from P2P to P2A to support IMS DC interworking via DC AS.
Observation 2) SDP answerer for the application DC shall not change the value of endpoint parameter in "a=3gpp-req-app" attribute.
Observation 3) DC application in the originating DCMTSI UE is required to identify the interworking mode is enabled to distinguish the actual target endpoint for a specific media flow.
IMS Bootstrap Data Channel Restart
Proposal 1: Include this topic in a key issue description in draft TR 26.823.
Proposal 2: Include the above potential solutions to that key issue in draft TR 26.823.
[FS_DCE_MED] Key Issue #4 - Description for Automatic Resumption
This document does not contain any proposals. The document provides descriptive text for Key Issue #4 regarding Automatic Resumption but does not include any sections explicitly marked as "Proposal" with any of the standard formats.
The Discussion of using a single DC stream for Multi DC Application Data Transmission
Proposal to study whether to use and how to enhance DC to support multiple DC Application Data Transmission in a single DC stream.
[FS_DC_MED] Proposed TR 26.814 skeleton
Looking through this 3GPP document (TR 26.814 V0.0.1), I can see that it is a template/skeleton document for a Technical Report on "Study on enhancements to IMS Data Channel" for Release 20.
After carefully reviewing the entire document, I can confirm that there are no proposals present in this document.
The document contains: - Standard front matter and copyright information - A table of contents - Section headers for key issues (KI#1 through KI#6) - Empty subsections for "Issue statement", "Solution direction", "Potential specification impacts", and "Open points and dependencies" - Empty sections for "Conclusions and recommended way forward" - Empty annexes
All the substantive sections are empty placeholders with no actual content, and therefore no proposals have been written yet in this document.
[FS_DC_MED] Draft time plan
Proposal: Adopt the proposed time plan for the Data Channel Enhancements Study Item (FS_DCE_MED) as outlined in this document.
[FS_DCE_MED] External resources for DC applications
Based on my analysis of the document, there are no formal proposals explicitly marked with the standard proposal formats (e.g., "Proposal X:", "Proposal:", "Proposal.", etc.).
The document discusses solutions and includes a "Way forward" section that describes recommendations and clarifications for SA4 to consider, but these are not formatted as formal proposals in the standard 3GPP proposal format.