Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : E.804     
  ITU-T A.5 justification information for referenced document OMA-TS-PoC_UserPlane-V2_0-20110802-A in draft E.804
1. Clear description of the referenced document:
Name: OMA-TS-PoC_UserPlane-V2_0-20110802-A
Title: PoC User Plane
2. Status of approval:
All of the documents are approved OMA specifications
3. Justification for the specific reference:
The referred document describes the User Plane signalling procedures for the Push to talk over Cellular (PoC) service over the POC-3, POC-4, POC-10 and POC-12 reference points. This reference is needed for Rec. E.804 to describe the PoC testing.
4. Current information, if any, about IPR issues:
http://openmobilealliance.org/about-oma/policies-and-terms-of-use/intellectual-property-rights/
5. Other useful information describing the "Quality" of the document:
All of the documents are approved OMA specifications
6. The degree of stability or maturity of the document:
The documents are all approved OMA specifications that are undergoing continuing development
7. Relationship with other existing or emerging documents:
None
8. Any explicit references within that referenced document should also be listed:
[3GPP2 S.R0100-0] 3GPP2 S.R0100-0 Push-to-Talk over Cellular (PoC) System Requirements, (v1.0). URL: http://www.3gpp2.org/ /
[OMA Dictionary] “Dictionary for OMA Specifications”, Version 2.3, Open Mobile Alliance™, OMA-ORG-Dictionary-V2_3, URL: http://www.openmobilealliance.org/ /
[OMA_SCR_Rules] "SCR Rules and Procedures”, Version 1.0, Open Mobile Alliance™, OMA-ORG-SCR_Rules_and_Procedures-V1_0, URL: http://www.openmobilealliance.org/ /
[OMA-IM-TS] "Instant Messaging using SIMPLE", Version 1.0, Open Mobile Alliance™, OMA-TS-SIMPLE_IM-V1_0, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-1-UP] "PoC User Plane", Version 1.0, Open Mobile Alliance™, OMA-TS-PoC_UserPlane-V1_0-20060609-A, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-AD] "Push to talk over Cellular (PoC) - Architecture", Version 2.0, Open Mobile Alliance™, OMA-AD_PoC-V2_0, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-CP] "OMA PoC Control Plane", Version 2.0, Open Mobile Alliance™, OMA-TS-PoC_ControlPlane-V2_0, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-DET-PROG-REP] "PoC - PoCV2.0 detailed Discrete Media Transfer Progress Report", Version 2.0, Open Mobile Alliance, OMA-SUP-XSD_poc_detProgressRep-V2_0, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-Document-Mgmt] "OMA PoC Document Management", Version 2.0, Open Mobile Alliance™, OMA-TS-PoC_Document_Management-V2_0, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-FINAL-REP] "PoC - PoCV2.0 Discrete Media Transfer Final Report", Version 2.0, Open Mobile Alliance, OMA-SUP-XSD_poc_finalReport-V2_0, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-IM] "OMA PoC Endorsement of OMA IM TS", Version 2.0, Open Mobile Alliance, OMA-TS-PoC_Endorsement_OMA_IM_TS-V2_0, URL: http://www.openmobilealliance.org/ /
[OMA-PoC-RD] “Push to talk over Cellular 2 Requirements”, Version 2.0, Open Mobile Alliance, OMA-RD-PoC-V2_0, URL: http://www.openmobilealliance.org/ /
[RFC768] IETF RFC 768 (STD 0006): "User Datagram Protocol", August 1980, URL: http://www.ietf.org/rfc/rfc768.txt /
[RFC1305] IETF RFC 1305: "Network Time Protocol (Version 3) Specification, Implementation and Analysis", March 1992. URL: http://www.ietf.org/rfc/rfc1305.txt /
[RFC2119] IETF RFC 2119: "Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997, URL:http://www.ietf.org/rfc/rfc2119.txt /
[RFC2396] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax", August 1998, URL:http://www.ietf.org/rfc/rfc2396.txt [RFC3261] IETF RFC 3261: "SIP: Session Initiation Protocol", June 2002, URL: http://www.ietf.org/rfc/rfc3261.txt /
[RFC3267] IETF RFC 3267: "Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs", June 2002, URL: http://www.ietf.org/rfc/rfc3267.txt /
[RFC3323] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc3323.txt [RFC3489bis] IETF draft-ietf-behave-rfc3489bis (August 2007): "Session Traversal Utilities for (NAT) (STUN)", URL: http://www.ietf.org/internet-drafts/draft-ietf-behave-rfc3489bis-13.txt NOTE: The referenced IETF draft is a work in progress. /
[RFC3550] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications", July 2003, URL: http://www.ietf.org/rfc/rfc3550.txt [RFC3558] IETF RFC 3558: "RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)", June 2003, URL: http://www.ietf.org/rfc/rfc3558.txt /
[RFC4566] IETF RFC 4566: "Session Description Protocol", July 2006, URL: http://www.ietf.org/rfc/rfc4566.txt /
[RFC4975] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)", September 2007, URL: http://www.ietf.org/rfc/rfc4975.txt [TS26.235] 3GPP TS 26.235 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Packet switched conversational multimedia applications; Default codecs (Release 6)", URL: http://www.3gpp.org/ftp/Specs/archive/26_series/26.235/ /
[TS26.236] 3GPP TS 26.236 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Packet switched conversational multimedia applications; Transport protocols (Release 6)", URL: http://www.3gpp.org/ftp/Specs/archive/26_series/26.236/ /
[3GPP2 C.S0047-0] 3GPP2 C.S0047-0 Link-Layer Assisted Service Options for Voice-over-IP: Header Removal (SO60) and Robust Header Compression (SO61), (v1.0). URL: http://www.3gpp2.org/Public_html/specs/index.cfm#tsgc/ /
[RFC2543] IETF RFC 2543: "SIP: Session Initiation Protocol", March 1999, URL: http://www.ietf.org/rfc/rfc2543.txt
9. Qualification of OMA:
Qualification of OMA: OMA is recognized under the provisions of ITU-T Recommendation A.5. Qualifying information is on file in TSB.
10. Other (for any supplementary information):
None
Note: This form is based on Recommendation ITU-T A.5