Re: [IPsec] Avoiding Authentication Header (AH)

Jack Kohn <kohn.jack@gmail.com> Mon, 02 January 2012 23:25 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 355AC1F0C59 for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 15:25:21 -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 gdlTGm32slZt for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 15:25:20 -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 9C9CE1F0C35 for <ipsec@ietf.org>; Mon, 2 Jan 2012 15:25:20 -0800 (PST)
Received: by qcsf15 with SMTP id f15so11397011qcs.31 for <ipsec@ietf.org>; Mon, 02 Jan 2012 15:25:20 -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=Mef/f7x6TaxdyNvqgxrnt9rl6BHCSpK6O0z/zA9qyPw=; b=DpBETBZEAUoginLQykSJRlcs4pONkI0T43MwCgGXDYESM49/4plQeQRLPU1gfsTD+6 yY3RLmPJixN8o1eA6BUdNR+7ccWEKXwtic8CPJXpCLu9LKTGp8BCCl3iItDwKCGRd3al sYVGjtIMDb6emkeP4D2WAf6da+ymJeCYfOgNE=
MIME-Version: 1.0
Received: by 10.229.78.225 with SMTP id m33mr17456083qck.59.1325546720195; Mon, 02 Jan 2012 15:25:20 -0800 (PST)
Received: by 10.229.39.139 with HTTP; Mon, 2 Jan 2012 15:25:20 -0800 (PST)
In-Reply-To: <639319E3-7725-4F23-9F78-46BB49FCF172@gmail.com>
References: <12533D04-6B3F-490F-935B-4F1FA612C938@gmail.com> <CAA1nO72z3yuOYkwkHCDphmOsVrFtrgq-0xWviY7XRC2vMS9kFg@mail.gmail.com> <639319E3-7725-4F23-9F78-46BB49FCF172@gmail.com>
Date: Tue, 03 Jan 2012 04:55:20 +0530
Message-ID: <CAA1nO73JiQTPM7n5ULeFEtNC2fffgxiqN=rmu8Q1hf8aGaJULQ@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 23:25:21 -0000

> An IPv4 example would be validating the [FIPS-188]
> IPv4 option, which can't be protected any other way.
>
> That option is supported by a range of operating systems,
> both commercial and open-source.  I'm told by a
> a major computer vendor that Linux supports this
> for both IPv4 and IPv6.  The option reportedly
> is deployed in environments ranging from certain
> large financial institutions to governments.
> Some devices that perform IP routing also perform
> security checks that ensure the label on a given
> packet is in range for the output interface;
> end systems also separately need to trust
> the label integrity.
>
> Similar IPv6 examples exist.

And i would like to know what those are.

So you suggest that AH should be retained and encouraged since it
supports FIPS-188 IP option. Great.

What about IPv6? I am curious to know if you can come up with yet
another esoteric extension header or application that only a handful
of people know and have used - the way you have come up with IPv4.

Jack