3 RFC 3588 Compliance

This chapter describes Oracle Communications Evolved Communications Application Server's compliance with the IETF RFC 3588 document.

RFC 3588 Compliance

Table 3-1 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the IETF document RFC 3588, "Diameter Base Protocol."

Table 3-1 RFC 3588 Compliance

Section Number Section Title Product Release Release caveats

1

Introduction

7.0.0

NA

1.1

Diameter Protocol

7.0.0

NA

1.1.1

Description of the Document Set

7.0.0

NA

1.2

Approach to Extensibility

7.0.0

NA

1.2.1

Defining New AVP Values

7.0.0

NA

1.2.2

Creating New AVPs

7.0.0

NA

1.2.3

Creating New Authentication Applications

7.0.0

NA

1.2.4

Creating New Accounting Applications

7.0.0

NA

1.2.5

Application Authentication Procedures

7.0.0

NA

1.3

Terminology

7.0.0

NA

2

Protocol Overview

7.0.0

NA

2.1

Transport

7.0.0

NA

2.1.1

SCTP Guidelines

7.0.0

NA

2.2

Securing Diameter Messages

7.0.0

NA

2.3

Diameter Application Compliance

7.0.0

NA

2.4

Application Identifiers

7.0.0

NA

2.5

Connections vs. Sessions

7.0.0

NA

2.6

Peer Table

7.0.0

NA

2.7

Realm-Based Routing Table

7.0.0

NA

2.8

Role of Diameter Agents

7.0.0

NA

2.8.1

Relay Agents

7.0.0

NA

2.8.2

Proxy Agents

7.0.0

NA

2.8.3

Redirect Agents

7.0.0

NA

2.8.4

Translation Agents

7.0.0

NA

2.9

End-to-End Security Framework

7.0.0

Only TLS or IPSec security is used.

2.10

Diameter Path Authorization

7.0.0

NA

3

Diameter Header

7.0.0

NA

3.1

Command Codes

7.0.0

NA

3.2

Command Code ABNF specification

7.0.0

NA

3.3

Diameter Command Naming Conventions

7.0.0

NA

4

Diameter AVPs

7.0.0

NA

4.1

AVP Header

7.0.0

NA

4.2

Basic AVP Data Formats

7.0.0

NA

4.3

Derived VP Data Formats

7.0.0

NA

4.4

Grouped AVP Values

7.0.0

NA

4.4.1

Example AVP with a Grouped Data type

7.0.0

NA

4.5

Diameter Base Protocol AVPs

7.0.0

NA

5

Diameter Peers

7.0.0

NA

5.1

Peer Connections

7.0.0

NA

5.2

Diameter Peer Discovery

7.0.0 (Partial)

Only static configuration of peers is supported.

5.3

Capabilities Exchange

7.0.0

NA

5.3.1

Capabilities-Exchange-Request

7.0.0

NA

5.3.2

Capabilities-Exchange-Answer

7.0.0

NA

5.3.3

Vendor-Id AVP

7.0.0

NA

5.3.4

Firmware-Revision AVP

7.0.0

NA

5.3.5

Host-IP-Address AVP

7.0.0

NA

5.3.6

Supported-Vendor-Id AVP

7.0.0

NA

5.3.7

Product-Name AVP

7.0.0

NA

5.4

Disconnecting Peer connections

7.0.0

NA

5.4.1

Disconnect-Peer-Request

7.0.0

NA

5.4.2

Disconnect-Peer-Answer

7.0.0

NA

5.4.3

Disconnect-Cause AVP

7.0.0

NA

5.5

Transport Failure Detection

7.0.0

NA

5.5.1

Device-Watchdog-Request

7.0.0

NA

5.5.2

Device-Watchdog-Answer

7.0.0

NA

5.5.3

Transport Failure Algorithm

7.0.0

NA

5.5.4

Failover and Failback Procedures

7.0.0

NA

5.6

Peer State Machine

7.0.0

NA

5.6.1

Incoming connections

7.0.0

NA

5.6.2

Events

7.0.0

NA

5.6.3

Actions

7.0.0

NA

5.6.4

The Election Process

7.0.0

NA

6

Diameter message processing

7.0.0

NA

6.1

Diameter Request Routing Overview

7.0.0

NA

6.1.1

Originating a Request

7.0.0

NA

