Re: [nvo3] LISP control plane input into gap analysis draft
Dino Farinacci <farinacci@gmail.com> Mon, 04 November 2013 22:00 UTC
Return-Path: <farinacci@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82FE811E815E for <nvo3@ietfa.amsl.com>; Mon, 4 Nov 2013 14:00:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xgGY-ZFANxV5 for <nvo3@ietfa.amsl.com>; Mon, 4 Nov 2013 14:00:53 -0800 (PST)
Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com [IPv6:2a00:1450:4008:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF5221E805D for <nvo3@ietf.org>; Mon, 4 Nov 2013 14:00:50 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id mx11so613571bkb.31 for <nvo3@ietf.org>; Mon, 04 Nov 2013 14:00:50 -0800 (PST)
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=U8eri5ZHNbVHL/eEuXlfBBYpkkqqr7qdQpO36G5+a5o=; b=zoqe0p2nQwGJAQiDAag0RASWV6XczCexdtDPlyW66pQFpcgbPTG3aMTqzhN1b+SNzw 7JQ0roVLsoUZt/FlkTCBMiseA2sLnQXSgSlCrHaFpocFL6CzruBYioEJh0tioIEGFR+q V/IJuueZ8mtazgeHD4GkgOwh9DLwkmaxDGhVI8GCV3aT3nqvTfG+DdwHmKVEEOnDIAPJ mcIM3H4BtY8XJjbtOkAZ5r7iZjYL4eOxYSMH7teWRLUszINY2m519phxiRUlbP3g/7Y4 Li5OHAj19RkW/KOkAzG4gVVyV3n+NF6dDyX9nPrcNHqQpGzPvWbfoJuDp1/i2qqhL3LY OE3Q==
X-Received: by 10.204.111.200 with SMTP id t8mr15308bkp.43.1383602450041; Mon, 04 Nov 2013 14:00:50 -0800 (PST)
Received: from wireless-v6.meeting.ietf.org ([2001:67c:370:160:752f:ae87:d00f:58fb]) by mx.google.com with ESMTPSA id a4sm16878850bko.11.2013.11.04.14.00.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Nov 2013 14:00:49 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D452EA758@dfweml509-mbx.china.huawei.com>
Date: Mon, 04 Nov 2013 14:00:45 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE890F7E-FE5A-4ABA-864D-D180060E64D3@gmail.com>
References: <CE9DC147.26AC7%yhertogh@cisco.com> <C53D6243-6F77-431A-8A85-A6B7E87E9C03@gmail.com> <2691CE0099834E4A9C5044EEC662BB9D452EA758@dfweml509-mbx.china.huawei.com>
To: Lucy Yong <lucy.yong@huawei.com>
X-Mailer: Apple Mail (2.1816)
Cc: Damien Saucez <damien.saucez@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-nvo3-gap-analysis@tools.ietf.org" <draft-ietf-nvo3-gap-analysis@tools.ietf.org>, "Yves Hertoghs (yhertogh)" <yhertogh@cisco.com>
Subject: Re: [nvo3] LISP control plane input into gap analysis draft
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2013 22:00:53 -0000
> Could someone explain to me how to use LISP solution to provide route path control? For example, in a VN, ingress NVE MUST forward the packets to another NVE at which a tenant system runs firewall software. The second NVE then forwards to the packets to the third NVE where an attached TS has the address that matches the destination address in the inner address on the packets. > > Lucy LISP has a decapsaltor/encasulator component called an RTR. An RTR can give you suboptimal paths by choice if you want to route around failures, congestion points, or use policy paths. You can find details in http://datatracker.ietf.org/doc/draft-farinacci-lisp-te. But yes, you can have an RTR co-located with a firewall, laod-balancer, and NAT type middle devices. Dino
- [nvo3] LISP control plane input into gap analysis… Yves Hertoghs (yhertogh)
- Re: [nvo3] LISP control plane input into gap anal… Damien Saucez
- Re: [nvo3] LISP control plane input into gap anal… Lucy yong
- Re: [nvo3] LISP control plane input into gap anal… Dino Farinacci
- Re: [nvo3] LISP control plane input into gap anal… Dino Farinacci
- [nvo3] LISP and Service chaining [ was Re: LISP c… Yves Hertoghs (yhertogh)
- Re: [nvo3] LISP control plane input into gap anal… Sharon
- [nvo3] Open Daylight Summit CFP Thomas Nadeau