Oracle® Communication and Mobility Server Administrator Guide Release 10.1.3 Part Number B31497-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 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 3265 Session Initiation Protocol (SIP)-Specific Event Notification
RFC 3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
RFC 3327 Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts
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 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
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 3903 Session Initiation Protocol (SIP) Extension for Event State Publication
RFC 3966 The tel URI for Telephone Numbers
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
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:
"A Model for Presence and Instant Messaging", RFC 2778
"Instant Messaging / Presence Protocol Requirements", RFC 2779
"Session Initiation Protocol (SIP)-Specific Event Notification", RFC 3265
"A Presence Event Package for the Session Initiation Protocol (SIP)", RFC 3856
"A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)", RFC 3857
"An Extensible Markup Language (XML) Based Format for Watcher Information", RFC 3858
"Common Profile for Presence (CPP)", RFC 3859
"Presence Information Data Format (PIDF)", RFC 3863
"Session Initiation Protocol (SIP) Extension for Event State Publication", RFC 3903
"A Presence-based GEOPRIV Location Object Format", RFC 4119
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
draft-ietf-simple-partial-notify
draft-ietf-simple-partial-pidf-format
draft-ietf-simple-partial-publish
"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
draft-ietf-simple-event-filter-funct
draft-ietf-simple-filter-format
Following are the standards and specifications supported by Diameter:
RFC4006 Diameter Credit Control Application
ID-NAS Diameter Network Access Server Application Internet Draft draft-ietf-aaa-diameter-nasreq-17.txt
RCF3589 Diameter command code for third generation partnership project (3GPP) release 5
RFC2975 Introduction to accounting management
RFC3539 Authentication, Authorization and Accounting (AAA) Transport Profile
RFC3588 Diameter Base Protocol
TS23.002 Network architecture
TS23.228 IP Multimedia Subsystem (IMS); Stage 2
TS29.230 Diameter applications; 3GPP specific codes and identifiers
TS29.328 IP Multimedia (IM) Subsystem Sh interface; Signaling flows and message contents
TS29.329 Sh Interface based on the Diameter protocol; Protocol details
TS32.200 Telecommunication management; Charging management; Charging principles
TS32.225 Telecommunication Management; Charging Management; Charging data description for the IP Multimedia Subsystem (IMS)
TS32.240 Telecommunication management; Charging management; Charging architecture and principles
TS32.260 Telecommunication management; Charging Management; IP Multimedia Subsystem (IMS) charging
TS32.299 Telecommunication Management; Charging Management; Diameter charging applications