RFC 3588:Diameter Base Protocol
RFC-Ref

state machine


Click on the red underlined text to get to the source

... application-layer acknowledgements, and defines failover algorithms and the associated state machine. This is described in Section 5.5 and [AAATRANS]. ...
... Diameter failover algorithm and state machine. The Mobile IPv4 ...
... accounting application should be viewed as a last resort and MUST NOT be used unless a new command or additional mechanisms (e.g., application defined state machine) is defined within the application, or new mandatory AVPs are added to the ABNF ...
... accounting is used without any mandatory AVPs, new commands or additional mechanisms (e.g., application defined state machine), then the base protocol defined standard accounting ...


... port 3868. A given Diameter instance of the peer state machine MUST NOT use more than one transport connection to communicate with a given peer, unless ...


... transport connection, they MUST exchange the Capabilities Exchange messages, as specified in the peer state machine (see Section 5.6). This message allows the discovery of a peer's identity and its capabilities (protocol version number ...
... Peer State Machine ...
... This section contains a finite state machine that MUST be observed by all Diameter implementations. Each Diameter node ...
... Diameter implementations. Each Diameter node MUST follow the state machine described below when communicating with each peer. Multiple actions are separated by commas, and may continue on succeeding lines, as space requires. Similarly, state ...
... may also span multiple lines, as space requires. This state machine is closely coupled with the state machine described in [AAATRANS ...
... This state machine is closely coupled with the state machine described in [AAATRANS], which is used to open, close, failover, ...
... connection on which the event occurred. The stable states that a state machine may be in are Closed, I-Open and R-Open; all other states are intermediate. Note that I-Open and R-Open are equivalent except for whether the initiator ...
... state. The state machine constrains only the behavior of a Diameter implementation as seen by Diameter ...
... For this reason, a Diameter peer must employ logic separate from the state machine to receive connection requests, accept them, and await CER ...
... connection, the Origin-Host that identifies the peer is used to locate the state machine associated with that peer, and the new connection and CER ...
... connection and CER are passed to the state machine as an R-Conn-CER event. ...
... incoming connections up to and including receipt of CER requires logic, separate from that of any individual state machine associated with a particular peer, it is described separately in this section rather than in the state machine above. ...
... CER requires logic, separate from that of any individual state machine associated with a particular peer, it is described separately in this section rather than in the state machine above. ...


... Authorization Session State Machine ...
... This section contains a set of finite state machines, representing the life cycle of Diameter sessions ...
... There are four different authorization session state machines supported in the Diameter base protocol ...
... session from a client perspective, the other from a server perspective. The second two state machines are used when the server does not maintain session state ...
... allocated for the particular session must be released. Any event not listed in the state machines MUST be considered as an error condition, and an answer, if applicable, MUST be returned to the originator of the message. ...
... successfully sent' is the complement of 'Failure to send X'. The following state machine is observed by a client when state is ...
... user/device The following state machine is observed by a server when it is maintaining state for the session ...
... Cleanup. The following state machine is observed by a client when state is not ...
... user/device The following state machine is observed by a server when it is not maintaining state for the session ...
... Accounting Session State Machine ...
... The following state machines MUST be supported for applications that have an accounting portion or that require only accounting ...
... accounting services. The first state machine is to be observed by clients. ...
... The server side in the accounting state machine depends in some cases on the particular application. The Diameter base protocol ...
... Diameter base protocol defines a default state machine that MUST be followed by all applications that have not specified other state machines. This is the second state machine ...
... default state machine that MUST be followed by all applications that have not specified other state machines. This is the second state machine in this section described below. ...
... state machine that MUST be followed by all applications that have not specified other state machines. This is the second state machine in this section described below. The default server side ...
... The default server side state machine requires the reception of accounting records in any order and at any time, and does not place ...
... base protocol defines one optional server side state machine that MAY be followed by applications that require keeping track of the session state ...
... accounting server. Note that such tracking is incompatible with the ability to sustain long duration connectivity problems. Therefore, the use of this state machine is recommended only in applications where the value of the Accounting-Realtime-Required AVP ...
... may be lost by the server which no longer accepts them after the connectivity is re-established. This state machine is the third state machine in this section. The state machine ...
... connectivity is re-established. This state machine is the third state machine in this section. The state machine is supervised by a supervision session ...
... state machine is the third state machine in this section. The state machine is supervised by a supervision session timer ...
... network failure. Any event not listed in the state machines MUST be considered as an error condition, and a corresponding answer, if applicable, MUST be ...


... Paul Funk and David Mitton were instrumental in getting the Peer State Machine correct, and our deep thanks go to them for their time. Text in this document was also provided by Paul Funk, Mark Eklund, ...



Google
Web
RFC-Ref