IETF Logo Mail Archive

Re: [lisp] Draft of new Proposed Charter

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 15 October 2015 16:08 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 386201B3358 for <lisp@ietfa.amsl.com>; Thu, 15 Oct 2015 09:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oys3NyCAx9qm for <lisp@ietfa.amsl.com>; Thu, 15 Oct 2015 09:08:32 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F0F21B312A for <lisp@ietf.org>; Thu, 15 Oct 2015 09:08:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 8CFF724022B; Thu, 15 Oct 2015 09:08:32 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id C4A4824143E; Thu, 15 Oct 2015 09:08:31 -0700 (PDT)
To: Dino Farinacci <farinacci@gmail.com>
References: <B25C7BF8-93D4-464E-8A3E-88720612E0AD@telecom-paristech.fr> <561D7D55.3090305@cisco.com> <CAGE_Qex6iVji+9=Fw79DeNQ+YAUpy_EcU-Yhr4NruOYADKzNnw@mail.gmail.com> <DE654947-A08B-47DD-A3FA-7DE611C42BA4@gigix.net> <CAGE_Qewmo6d4n+f0MLVMH7kje_H+BVRj33h7H876Fs3JLR-LLQ@mail.gmail.com> <561EDF6E.60805@joelhalpern.com> <BF726F7B-815F-46C0-8479-8E3F08BD1A75@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <561FCF7E.2050107@joelhalpern.com>
Date: Thu, 15 Oct 2015 12:08:30 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <BF726F7B-815F-46C0-8479-8E3F08BD1A75@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/jNW6isHVtNXiVival5HExnvPm0Q>
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] Draft of new Proposed Charter
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 16:08:34 -0000

Agreed.  My concerns in the LCAF aspects revolve around EID usage.  RLOC 
usage is, as you say, understandable.

Yours,
joel

On 10/15/15 11:26 AM, Dino Farinacci wrote:
>> I am really unclear as to what the problem being addressed by creating a programmatic language for LCAFs is.  Heck, I am confused by what the JSON LCAFs are solving too.
>
> At this point in time, it is not clear to me how the JSON LCAF would be used as an EID-record. However, returning a JSON dictionary array as output of a lookup (an RLOC-record), is quite useful. Doing that latter requires no mapping system changes. Doing the former would require a major change IMO.
>
> Dino
>

v2.23.0 | Report a Bug | By Email