IETF Logo Mail Archive

Re: [lisp] [nvo3] New Version Notification for draft-quinn-vxlan-gpe-00.txt

Dino Farinacci <farinacci@gmail.com> Thu, 26 September 2013 18:58 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099D321E80B0; Thu, 26 Sep 2013 11:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 gfGInHjGxqUC; Thu, 26 Sep 2013 11:58:09 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 217AC21E8094; Thu, 26 Sep 2013 11:58:06 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id to1so2028897ieb.9 for <multiple recipients>; Thu, 26 Sep 2013 11:58:05 -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=nkac/6t9kD7tNIY5tKPTv5sLwFu++du45po8yzYbRVY=; b=Yh4diY/U3Js6l3UPKmfTQBYIjH/MQ5KeFvkMt2m9xA4zk2vPQJwasAdoNV64zwXGWa NK6BWXcrV8NkbSS5PNej80n8PJyYB1BbfaZKSUr4sWTT9HpB0gRfczOFOBL/dkUhGXUF 7W0cvUL/bOY6N0U5tjk3Q1AnwDRGLuf+Uq5GbcOGceNbd4AkaO/kxi1/LaAExZEhp1Dm DZ7cl3PeCnmph/eIjFwiC6PyHa8jaV5eWEbZ4xxwY1lrm+8aCYfwJsuIJ78m3LJv2HEL 2YU+Kp4DUAOVCnen7InLwhn4OsX3Zy64RCD7nqBp5UasH/YuM0Fr7GNpQYo/ppOYXXMF pPtQ==
X-Received: by 10.43.129.197 with SMTP id hj5mr2853339icc.84.1380221885615; Thu, 26 Sep 2013 11:58:05 -0700 (PDT)
Received: from [172.19.131.134] ([12.130.123.252]) by mx.google.com with ESMTPSA id m1sm96505igj.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 26 Sep 2013 11:58:05 -0700 (PDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAKFn1SHOCV-V+dodAgLk73CBCzv_vYD2rh_KTZnBJrc5i2EC8A@mail.gmail.com>
Date: Thu, 26 Sep 2013 11:57:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <16DF95BC-8820-4318-899B-DA0AC10BF19E@gmail.com>
References: <20130924150710.B45F118C094@mercury.lcs.mit.edu> <524329EB.7050704@cisco.com> <CF7B7553-BBE5-482C-AB29-D4F3B92680CD@gmail.com> <CAKFn1SHOCV-V+dodAgLk73CBCzv_vYD2rh_KTZnBJrc5i2EC8A@mail.gmail.com>
To: Roger Jørgensen <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] [nvo3] New Version Notification for draft-quinn-vxlan-gpe-00.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 26 Sep 2013 18:58:14 -0000

> On Wed, Sep 25, 2013 at 9:03 PM, Dino Farinacci <farinacci@gmail.com> wrote:
>>> Hi Noel,
>>> there's certainly no intention of keeping this out of the LISP WG, since this is not part of the charter we just thought an individual submission was more appropriate.
>>> 
>>> We just started from the very practical consideration of the proliferation of encapsulations in the data center, and the lack of multiprotocol support in both VXLAN and LISP.
>> 
>> Sorry I have to disagree. The protocols that LISP supports are *IP* protocols and the protocols that VXLAN supports are *the rest* since it is layer-2 solution. So this appears to be just rearranging the deck chairs.
> 
> This trouble me... why do we want to mix LISP and VXLAN? What is the
> gain in it? I only smell complexity. L2 in L3 over L3?

We shouldn't but let the authors reply. If you want to carry more than IP protocols in LISP, then you use the L2 UDP port and carry MAC addresses in LISP. You can carry all of MAC, IPv4, and IPv6 EIDs with one control-plane, the LISP mapping database using LISP-DDT.

> How will a mix of LISP and VXLAN benefit the administrators of
> datacenters, end-users in the end?

The VXLAN authors have to answer that. They came afterwards (by 5 years).

Dino

> 
> 
> 
> -- 
> 
> Roger Jorgensen           | ROJO9-RIPE
> rogerj@gmail.com          | - IPv6 is The Key!
> http://www.jorgensen.no   | roger@jorgensen.no
> 
> (I really start to really dislike gmails new better editor)

v2.23.0 | Report a Bug | By Email