761

DoD Standard Transmission Control Protocol

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc761.txt

768

User Datagram Protocol

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc768.txt

1157

A Simple Network Management Protocol (SNMP)

Yes

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)

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

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

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

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)

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc1907.txt

2183

Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field

Yes (Platform)

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

Converged Application Server supports TLS. See

http://www.ietf.org/rfc/rfc2246.txt

2460

Internet Protocol, Version 6 (IPv6) Specification

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2460.txt

2543

SIP: Session Initiation Protocol (v1)

Yes

Converged Application Server supports backward compatibility as described in this specification. See

http://www.ietf.org/rfc/rfc2543.txt

2571

An Architecture for Describing SNMP Management Frameworks

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2571.txt

2572

Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2572.txt

2573

SNMP Applications

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2573.txt

2574

User-based Security Model (USM) for version 3 of theSimple Network Management Protocol (SNMPv3)

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2574.txt

2575

View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2575.txt

2576

Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2576.txt

2616

Hypertext Transfer Protocol — HTTP 1.1

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2616.txt

2617

HTTP Authentication: Basic and Digest Access Authentication

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2617.txt

2782

A DNS RR for specifying the location of services (DNS SRV)

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2782.txt

2786

Diffie-Helman USM Key Management Information Base and Textual Convention

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2786.txt

2806

URLs for Telephone Calls

Yes

Converged Application Server supports applications that conform to this specification. 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 Converged Application Server. See

http://www.ietf.org/rfc/rfc2848.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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc2976.txt

3204

MIME media types for ISUP and QSIG Objects

Yes (Platform)

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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3261.txt

3262

Reliability of Provisional Responses in the Session Initiation Protocol (SIP)

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3262.txt

3263

Session Initiation Protocol (SIP): Locating SIP Servers

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3263.txt

3264

An Offer/Answer Model with Session Description Protocol (SDP)

Yes (Platform)

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)

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)

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

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)

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)

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)

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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3325.txt

3326

The Reason Header Field for the Session Initiation Protocol (SIP)

Yes (Platform)

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)

Converged Application Server supports applications that conform to this specification. 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)

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)

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3372.txt

3420

Internet Media Type message/sipfrag

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3420.txt

3428

Session Initiation Protocol (SIP) Extension for Instant Messaging

Yes

Converged Application Server supports applications that conform to this specification. 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)

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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3515.txt

3524

Mapping of Media Streams to Resource Reservation Flows

Yes (Platform)

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)

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)

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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3581.txt

3589

Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3589.txt

3588

Diameter Base Protocol

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3588.txt

3605

Real Time Control Protocol (RTCP) attribute in Session Description Protocol ((SDP)

Yes (Platform)

Converged Application Server supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3605.txt

3608

Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration.

Yes (Platform)

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

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)

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)

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)

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)

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

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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3725.txt

3761

The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3761.txt

3764

Enumservice Registration for Session Initiation Protocol (SIP) Addresses-of-Record

Yes (Platform)

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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3824.txt

3826

The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3826.txt

3840

Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)

Yes (Platform)

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)

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)

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)

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)

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)

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

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3903.txt

3911

The Session Initiation Protocol (SIP) "Join" Header

Yes (Platform)

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3911.txt

3959

The Early Session Disposition Type for the Session Initiation Protocol (SIP)

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc3959.txt

3960

Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)

Yes (Platform)

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)

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)

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)

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc4244.txt

4320

Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction

Yes

Converged Application Server supports applications that conform to this specification, specifically including:

• If the application or proxy does not respond to a non-invite request before TimerE reaches T2, the container responds with a 100 TRYING message.

• A system parameter that disables this feature: -Dwlss.send100ForNonInviteTransaction=false. The parameter is true by default.

See http://www.ietf.org/rfc/rfc4320.txt

4321

Problems Identified Associated with the Session Initiation Protocol's (SIP) Non_INVITE Transaction

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc4321.txt

4474

Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)

Yes

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc4474.txt.

4483

A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages

Yes (Platform)

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc4483.txt.

4566

SDP: Session Description Protocol

Yes

Converged Application Server supports applications that consume or generate SDP. See

http://www.ietf.org/rfc/rfc4566.txt

4916

Connected Identity in the Session Initiation Protocol (SIP)

Yes

See

https://tools.ietf.org/html/rfc4916

5393

Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies

Partial

Converged Application Server supports the Max-Breadth Header portion of JSR 359, section 12.2.11, “Max-Breadth Check." Specifically, it implements a Max-Breadth header to limit the number of parallel forks that can be made on a SIP request by the downstream proxies. See

https://www.jcp.org/en/jsr/detail?id=359

5626

Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)

Yes

Converged Application Server supports JSR 359, section 17.4, “Managing Client Initiated Connections," which includes support for UDP/TCP with cluster deployment. See

https://www.jcp.org/en/jsr/detail?id=359

5630

The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)

Yes

When a proxy sends a request using a SIPS Request-URI and receives one of:

• A 3XX response with a SIP Contact header field

• A 416 response

• A 480 (Temporarily Unavailable) response with a Warning header with warn-code 380 "SIPS Not Allowed" response

The proxy must not recurse on the response. In this case, the proxy should forward the best response instead of recursing. This allows the UAC to take the appropriate action.

When a proxy sends a request using a SIP Request-URI and receives:

• A 3XX response with a SIPS Contact header field

• A 480 (Temporarily Unavailable) response with a Warning header with warn-code 381 "SIPS Required"

The proxy must not recurse on the response. In this case, the proxy should forward the best response instead of recursing. This allows the UAC to take the appropriate action.

5888

The Session Description Protocol (SDP) Grouping Framework

Yes (Platform)

Converged Application Server supports applications that conform to this specification. See

http://www.ietf.org/rfc/rfc5888.txt

5806

Diversion Indication in SIP

Yes

Converged Application Server supports applications that conform to this specification. See

https://datatracker.ietf.org/doc/rfc5806/

5954

Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261

Yes

Converged Application Server now includes a task to update the equals() and hashcode() methods of SipURIImpl based on this RFC. See

https://tools.ietf.org/html/rfc5954

6026

Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests

Yes

Converged Application Server supports applications that conform to this specification. See

https://tools.ietf.org/html/rfc6026

6141

Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)

Yes

Converged Application Server supports applications that conform to this specification. See

https://tools.ietf.org/html/rfc6141

6665

SIP-Specific Event Notification

Yes

Converged Application Server supports applications that conform to this specification. See

https://tools.ietf.org/html/rfc6665

draft-donovan-mmusic-183-00

SIP 183 Session Progress Message Draft

Yes (Platform)

Converged Application Server supports applications that conform to this specification. See

https://datatracker.ietf.org/doc/html/draft-donovan-mmusic-183-00

draft-reeder-snmpv3-usm-3desede-00

Extension to the User-Based Security Model (USM) to Support Triple-DES EDE in "Outside" CBC Mode

Yes

See

https://tools.ietf.org/id/draft-reeder-snmpv3-usm-3desede-00.txt