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

Andrew McGregor <andrewmcgr@gmail.com> Thu, 01 September 2011 21:45 UTC

Return-Path: <andrewmcgr@gmail.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 01CE221F9875 for <hipsec@ietfa.amsl.com>; Thu, 1 Sep 2011 14:45:16 -0700 (PDT)
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 7+3h14itGoFJ for <hipsec@ietfa.amsl.com>; Thu, 1 Sep 2011 14:45:15 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 566AE21F9873 for <hipsec@ietf.org>; Thu, 1 Sep 2011 14:45:15 -0700 (PDT)
Received: by vxi29 with SMTP id 29so2071106vxi.31 for <hipsec@ietf.org>; Thu, 01 Sep 2011 14:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=44JTqKh7G2qJ/lcV4T4upf46o5TtPaptbyWYuS5bd7w=; b=DzpMBq/8FyMlsmW53U0IjXHdTBLnABysXMVBpt7pmwQd769NOSMGy6uR4KicYJfqWq OfYY72U5ZCYii86xmwBTMG1XI5zI97z6aKEdxcj7N7otCFKSqmSZOaxnwd5cF5R2NL5a k8GSP332olDTd0J2ug/6Z4RdNXsLpFujdctD4=
Received: by 10.52.27.167 with SMTP id u7mr344261vdg.350.1314913609159; Thu, 01 Sep 2011 14:46:49 -0700 (PDT)
Received: from andrewm-lo.lan (121-74-4-70.telstraclear.net [121.74.4.70]) by mx.google.com with ESMTPS id db1sm256084vdb.14.2011.09.01.14.46.46 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Sep 2011 14:46:48 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset="us-ascii"
From: Andrew McGregor <andrewmcgr@gmail.com>
In-Reply-To: <4E5FC610.7030504@htt-consult.com>
Date: Fri, 02 Sep 2011 09:46:42 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEA55D1F-D7D8-446A-9D6C-3F331C3C0723@gmail.com>
References: <7CC566635CFE364D87DC5803D4712A6C4CED25B0F2@XCH-NW-10V.nw.nos.boeing.com> <4E5FC610.7030504@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.1244.3)
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: Thu, 01 Sep 2011 21:45:16 -0000

On 2/09/2011, at 5:51 AM, Robert Moskowitz wrote:

> Finally completed an update of 4423-bis.
> 
> now to NOT get bogged down in minutia in 5201-bis...
> 
> On 04/04/2011 10:35 AM, Henderson, Thomas R wrote:
> 
>> Section 3
>> ---------
>> I was not sure about the statement that IP addresses are a confounding
>> of two namespaces.  I think it may be more accurate to say that
>> the namespaces for endpoint identifiers and interface names overlap
>> since IP addresses are used for both names (or that there is
>> no separate namespace for endpoint identifiers, for historical reasons).
>> 
>> Here is suggested replacement text for paragraph 3:
>> 
>>    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?

Andrew