Next Generation ESNet Arch Requirements - ATIS

1. If the RG detects the failure, then it closes its side of the connection and awaits anew connection attempt from the CESE.2. If the CESE detects the failure, it must close and reinitialize as if it is just cominginto service, per Section 7.2.1. The new application connection will most likely beestablished with a different RG.7.1.1.2 CESE LogoutA CESE sends a Logout message when it will be terminating its connection to the ESNet.The Logout message is intended when there is no other connection in place and there is noprospect of immediately initiating another connection.The Logout message is not usedwhen the CESE is rotating its connection from one RG to another via the acquiescesequence. The CESE sends this message before it closes its current connection to the RG(Shown by Steps 1 and 2 of Figure 7-2).The CESE Logout message does not have a corresponding Login message. If a CESElogs out or terminates its only ESNet connection abnormally and later requests a newconnection with an RG, the CESE is required to go through the initialization set up steps,as defined in Section 7.2.1, to supply the Authorization Session Identifier previouslygenerated by the ESNet.This Logout message allows a CESE to close the application connection withoutgenerating an alarm on the RG side.CESE Sends: Logout Message + ceseid + Authentication Session IdentifierCESE Receives: Logout ACKNotes:1. If the RG fails to acknowledge, the CESE may still shut down.2. The RG will continue to allow the CESE to initiate new events after the CESE hassent a logout message.3. Disconnecting in this way will not raise an alarm. If the CESE connection closesdown without a logout, an error condition is assumed.4. If the CESE connection stays up for some administratively-configurable time periodafter the logout message has been received and acknowledged by the RG, an errorcondition will be assumed.4 Version 1 9/23/04