Re: [lisp] LISP Use Cases

Dino Farinacci <farinacci@gmail.com> Tue, 25 August 2015 17:02 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 E45EB1A1A98 for <lisp@ietfa.amsl.com>; Tue, 25 Aug 2015 10:02:01 -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 1RR_XuGggPVs for <lisp@ietfa.amsl.com>; Tue, 25 Aug 2015 10:02:00 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (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 CD5401A90F0 for <lisp@ietf.org>; Tue, 25 Aug 2015 10:02:00 -0700 (PDT)
Received: by pacti10 with SMTP id ti10so56708932pac.0 for <lisp@ietf.org>; Tue, 25 Aug 2015 10:02:00 -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=T0Gf657k00mLq6mjw1WrvOtqAbOa2WKeNeLiU4mp+Js=; b=Zf90W1jIYE31QYpoOAGIxmcVoIa9jFrwwczhCC1Gkq3PQoMvgO5tTUdS52LCEQRHXb Q+sWiyyyb1ryQvDvutG7hhLQFlReQJNV8RoKHRGHmzO17uAMtOAAzJT6TmTuVUTT2NZ5 yuGSeWsvC1iWPvYDUdR73KHYM0QJZ1SYQzao9HwRCn2X99v2qTiPuRCfa3z4ER02BDV6 ZLig3pcsRHHu7M0/aiHZVfHVkm0qFMdzMrZWgB69nSoNk8Oo756YSpr1z2KQxmn4ATXe O2hu9fH7V47m9oHLppUzJDfRnithwdTQbupWIUEFdXMQ/bTz87cN24cp7bi3eQI9jias ltAw==
X-Received: by 10.66.154.167 with SMTP id vp7mr57307771pab.147.1440522120457; Tue, 25 Aug 2015 10:02:00 -0700 (PDT)
Received: from [172.20.10.2] ([166.170.42.197]) by smtp.gmail.com with ESMTPSA id fn15sm21696471pdb.50.2015.08.25.10.01.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Aug 2015 10:01:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <79C91048-2FD5-4DE7-9FBD-381E8489C9AF@gigix.net>
Date: Tue, 25 Aug 2015 10:02:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A119874-1017-4D3E-BDAA-8D8E088E430C@gmail.com>
References: <77630894-48BB-483D-BE68-A15555F55CE2@gigix.net> <B1A519EE-2953-4BD2-920C-45AA21617147@gmail.com> <55C92A78.2050406@joelhalpern.com> <20E63E0C-01BC-4370-9C0D-12E11630E9AA@gmail.com> <CAHANBtK5WKh-9Ljw98JwtsAc3qtgzkMu1wuZE4a3nKmOerLJTA@mail.gmail.com> <7D1E5F8A-7A83-4158-A770-4468986EC380@gmail.com> <CAHANBtLNmXuub6Y7P1v497rGWN9TvMak7y9S_beYW6xHwkg5-Q@mail.gmail.com> <C92EE070-B694-44AE-B273-4E6BBBA70C05@gmail.com> <0BD14407-A35D-451D-B166-0D5CD36619D5@gmail.com> <79C91048-2FD5-4DE7-9FBD-381E8489C9AF@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/m__gLRIcrw1j28WHuqI6nTgrwl8>
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] LISP 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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 25 Aug 2015 17:02:02 -0000

> We cannot write a charter that states “LISP will support NVO3 use-cases”.

How about this specific text:

For the NVo3 use-case, LISP will support L2-overlays by selecting a data-plane that supports encapsulation of MAC frames in IPv4 or IPv6 packets and by using the mapping database that supports (instance-ID, MAC-address) extended-EIDs.

Dino