Standards Alignment

The following sections describe how Oracle Communications Converged Application Server complies with various specifications and RFCs:

Overview of Oracle Communications Converged Application Server Standards Alignment

Oracle Communications Converged Application Server is developed with special attention to Internet Engineering Task Force and 3rd Generation Partnership Project specifications. Feature development is prioritized according to general market trends, both observed and predicted. In cases where certain specifications are obsolete or where Internet drafts are formalized as ‘Request For Comments’ standards, Oracle Communications Converged Application Server places priority on compliance with those specifications. In cases where specifications are part of a larger release plan, as with the 3GPP, Oracle prioritizes compliance with the latest ratified release (in this case, Release 6). This should not be presumed to mean that the product is not compliant with subsequent versions of component specifications, although this document does not summarize compliance with those specifications.

Java Sun Recommendation (JSR) Standards Compliance

Oracle Communications Converged Application Server is compliant with Java EE version 5.0 and the corresponding Java EE component specifications. See Standards Support in the Oracle WebLogic Server 10g Release 3 documentation for more details.

Oracle Communications Converged Application Server is further enhanced by the addition of a SIP Servlet container defined by JSR 289: “SIP Servlet API.”

Oracle Communications Converged Application Server has executed all related Test Compatibility Kits (TCKs) and has met the formal requirements established by Sun Microsystems for formal public statements of compliance.

IETF RFC Compliance

The following table lists the Oracle Communications Converged Application Server level of compliance to common Internet Engineering Task Force (IETF) Requests for Comment (RFCs) and Internet drafts. The level of compliance is defined as follows:

Yes—Indicates that Oracle Communications Converged Application Server container directly supports the feature or specification.

Yes (Platform)—Indicates Oracle Communications Converged Application Server can host applications or components that implement the RFC. However, the RFC or feature has no impact on the transaction layer of the protocol or on the behavior of the SIP Servlet container.

