IETF Logo Mail Archive

Re: [lisp] LISP Use Cases

Sharon Barkai <Sharon@Contextream.com> Mon, 17 August 2015 12:47 UTC

Return-Path: <Sharon@Contextream.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 9DAD21B2D54 for <lisp@ietfa.amsl.com>; Mon, 17 Aug 2015 05:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level:
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_91=0.6, SPF_HELO_PASS=-0.001, 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 hVNPQRsGRkLY for <lisp@ietfa.amsl.com>; Mon, 17 Aug 2015 05:47:09 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0601.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::601]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 747EA1B2D52 for <lisp@ietf.org>; Mon, 17 Aug 2015 05:47:08 -0700 (PDT)
Received: from DB4PR06MB0912.eurprd06.prod.outlook.com (10.161.250.144) by DB4PR06MB189.eurprd06.prod.outlook.com (10.242.155.140) with Microsoft SMTP Server (TLS) id 15.1.231.21; Mon, 17 Aug 2015 12:46:48 +0000
Received: from DB4PR06MB0909.eurprd06.prod.outlook.com (10.161.250.141) by DB4PR06MB0912.eurprd06.prod.outlook.com (10.161.250.144) with Microsoft SMTP Server (TLS) id 15.1.231.21; Mon, 17 Aug 2015 12:46:47 +0000
Received: from DB4PR06MB0909.eurprd06.prod.outlook.com ([10.161.250.141]) by DB4PR06MB0909.eurprd06.prod.outlook.com ([10.161.250.141]) with mapi id 15.01.0231.024; Mon, 17 Aug 2015 12:46:47 +0000
From: Sharon Barkai <Sharon@Contextream.com>
To: "farinacci@gmail.com" <farinacci@gmail.com>
Thread-Topic: [lisp] LISP Use Cases
Thread-Index: AQHQ0u/B0PocOJ4G70qe3fIPBIUe2p4F1cGAgAAB/wCAAAYlAIACwo6AgAAAtYCAAAX1AIADDKwAgAHyuwCAAokqeA==
Date: Mon, 17 Aug 2015 12:46:47 +0000
Message-ID: <A4711991-B4F2-4005-9A4D-7E42A6988B0E@Contextream.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>
In-Reply-To: <0BD14407-A35D-451D-B166-0D5CD36619D5@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Sharon@Contextream.com;
x-originating-ip: [98.248.50.149]
x-microsoft-exchange-diagnostics: 1; DB4PR06MB0912; 5:Xb+h2laXKUzBD6ibXYp1VUlIUnyAJ0X6fQ034DBLulr1dNruOKffYoXg5QOrtsoi6th5Rs0PunkXU+hcqQqWa9AOulkURXs6gn0Tf1Ddx6NyMjT1VvNGDL7jvqKP2cTTqj8djsQnWen9rbhPzz6Seg==; 24:emx9ejF5gfmCTsvedm+jMLZPvuvRCMhEuEYsVRpovamW8T82dc0x55ZnRKfmQ0Cvt1mAsEbcE+KAXW+GCbOrEoC6hKgdHbMDbYs+sg6+M2o=; 20:ktB2WxJEXZ2MWnh7xQGYm27K4h/DCeNTV4351/1UGPb4eE54f6/ygkcvFa6NT4uV7sSznvNE/ConKn7bN/8ArQ==
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(42139001); SRVR:DB4PR06MB0912; UriScan:; BCL:0; PCL:0; RULEID:(42139001); SRVR:DB4PR06MB189;
x-microsoft-antispam-prvs: <DB4PR06MB0912D57145DF02E9580D7E07D8790@DB4PR06MB0912.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(8121501046)(3002001); SRVR:DB4PR06MB0912; BCL:0; PCL:0; RULEID:; SRVR:DB4PR06MB0912;
x-forefront-prvs: 0671F32598
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(24454002)(189002)(199003)(377454003)(68736005)(106356001)(2351001)(1411001)(16236675004)(80792005)(105586002)(5002640100001)(64706001)(2501003)(36756003)(46102003)(33656002)(2950100001)(15975445007)(40100003)(102836002)(2900100001)(19580405001)(77156002)(10400500002)(106116001)(19617315012)(62966003)(122556002)(77096005)(97736004)(5001830100001)(4001540100001)(110136002)(5001860100001)(5001960100002)(81156007)(66066001)(82746002)(50986999)(76176999)(2656002)(83716003)(101416001)(54356999)(189998001)(86362001)(87936001)(92566002)(19580395003)(93886004)(5001920100001)(7059030)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR06MB0912; H:DB4PR06MB0909.eurprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: Contextream.com does not designate permitted sender hosts)
Content-Type: multipart/alternative; boundary="_000_A4711991B4F240059A4D7E42A6988B0EContextreamcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Aug 2015 12:46:47.0078 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 31ea6a41-1b19-4e44-95ed-6c61c89a1582
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB0912
X-Microsoft-Exchange-Diagnostics: 1; DB4PR06MB189; 2:jzfGIYheGXpusoq9lkrXFzLQeEzMzWhABvoK5xHrC2gfaksGdDneJfCgPU9LfsBFTcoB7LlEcZ6qGIVTuzZ3OFKoJRhzdoTczgD9hxLgo73MbMnEIvg94+E0Wacp2Q5FDykrrIjyEkij6LiP8dvR98zHyXjsY7RHU+GuI+A6Vcg=; 3:SZYRc60wdE4JPSX6+2iuYV28OAdulhXxcOAwx9Piza3KbisLWbV3Hcoj6GZAYQogXD1MT2SBoEVEHJLRouuebFw+Pxgq0pgPiNlZL7Qyz5wny8Sgsm2UADWmLdylQNRLKfmF9s4NDBEWvf7wlu9n1/2wUGvhwYXraGEuj/AIL7I=; 25:Gn2mguzsSO/uBJP9w6oV1kJcDbdeXFLYv/+ZWUmIpJxU0xpL/JEn4iMe9mUstoydmhDYZGQ0UGnhM0bpkK2fDdzu1lAABRtaZUqgZIPe9bo67VaCM3YOqHkZXvwuhXbPI1zPcaD8rw4gAOWXY8Tu6K76cGdl4cKeRiipSxNNK6UYwUquDxpTl7+VfHgMavOzxdxuWqiI2n5C7aFLvjGc0HT5rD92m9HCoUK7/8PxHLHKzVyOSPg4fPi9mazLrHlIW48gtqtnwqmDDXBH4P54/w==; 23:kv9r5nrgy0qC0O8UKz4+jVtNq5hAire7fyFha6qToWOH/po8bKkuxl0DGDY//Nst4xzGzuVH4+6rz4+EUugCAQYBH1JWkt9cz85VWQXWglDH54meRQXySgGvSmspTp0XJH3lr5blvDPdLOqBD4kYjjDStLZiuOW2NmkYdUsjq9XclWjSZjSq/wTc0u3GQKI2
X-OriginatorOrg: Contextream.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/NxwvbXOxjcYZmtbTijFO-puqXdU>
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 12:47:11 -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

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.

--szb

On Aug 15, 2015, at 3:03 PM, "farinacci@gmail.com<mailto:farinacci@gmail.com>" <farinacci@gmail.com<mailto: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
_______________________________________________
lisp mailing list
lisp@ietf.org<mailto:lisp@ietf.org>
https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email