IETF Logo Mail Archive

Re: [lisp] LISP: update to charter in external review - LISP does not involve separate namespaces for EIDs and RLOCs

Sam Hartman <hartmans-ietf@mit.edu> Tue, 31 March 2009 02:51 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B480028C0E7 for <ietf@core3.amsl.com>; Mon, 30 Mar 2009 19:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 DbIA1pjrPACO for <ietf@core3.amsl.com>; Mon, 30 Mar 2009 19:51:39 -0700 (PDT)
Received: from QMTA02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by core3.amsl.com (Postfix) with ESMTP id A7D0F3A6B68 for <ietf@ietf.org>; Mon, 30 Mar 2009 19:51:39 -0700 (PDT)
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by QMTA02.emeryville.ca.mail.comcast.net with comcast id ZcJq1b0020EPchoA2esfYf; Tue, 31 Mar 2009 02:52:39 +0000
Received: from carter-zimmerman.suchdamage.org ([74.92.229.90]) by OMTA01.emeryville.ca.mail.comcast.net with comcast id Zesd1b00D1xg5mq8Mese5E; Tue, 31 Mar 2009 02:52:39 +0000
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 706D74182; Mon, 30 Mar 2009 22:52:35 -0400 (EDT)
To: Robin Whittle <rw@firstpr.com.au>
Subject: Re: [lisp] LISP: update to charter in external review - LISP does not involve separate namespaces for EIDs and RLOCs
References: <tslwsa7662z.fsf@mit.edu> <969E87F8-3ED2-4550-BA18-240071FBC600@linquest.com> <00275A5B436CA441900CB10936742A3801FD3652@FRVELSMBS22.ad2.ad.alcatel.com> <49D17008.3010608@firstpr.com.au>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 30 Mar 2009 22:52:35 -0400
In-Reply-To: <49D17008.3010608@firstpr.com.au> (Robin Whittle's message of "Tue\, 31 Mar 2009 12\:21\:12 +1100")
Message-ID: <tslvdpq4d58.fsf@mit.edu>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Dow Street <dow.street@linquest.com>, Sam Hartman <hartmans-ietf@mit.edu>, PAPADIMITRIOU Dimitri <Dimitri.Papadimitriou@alcatel-lucent.be>, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 31 Mar 2009 02:51:40 -0000

>>>>> "Robin" == Robin Whittle <rw@firstpr.com.au> writes:

    Robin> Short version: I support Dimitri's suggested changes about
    Robin> the roles of Locators and Identifiers.

    Robin>                   The current draft still contains an
    Robin> erroneous inference that the one address could be used as
    Robin> both a locator (RLOC) and an identifier (EID).

For the information of the IETF and IESG, I made a consensus call on
the lisp list that there was rough consensus that there will be cases where the same IP stands both as an EID and a
RLOC.

Robin challenged this consensus call but has not found support on the
list for his challenge.

So, I believe the community disagrees with Robin's claim that the
discussion of LISP identifiers and locators is erroneous.

That said, I don't see that Dimitri's rewording of the second
paragraph actually touches on how LISP identifiers and locators relate
to each other.  As such, I don't think there has been community
discussion prior to his proposal that would either support or oppose
his proposal.

There is a desire to be done with the charter sooner rather than
later.

v2.23.0 | Report a Bug | By Email