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

"Joel M. Halpern" <jmh@joelhalpern.com> Sat, 13 May 2017 18:06 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEAAD129411 for <int-area@ietfa.amsl.com>; Sat, 13 May 2017 11:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level:
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 I7gHqj8fdvFs for <int-area@ietfa.amsl.com>; Sat, 13 May 2017 11:06:15 -0700 (PDT)
Received: from mailb1.tigertech.net (mailb1.tigertech.net [208.80.4.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF0A8129ADC for <int-area@ietf.org>; Sat, 13 May 2017 11:03:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb1.tigertech.net (Postfix) with ESMTP id B2289D40329; Sat, 13 May 2017 11:03:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1494698592; bh=221/jjz0SEzOEY0jFS9fRasvKmET9GihEuNe43gB/m0=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=A5V9n3UHphcYNb4J9Ov7SAx87L+1YcHnkjXcZhm4+VUPFijxBnlWZH4bzpOD+nvSN Ol10kQ76ZPZkzlnOg+XceOf2IL36gwtek39XIW0KeSje2NKe+XV/RZigXOEcXmIF7T CND5OOrXyiyVxyySZjwsOoCLzJ1U5LVMmeETjkSk=
X-Virus-Scanned: Debian amavisd-new at mailb1.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb1.tigertech.net (Postfix) with ESMTPSA id 1A83DD401AE; Sat, 13 May 2017 11:03:11 -0700 (PDT)
To: Tom Herbert <tom@herbertland.com>, "int-area@ietf.org" <int-area@ietf.org>
References: <CALx6S34A5k_DtEb7YWQs=Y79p4rCpe-9Hg3_YiqbOSyWzqepYA@mail.gmail.com>
Cc: Petr Lapukhov <petr@fb.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <813a6560-4513-958a-0898-d42133285a34@joelhalpern.com>
Date: Sat, 13 May 2017 14:03:10 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CALx6S34A5k_DtEb7YWQs=Y79p4rCpe-9Hg3_YiqbOSyWzqepYA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/8_b87buk0fCr1xJZqwCKRF1Fo4s>
Subject: Re: [Int-area] ILA and int-area
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 May 2017 18:06:17 -0000

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.

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
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>