Re[2]: AH (without ESP) on a secure gateway

"Whelan, Bill" <bwhelan@nei.com> Mon, 02 December 1996 16:30 UTC

Received: from cnri by ietf.org id aa06838; 2 Dec 96 11:30 EST
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa07499; 2 Dec 96 11:30 EST
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id LAA22243 for ipsec-outgoing; Mon, 2 Dec 1996 11:21:15 -0500 (EST)
Date: Mon, 02 Dec 1996 09:55:58 -0500
From: "Whelan, Bill" <bwhelan@nei.com>
Message-Id: <9611028495.AA849549400@netx.nei.com>
To: ipsec@tis.com, Stephen Kent <kent@bbn.com>
Subject: Re[2]: AH (without ESP) on a secure gateway
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

 Steve,
     
     

 >AH is
 >nominally a "transport" mode security protocol, using the terminlogy 
 >adopted for ESP in the IPSEC context.  In this mode, AH cannot be
 >used unambiguously by a pair of firewalls, because it conflicts with 
 >possible use of AH by subscriber hosts served by these firewalls.
 
 Thanks, this ambiguity is the heart of my original question.
 
 >One can address this problem by tunneling between the firewalls,
 >and using AH in the exterior IP header.
 
 I agree - AH with ESP on a secure gateway seems pretty unambiguous.
 
 >One also can achieve a similar (though not identical)  capability by 
 >using ESP in tunnel mode, but NOT electing to perform encryption.  Since 
 >ESP is being revised to be general enough to NOT requre encryption, this 
 >would address the export or import concerns cited earlier.
 
 Hmm, this might be a solution, but it seems somewhat expensive.  Would all 
 host systems providing AH need to provide ESP to handle the possibility 
 they are communicating through a gateway?
     
     
 >Steve
 
 Bill