Table 5-1 Oracle Communications Converged Application Server IETF Compliance
RFC or Specification Number	Title	Compliant?	Additional Information
761	DoD Standard Transmission Control Protocol	Yes	See http://www.ietf.org/rfc/rfc761.txt
768	User Datagram Protocol	Yes	See http://www.ietf.org/rfc/rfc768.txt
1157	A Simple Network Management Protocol (SNMP)	Yes	Oracle Communications Converged Application Server supports SNMP V2c traps. See http://www.ietf.org/rfc/rfc1157.txt
1847	Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted	Yes (Platform)	Oracle Communications Converged Application Server supports applications that consume or generate signed or encrypted multipart MIME objects. See http://www.ietf.org/rfc/rfc1847.txt
1901	Introduction to Community-based SNMPv2	Yes	Oracle Communications Converged Application Server supports SNMP V2c traps. See http://www.ietf.org/rfc/rfc1901.txt
1905	Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)	Yes	Oracle Communications Converged Application Server supports SNMP V2c traps. See http://www.ietf.org/rfc/rfc1905.txt
1906	Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)	Yes	Oracle Communications Converged Application Server supports SNMP over both TCP and UDP. See http://www.ietf.org/rfc/rfc1906.txt
1907	Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)	Yes (Platform)	See http://www.ietf.org/rfc/rfc1907.txt
2183	Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc2183.txt
2246	The TLS Protocol Version 1.0	Yes	Oracle Communications Converged Application Server supports TLS. See http://www.ietf.org/rfc/rfc2246.txt
2327	SDP: Session Description Protocol	Yes	Oracle Communications Converged Application Server supports applications that consume or generate SDP. See http://www.ietf.org/rfc/rfc2327.txt
2460	Internet Protocol, Version 6 (IPv6) Specification	Yes	See http://www.ietf.org/rfc/rfc2460.txt
2543	SIP: Session Initiation Protocol (v1)	Yes	Oracle Communications Converged Application Server supports backward compatibility as described in this specification. See http://www.ietf.org/rfc/rfc2543.txt
2616	Hypertext Transfer Protocol -- HTTP 1.1	Yes	See http://www.ietf.org/rfc/rfc2616.txt
2617	HTTP Authentication: Basic and Digest Access Authentication	Yes	See http://www.ietf.org/rfc/rfc2617.txt
2782	A DNS RR for specifying the location of services (DNS SRV)	Yes	See http://www.ietf.org/rfc/rfc2782.txt
2806	URLs for Telephone Calls	Yes	See http://www.ietf.org/rfc/rfc2806.txt
2848	The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services	Yes (Platform)	Note that implementing PINT services implies a pre-IMS architecture. Although Oracle favors the 3GPP/TISPAN architecture and approach to class 4/5 Service Emulation and does not advocate PINT, it is possible to implement PINT service elements using Oracle Communications Converged Application Server. See http://www.ietf.org/rfc/rfc2848.txt
2916	E.164 number and DNS	Yes	See http://www.ietf.org/rfc/rfc2916.txt
2960	Stream Control Transmission Protocol	Yes	SCTP supported only for Diameter traffic. See http://www.ietf.org/rfc/rfc2960.txt
2976	The SIP INFO Method	Yes	See http://www.ietf.org/rfc/rfc2976.txt
3204	MIME media types for ISUP and QSIG Objects	Yes (Platform)	Oracle Communications Converged Application Server does not directly consume or generate ISUP and QSIG objects, but it supports applications that consume or generate these objects. See http://www.ietf.org/rfc/rfc3204.txt
3261	SIP: Session Initiation Protocol	Yes	See http://www.ietf.org/rfc/rfc3261.txt
3262	Reliability of Provisional Responses in the Session Initiation Protocol (SIP)	Yes	See http://www.ietf.org/rfc/rfc3262.txt
3263	Session Initiation Protocol (SIP): Locating SIP Servers	Yes	See http://www.ietf.org/rfc/rfc3263.txt
3264	An Offer/Answer Model with Session Description Protocol (SDP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3264.txt
3265	Session Initiation Protocol (SIP)-Specific Event Notification	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3265.txt
3268	Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)	Yes (Platform)	Oracle Communications Converged Application Server supports cryptographic services, but specific algorithms that are used are subject to local availability and export control. See http://www.ietf.org/rfc/rfc3268.txt
3311	The Session Initiation Protocol (SIP) UPDATE Method	Yes	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3311.txt
3312	Integration of Resource Management and Session Initiation Protocol (SIP).	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3312.txt
3313	Private Session Initiation Protocol (SIP) Extensions for Media Authorization	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3313.txt
3323	A Privacy Mechanism for the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3323.txt
3325	Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks	Yes	See http://www.ietf.org/rfc/rfc3325.txt
3326	The Reason Header Field for the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3326.txt
3327	Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts.	Yes (Platform)	See http://www.ietf.org/rfc/rfc3327.txt
3351	User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3351.txt
3372	Session Initiation Protocol for Telephones (SIP-T): Context and Architectures	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3372.txt
3388	Grouping of Media Lines in the Session Description Protocol (SDP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3388.txt
3428	Session Initiation Protocol (SIP) Extension for Instant Messaging	Yes	See http://www.ietf.org/rfc/rfc3428.txt
3455	Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3455.txt
3515	The Session Initiation Protocol (SIP) Refer Method.	Yes	See http://www.ietf.org/rfc/rfc3515.txt
3524	Mapping of Media Streams to Resource Reservation Flows	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3524.txt
3556	Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3556.txt
3578	Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification, but it does not provide an ISUP interface. See http://www.ietf.org/rfc/rfc3578.txt
3581	An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing	Yes	See http://www.ietf.org/rfc/rfc3581.txt
3589	Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5	Yes	See http://www.ietf.org/rfc/rfc3589.txt
3588	Diameter Base Protocol	Yes	See http://www.ietf.org/rfc/rfc3588.txt
3608	Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration.	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification, but it does not provide a means of storing the ServiceRoute established during registration. This functionality can be implemented as part of the application. See http://www.ietf.org/rfc/rfc3608.txt
3665	Session Initiation Protocol (SIP) Basic Call Flow Examples.	Yes	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3665.txt
3666	Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3666.txt
3680	A Session Initiation Protocol (SIP) Event Package for Registrations	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3680.txt
3689	General Requirements for Emergency Telecommunication Service (ETS)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3689.txt
3690	IP Telephony Requirements for Emergency Telecommunication Service (ETS)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3690.txt
3702	Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP)	Yes	Oracle Communications Converged Application Server version supports JDBC and LDAP. See http://www.ietf.org/rfc/rfc3702.txt
3725	Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)	Yes	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3725.txt
3764	Enumservice Registration for Session Initiation Protocol (SIP) Addresses-of-Record	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3764.txt
3824	Using E.164 numbers with the Session Initiation Protocol (SIP)	Yes	See http://www.ietf.org/rfc/rfc3824.txt
3840	Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3840.txt
3841	Caller Preferences for the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3841.txt
3853	S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3853.txt
3891	The Session Initiation Protocol (SIP) 'Replaces' Header	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3891.txt
3892	The Session Initiation Protocol (SIP) Referred-By Mechanism	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3892.txt
3893	Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3893.txt
3903	Session Initiation Protocol (SIP) Extension for Event State Publication	Yes	See http://www.ietf.org/rfc/rfc3903.txt
3911	The Session Initiation Protocol (SIP) “Join” Header	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3911.txt
3960	Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3960.txt
3966	The tel URI for Telephone Numbers	Yes	See http://www.ietf.org/rfc/rfc3966.txt
4028	Session Timers in the Session Initiation Protocol (SIP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4028.txt
4032	Update to the Session Initiation Protocol (SIP) Preconditions Framework	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4032.txt
4244	An Extension to the Session Initiation Protocol (SIP) for Request History Information	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4244.txt
4474	Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)	Yes	See http://www.ietf.org/rfc/rfc4474.txt.
4483	A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4483.txt.
4825	The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4825.txt
draft-levy-sip-diversion-08	Diversion Indication in SIP	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=6002
draft-donovan-mmusic-183-00	SIP 183 Session Progress Message Draft	Yes (Platform)	Oracle Communications Converged Application Server supports applications that conform to this specification. See https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=4308
draft-ietf-sip-gruu-15	Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)	Yes	See http://www.ietf.org/internet-drafts/draft-ietf-sip-gruu-15.txt

