Session Deletion
Tanya Shastri <tanyas@cisco.com> Thu, 24 February 2005 06:01 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22851; Thu, 24 Feb 2005 01:01:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4CQf-0005SV-HZ; Thu, 24 Feb 2005 01:24:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D41hJ-0002NW-QW; Wed, 23 Feb 2005 13:57:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D41hH-0002Im-K8 for rtg-bfd@megatron.ietf.org; Wed, 23 Feb 2005 13:57:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28720 for <rtg-bfd@ietf.org>; Wed, 23 Feb 2005 13:57:12 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D423v-0005TC-Vw for rtg-bfd@ietf.org; Wed, 23 Feb 2005 14:20:44 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-4.cisco.com with ESMTP; 23 Feb 2005 10:57:08 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j1NIv0ZV018246; Wed, 23 Feb 2005 10:57:01 -0800 (PST)
Received: from cisco.com (tanyas-sb100.cisco.com [128.107.162.227]) by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BDZ87341; Wed, 23 Feb 2005 10:56:56 -0800 (PST)
Message-ID: <421CD1F7.20507@cisco.com>
Date: Wed, 23 Feb 2005 10:56:55 -0800
From: Tanya Shastri <tanyas@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: rtg-bfd@ietf.org
Content-Type: multipart/mixed; boundary="------------040203090904090404000900"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017
Cc: Tanya Shastri <tanyas@cisco.com>
Subject: Session Deletion
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Hi, Session deletion has not been mentioned explicitly in the draft. It is not clear to me whether Admin Down could be used for deletion. So I am not sure which of the following is correct: - Admin down should be treated as a transitionary state during session deletion (Putting a session in Admin Down leads to it being deleted). - Admin down is a state that a session may be held in. If Admin down is to be treated as a temporary state then the draft could include a description on how to transition out of AdminDown state to complete deletion of the session. "TABLE 1" below should be valid i.e. Transition out of Admin Down state or receiving IHY=0 from the other end or on Timer Expiry. Possible events are: Create, IHY=0, IHY=1, GoAdminDown(Delete), GoAdminUp TABLE 1: Finite State Machine Transition from Old State to New State, on the above events. (Interesting cells have a *). --------------------------------------------------------------------- New state -> |Deleted | Init | Failing | Down | UP | AdminDown| |(session| | | | | | Old state |does not| | | | | | | |exist) | | | | | | v | | | | | | | --------------------------------------------------------------------- Deleted | | | Create | | | | (adj does | | | | | | | not exist) | | | | | | | --------------------------------------------------------------------- Init | | IHY=0 |TimerExp | | IHY=1 | GoAdminDn| --------------------------------------------------------------------- Failing | | | Create | IHY=0 | | GoAdminDn| | | | IHY=1 | | | | --------------------------------------------------------------------- Down | | IHY=0 | | | IHY=1 | GoAdminDn| --------------------------------------------------------------------- Up | | | IHY=0 | | IHY=1 | GoAdminDn| | | | TimerExp| | | | --------------------------------------------------------------------- AdminDown |* IHY=0 | |GoAdminUp| | | | |TimerExp| | | | | IHY=1 | --------------------------------------------------------------------| If Admin down is to be treated as a state that a session may be held in (not just to transition to deleted state) then an extra state may be needed (Deleting) as shown in the state transition table below. A session in deleting state could behave similiar to if it were in AdminDown state (i.e. the diagnostic code could be set to Admin Down in outgoing BFD control packets). Possible events are: Create, IHY=0, IHY=1, Delete, GoAdminUp, GoAdminDown(GoAdDn) TABLE 2: Finite State Machine Transition from Old State to New State. -----------------------------------------------------------------------| New state->|Deleted | Init| Failing | Down | UP | Deleting | AdDn | |(session| | | | | | | Old state |does not| | | | | | | | |exist) | | | | | | | v | | | | | | | | -----------------------------------------------------------------------| Deleted | | | Create | | | |GoAdDn| (adj does | | | | | | | | not exist) | | | | | | | | -----------------------------------------------------------------------| Init | Delete |IHY=0|TimerExp | | IHY=1 | |GoAdDn| -----------------------------------------------------------------------| Failing | | | Create | IHY=0 | | Delete |GoAdDn| | | | IHY=1 | | | | | -----------------------------------------------------------------------| Down | Delete |IHY=0| | | IHY=1 | |GoAdDn| -----------------------------------------------------------------------| Up | | | IHY=0 | | IHY=1 | Delete |GoAdDn| | | | TimerExp| | | | | -----------------------------------------------------------------------| Deleting |* IHY=0 | |* Create | | |* IHY=1 | | |TimerExp| | | | | GoAdminDn| | -----------------------------------------------------------------------| AdminDown | | |GoAdminUp| | |* Delete |GoAdDn| -----------------------------------------------------------------------| Please clarify deletion of a session and which (if) one of the above approaches is correct. Also I think it would help to have a state transition table like the ones above or a state diagram (I guess that is in the works) to explain section 6.6.6 in the draft. Thanks, Tanya
- Session Deletion Tanya Shastri
- Re: Session Deletion Dave Katz