IETF Logo Mail Archive

[lisp] LISP Overlay Model

Luigi Iannone <ggx@gigix.net> Sun, 09 August 2015 22:05 UTC

Return-Path: <ggx@gigix.net>
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 87DE01A8745 for <lisp@ietfa.amsl.com>; Sun, 9 Aug 2015 15:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 jM90XLGyD-wR for <lisp@ietfa.amsl.com>; Sun, 9 Aug 2015 15:05:33 -0700 (PDT)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B1471A870C for <lisp@ietf.org>; Sun, 9 Aug 2015 15:05:33 -0700 (PDT)
Received: by wicja10 with SMTP id ja10so2150569wic.1 for <lisp@ietf.org>; Sun, 09 Aug 2015 15:05:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version; bh=y35v8IIy3haObQSyLR9B8MmJmUWQ55XY8uldZO2/z7o=; b=XguBtPMNhbZrTUhWQqONXc5NcHZ4tbkoWibiTy8ZT8id2kkb13psOpfURUqWvjWiMX CnEw+dCtCoET7rlXBWxKyY4pTffqlt2HzFMp8udfyyQg8V6oZtfM+9D3GY2VN5gZoeMK oLDHN5tZyNYar1ZquPbFhtdtKv7vqr512xEPtXV4lBnrs4s3y6MoQ7/2sn5I9LeafF+m FQ+d9AgCDLEXI8Yx0LLnblBU/u4bulJSW065MYOckxjMBhaFFmiP7ZSr4LXJ7dDw4icN D049EM6Sl473NvkIXie+TN/RzJWewBtjg1cdP8km9ypci5GqbFl2z4tPb7iKN3MpHJHV YTSQ==
X-Gm-Message-State: ALoCoQkDsS/zYFXUYT7bae7JoXvzd241kM0RKC+7OD4cegc4jT1QSp56hKtJobfaqgiT4K+P1yJ1
X-Received: by 10.194.109.36 with SMTP id hp4mr40594345wjb.4.1439157931807; Sun, 09 Aug 2015 15:05:31 -0700 (PDT)
Received: from [172.20.10.3] ([37.162.14.138]) by smtp.gmail.com with ESMTPSA id e8sm6855230wiz.0.2015.08.09.15.05.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Aug 2015 15:05:31 -0700 (PDT)
From: Luigi Iannone <ggx@gigix.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Aug 2015 00:05:29 +0200
Message-Id: <89CA974F-ADB1-444E-BF65-7C2B8C572AA6@gigix.net>
To: LISP mailing list list <lisp@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/xmAl6BuXGx2-G1q4WjXm-omXwK4>
Cc: Joel Halpern Direct <jmh.direct@joelhalpern.com>, Damien Saucez <damien.saucez@inria.fr>
Subject: [lisp] LISP Overlay Model
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 09 Aug 2015 22:05:34 -0000

Hi,

LISP provides a rather complete and powerful control-plane, where 
by means of LCAF, possibly any existing namespace can be mapped 
on each other.
However, the data-plane is not as flexible. The current specifications
allow only IPv4 over IPv6 and vice versa.

In order to create what Sharon Barakai defined “map assisted overlays”
more work is needed.

In this context the WG should also decide whether just an extended/enhanced
data-plane is sufficient/needed. Or should the scope be slightly larger and 
allow as well to support multiple headers type?
Such header are not necessarily defined by the LISP WG 
(e.g.  VXLAN-GPE, GENEVE, GUE, etc.)

Would the WG be interested in working in extending the LISP overlay model
in order to provide data-plane support for what the control plane already allows?
And what should be the scope?

Joel & Luigi

v2.23.0 | Report a Bug | By Email