Re: [IPsec] Avoiding Authentication Header (AH)

RJ Atkinson <rja.lists@gmail.com> Mon, 02 January 2012 21:28 UTC

Return-Path: <rja.lists@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CBAF1F0C36 for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 13:28:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1kY-Ml+eg31 for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 13:28:55 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88BFE1F0C35 for <ipsec@ietf.org>; Mon, 2 Jan 2012 13:28:55 -0800 (PST)
Received: by qcsf15 with SMTP id f15so11360198qcs.31 for <ipsec@ietf.org>; Mon, 02 Jan 2012 13:28:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=Pi8CkoNlnth/N4X6iPBDIs5nRnLSzjh0BWsq3mjBYEY=; b=fAjffnfxdyw6kYqCe8mP0MHDFYvVG32EIU4TTYpRAWXNR0uEA7icr1yfOGx8ZS8IPX cnpFXmIvouFlmcqvdHPvQt62BtLo+NXmNNHP90fvR+JghnXeg6PWhzDZbClyzccgY5FH /mkQWdjHsXx/5GzEOhspioIofsi5k1Di+mNhk=
Received: by 10.229.111.89 with SMTP id r25mr7656761qcp.106.1325539734080; Mon, 02 Jan 2012 13:28:54 -0800 (PST)
Received: from [10.30.20.12] (pool-96-225-134-175.nrflva.fios.verizon.net. [96.225.134.175]) by mx.google.com with ESMTPS id t4sm16759535qal.17.2012.01.02.13.28.52 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 02 Jan 2012 13:28:53 -0800 (PST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CAA1nO73AL-n+rfRuJegN=j7NQ0y7=6uxpNtZ9mCCJRW6OjxwEg@mail.gmail.com>
Date: Mon, 02 Jan 2012 16:28:53 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <75E7DE71-65E0-40E9-8F7D-4EE5317F908C@gmail.com>
References: <12533D04-6B3F-490F-935B-4F1FA612C938@gmail.com> <CAA1nO73AL-n+rfRuJegN=j7NQ0y7=6uxpNtZ9mCCJRW6OjxwEg@mail.gmail.com>
To: IPsec ME WG List <ipsec@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [IPsec] Avoiding Authentication Header (AH)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jan 2012 21:28:56 -0000

On 02  Jan 2012, at 14:24 , Jack Kohn wrote:
>> While AH uses are limited today, just as the use of
>> IP options/extensions are limited today, current active
>> uses of AH in real-world deployments today include at least
>> these -- built using commercial off-the-shelf products:
> 
> BTW, there is a discussion going on in NANOG on who uses AH
> and nobody seems to be raising their hands.
> 
> Obviously, one cant take draw to much from that,
> but it just gives you a data point.

I absolutely believe that.  It is not a surprise.  
More data is almost always better than less data.

NANOG list membership is mostly, not entirely, but mostly, 
ISP folks and content providers.  Threat models for ISPs 
tend to focus on protecting the transit infrastructure 
and their provisioning/management platforms.  Many ISPs 
seem to share similar threat models.

Threat models for end users tend to be different -- and 
vary pretty widely.

I haven't been at an ISP for a decade, but I'd be surprised 
to see an ISP put a firewall in their transit network, 
whereas many enterprise deployments have multiple firewalls 
(and also IDSs and other boxes) throughout their network.

Threat models vary between ISPs and enterprises and other users.  
Common deployment models vary also by type of user.

ISPs tend to deploy I/IS-IS as their IGP for a range of reasons,
while other users more commonly deploy OSPF as their IGP.
No doubt there are exceptions to those trends.

Financial institutions are obvious examples of high-threat 
environments.  A compromise at a large financial institution 
could have a very high monetary cost to the victim institution.
Often this means large financial institutions find it 
worthwhile to deploy security measures that other sites 
do not find worthwhile.  

Cheers,

Ran