6.1.2

Sending a Request

7.0.0

NA

6.1.3

Receiving Requests

7.0.0

NA

6.1.4

Processing Local Requests

7.0.0

NA

6.1.5

Request Forwarding

7.0.0

NA

6.1.6

Request Routing

7.0.0

NA

6.1.7

Reidrecting requests

7.0.0

NA

6.1.8

Relaying and Proxying Requests

7.0.0

NA

6.2

Diameter Answer Processing

7.0.0

NA

6.2.1

Processing received Answers

7.0.0

NA

6.2.2

Relaying and Proxying Answers

7.0.0

NA

6.3

Origin-Host AVP

7.0.0

NA

6.4

Origin-Realm AVP

7.0.0

NA

6.5

Destination-Host AVP

7.0.0

NA

6.6

Destination-Realm AVP

7.0.0

NA

6.7

Routing AVPs

7.0.0

NA

6.7.1

Route-Record AVP

7.0.0

NA

6.7.2

Proxy-Info AVP

7.0.0

NA

6.7.3

Proxy-Host AVP

7.0.0

NA

6.7.4

Proxy-State AVP

7.0.0

NA

6.8

Auth-ApplicationNAId AVP

7.0.0

-

6.9

Acct-Application-Id AVP

7.0.0

NA

6.10

Inband-Security-Id AVP

7.0.0

NA

6.11

Vendor-Specific-Application-Id AVP

7.0.0

NA

6.12

Redirect-Host AVP

7.0.0 (Partial)

OCECAS diameter client treats redirects as generic errors.

6.13

Redirect-Host-Usage AVP

7.0.0 (Partial)

OCECAS diameter client treats redirects as generic errors.

6.14

Redirect-Max-Cache-Time AVP

7.0.0 (Partial)

OCECAS diameter client treats redirects as generic errors.

6.15

E2E-Sequence AVP

7.0.0

NA

7

Error Handling

7.0.0

NA

7.1

Result-Code AVP

7.0.0

NA

7.1.1

Informational

7.0.0

NA

7.1.2

Success

7.0.0

NA

7.1.3

Protocol Errors

7.0.0

NA

7.1.4

Transient Failures

7.0.0

NA

7.1.5

Permanent Failures

7.0.0 (Partial)

OCECAS treats Permanent and Transient Failures the same, and Control Flow logic may dictate that the request is repeated.

7.2

Error Bit

7.0.0

NA

7.3

Error-Message AVP

7.0.0

Out-Of-The-Box configuration does not have the storing of this AVP configured.

7.4

Error-Reporting-Host AVP

7.0.0

NA

7.5

Failed-AVP AVP

7.0.0

The Failed-AVP is available as an External-Concept string in the Control Flow

7.6

Experimental-Result AVP

7.0.0

NA

7.7

Experimental-Result-Code AVP

7.0.0

NA

8

Diameter User Sessions

7.0.0

NA

8.1

Authorization Session State Machine

7.0.0

NA

8.2

Accounting Session State Machine

7.0.0

NA

8.3

Server-Initiated Re-Auth

7.0.0

NA

8.3.1

Re-Auth-Request

7.0.0

NA

8.3.2

Re-Auth-Answer

7.0.0

NA

8.4

Session Termination

7.0.0

NA

8.4.1

Session-Termination-Request

7.0.0

Not used by OCECAS

8.4.2

Session-Termination-Answer

7.0.0

Ignored by OCECAS

8.5

Aborting a Session

7.0.0

NA

8.5.1

Abort-Session-Request

7.0.0

OCECAS Out-of-the-box configuration needs adjustment to enact the session termination as per operator policy.

8.5.2

Abort-Session-Answer

7.0.0

NA

8.6

Inferring Session Termination from Origin-State-Id

7.0.0

NA

8.7

Auth-Request-Type AVP

7.0.0

NA

8.8

Session-Id AVP

7.0.0

NA

8.9

Authorization-Lifetime AVP

Non-compliant

Not used by OCECAS

8.10

Auth-Grace-Period AVP

Non-compliant

Not used by OCECAS

8.11

Auth-Session-State AVP

Non-compliant

Not used by OCECAS

8.12

Re-Auth-Request-Type

Non-compliant

Not used by OCECAS

8.13

Session-Timeout AVP

Non-compliant

