Re: [Int-area] ILA and int-area

Tom Herbert <> Sat, 13 May 2017 18:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BA681129B16 for <>; Sat, 13 May 2017 11:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QgSl7Ywc_8Fw for <>; Sat, 13 May 2017 11:24:04 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 16C7C129BDB for <>; Sat, 13 May 2017 11:21:13 -0700 (PDT)
Received: by with SMTP id y201so69341927qka.0 for <>; Sat, 13 May 2017 11:21:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JbHDR5C3E51vVlPosQIZdymUi9RzL6FzbD/nOy/aLR8=; b=PvYwFUtjlRo3xsKjXEpxZ7BoS7y66mu+t9InF77CTj6KBCRTPv8sndI1SFxnEsGBU4 8+yQUnPTQJKZqSVFnKLQlI3SZUPCE0us0Fp+DqpsabKP4tU2Y/hMGN/oY5mjjRI92/cz oohnXeYNh05mz8VKTlnH//WPMGvDhIllQIcJk40w70WFxmPvEywPcEQS65NX+35R48f9 eqhc7fFYwe2X94aBIzxYbT5UtqS5lPfWqz9tJtLpzaMk9Upuq+qW6uSL1fQ2i5td6ZAE Ca+oiEtFRPQ1mQI6h9KrQiLJorDDr9bGvkgkzE3m86VoDoa2zFiJUzIkPaXuYGjU+o+7 m3Dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JbHDR5C3E51vVlPosQIZdymUi9RzL6FzbD/nOy/aLR8=; b=THXAC29cblYSMcbgUkQLL1fTVMDSCP513KU6TYI6jTm5+KH98RrtdM9yr/Pk+bC19u 6eGhGaHODbga3H9c3hi6bB7ScM7nIF406jzJfpjWZGhqIaDMSw6rvuzvmf1yS86pesiP wrGo5RRbicNyMm3E7SxMw1pGT3rqLlWaMtX9YcUjZ/HHjWtiLIap8UEcGfDtB1mU5okh fVRl4e51+4CPTIswgvUuO8UWUs6Wyp1xhWrDv3Fy2BL48yeT83bkk9BpFKcxh4MVV/Y1 37bJavdtcS6iCPF0yM6SqgznkDaZn3YFB8GsSGKTn4LBUdSCxS0kOvUbRtbywtIPvDrG Rsig==
X-Gm-Message-State: AODbwcBVpSf2z8DJ8bPcaYZ7mg8W+uwgRgoK8vxzezdt8P/sh6VEFlwS 3YryDBQ9/i5eI98wbGeCHk1K8yBBKA==
X-Received: by with SMTP id m1mr9585347qkd.270.1494699672203; Sat, 13 May 2017 11:21:12 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sat, 13 May 2017 11:21:11 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: Tom Herbert <>
Date: Sat, 13 May 2017 11:21:11 -0700
Message-ID: <>
To: "Joel M. Halpern" <>
Cc: "" <>, Petr Lapukhov <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Int-area] ILA and int-area
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 13 May 2017 18:24:06 -0000

On Sat, May 13, 2017 at 11:03 AM, Joel M. Halpern <> wrote:
> It appears to me that there are contexts in which it is likely that ILA is
> useful.
> Using the example of the progression of LISP, I have concern with the
> current approach of NOT spelling out how and where it would be used. LISP
> started out as experimental in significant part because it was not clear
> where it would be useful.  We re now progressing it to PS with a clear
> context.  And that context is NOT Internet-wide deployment for Internet
> scaling.  Because that deployment problem is REALLY challenging.
> As such, if ILA wants to either be developed for the data center context or
> be developed as an interesting experiment across a range of potential uses,
> I can not object.
> I do have problems moving it forward towards standards track for some
> unspecified but general use in its current form.  The dependence of the data
> plane protocol on the information distribution is so strong that I do not
> see how the general case can be treated.
Hi Joel,

Intended status is listed as informational if that helps.

I tend to think that the relationship between an ILA data plane and
control plane is analogous to the relationship between the IP protocol
and routing protocols. Yes, there is a strong dependency on having a
control plane, but mandating a specific control plane as part of the
core protocol reduces flexibility and extensibility.


> Yours,
> Joel
> On 5/13/17 1:42 PM, Tom Herbert wrote:
>> Hello,
>> At the Chicago WG meeting I made a request that ILA be taken up as a
>> WG item in int-area. The WG chairs and AD requested that we raise a
>> discussion on the list about what else is needed to be done for ILA
>> (Identifier Locator Addressing draft-herbert-nvo3-ila-04). The
>> question was also raised if int-area is the right WG for ILA or if it
>> should have a BOF.
>> The current draft of ILA describes the data plane and addressing, a
>> model for ILA for ILA routing and network topology, several use case
>> scenarios on how ILA might be applied, a format for identifiers to
>> allow different types of identifiers and checksum neutral mapping. As
>> I mentioned we intend to make the last one optional so that
>> administrators can choose how structure the 64 bit identifiers as they
>> see fit-- this will be reflected in the next version of the draft.
>> The draft explicitly does not define a specific control plane (e.g.
>> routing protocol) for ILA and I don't think that it should. IMO ILA
>> would be better served to allow various methods that are protocol
>> generic where ILA could be a use case of those mechanisms. For
>> instance, draft-lapukhov-bgp-ila-afi-02 describes and extension for
>> BGP. Similarly, if a protocol agnostic control plane is developed in
>> IDEAS or in nvo3, then ILA could be one use case for those. I would
>> think the control plane seems more appropriate to be in routing area
>> than int-area.
>> As for what is still missing in the core ILA draft, besides making
>> typed identifiers optional, I think it is fairly complete for the data
>> plane description. It is being deployed in a least on datacenter for
>> network virtualization, and it is being discussed as part of a
>> solution to support IP mobility (see 5GandIP discussions).
>> Tom
>> _______________________________________________
>> Int-area mailing list