IETF Logo Mail Archive

Re: [lisp] draft-ietf-lisp-introduction - Design Principles and Use Cases

Dino Farinacci <farinacci@gmail.com> Mon, 13 October 2014 20:18 UTC

Return-Path: <farinacci@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 1BFED1A000A for <lisp@ietfa.amsl.com>; Mon, 13 Oct 2014 13:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 7dfQRNhexWjJ for <lisp@ietfa.amsl.com>; Mon, 13 Oct 2014 13:18:47 -0700 (PDT)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBE401A0033 for <lisp@ietf.org>; Mon, 13 Oct 2014 13:18:45 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id v10so4987987qac.12 for <lisp@ietf.org>; Mon, 13 Oct 2014 13:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QIDGuSUGVeIXA59lKwlba24zOUMstnfTUVOy7RHgenk=; b=j+p2Re9xQfHrUwTi+c5VYajUwV9lbZK0fpjgUBaek1VklQl/L5d+dslv/WjjnVzArv SxFHzngXql0RbONtmEpz8zbLbmN4Kf4Q26o4PuTauMIIyY4Yc+aaY6AOjSBg+oMvsVQ3 U5ZGo4VQL++YBnPK1ZGVJACT6J8VF01uK++vMtLXgfDxvijoJav2V5M4fRyMPuDhkpj7 qAlbDA4nZ+CA2+aJpm/1ZUP7vGHpseGHQ763p+HDG4DgkEvLTR7aoADV75D49/6Ejbke TK3ATxoM4T134VTufmwgoTO1iMnAnERg8LtEgbweoV6aou79HolQbVBqHOGbZEaRin05 Qoxw==
X-Received: by 10.140.108.35 with SMTP id i32mr1497902qgf.66.1413231524975; Mon, 13 Oct 2014 13:18:44 -0700 (PDT)
Received: from [172.20.10.2] ([166.170.28.78]) by mx.google.com with ESMTPSA id p3sm13679145qaa.31.2014.10.13.13.18.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Oct 2014 13:18:44 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAGE_QezAGP7Rvg2hLBrbKs-JDFNXQ6qga15pg8WnX9GO+qU4Pg@mail.gmail.com>
Date: Mon, 13 Oct 2014 13:18:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A935778-02D5-4F41-AC84-153025645B24@gmail.com>
References: <a9e800cf8a2c468ab72524d182aaad64@CO1PR05MB442.namprd05.prod.outlook.com> <BE54EC54-FCEA-4333-B5BD-1861AA0537EC@gmail.com> <5ad34cf8c2bb4e87a471cf80e9dcc3f3@CO1PR05MB442.namprd05.prod.outlook.com> <20139005-A5CE-4E48-A5AD-04B395DA934E@gmail.com> <241960CF-6E66-4F1B-B7FC-33096A718EE7@gigix.net> <9E9D872A-39A7-4FCE-9166-C5FDC3224EBB@gmail.com> <CAGE_QezAGP7Rvg2hLBrbKs-JDFNXQ6qga15pg8WnX9GO+qU4Pg@mail.gmail.com>
To: Albert Cabellos <acabello@ac.upc.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/YAMR967gmk_8l1dygDRYAijvM_8
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] draft-ietf-lisp-introduction - Design Principles and Use Cases
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: Mon, 13 Oct 2014 20:18:49 -0000

> Hi all
> 
> What about this (as a new item in section 2.1)?
> 
> * Pull Architecture: With this principle the network state is stored
> at the control-plane -in a potentially distributed database- and
> retrieved on-demand by the data-plane. Pull architectures allow to
> push important routing mechanisms such as Traffic Engineering to the
> control-plane, alleviating the data-plane. At the same time they
> require of additional techniques to handle data-plane events, such as
> network failures.

Well even though we like to stress a Pull architecture with LISP, we all know well that if xTRs run LISP-ALT that it is very much a push archtecture. 

See (I hope Alia is listening), it is not about a LISP versus BGP control-plane, because one of the RFC documented mapping database transport system is LISP-ALT which IS BGP.

LISP is indeed a "cached architecture" which means the FIB needs to be populated on demand. But if the state is local in a database, LISP-ALT BGP RIB, then the information is available locally.

When I was at cisco, we did some customer testing where the customer wanted to use BGP as the mapping database so FIB hardware lookups cache-missed, then the BGP RIB was consulted. They had requirements to not go outside of the box to get the cache populated. Turns out they wanted small hardware FIBs and had large software RIBs, hence using LISP to push via BGP was a naturual fit.

Dino

> 
> Albert
> 
> On Mon, Oct 13, 2014 at 4:31 PM, Dino Farinacci <farinacci@gmail.com> wrote:
>>> 
>>> The only remaining question is whether or not we want to add a bullet concerning the push/pull model & Mapping database
>> 
>> Well since a large portion of the document discusses the mapping system, I would say yes.
>> 
>> Dino
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email