ISAKMP DELETE payload
pau@watson.ibm.com Tue, 03 December 1996 16:36 UTC
Received: from cnri by ietf.org id aa27699; 3 Dec 96 11:36 EST
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa13354; 3 Dec 96 11:36 EST
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id LAA24295 for ipsec-outgoing; Tue, 3 Dec 1996 11:27:59 -0500 (EST)
From: pau@watson.ibm.com
Date: Tue, 03 Dec 1996 11:33:05 -0500
Message-Id: <9612031633.AA22788@secpwr.watson.ibm.com>
To: ipsec@tis.com, isakmp-proto@epoch.ncsc.mil
Subject: ISAKMP DELETE payload
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Md5: BleGdb7qODg3x5+7u1cnzQ==
Sender: owner-ipsec@ex.tis.com
Precedence: bulk
Should the DELETE payload be authenticated using an ISAKMP SA (or pre-shared key) ? Otherwise there seems to be an easy denial-of-service attack. Pau-Chen
- ISAKMP DELETE payload pau
- Re: ISAKMP DELETE payload Ran Atkinson
- Re: ISAKMP DELETE payload W. Douglas Maughan
- Re: ISAKMP DELETE payload pau
- Re: ISAKMP DELETE payload W. Douglas Maughan
- Re: ISAKMP DELETE payload pau
- Re: ISAKMP DELETE payload W. Douglas Maughan
- Re: ISAKMP DELETE payload Shawn Mamros
- Re: ISAKMP DELETE payload pau
- Re: ISAKMP DELETE payload Daniel Harkins
- Re: ISAKMP DELETE payload Shawn Mamros
- Re: ISAKMP DELETE payload Daniel Harkins
- Re: ISAKMP DELETE payload pau