Re: [Hipsec] Well back at this yet again -- Re: RFC4423bis review

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Fri, 02 September 2011 04:59 UTC

Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B06721F9374 for <hipsec@ietfa.amsl.com>; Thu, 1 Sep 2011 21:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.414
X-Spam-Level:
X-Spam-Status: No, score=-106.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 8TPAAn-IKfPq for <hipsec@ietfa.amsl.com>; Thu, 1 Sep 2011 21:59:23 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by ietfa.amsl.com (Postfix) with ESMTP id D5CB321F9369 for <hipsec@ietf.org>; Thu, 1 Sep 2011 21:59:23 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p8250otX021071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 1 Sep 2011 22:00:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with SMTP id p8250oMA014135; Thu, 1 Sep 2011 22:00:50 -0700 (PDT)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p8250jKJ013523 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 1 Sep 2011 22:00:45 -0700 (PDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Thu, 1 Sep 2011 22:00:44 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: 'Andrew McGregor' <andrewmcgr@gmail.com>, Robert Moskowitz <rgm@htt-consult.com>
Date: Thu, 01 Sep 2011 22:00:44 -0700
Thread-Topic: [Hipsec] Well back at this yet again -- Re: RFC4423bis review
Thread-Index: Acxo8KoTbfA7cxPrTd2vXScooLifvQAPGC0A
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEFAF06B7@XCH-NW-10V.nw.nos.boeing.com>
References: <7CC566635CFE364D87DC5803D4712A6C4CED25B0F2@XCH-NW-10V.nw.nos.boeing.com> <4E5FC610.7030504@htt-consult.com> <EEA55D1F-D7D8-446A-9D6C-3F331C3C0723@gmail.com>
In-Reply-To: <EEA55D1F-D7D8-446A-9D6C-3F331C3C0723@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] Well back at this yet again -- Re: RFC4423bis review
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Sep 2011 04:59:24 -0000

> >>    The IP addressing namespace has been overloaded to name both
> >>    interfaces (at layer-3) and endpoints (for the endpoint-specific
> >>    part of layer-3, and for layer-4).  In their role as interface
> >>    names, IP addresses are sometimes called "locators" and serve
> >>    as an address within a routing topology.
> >
> > I grant your point. I have a particular attachment to the term
> 'confounding', as one of my Stat profs was always confounding us with
> it!
> >
> > But I will go with this due to the evolution of the discussion of IP
> address 'meaning' with one change:
> >
> > as an endpoint within a routing topology.
> 
> Isn't the exact word you are looking for 'conflation'?  As in, using
> the same name for multiple different ideas?
> 

Yes, 'conflation' works well here.

- Tom