[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: default life negotiation issue

To: Jan Vilhuber <vilhuber@cisco.com>
Subject: Re: default life negotiation issue
From: Will Fiveash <will@austin.ibm.com>
Date: Wed, 21 Jun 2000 11:17:13 -0500
Cc: IETF IPsec <ipsec@lists.tislabs.com>
In-Reply-To: <Pine.LNX.4.21.0006201715450.2623-100000@janpc-home.cisco.com>; from vilhuber@cisco.com on Tue, Jun 20, 2000 at 05:17:00PM -0700
Mail-Followup-To: Jan Vilhuber <vilhuber@cisco.com>,IETF IPsec <ipsec@lists.tislabs.com>
References: <20000620190156.D25104@austin.ibm.com> <Pine.LNX.4.21.0006201715450.2623-100000@janpc-home.cisco.com>
Sender: owner-ipsec@lists.tislabs.com
User-Agent: Mutt/1.3.4i

Jan,

Okay, I understand your answer.  I still think that that this sentence in
RFC2407 is vague (discussing SA Life Type/Duration):

  If unspecified, the default value shall be assumed to be 28800 seconds (8
  hours).  

One could easily interpret this to mean that only if there are no life
attributes in a proposal should the default value be assumed.

On Tue, Jun 20, 2000 at 05:17:00PM -0700, Jan Vilhuber wrote:
> Here's how I understand the paragraph in IPDOI you referred to:
> 
> If there's no lifetime indicated in the exchange, then both sides MUST assume
> the default of 28800 seconds. If a lifesize is given, the default lifetime
> applies ALSO, and whichever conditions is hit first triggers the death of the
> SA ;)
> 
> jan

-- 
Will Fiveash
IBM AIX System Development (IPsec/IKE)

References:

Re: default life negotiation issue

From: Will Fiveash <will@austin.ibm.com>

Re: default life negotiation issue

From: Jan Vilhuber <vilhuber@cisco.com>

Prev by Date: RE: Minimum IP Compression Algorithm for Interoperability
Next by Date: RE: Minimum IP Compression Algorithm for Interoperability
Prev by thread: Re: default life negotiation issue
Next by thread: uniqueness of Message IDs and related issues
Index(es):
- Main
- Thread