IETF Logo Mail Archive

Re: [lisp] LISP Use Cases

Luigi Iannone <ggx@gigix.net> Tue, 25 August 2015 09:14 UTC

Return-Path: <ggx@gigix.net>
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 5E4691A90EC for <lisp@ietfa.amsl.com>; Tue, 25 Aug 2015 02:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 LEjeQajnZcXU for <lisp@ietfa.amsl.com>; Tue, 25 Aug 2015 02:14:16 -0700 (PDT)
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (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 53D2A1A8A4F for <lisp@ietf.org>; Tue, 25 Aug 2015 02:14:16 -0700 (PDT)
Received: by wicne3 with SMTP id ne3so8657965wic.0 for <lisp@ietf.org>; Tue, 25 Aug 2015 02:14:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=OLsDZFrT0R6dRvyYaIPANc3NnGr7uL00H3X6bzDIl9Q=; b=Yi4DBmnIIFyTv/w7EHdhJoTN9wOzmlJYI7eRt0SUHL74oeoJ8q+xvUQIsVr99uHOzH 6CvSJ6zj9T0gj3OykKPFowQ2mvuszSCYCg17nuQM74Wn+J19Db+BqcBiGF7jgAHfDfMV bLIqML+rBFyvcaOnWsEdgBMdVSYtqAilNKoUFgryYEUgD7jZ8vdtK3LlAExOfiGr25PP tsUmGlS5k+PsWvDo2rMpRSU6o7unuTbYp/fOWQor6QvhcN9SpV9XCR51iCjnX/u5lOqH bOmI+a/TxM5/aiLjHBQFZqCV5QooBEPJLRpMCf2XdHi+CjOY27YeJZLQje8VR0BCu4+T Aj7g==
X-Gm-Message-State: ALoCoQkTu2GCFDB4CnKyUP8VwXVOirwnY9P3++m+QpP7/Gh/ltnVS54BDYQAB44wjaXPZOkn6viE
X-Received: by 10.180.108.103 with SMTP id hj7mr3013049wib.11.1440494055081; Tue, 25 Aug 2015 02:14:15 -0700 (PDT)
Received: from ?IPv6:2001:660:330f:a4:5dc6:371c:a6f1:e37b? ([2001:660:330f:a4:5dc6:371c:a6f1:e37b]) by smtp.gmail.com with ESMTPSA id r19sm1642617wib.7.2015.08.25.02.14.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Aug 2015 02:14:13 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9B1B4424-19E9-4445-B855-2283088F8D62"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <0BD14407-A35D-451D-B166-0D5CD36619D5@gmail.com>
Date: Tue, 25 Aug 2015 11:14:53 +0200
Message-Id: <79C91048-2FD5-4DE7-9FBD-381E8489C9AF@gigix.net>
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>
To: farinacci@gmail.com
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/UeC0UKTbiDrsyAdYu5Lqn6u2hxk>
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 09:14:18 -0000

Dino,

what you write make sense, but let me invite the WG to discuss more on the first _IF_ of your logic: “if NVO3 …".

As I pointed out in another mail, we need more discussion on what we are going to support.

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

L.

> On 16 Aug 2015, at 00:03, farinacci@gmail.com wrote:
> 
> The logic follows like this:
> 
> If NVo3 is a requirement for the recharter, then L2 overlay support is required. If L2 overlay support is required, then you must stretch subnets. If you stretch subnets, broadcast frame support is required. If broadcast frame support is needed, then multicast support on the overlay is needed. 
> 
> And if L2 overlays are going to be supported in cloud environments, homenet, or in containers, then NAT-traversal support is required. 
> 
> Dino
> 
> On Aug 14, 2015, at 9:18 AM, Damien Saucez <damien.saucez@gmail.com <mailto:damien.saucez@gmail.com>> wrote:
> 
>> Hello,
>> 
>> I understand that multicast and nat traversal are potentially required in all use cases, but the "must support" sounds extreme to me. Are they hypothetical requirements or real demand from the market targeted by LISP, new version ?
>> 
>> Damien Saucez 
>> 
>> On 12 Aug 2015, at 19:44, Stig Venaas <stig@venaas.com <mailto:stig@venaas.com>> wrote:
>> 
>>> 
>>> On Aug 12, 2015 10:22 AM, "Dino Farinacci" <farinacci@gmail.com <mailto:farinacci@gmail.com>> wrote:
>>> >
>>> > Yes, where but multicast sources as well as multicast receivers are moving. There are severl military applications for this use-case.
>>> 
>>> Agree
>>> 
>>> Stig
>>> 
>>> >
>>> > Dino
>>> >
>>> > > On Aug 12, 2015, at 10:20 AM, Stig Venaas <stig@venaas.com <mailto:stig@venaas.com>> wrote:
>>> > >
>>> > > I agree we need to consider multicast. There are people that want to do multicast over LISP. Some are already doing it. This also includes mobility.
>>> > >
>>> > > Stig
>>> >
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org <mailto:lisp@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/lisp <https://www.ietf.org/mailman/listinfo/lisp>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email