Re: [lisp] LISP SDN
"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 17 February 2014 17:20 UTC
Return-Path: <jmh@joelhalpern.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 B2A691A03F6 for <lisp@ietfa.amsl.com>; Mon, 17 Feb 2014 09:20:44 -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=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 utkbWfCVc7DW for <lisp@ietfa.amsl.com>; Mon, 17 Feb 2014 09:20:40 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7A01A024B for <lisp@ietf.org>; Mon, 17 Feb 2014 09:20:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 62911240757; Mon, 17 Feb 2014 09:20:38 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-64.clppva.east.verizon.net [70.106.135.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id CA9CB240764; Mon, 17 Feb 2014 09:20:37 -0800 (PST)
Message-ID: <530244E4.4060906@joelhalpern.com>
Date: Mon, 17 Feb 2014 12:20:36 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Alberto Rodriguez-Natal <arnatal@ac.upc.edu>, "lisp@ietf.org list" <lisp@ietf.org>
References: <CA+YHcKF5aUK-ADsxaE7W1T9DmkON51LogDdDXVEWTq1jF5tDDA@mail.gmail.com>
In-Reply-To: <CA+YHcKF5aUK-ADsxaE7W1T9DmkON51LogDdDXVEWTq1jF5tDDA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/coi11WjCf47iPC4wcnyAMNBsntE
Subject: Re: [lisp] LISP SDN
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: <http://www.ietf.org/mail-archive/web/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 Feb 2014 17:20:45 -0000
I would really like to see an answer to how these n-tuple matches are supposed to work with prefix matches on various fields. What is the match algorithm? What assumptions are placed on the mapping system to support these tuples? How will the ETR know that the mapping system it is talking to supports this capability? In particular, what if the same device is serving as an ETR for conventional operations and for these enhanced operations. Does it need to be configured to know which map server handles which mode? Does it guess? Is the same map server required to handle both? Yours, Joel On 2/17/14, 11:45 AM, Alberto Rodriguez-Natal wrote: > Dear all, > > We have submitted a new draft, "SDN extensions for LISP", that you can > find here: > > http://tools.ietf.org/html/draft-rodrigueznatal-lisp-sdn-00 > > We believe that LISP can serve as a southbound protocol for SDN. With > this draft we aim to improve vanilla LISP with some extensions to make > it even more suitable for SDN scenarios. > > This draft also complements and provides the foundations for the current > LISP NFV draft. > > http://tools.ietf.org/html/draft-barkai-lisp-nfv-04 > > Your thoughts and feedback on both drafts are more than welcome. > > Best, > Alberto > > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp >
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Joel M. Halpern
- Re: [lisp] LISP SDN Michiel Blokzijl (mblokzij)
- Re: [lisp] LISP SDN Dino Farinacci
- Re: [lisp] LISP SDN Robert Raszuk
- Re: [lisp] LISP SDN Sharon Barkai
- Re: [lisp] LISP SDN Dino Farinacci
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Lori Jakab
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Michiel Blokzijl (mblokzij)
- Re: [lisp] LISP SDN Lori Jakab
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Dino Farinacci
- Re: [lisp] LISP SDN Dino Farinacci
- Re: [lisp] LISP SDN Sharon Barkai
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Sharon
- Re: [lisp] LISP SDN Alberto Rodriguez-Natal
- Re: [lisp] LISP SDN Dino Farinacci
- Re: [lisp] LISP SDN Dino Farinacci