IETF Logo Mail Archive

Re: [lisp] LISP Use Cases

Dino Farinacci <farinacci@gmail.com> Mon, 17 August 2015 16:42 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 B225B1A00BD for <lisp@ietfa.amsl.com>; Mon, 17 Aug 2015 09:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_91=0.6, SPF_PASS=-0.001] autolearn=no
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 eDha1Y6xBbcU for <lisp@ietfa.amsl.com>; Mon, 17 Aug 2015 09:41:55 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (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 BB3F91A00C0 for <lisp@ietf.org>; Mon, 17 Aug 2015 09:41:55 -0700 (PDT)
Received: by pawq9 with SMTP id q9so14330128paw.3 for <lisp@ietf.org>; Mon, 17 Aug 2015 09:41:55 -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=q2egy1yliPhPxuhJjx8Bb7u5ccISfulrC9e3yQ1zyqY=; b=iPaO2dp+xoBQCEkIWzErlYUXGqBM96yYf6LJ1n3JhK+YnbPp5DfEvdOKXa/gPpUrNo bEv9x3tC2uBX+cZTFF9bHz+Y89vGQp8P9t78vlL8V2v24dc6nEGArivAt45ARaP3JPP9 8QJfynJ6mWwz13UnyIplqtXGpwkOfCHktidvodery41XnWShhPOWyqAUhTuSAxjqwzFu tOuxUFsxQ8FsnFsPQb/jhJINBLyWRZqdwwSU9yAcUx6avLZ4VLMvIUb0z+vt0I8jlnHI iweQspajnsb43wWVlf0Yi5+ZefJB4hmdWw9EysRhNRlxWb1/MsMpe67JKED6dH2Gcpvw +DPA==
X-Received: by 10.68.116.109 with SMTP id jv13mr4162377pbb.137.1439829715434; Mon, 17 Aug 2015 09:41:55 -0700 (PDT)
Received: from [172.20.10.2] ([166.170.39.25]) by smtp.gmail.com with ESMTPSA id nj9sm15235068pdb.77.2015.08.17.09.41.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Aug 2015 09:41:54 -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: <A4711991-B4F2-4005-9A4D-7E42A6988B0E@Contextream.com>
Date: Mon, 17 Aug 2015 09:41:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C584B134-B7B3-4C6D-981A-53ACD31C58DA@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> <A4711991-B4F2-4005-9A4D-7E42A6988B0E@Contextream.com>
To: Sharon Barkai <Sharon@Contextream.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/CHGTyxfg46ifRCzpdL5G4VxOV2s>
Cc: Sharon Barkai <sharon.barkai@hp.com>, 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, 17 Aug 2015 16:42:01 -0000

> would also say that if we are to help implement  overlays with the lisp mapping architecture, then we could expect any overlay aggregation node to subscribe to any traffic identifiers/classifiers 
> - unicast, multicast.g, taps, chain.index.. and to the mappings them selves

Yes, definitely agree. And the lisp-subscription ID reflects that.

Note to WG, this draft is about to be published soon.

> Doesn't mean they get it, may be other policies in place, both in the mapping and in the itr, but xtr can subscribe by essence of overlays - logical not topological connectionless traffic forwarding over IP.

Right. 

Dino

> 
> --szb
> 
> On Aug 15, 2015, at 3:03 PM, "farinacci@gmail.com" <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> 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> wrote:
>>> 
>>>> 
>>>> On Aug 12, 2015 10:22 AM, "Dino Farinacci" <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> 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
>>>> 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