Re: simplifying rekeying [draft-jenkins-ipsec-rekeying-06.txt]
Paul Koning <pkoning@xedia.com> Mon, 17 July 2000 15:27 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 IAA16914; Mon, 17 Jul 2000 08:27:21 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id JAA14625 Mon, 17 Jul 2000 09:40:06 -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: <14707.3806.575040.769888@xedia.com>
Date: Mon, 17 Jul 2000 09:49:18 -0400
To: dharkins@cips.nokia.com
Cc: hugh@mimosa.com, henry@spsystems.net, ipsec@lists.tislabs.com, hugh@toad.com, gnu@toad.com
Subject: Re: simplifying rekeying [draft-jenkins-ipsec-rekeying-06.txt]
References: <Pine.LNX.4.21.0007161228070.21743-100000@redshift.mimosa.com> <200007170330.UAA24108@potassium.network-alchemy.com>
X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
>>>>> "Dan" == Dan Harkins <dharkins@cips.nokia.com> writes: Dan> On Sun, 16 Jul 2000 14:35:30 EDT you wrote >> We read the word "unique" as having its standard meaning and hence >> reach the stated conclusion. You seem to read it as having some >> other unspecified meaning ("kind of rare"?) and hence essentially >> meaningless. If you can read any word that vaguely, there is no >> standard. Dan> Sigh. I'll appeal to authority then. Websters's Encyclopedic Dan> Unabridged Dictionary ... All this is of great academic interest to those of us who are language buffs, but it in no way contributes to a useful technical discussion on the merits of various key management algorithms. >From what I can tell, the wording of the current spec on the requirements for message IDs is ambiguous (witness this discussion). So the conclusion is that the spec needs repair. Can we please agree on what the *technical* requirement is and proceed from there? Once that is known it should be possible to craft an English phrase that clearly expresses the desired requirement. paul
- simplifying rekeying [draft-jenkins-ipsec-rekeyin… D. Hugh Redelmeier
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Jan Vilhuber
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… D. Hugh Redelmeier
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Dan Harkins
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Jan Vilhuber
- RE: simplifying rekeying [draft-jenkins-ipsec-rek… Andrew Krywaniuk
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Henry Spencer
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Dan Harkins
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… D. Hugh Redelmeier
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Bill Sommerfeld
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Dan Harkins
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Valery Smyslov
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Bill Sommerfeld
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Paul Koning
- RE: simplifying rekeying [draft-jenkins-ipsec-rek… D. Hugh Redelmeier
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Valery Smyslov
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… David W. Faucher
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… Dan Harkins
- Re: simplifying rekeying [draft-jenkins-ipsec-rek… D. Hugh Redelmeier