Not used by OCECAS

8.14

User-Name AVP

7.0.0

NA

8.15

Termination-Cause AVP

7.0.0

NA

8.16

Origin-State-Id AVP

7.0.0

NA

8.17

Session-Binding AVP

Non-compliant

Not used by OCECAS

8.18

Session-Server-Failover AVP

Non-compliant

Not used by OCECAS

8.19

Multi-Round-Time-Out AVP

Non-compliant

Not used by OCECAS

8.20

Class AVP

Non-compliant

Not used by OCECAS

8.21

Event-Timestamp AVP

7.0.0

NA

9

Accounting

7.0.0

NA

9.1

Server Directed Model

7.0.0 (Partial)

Accounting-Realtime-Required AVP is ignored by OCECAS

9.2

Protocol Messages

7.0.0

NA

9.3

Application document requirements

7.0.0

NA

9.4

Fault Resilience

7.0.0

Non-volatile memory is used to store a non-Diameter CDR, which is not automatically played back on connection resumption.

9.5

Accounting Records

7.0.0

NA

9.6

Correlation of Accounting Records

7.0.0

NA

9.7

Accounting Command-Codes

7.0.0

NA

9.7.1

Accounting-Request

7.0.0

NA

9.7.2

Accounting-Answer

7.0.0

NA

9.8

Accounting AVPs

7.0.0

NA

9.8.1

Accounting-Record-Type AVP

7.0.0

NA

9.8.2

Acct-Interim-Interval

7.0.0

NA

9.8.3

Accounting-Record-Number AVP

7.0.0

NA

9.8.4

Acct-Session-Id AVP

7.0.0

Not configured Out-Of-The-Box

9.8.5

Acct-Multi-Session-Id AVP

7.0.0

Not configured Out-Of-The-Box

9.8.6

Accounting-Sub-Session-Id AVP

7.0.0

Not configured Out-Of-The-Box

9.8.7

Accounting-Realtime-Required AVP

7.0.0

Not configured Out-Of-The-Box

10

AVP Occurrence Table

7.0.0

NA

10.1

Base Protocol Command AVP Table

7.0.0

NA

10.2

Accounting AVP Table

7.0.0

NA

11

IANA Considerations

7.0.0

NA

11.1

AVP Header

7.0.0

NA

11.1.1

AVP Codes

7.0.0

NA

11.1.2

AVP Flags

7.0.0

NA

11.2

Diameter Header

7.0.0

NA

11.2.1

Command Codes

7.0.0

NA

11.2.2

Command Flags

7.0.0

NA

11.3

Application Identifiers

7.0.0

NA

11.4

AVP Values

7.0.0

NA

11.4.1

Result-Code AVP Values

7.0.0

NA

11.4.2

Accounting-Record-Type AVP Values

7.0.0

NA

11.4.3

Termination-Cause AVP Values

7.0.0

NA

11.4.4

Redirect-Host-Usage AVP Values

7.0.0

NA

11.4.5

Session-Server-Failover AVP Values

7.0.0

NA

11.4.6

Session-Binding AVP Values

7.0.0

NA

11.4.7

Disconnect-Cause AVP Values

7.0.0

NA

11.4.8

Auth-Request-Type AVP Values

7.0.0

NA

11.4.9

Auth-Session-State AVP Values

7.0.0

NA

11.4.10

Re-Auth-Request-Type AVP Values

7.0.0

NA

11.4.11

Accounting-Realtime-Required AVP Values

7.0.0

NA

11.4.12

Inband-Security-Id AVP Values

7.0.0

NA

11.5

Diameter TCP/SCTP Port Numbers

7.0.0

NA

11.6

NAPTR Service Fields

7.0.0

NA

12

Diameter protocol related configurable parameters

7.0.0

NA

13

Security Considerations

7.0.0

TLS is supported.

13.1

IPsec Usage

7.0.0

IPSec is implemented at the IP layer, so this is dependent on the OS used to deploy OCECAS. (Or IPSec could be implemented at another IP endpoint)

13.2

TLS Usage

7.0.0

Configured by default.

13.3

Peer-to-Peer Considerations

7.0.0

NA

14

References

7.0.0

NA

14.1

Normative References

7.0.0

Noted

14.2

Informative References

7.0.0

Noted

15

Acknowledgements

7.0.0

NA