| Oracle® Communication and Mobility Server Administrator's Guide 10g Release 3 (10.1.3) Part Number E12656-01 |
|
|
View PDF |
| Oracle® Communication and Mobility Server Administrator's Guide 10g Release 3 (10.1.3) Part Number E12656-01 |
|
|
View PDF |
This appendix lists the protocols, RFCs, and standards supported by Oracle Communication and Mobility Server in the following sections:
The following sections list the RFCs, drafts, and specification requests supported by the OCMS SIP Servlet container:
RFC 2246 The TLS Protocol
RFC 2543 SIP: Session Initiation Protocol
RFC 2782 A DNS RR for Specifying the Location of Services (DNS SRV)
RFC 2806 URLs for Telephone Calls
RFC 2976 The SIP INFO Method
RFC 3261 SIP: Session Initiation Protocol
RFC 3262 Reliability of Provisional Responses in the Session Initiation Protocol
RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers
RFC 3264 An Offer/Answer Model with the Session Description Protocol (SDP)
RFC 3265 Session Initiation Protocol (SIP)-Specific Event Notification
RFC 3266 Support for IPv6 in Session Description Protocol (SDP)
RFC 3311 The Session Initiation Protocol (SIP) UPDATE Method
RFC 3312 Integration of Resource Management and Session Initiation Protocol (SIP)
RFC 3323 A Privacy Mechanism for the Session Initiation Protocol (SIP)
RFC 3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
RFC 3326 The Reason Header Field for the Session Initiation Protocol (SIP)
RFC 3327 Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts
RFC 3420 Internet Media Type message/sipfrag
RFC 3428 Session Initiation Protocol (SIP) Extension for Instant Messaging
RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)
RFC 3489 STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
RFC 3515 The Session Initiation Protocol (SIP) Refer Method
RFC 3556 Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth
RFC 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
RFC 3605 Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)
RFC 3608 Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration
RFC 3665 Session Initiation Protocol (SIP) Basic Call Flow Examples
RFC 3725 Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)
RFC 3761 The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
RFC 3824 Using E.164 numbers with the Session Initiation Protocol (SIP)
RFC 3840 Caller Preferences for the Session Initiation Protocol (SIP): partial support
RFC 3891 The Session Initiation Protocol (SIP) "Replaces" Header
RFC 3903 Session Initiation Protocol (SIP) Extension for Event State Publication
RFC 3911 The Session Initiation Protocol (SIP) "Join" Header
RFC 3959 The Early Session Disposition Type for the Session Initiation Protocol (SIP)
RFC 3966 The tel URI for Telephone Numbers
RFC 4028 Session Timers in the Session Initiation Protocol (SIP)
RFC 4320 Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction
RFC 4321 Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE Transaction
RFC 4483 A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages
campen-sipping-stack-loop-detect An Efficient Loop Detection Algorithm for SIP Proxies
lawrence-maxforward-problems Problems with Max-Forwards Processing (and Potential Solutions)
ietf-sip-connect-reuse Connection Reuse in the Session Initiation Protocol (SIP)
sparks-sipping-max-breadth Limiting the Damage from Amplification Attacks in SIP Proxies
ietf-sip-fork-loop-fix Addressing an Amplification Vulnerability in Forking Proxies
JSR 116 SIP Servlet 1.0
The following sections list protocols, RFCs, drafts, and standards supported by the OCMS Presence Server and its components:
RFC 2778 A Model for Presence and Instant Messaging
RFC 2779 Instant Messaging / Presence Protocol Requirements
RFC 3265 Session Initiation Protocol (SIP)-Specific Event Notification
RFC 3856 A Presence Event Package for the Session Initiation Protocol (SIP)
RFC 3857 A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)
RFC 3858 An Extensible Markup Language (XML) Based Format for Watcher Information
RFC 3859 Common Profile for Presence (CPP)
RFC 3863 Presence Information Data Format (PIDF)
RFC 3903 Session Initiation Protocol (SIP) Extension for Event State Publication
RFC 4119 A Presence-based GEOPRIV Location Object Format
RFC 4479 A Data Model for Presence
RFC 4480 RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
RFC 4481 Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals
RFC 4825 The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Note:
RFC 4825 is partially supported. There is no support for partial document manipulation (XPATH).4827 An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents
The following drafts are transparent to the server, but are important for clients. These drafts are specifically referenced in composition policies such as the OMA composition policy.
"RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", draft-ietf-simple-rpid-10
"CIPID: Contact Information in Presence Information Data Format", draft-ietf-simple-cipid-07
"Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Presence Information for Past and Future Time Intervals", draft-ietf-simple-future-05
Partial Publish and Partial Notify:
"Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information", draft-ietf-simple-partial-notify
"Presence Information Data format (PIDF) Extension for Partial Presence", draft-ietf-simple-partial-pidf-format
"Publication of Partial Presence Information",draft-ietf-simple-partial-publish
"Presence Authorization Rules", draft-ietf-simple-presence-rules-10
"OMA Extensions to the Presence Data Model", OMA-TS-Presence_SIMPLE-V1_0-20051122-C
"OMA extensions to geopriv common policy", OMA-TS-XDM_Core-V1_0-20051122-C
"OMA Extensions to Presence Rules", OMA-TS-Presence_SIMPLE_XDM-V1_0-20051122-C
"The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)", draft-ietf-simple-xcap-08
"A Framework for Session Initiation Protocol User Agent Profile Delivery", draft-ietf-sipping-config-framework-07
"A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages", draft-ietf-sip-content-indirect-mech-05
Exceptions:
The current XCAP application does not support partial document put or get.
"A Document Format for Expressing Privacy Preferences", draft-ietf-geopriv-common-policy-05
"Presence Authorization Rules", draft-ietf-simple-presence-rules-04
draft-ietf-geopriv-common-policy-05
"A Data Model for Presence", draft-ietf-simple-presence-data-model-07
"A Processing Model for Presence", draft-rosenberg-simple-presence-processing-model-01
[urn:oma:params:xml:ns:pidf:oma-pres] OMA extensions to the presence data model (OMA-TS-Presence_SIMPLE-V1_0-20051122-C)
[urn:oma:params:xml:ns:common-policy] OMA extensions to geopriv common policy (OMA-TS-XDM_Core-V1_0-20051122-C)
[urn:oma:params:xml:ns:pres-rule] OMA extensions to presence rules (OMA-TS-Presence_SIMPLE_XDM-V1_0-20051122-C)
"An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents", draft-ietf-simple-xcap-pidf-manipulation-usage-02
