IETF Logo Mail Archive

Re: [lisp] LISP SDN

Sharon <sbarkai@gmail.com> Wed, 19 February 2014 06:42 UTC

Return-Path: <sbarkai@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 8DA661A0550 for <lisp@ietfa.amsl.com>; Tue, 18 Feb 2014 22:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 hnldCYYPLCT3 for <lisp@ietfa.amsl.com>; Tue, 18 Feb 2014 22:42:20 -0800 (PST)
Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 143AE1A033F for <lisp@ietf.org>; Tue, 18 Feb 2014 22:42:19 -0800 (PST)
Received: by mail-yh0-f54.google.com with SMTP id z6so16783670yhz.27 for <lisp@ietf.org>; Tue, 18 Feb 2014 22:42:16 -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=8Qhl5/yk9wlbnpSmfVj+3ni3GqPYbxSLvITlHP0ruJI=; b=QRHerd5Wtnyk8OA+/TU3XrqgMDcgkosTLEXtivUXrVe/hcNcW0OXlf+acMbBvaTjuD ZOvy7fKOV0OCurvv8vUAigXXRg62tCSFKtZFQmaqThrTC4A7c8k5Cl6oQgF6b9UgMdkc pvVLkHeW4aaI9stYWIclXdt93265xipAvv0p4Aied1zeVu5kf5DsO+LsQrkUncGnAzUU lTtZzxwON672KBMz++MpMJVEH0N/ji+zZmLUy718wZFEtAyemh9Ff2yb2u3p+ZHHrr1J ABlHz5yeNcTwGA6mpKuclfKKxjYf22jb6pCgyxXCOlrKJEQpmRTTE0XrIoo49SUNB4+a QR3w==
X-Received: by 10.236.123.193 with SMTP id v41mr30140748yhh.68.1392792136680; Tue, 18 Feb 2014 22:42:16 -0800 (PST)
Received: from [192.168.1.102] (108-214-96-27.lightspeed.sntcca.sbcglobal.net. [108.214.96.27]) by mx.google.com with ESMTPSA id c23sm43276660yhk.23.2014.02.18.22.42.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 22:42:16 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Sharon <sbarkai@gmail.com>
X-Mailer: iPhone Mail (11B554a)
In-Reply-To: <5AE8BFEE-F910-4BE5-BA68-71577B323CD6@gmail.com>
Date: Tue, 18 Feb 2014 22:42:12 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E2ADF1A-A0FC-4C82-97F9-C42E15C844C6@gmail.com>
References: <CA+YHcKF5aUK-ADsxaE7W1T9DmkON51LogDdDXVEWTq1jF5tDDA@mail.gmail.com> <530244E4.4060906@joelhalpern.com> <E7F7C080-38DF-4AF7-B0AD-CB0F95D74BBD@cisco.com> <CA+YHcKFpmKd07Y_TdPSVgovdbc6c8vx+H=SR=0mu_b87JZPeyQ@mail.gmail.com> <33991468-3841-42FA-BF1B-BE9DD6E98188@cisco.com> <5AE8BFEE-F910-4BE5-BA68-71577B323CD6@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/FZiRqvP5U7cyre_SOXhKz6A5qb0
Cc: "lisp@ietf.org" <lisp@ietf.org>
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: Wed, 19 Feb 2014 06:42:22 -0000

LISP Pattern Matching Hashing Caching :)

--szb

> On Feb 18, 2014, at 8:02 AM, Dino Farinacci <farinacci@gmail.com> wrote:
> 

> I was thinking a draft title that incorporates "flow" would probably be suitable, since you're extending LISP to deal with L4 flows. I was almost going to suggest lisp-flowmapping, or "flow mapping extension for LISP", or something like that.. But I don't know enough about the other projects you are involved in to know whether a title like the above sufficiently and/or correctly differentiates this draft from the other ones, if that's required.

How a title that indicate "LISP with a Granular Map-Cache". Because even not going too granular this draft could also include (S-prefix, G-prefix) entries. Which are not flows but source/destination pairs in prefix form.

Dino

_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email