IETF Logo Mail Archive

Re: [IPsec] Avoiding Authentication Header (AH)

Jack Kohn <kohn.jack@gmail.com> Mon, 02 January 2012 19:15 UTC

Return-Path: <kohn.jack@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 1808021F84B7 for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 11:15:38 -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 KAbmI7fVNF7K for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 11:15:37 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5D621F84AE for <ipsec@ietf.org>; Mon, 2 Jan 2012 11:15:37 -0800 (PST)
Received: by qadz3 with SMTP id z3so10271908qad.10 for <ipsec@ietf.org>; Mon, 02 Jan 2012 11:15:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=yJJW4K3whmQXAQMuoxcnHkEiHSAsPfgrDjyNj95jUcc=; b=WCjPQqyv700txMh4BXKGRIRQ3zP9/DlO9sJnUS2ztgqVW37h8I4lUStGLWpget8Izf E6pjP2ry/CNg1sKUjuaboq7mMnYaxcsA4xFdNfvwAY6va1JPfBuToYECeetsbv1faH4z 40poXutgRrDOyYwz5mJd6h/IfXpSwkYRP/Vjo=
MIME-Version: 1.0
Received: by 10.224.183.65 with SMTP id cf1mr58171975qab.55.1325531736435; Mon, 02 Jan 2012 11:15:36 -0800 (PST)
Received: by 10.229.39.139 with HTTP; Mon, 2 Jan 2012 11:15:36 -0800 (PST)
In-Reply-To: <12533D04-6B3F-490F-935B-4F1FA612C938@gmail.com>
References: <12533D04-6B3F-490F-935B-4F1FA612C938@gmail.com>
Date: Tue, 03 Jan 2012 00:45:36 +0530
Message-ID: <CAA1nO72z3yuOYkwkHCDphmOsVrFtrgq-0xWviY7XRC2vMS9kFg@mail.gmail.com>
From: Jack Kohn <kohn.jack@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: IPsec ME WG List <ipsec@ietf.org>
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 19:15:38 -0000

>
>        - AH with IPv6 to authenticate certain IPv6
>          extension headers and options, primarily in
>          certain high-threat environments.
>
>        - AH with IPv6 to prevent extension-header-based
>          and options-based attacks, primarily in certain
>          high-threat environments.

This piqued my interest.

Which "extension header" does AH specifically protect in these
"high-threat environments"?

In case of IPv4, which field in the IP header are you most interested
in protecting?

Jack

v2.23.0 | Report a Bug | By Email