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

RE: Specification of tunnel/transport attribute in IKEv2

To: andrew.krywaniuk@alcatel.com
Subject: RE: Specification of tunnel/transport attribute in IKEv2
From: Michael Thomas <mat@cisco.com>
Date: Mon, 3 Jun 2002 16:32:25 -0700 (PDT)
Cc: "'Charlie Kaufman'" <Charlie_Kaufman@notesdev.ibm.com>, " 'ipsec list'" <ipsec@lists.tislabs.com>
In-Reply-To: <000901c20b43$1faed0e0$1e72788a@ca.alcatel.com>
References: <OF0DBA4DC4.F36E9556-ON85256BCC.000C396D-85256BCC.000FFBDD@iris.com><000901c20b43$1faed0e0$1e72788a@ca.alcatel.com>
Sender: owner-ipsec@lists.tislabs.com

Andrew Krywaniuk writes:
 > Sadly, people do want to do this. Authentication was added to ESP more than
 > 3 years ago, and I still get frequent questions from people that either a)
 > don't realize that ESP can provide authentication, b) believe that
 > authenticating the header is important [even in tunnel mode], or c) want
 > that "extra level of security" that comes from doing authentication in both
 > ESP and AH. I don't know why, but it just seems like we're just not getting
 > the message out.

Choose one:

o RFC2402 IP Authentication Header  S. Kent, R. Atkinson November 1998
ASCII Obsoletes RFC1826  Historic

o RFC2402 IP Authentication Header  S. Kent, R. Atkinson November 1998
ASCII Obsoletes RFC1826  Updated by RFC2406

:-)

		Mike

References:
- Re: Specification of tunnel/transport attribute in IKEv2
  - From: Charlie_Kaufman@notesdev.ibm.com
- RE: Specification of tunnel/transport attribute in IKEv2
  - From: "Andrew Krywaniuk" <andrew.krywaniuk@alcatel.com>

Prev by Date: RE: Public Keys to initiate IPsec.
Next by Date: RE: Public Keys to initiate IPsec.
Prev by thread: RE: Specification of tunnel/transport attribute in IKEv2
Next by thread: Re: Specification of tunnel/transport attribute in IKEv2
Index(es):
- Date
- Thread