Re: [Ila] [lisp] LISP for ILA - scaling

Dino Farinacci <farinacci@gmail.com> Sat, 17 March 2018 00:44 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: ila@ietfa.amsl.com
Delivered-To: ila@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 835321243F3; Fri, 16 Mar 2018 17:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dUyExRCPBYFA; Fri, 16 Mar 2018 17:44:36 -0700 (PDT)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FE28120454; Fri, 16 Mar 2018 17:44:36 -0700 (PDT)
Received: by mail-pg0-x22f.google.com with SMTP id w17so4723793pgq.8; Fri, 16 Mar 2018 17:44:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=21KZz7+CxjlgjW8xFbD569j2Aev8/nDwAHZVvKQpcnI=; b=bz+9KM8tVw4lQICKizOCOzY15a3ZG7npzWSMm3JI3VRRhZJLOH0I31WE4LZFbyx+C8 fg7o7A1b0Yj3bMjOdKQtZQ1fGXvqi9PN0oOB957n60gV2EGO/FgYCNIsFMvrfIWZyRPw gVgSLN+/G4j/GBTyzQ3nw6h4I95xADAhk9OByjux1XXylWjBZdqua6R44dbxtwo1hlRu cGXOoGkc+8uOvKBMV3urhBXj1+hC/wpouthDdGzhRuwNvtHrtrtkTTWDqsjPoDRCF66x P6n6CSpolMTJ09/gtCG+Tli1Eg9x3Sn325114pqYtS9gjvD1BZQKLGFgKSfk7D0T2eZu iJTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=21KZz7+CxjlgjW8xFbD569j2Aev8/nDwAHZVvKQpcnI=; b=c2b1abS2Rtts7eCfLck/XdclH/fTbilNtedA54H+Q4shWHA4MhzSWuamiz4GYWWANE eYgV2CXacZ3ZvUVnZpJJL6XCgWwk7y+1Va3go56hrMvf6Pz4LV2badqEtAJwo9GcJOg7 TYNQwJsj5yAOLa8W2L5x+VyMzAF0Hp2E5NwA72EsxtUEVikxtzNegCgxFkkw9sqqY4Ck hwqE6b49gLyxGuTRsAuWEWCFzp+faXvbCXBKwSc+5UtgQplPqejuxaMIK3UrhtzxoYGq UsxT606bEsCAYuN/BUfow8OiRUVHqEombJa/r9IrUpgmIYw8QijZbDRANXVpgn2yPz9K 2itw==
X-Gm-Message-State: AElRT7EB5gdC4H/gzJakzOxvgow/jymi8W9Pievny5RX++l10VGQsr6t A0HKeDGi9dtHn3VLiHJpFvE=
X-Google-Smtp-Source: AG47ELseCku2MCwwRFmLDA+sizUPA5Ue87RofztRglkG06gzH99olk8PEe5dtYJt1N4wCu6XtyU5DA==
X-Received: by 10.98.150.82 with SMTP id c79mr3273944pfe.88.1521247475891; Fri, 16 Mar 2018 17:44:35 -0700 (PDT)
Received: from ?IPv6:2603:3024:151c:55f0:f0b2:7957:5409:30dd? ([2603:3024:151c:55f0:f0b2:7957:5409:30dd]) by smtp.gmail.com with ESMTPSA id a67sm14884428pgc.6.2018.03.16.17.44.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Mar 2018 17:44:35 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <d70c3927-bb59-a78c-7675-185968ab222d@joelhalpern.com>
Date: Fri, 16 Mar 2018 17:44:34 -0700
Cc: Tom Herbert <tom@quantonium.net>, David Meyer <dmm@1-4-5.net>, "Alberto Rodriguez Natal (natal)" <natal@cisco.com>, Florin Coras <fcoras.lists@gmail.com>, "ila@ietf.org" <ila@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, Eliot Lear <elear@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <03B18A68-D80B-4B7D-A2A4-5D539FF1AEEC@gmail.com>
References: <F1093230-C087-4168-9C5F-8DA7AB677677@cisco.com> <CAPDqMer58nxEixtH=JuZh9WgM0xKkEQYEjwZ6zg3wTjD76gOHQ@mail.gmail.com> <F920CAE2-9042-41DF-B013-E8FE6F891596@cisco.com> <CAPDqMeriMzM82-R-JOgx4zuqJTk2YOoBaWV_58no2V8yPas9QA@mail.gmail.com> <CF1C238D-FBE9-48BC-A7A6-49E45249E5E2@cisco.com> <CAPDqMeqL1kE+N9APFOSR4fUaek0TjZuDZMZDzDmJfMvyLO38GA@mail.gmail.com> <DA74C61A-647A-44BA-8FE7-916CF8895C49@gmail.com> <CAPDqMeqkGH0ELN=XmqF3dmsdeAurE-y+_H9+_E8mzhHo9d9nXw@mail.gmail.com> <7793B214-A235-4795-983B-CCC75A0B90BE@gmail.com> <CAPDqMeo2bdmwSEkPk002W9oxPhyxnLrr-k9MYeR5ZXEG_OGH0g@mail.gmail.com> <11EDF4FB-8636-4DF2-B687-1AB4934C4F9D@gmail.com> <CAPDqMeoSLqC=mN_hcgiLe-3Dv0c=uezbrZZ9xHn47Osb7rfLVQ@mail.gmail.com> <16F3AEC4-EDCF-417B-8165-D22C48A06F3D@gmail.com> <CAPDqMer8m5ySuXBoSbBW0vcMnNTj-DxiHykNW+S6y=ReYnMrjA@mail.gmail.com> <C7DECE90-D5D6-496B-A5AA-4C3E3695C546@gmail.com> <CAPDqMepNbTJvC-=5fhX0wLOaxX3znmNCb44D77qN7XmfR_eWHQ@mail.gmail.com> <d70c3927-bb59-a78c-7675-185968ab222d@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/Vc763Zt4DrjDmXC-VSnC2xrrOXc>
Subject: Re: [Ila] [lisp] LISP for ILA - scaling
X-BeenThere: ila@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Identifier Locator Addressing <ila.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ila>, <mailto:ila-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ila/>
List-Post: <mailto:ila@ietf.org>
List-Help: <mailto:ila-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ila>, <mailto:ila-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2018 00:44:39 -0000

