IETF Logo Mail Archive

Re: [Hipsec] [saag] NULL encryption mode in RFC 5202-bis

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 08 July 2014 15:24 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6C4D1A01AC; Tue, 8 Jul 2014 08:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0i90uO_OF8OI; Tue, 8 Jul 2014 08:24:34 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 946571A007E; Tue, 8 Jul 2014 08:24:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 86964BE07; Tue, 8 Jul 2014 16:24:33 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxgTZOa__BV5; Tue, 8 Jul 2014 16:24:32 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.45.57.103]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 71D51BE02; Tue, 8 Jul 2014 16:24:32 +0100 (IST)
Message-ID: <53BC0D30.2070507@cs.tcd.ie>
Date: Tue, 08 Jul 2014 16:24:32 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: James Cloos <cloos@jhcloos.com>, Tom Henderson <tomh@tomh.org>
References: <53BB798A.3080101@tomh.org> <m3lhs3dh5w.fsf@carbon.jhcloos.org>
In-Reply-To: <m3lhs3dh5w.fsf@carbon.jhcloos.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/hipsec/DhMNQF3TUXfz7gXM_3XcDUFoBLU
Cc: hipsec@ietf.org, saag@ietf.org
Subject: Re: [Hipsec] [saag] NULL encryption mode in RFC 5202-bis
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jul 2014 15:24:36 -0000


On 08/07/14 16:06, James Cloos wrote:
> 
> If those doing IP over Amateur Radio are a use case, they require NULL.

That'd be IPsec, not IP, I guess. How many people actually
use IPsec that way?

For corner cases like that (and it is utterly a corner
case regardless of how laudable a corner case) I'd not
have an issue with there being some other RFC to which
they could conform, should there be sufficient interest
in writing such. I don't myself see that can ever justify
an MTI for all implementations though.

S.

v2.23.0 | Report a Bug | By Email