3GPP R6 Specification Conformance

Table 5-2, 3GPP R6 Specification Conformance, on page 5-13 summarizes the ability of Oracle Communications Converged Application Server to support implementation of the enablers or application functions identified by each applicable 3GPP Release 6 specification.

Other than the exceptions noted, Oracle Communications Converged Application Server does not impose any restrictions on implementing applications or functions that are compliant with those associated with the Application Server entity described in the specification. In some cases, applications must implement support for SIP methods or headers. The default behavior of the Oracle Communications Converged Application Server Sip Servlet Container is to pass unrecognized headers, request methods and payloads to SIP Servlets using normal SIP Servlet API procedures.

Specification	Comments
3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2 (Release 6)”	No comments.
3GPP TS 24.229: “IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 6)”	Oracle Communications Converged Application Server does not enforce the requirement that only one p-charging-function-address header per SIP request as described in sub-section 5.7.1.2. Oracle Communications Converged Application Server does enforce uniqueness. Oracle Communications Converged Application Server does not provide privacy support as described in sub-section 5.7.3.
3GPP TS 23.141: “Presence Service; Architecture and Functional description (Release 6)”	Oracle Communications Converged Application Server does not natively support the Ph (MAP), Pl (LIF-MLP), Px (DIAMETER Cx/Dx), Pg (phase 4, 3GPP Release 5),Pc (CAMEL phase 4, 3GPP Release 5) or Pr, Pk and Pp (RADIUS) reference points. Oracle Communications Converged Application Server does not support IPv6 as required for the Presence User Agent (Peu) reference point as required in sub-section 4.3.1.
3GPP TS 23.218: “IP Multimedia (IM) session handling; IM call model; Stage 2 (Release 6)”	No comments.
3GPP TS 24.247 “Messaging using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (Release 6)”	Oracle Communications Converged Application Server does not provide support for the Message Session Relay Protocol (MSRP), although it is presumed that an MSRP relay will typically be implemented as a Media Resource Function in the IMS architecture.
3GPP TS 24.841: “Presence service based on Session Initiation Protocol (SIP); Functional models, information flows and protocol details (Release 6)”	Oracle Communications Converged Application Server does not provide support for IETF RFC 3310: “Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)”.
3GPP TS 24.109: “Bootstrapping interface (Ub) and Network application function interface (Ua); Protocol details (Release 6)”	Oracle Communications Converged Application Server does not provide support for IETF RFC 3310: “Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)”. Oracle Communications Converged Application Server supports the ‘X-3GPP-Asserted-Identity extension-header’ for use in applying access control and authorization constraints within the integrated security framework.
3GPP TS 29.328: “IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents”	No comments.
3GPP TS 29.329: “Sh interface based on the Diameter protocol; Protocol details”	No comments.
3GPP TS 32.299: “Telecommunication management; Charging management; Diameter charging applications”	No comments.
3GPP TS 33.222: “Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) (Release 6)”	Oracle Communications Converged Application Server supports the Application Server role in the GAA.

Technical Product Description

Standards Alignment

Overview of Oracle Communications Converged Application Server Standards Alignment

Java Sun Recommendation (JSR) Standards Compliance

IETF RFC Compliance

3GPP R6 Specification Conformance