Acronyms for Locator/ID Separation Protocol

Hector <sant9442@gmail.com> Fri, 28 October 2011 11:38 UTC

Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD38721F8B62 for <ietf@ietfa.amsl.com>; Fri, 28 Oct 2011 04:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.738
X-Spam-Level:
X-Spam-Status: No, score=-2.738 tagged_above=-999 required=5 tests=[AWL=-0.431, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 SUPj8C6O7tmX for <ietf@ietfa.amsl.com>; Fri, 28 Oct 2011 04:38:18 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4FE7021F8B43 for <IETF@ietf.org>; Fri, 28 Oct 2011 04:38:18 -0700 (PDT)
Received: by ywt2 with SMTP id 2so4232073ywt.31 for <IETF@ietf.org>; Fri, 28 Oct 2011 04:38:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=kHixKd0Op3tFF0b2QFkWNL7FMpXsVOTUS5PYxa3CLgY=; b=jOO0xIR/3CNN9ziv47EslXEtH+HQujpm4K+am8f0fvrlQeTMgCWbwjx6A9baQBsOZQ uy0OTYMy6UmSRjj3+3f1AOQBUgW1VgzncAZ1Eh4e5CZUUjhLy0TKGd6+P0haMUhzL7H9 UGNtAyhdMe6Gvo8HQdLpkuzbYVashagkqy4CI=
Received: by 10.101.90.8 with SMTP id s8mr455929anl.93.1319801897815; Fri, 28 Oct 2011 04:38:17 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id r9sm23876126anh.8.2011.10.28.04.38.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Oct 2011 04:38:17 -0700 (PDT)
Message-ID: <4EAA9427.6020805@gmail.com>
Date: Fri, 28 Oct 2011 07:38:15 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF@ietf.org
Subject: Acronyms for Locator/ID Separation Protocol
References: <552F103D-2C46-44E6-8CE4-6793DC326E87@gmail.com> <4EA9EF9C.4060108@gmail.com> <7A3CBCEB3F7E80FC15706A46@PST.JCK.COM> <4EAA2DE0.5040506@bogus.com> <4EAA4BB4.4070100@piuha.net> <4EAA4C18.8050607@piuha.net> <4EAA54C6.1060706@gmail.com> <5158E96C-75FB-47D5-8086-D0C7C1946937@gigix.net> <4EAA84FA.7060607@firstpr.com.au>
In-Reply-To: <4EAA84FA.7060607@firstpr.com.au>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 11:38:18 -0000

There is actually an black art (i.e. it takes practice) in technical 
writing to develop abbreviations. Lets see

             Locator/ID Separation Protocol

Generally it good to make it pronounceable, easy to remember:

   LISP ... "hmmm, I heard that one before, no good."
   LIDS
   LIDSEP
   LOSEP
   LOSP
   LOISP
   LOIDS  <--- I like this one!!

You could also always twist the title:

      Protocol to Separate Location IDs

And now you have a new range of potentials easy to pronounce names.

<g>


Robin Whittle wrote:
> Hi Luigi,
> 
> As I wrote in a recent message:
> 
>   Misnamed WGs, e.g. LISP != Loc/ID Split
>   http://www.ietf.org/mail-archive/web/ietf/current/msg70176.html
> 
> HIP, which is a Locator-Identifier Separation protocol, dates from
> 2003, 8 years ago.  However, HIP goes back to draft-moskowitz-hip-00 of
> May 2009.  I should have mentioned GSE, which is also a Loc-ID
> Separation protocol.  GSE goes back at least to March 1997:
> 
>   http://tools.ietf.org/html/draft-ietf-ipngwg-esd-analysis-00
> 
> Four months later - 14 years ago - the next version had the title:
> 
>   Separating Identifiers and Locators in Addresses:
>   An Analysis of the GSE Proposal for IPv6
> 
> GSE and HIP are both Locator-Identifier Separation protocols.  LISP is
> not, since it operates on totally different principles.
> 
> In referring to LISP as "the loc/ID separation protocol", as you did:
> 
>> Like Jari and others I do not see the name as disrespectful and it is
>> unrealistic to believe that the loc/ID separation protocol can be
>> renamed. It has been around for more than 5 years it is just too late.
> 
> it seems that you are both asserting and assuming that LISP is not only
> a Loc/ID Separation protocol, but "*the* Loc/ID Separation protocol".
> 
> It was mistake to think of LISP as a Loc/ID Separation protocol.
> Asserting that it is - or behaving as if it is - does not alter the fact
> that it is not.
> 
> I can't imagine why "LISP" as the name for an Internet protocol should
> be regarded as homage to the programming language.  Is there any
> evidence that this was the intention in late 2006 or early 2007?
> 
>   - Robin 	
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
>