Re: [lisp] WG Charter

Dino Farinacci <> Mon, 06 July 2015 22:15 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 025D41A7017 for <>; Mon, 6 Jul 2015 15:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9AVpjfGwZwTl for <>; Mon, 6 Jul 2015 15:15:49 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 63CE71A1B4C for <>; Mon, 6 Jul 2015 15:15:44 -0700 (PDT)
Received: by pdbdz6 with SMTP id dz6so17856706pdb.0 for <>; Mon, 06 Jul 2015 15:15:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DhvRbbdTmikp6pIBscR8XbdLEPn8e1DlMvAnshnyyqg=; b=mOaq9d9+wR3gWPOS2Bw03f0+cD0Ljd/F4Z2+8G+jeA5L0oXwd+oC3YzfJpVrBJUzdg JAx09bpPK2x2TRCZIywtq2kh42/5Av7q8EeXlBgcgyqIl65vIUEY5RGjxqEDlBkVkFon 4r7fWxIdGL/eQZ0Ki9XsN/rkT+VFX08yOmFINPphcF8b3Mj9Gw0sBP5aANW/JTUE3tWu vSxELJevT0zXixF0HGQFS5ct/vcVjRm2GiHYeclr8UCE+FFuYwqBlJHyKD8zhW9Z2Ih9 IvOPhpj3IAZuVUVZ4HEjwXDmhP8lgvHvkZK/BXn72rc8cy5m9p5IoWDKyzXY95M9xqKN Hs9w==
X-Received: by with SMTP id vt4mr2086945pab.32.1436220944048; Mon, 06 Jul 2015 15:15:44 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id yp5sm19388452pbb.22.2015. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Jul 2015 15:15:43 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Dino Farinacci <>
In-Reply-To: <>
Date: Mon, 6 Jul 2015 15:15:45 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <>
To: Xuxiaohu <>
X-Mailer: Apple Mail (2.2102)
Archived-At: <>
Cc: LISP mailing list list <>
Subject: Re: [lisp] WG Charter
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 06 Jul 2015 22:15:51 -0000

> If IP-based tunnels (e.g., MPLS-in-GRE or MPLS-in-UDP) are used between PE routers, is there still any difference on applicability between these two VPN technologies?

The mechanism and location of tunneling is not important. It is the type of service the solution can offer and what was intended in its initial design.

There is a lot of difference when you look at the type of services ISP based VPNs offer and what LISP VPNs offer with all the other solutions LISP can offer along with VPNs.

>>> From the data plane perspective, given the fact that there is unprecedented
>> enthusiasm for defining various data plane encapsulations (e.g., VXLAN, NVGRE,
>> VXLAN-GPE, GUE-NVO, GENEVE...) , it seems no surprise to add two more (e.g.,
>> LISP and LISP-GPE). From the control plane perspective, as BGP could be used as
>> a pull-based control plane as well due to its prefix-ORF mechanism, what's the
>> major advantage of LISP over BGP?
>> There have been many pros and cons using BGP as a push control-plane and
>> LISP as a control-plane. At the high-level, I’ll state one difference. The LISP
>> control plane (the mapping database nodes), are in less places in the network
>> than BGP nodes. So that means less coordination and management.
> In the data center network environment, route reflectors could be run over spine nodes or even servers. As such, these route reflectors could be looked as mapping database nodes. Hence, from the coordination and management perspectives, these two approaches seem almost the same, No?

Yes, but the information is pushed. At some point any protocol and architecture can be changed, used, or misused to look like another. But what is important is how it was designed from the beginning.

> Due to the new mobility requirements in 5G architecture (e.g., ultra-low
>> latency), LISP-MN mobility may be a competitive candidate.
>> Why do you say that? Compared to other solutions its better. Or some technical
>> aspect?
> Compared to other HA-based mobile IP solution, I think id/locator split solution looks better in the long run since it has the potential of eliminating the path stretch issue.

Right, agree.


> Best regards,
> Xiaohu