Re: Heartbeats Straw Poll

Skip Booth <ebooth@cisco.com> Mon, 07 August 2000 17:02 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA28847; Mon, 7 Aug 2000 10:02:58 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id MAA28897 Mon, 7 Aug 2000 12:04:31 -0400 (EDT)
Date: Mon, 07 Aug 2000 12:12:28 -0400
From: Skip Booth <ebooth@cisco.com>
To: Bill Sommerfeld <sommerfeld@East.Sun.COM>
cc: Paul Hoffman <paul.hoffman@vpnc.org>, ipsec@lists.tislabs.com
Subject: Re: Heartbeats Straw Poll
In-Reply-To: <200008060352.e763qKS110811@thunk.east.sun.com>
Message-ID: <Pine.GSO.4.10.10008071210200.11449-100000@uzura.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

Check out draft-ietf-ipsra-reqmts-01.txt.  Section 2.4 has the following
statements:

2.4 Accounting

   Accounting is used here to refer to the collection and reporting of
   connection status information by the IRAS. For remote access, the
   following accounting information is useful:

     o connection start time
     o connection end time
     o incoming octets (with respect to the IRAS)
     o outgoing octets (with respect to the IRAS)

   Note that the requirement for a connection-end-time attribute implies
   the need for a connection keep-alive mechanism of some sort so that
   the IRAS can accurately determine this quantity in cases where the
   IRAC does not explicitly terminate the connection. Also note that the
   keep-alive mechanism in this case is always directed from the IRAC to the
   IRAS.

-Skip

On Sat, 5 Aug 2000, Bill Sommerfeld wrote:

> > I would add a third reason for heartbeats/keepalives.  To be able to do accurate
> > accounting the SG needs to know within a reasonable time that the client has
> > disconnected.  
> 
> I just re-read the ipsec and ipsra charters and saw no mention of
> accounting as required functionality..
> 
> 					- Bill
> 
>