Re: [lisp] LISP Use Cases

Dino Farinacci <farinacci@gmail.com> Mon, 10 August 2015 23:11 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 A6AEA1A1A12 for <lisp@ietfa.amsl.com>; Mon, 10 Aug 2015 16:11:32 -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 iiZpPdNjhMGZ for <lisp@ietfa.amsl.com>; Mon, 10 Aug 2015 16:11:31 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::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 46F641A1A0C for <lisp@ietf.org>; Mon, 10 Aug 2015 16:11:31 -0700 (PDT)
Received: by pacgr6 with SMTP id gr6so36241916pac.2 for <lisp@ietf.org>; Mon, 10 Aug 2015 16:11:31 -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=TuLfrHWbqs6t+TSCQW9oDIzG4YzSx4l55sbi8c0S9Aw=; b=g1LukYL89RBNHvbcZqyth80fVPQLzy2wMNx2IwQ6aTITXySvkOwkTaaqXrZQNCIWIH oN6hY7GNiruq4bipW4pGtVwLx0Z0JJc/jpWe24MqYlIrNUKFb4r7xMr2EON1KPkllU59 /40uVhWlDIoylzqVwH7h12VKOZU+kCMEHjs3U45KvbfcYJkGD9KWTjVz7DvnzrTj6rnM N5Av4x12V/02FE5Jj1fjrmxjI+vsq0kDCYiLF2QooIEs2yyJysqk/tvrYSpMDfg4AmI8 b9SKo0jD8v5Qyb/+C/VpRJuRrECJxJzRWc34T2pD+QNPWf2R4mRenblyCcylpRKwVr5J FsEw==
X-Received: by 10.66.160.1 with SMTP id xg1mr49481226pab.27.1439248290956; Mon, 10 Aug 2015 16:11:30 -0700 (PDT)
Received: from [172.20.10.2] ([166.170.37.247]) by smtp.gmail.com with ESMTPSA id nh3sm34529pdb.72.2015.08.10.16.11.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Aug 2015 16:11:30 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <55C92A78.2050406@joelhalpern.com>
Date: Mon, 10 Aug 2015 16:11:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <20E63E0C-01BC-4370-9C0D-12E11630E9AA@gmail.com>
References: <77630894-48BB-483D-BE68-A15555F55CE2@gigix.net> <B1A519EE-2953-4BD2-920C-45AA21617147@gmail.com> <55C92A78.2050406@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/RE1JOYqeuwNNzwwtUEtt9MhZHoA>
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: Mon, 10 Aug 2015 23:11:32 -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.

On IoT or mobile node may want to send multicast packets. Those multicast packets need to get to receivers. The receivers may be at LISP sites.

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

If you want to support other transports and you want to stretch L2 subnets, then ARP and IPv6 link-local multicast will need to be supported. That means the overlay needs to transport multicast packets.

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

Right. And a node in a VPN site can be anywhere.

> 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.

SDN, in my mind is a network management mechanism. When we talk about the LISP architecture and protocols, we are talking about in-network control-plane mechanisms (and I mean between nodes in the network in a distributed fashion).

Dino

> 
> 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
>> 
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp