IETF Logo Mail Archive

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

Dino Farinacci <farinacci@gmail.com> Sun, 12 October 2014 01:32 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 6F9E81A02E8 for <lisp@ietfa.amsl.com>; Sat, 11 Oct 2014 18:32:38 -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 WjHhKT44rVZx for <lisp@ietfa.amsl.com>; Sat, 11 Oct 2014 18:32:36 -0700 (PDT)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 736411A02DA for <lisp@ietf.org>; Sat, 11 Oct 2014 18:32:36 -0700 (PDT)
Received: by mail-qg0-f48.google.com with SMTP id i50so5492007qgf.21 for <lisp@ietf.org>; Sat, 11 Oct 2014 18:32:35 -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=ncwxyAgp/UL2eimtBacut82YoAy2qSsrMYrgytFlY5k=; b=fpY8EvuBkHe4YUFyJh64jFpZet/7WhXcGGIias9kbhTJELdyzoq0f5M+8sxp3lnsCk zer6Ahn839V66aJGfnacAEU/lMy5bC29dEI0ENG1Jr1bY7aNIBg1v8/LFUyktaVVWmz9 v/YJ7DmkoXt0MPMGaQTQxET+OGP1usVeYizEGdrf7qvrXNFVetCyMF+6XRZQxeGIhlSX 5LbpshtQjtI9dPdyh38Gb02wgnf7GpL61Ap8AW97A5fmCR5+6oINmur9rP8nxX24QaQ6 DrTY6qdFHccmS6AYD3nvJsmDV/coTtiPW9ceX41LkuPf1E0ezEI1tTzSq5eGHFzYJ9yl 94jA==
X-Received: by 10.140.28.8 with SMTP id 8mr23938402qgy.19.1413077555568; Sat, 11 Oct 2014 18:32:35 -0700 (PDT)
Received: from [192.168.1.31] (pool-72-92-14-140.phlapa.east.verizon.net. [72.92.14.140]) by mx.google.com with ESMTPSA id n46sm8876833qgn.9.2014.10.11.18.32.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 Oct 2014 18:32:35 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (12A405)
In-Reply-To: <5ad34cf8c2bb4e87a471cf80e9dcc3f3@CO1PR05MB442.namprd05.prod.outlook.com>
Date: Sat, 11 Oct 2014 21:32:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <20139005-A5CE-4E48-A5AD-04B395DA934E@gmail.com>
References: <a9e800cf8a2c468ab72524d182aaad64@CO1PR05MB442.namprd05.prod.outlook.com> <BE54EC54-FCEA-4333-B5BD-1861AA0537EC@gmail.com> <5ad34cf8c2bb4e87a471cf80e9dcc3f3@CO1PR05MB442.namprd05.prod.outlook.com>
To: Ronald Bonica <rbonica@juniper.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/a2L4y24Mfc2nT5rpe_0YMrOaa98
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: Sun, 12 Oct 2014 01:32:38 -0000

Well everything tends to look the same but not in this case. This is the first mapping database that is really fully specified and tested at the network layer. 

Dino


> On Oct 11, 2014, at 9:20 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> 
> Dino,
> 
> That too!
> 
> However, the mapping database system is not entirely unique to LISP. Every architecture that maps one address space to another needs a data base to maintain mapping information. The part that is unique to LISP is how the data is distributed
> 
>                                                                     Ron
> 
> 
>> -----Original Message-----
>> From: Dino Farinacci [mailto:farinacci@gmail.com]
>> Sent: Saturday, October 11, 2014 9:02 PM
>> To: Ronald Bonica
>> Cc: lisp@ietf.org
>> Subject: Re: [lisp] draft-ietf-lisp-introduction - Design Principles and Use
>> Cases
>> 
>>> On Oct 11, 2014, at 7:51 PM, Ronald Bonica <rbonica@juniper.net> wrote:
>>> 
>>> In Section 2.1, we say that LISP is built on top of four basic design principles:
>>> 
>>>  - Locator/Identifier split
>>>  - Overlay architecture
>>>  - Decoupled data and control-plane
>>>  - Incremental deployability
>> 
>> You left out one that is really important:
>> 
>> - A Mapping Database System
>> 
>> Dino

v2.23.0 | Report a Bug | By Email