Re: [Hipsec] Selection of LSI address block

"Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com> Wed, 19 August 2009 22:25 UTC

Return-Path: <jeffrey.m.ahrenholz@boeing.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C3123A6FDB for <hipsec@core3.amsl.com>; Wed, 19 Aug 2009 15:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ESOWhNoijhC for <hipsec@core3.amsl.com>; Wed, 19 Aug 2009 15:25:53 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id EEB403A6FD2 for <hipsec@ietf.org>; Wed, 19 Aug 2009 15:25:52 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n7JMPVDh024140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Aug 2009 15:25:31 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n7JMPVUW008796; Wed, 19 Aug 2009 15:25:31 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n7JMPUYa008780; Wed, 19 Aug 2009 15:25:31 -0700 (PDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 19 Aug 2009 15:25:26 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Aug 2009 15:24:37 -0700
Message-ID: <0DF156EE7414494187B087A3C279BDB404AD7C6A@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <4A8C708D.4010503@htt-consult.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Hipsec] Selection of LSI address block
Thread-Index: AcohFUvC6kOBKxtZTqO1/4y+KNnMHAABaLLQ
References: <4A8C708D.4010503@htt-consult.com>
From: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>
To: Robert Moskowitz <rgm@htt-consult.com>, hipsec@ietf.org
X-OriginalArrivalTime: 19 Aug 2009 22:25:26.0552 (UTC) FILETIME=[F3700980:01CA211B]
Subject: Re: [Hipsec] Selection of LSI address block
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Wed, 19 Aug 2009 22:25:53 -0000

 
> We have discussed using 127.0.0.0 for LSIs, say 
> 127.100.0.0/16, but will 
> that really work?

in the OpenHIP software we have a macro IN_LOOP() to check if an IPv4
address is equal to 
(INADDR_LOOPBACK >> IN_CLASSA_NSHIFT), i.e. if the top bits equal 127
(see /usr/include/netinet/in.h on Linux)

I wonder if other applications use similar techniques to check for
loopback addresses? Using 127.100.0.0/16 would be problematic in that
case.

-Jeff