Copying Eliot.

I don’t remember Eliot analyzing the data-plane. But he did see how far the mapping database could scale with push and don’t recall he saying 1 billion would be achievable either.

Dino

> On Mar 16, 2018, at 2:53 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> From the analysis Eliot did many years ago for a LISP push solution, for any constrained solution (a data center, a mobile operator, a fixed service operator) the number of entries is probably not a problem.  Even for a conventional router.  Churn rate, in its various manifestations, could well be an issue.
> 
> Sharding is but one of several ways to divide and conquer to avoid those issues.  Separating control load from data plane load is also a useful way to help keep things manageable.
> 
> Yours,
> Joel
> 
> On 3/16/18 3:33 PM, Tom Herbert wrote:
>> On Fri, Mar 16, 2018 at 12:17 PM, Dino Farinacci <farinacci@gmail.com> wrote:
>>> Yes, understand. But even in your constrained “domain”, there may be just too much state to push to all nodes. Especially in the 5G use-case. It wasn’t a problem in the LISP beta network because the proxy xTRs had relatively coarse prefixes that reached lots of EIDs.
>>> 
>> The state would need to be sharded. You'd probably need to do this
>> anyway for mapping-servers or high thoughput Internet facing routers
>> for which using a cache would be challenging.
>> Tom
>>>> require provisioning ILA-Rs to handle the full load if necessary to be
>>>> robust.
>>> 
>>> Yes indeed.
>>> 
>>> Dino
>>> 
>> _______________________________________________
>> ila mailing list
>> ila@ietf.org
>> https://www.ietf.org/mailman/listinfo/ila