Re: [lisp] Capabilities Type LCAF - a proposal

Roger Jørgensen <rogerj@gmail.com> Wed, 20 November 2013 19:20 UTC

Return-Path: <rogerj@gmail.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 B2D901AE0A1 for <lisp@ietfa.amsl.com>; Wed, 20 Nov 2013 11:20:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 5md2AFQizR1z for <lisp@ietfa.amsl.com>; Wed, 20 Nov 2013 11:20:02 -0800 (PST)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1F76A1ADF8E for <lisp@ietf.org>; Wed, 20 Nov 2013 11:20:01 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id n12so9618853wgh.10 for <lisp@ietf.org>; Wed, 20 Nov 2013 11:19:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y67B6JH5TJHv5Y+deHJVUrOd56rev18hpFvfF0tu0sM=; b=WOSXJh/UFM5HJQLqHlrbTjkmSOLmA21oEbI8mRKK/+6XJyLjY86Hx56Fj4OZ/klDtI 3zPX1SRefZNV20j+wjKUrbwan05sFxhaWzF4gdvRa6LpkRyPEAQ2hkCOCGrqNqGselk8 X5PT8s17xZq56oKWxa4K1Df5EpYYyQ7yLDOKOwzTwMxyGf6QkYELubeh1P3gno4Fnv4O /utvLt6uajCT/Fc9TZcdiu3SyQ5LE/PcGWJPtS+6l+aV+W8VepIV59/5Wr2xJ+0ITFnG TEkFh2lFGGMl3byecEUDsohBhIw8QMqiyzqI1pb+fA8Bs+djfjb2J9e0NubVgpzb2RGN bALA==
MIME-Version: 1.0
X-Received: by 10.194.63.228 with SMTP id j4mr2182056wjs.34.1384975195145; Wed, 20 Nov 2013 11:19:55 -0800 (PST)
Received: by 10.217.89.4 with HTTP; Wed, 20 Nov 2013 11:19:55 -0800 (PST)
In-Reply-To: <20131120124143.CD2B618C147@mercury.lcs.mit.edu>
References: <20131120124143.CD2B618C147@mercury.lcs.mit.edu>
Date: Wed, 20 Nov 2013 20:19:55 +0100
Message-ID: <CAKFn1SE13S_BgepxHMfkOwPT-wx=H0V7H2mgRVjV=1Ut2kWzzQ@mail.gmail.com>
From: Roger Jørgensen <rogerj@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, Dino Farinacci <farinacci@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] Capabilities Type LCAF - a proposal
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: <http://www.ietf.org/mail-archive/web/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: Wed, 20 Nov 2013 19:20:03 -0000

On Wed, Nov 20, 2013 at 1:41 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>     > From: Damien Saucez <damien.saucez@gmail.com>
>
>     > I would have a question, if there is capability, it means that there is
>     > a possibility to meet no capability so in this case what is replied?
>     > ...
>     > If 0 locators then it is a negative reply but conceptually this is not
>     > a negative reply. If no answer, then the requester will keep continuing
>     > sending requests.
>
> Good points.
>
> In general, I don't think we should keep tweaking Map-Request and Map-Reply
> messages 'because they are there'. If we need to extend semantics, let's do
> it right.

Keep tweaking existing things to support all sort of new idea only
lead to complexity, and more problem somewhere down the road.

But I do see the need for that Dino describe.


>     > If a new message, what kind of message?
>
> The has been some discussion about adding a new message-type to fill a
> variety of roles which involve transferring information around (e.g.
> dynamically loading configuration information such as default PxTRs into
> small xTRs, a la DHCP, instead of having to manuall configure them).
>
> This would seem to naturally fall into that general classification?

I would support doing this as a new message in the form of a framework
to support existing idea, new idea and future needs. Sort of a version
2 extension. You don't need it, but if you support it an use it you
get access to a whole range of cool and fancy extension of LISP :-)



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no