IETF Logo Mail Archive

RE: problems with draft-jenkins-ipsec-rekeying-06.txt

Paul Koning <pkoning@xedia.com> Wed, 19 July 2000 19:57 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 MAA21511; Wed, 19 Jul 2000 12:57:15 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id OAA25867 Wed, 19 Jul 2000 14:46:56 -0400 (EDT)
From: Paul Koning <pkoning@xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <14709.63954.655560.534909@xedia.com>
Date: Wed, 19 Jul 2000 14:56:18 -0400
To: andrew.krywaniuk@alcatel.com
Cc: ipsec@lists.tislabs.com
Subject: RE: problems with draft-jenkins-ipsec-rekeying-06.txt
References: <Pine.BSI.3.91.1000717230619.23232C-100000@spsystems.net> <003b01bff1ab$fe147b40$d23e788a@andrewk3.ca.newbridge.com>
X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

>>>>> "andrew" == andrew krywaniuk <andrew.krywaniuk@alcatel.com> writes:

 andrew> ...Replacing unbounded state creation with unbounded rekeying
 andrew> frequency is no solution. Fine, so this problem is kind of
 andrew> academic, but you are endagering the ability of a host to be
 andrew> fully self-stablizing (and that is of academic interest to
 andrew> me).

Self-stabilization is of far *more* than "academic" interest to me. 
I know that it is a property that is critically important in reliable
networks.  I look for it in real world protocols to make them safe for
use in real world situations.

    paul

v2.23.0 | Report a Bug | By Email