IETF Logo Mail Archive

Re: [lisp] LISP Use Cases

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 10 August 2015 22:49 UTC

Return-Path: <jmh@joelhalpern.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 342891A0191 for <lisp@ietfa.amsl.com>; Mon, 10 Aug 2015 15:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 D55X9UViZduK for <lisp@ietfa.amsl.com>; Mon, 10 Aug 2015 15:49:30 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 299031A00CD for <lisp@ietf.org>; Mon, 10 Aug 2015 15:49:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 151CB24024B for <lisp@ietf.org>; Mon, 10 Aug 2015 15:49:30 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id C2DF5240C1C for <lisp@ietf.org>; Mon, 10 Aug 2015 15:49:29 -0700 (PDT)
References: <77630894-48BB-483D-BE68-A15555F55CE2@gigix.net> <B1A519EE-2953-4BD2-920C-45AA21617147@gmail.com>
To: LISP mailing list list <lisp@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <55C92A78.2050406@joelhalpern.com>
Date: Mon, 10 Aug 2015 18:49:28 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <B1A519EE-2953-4BD2-920C-45AA21617147@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/d6lSMMzbFKRgSS52SnU9wCoq70k>
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: Mon, 10 Aug 2015 22:49:31 -0000

Casn you expand a bit.  It is not obvious to me that either IoT or 
Mobile Node needs multicast support from LISP for its LISP usage.

For example, people keep talking about multicast video, but in fact we 
know that is a corner case and become even less common.

Data Center clearly needs some multicast.  I can see some argument for VPN.

Since SDN is simply a way of deploying other things, multicast in VPN 
contexts clearly depends upon what problem you are using SDN to solve.

Yours,
Joel

On 8/10/15 6:42 PM, Dino Farinacci wrote:
>> - LISP VPN (including integration with IPsec)
>> - NVO3 use case for DC virtualization (including support for VM mobility)
>> - SDN/NFV (including support for service chaining)
>> - IoT (LISP as connecting infrastructure for IoT applications)
>> - Mobile Node  (LISP-MN mobility)
>
> And I would say all these use-cases must support multicast packets and packets that traverse through NATs. Those are not separate use-cases but baselines that each use-case needs to support.
>
> Dino
>

v2.23.0 | Report a Bug | By Email