[lisp] Standard Track

Luigi Iannone <ggx@gigix.net> Sun, 09 August 2015 22:02 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 BC31E1A6FEE for <lisp@ietfa.amsl.com>; Sun, 9 Aug 2015 15:02:57 -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 ZoUQv3DTtac1 for <lisp@ietfa.amsl.com>; Sun, 9 Aug 2015 15:02:56 -0700 (PDT)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (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 649971A6FEF for <lisp@ietf.org>; Sun, 9 Aug 2015 15:02:56 -0700 (PDT)
Received: by wijp15 with SMTP id p15so114361394wij.0 for <lisp@ietf.org>; Sun, 09 Aug 2015 15:02:55 -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=Ubj4/goZGvxWY8ClH9MRDXGlSBL1S6fkR27R22WWqlE=; b=K/6Z9tx4pLt2TqphbTYWtAuc1wehK0TsFDc0TQ+cBYWDxYDEeutTyBfsCbMPlmtaOe wDcwHHiGzqUaIVMYVncH6Ng+YrlWfOgAZWH7T6XZPxKF/KpEArZTGgoRWitLwyWcXgT3 VjyIGhVmN96fz9B9MKKij+gniCGMZ06tqjebGG3Oizu1ZlSkEq8A4vjGE1bwHLXuWFyV Z8H3HKBPRvWvHLW9TKBSnZHAkLChwrsSn1pjle/27xgM0VhJRnZbQMsXe6OFqmX6ZjsE Ic8G48OEAPbCC/+LQ//51jKX3kBwxcdk8mprT6PS4WyL6etQ2G1nwRbtGkmo+ZS2F+hY KsEw==
X-Gm-Message-State: ALoCoQnrBB/SRstLapoVFqMRvNGX/jvWw8EqJ0sHBo4oBDtou3LU38hMdFtK06FaqbUQ2wdIppT8
X-Received: by 10.180.9.162 with SMTP id a2mr17275014wib.95.1439157775079; Sun, 09 Aug 2015 15:02:55 -0700 (PDT)
Received: from [172.20.10.3] ([37.162.14.138]) by smtp.gmail.com with ESMTPSA id lk16sm10561140wic.6.2015.08.09.15.02.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Aug 2015 15:02:54 -0700 (PDT)
From: Luigi Iannone <ggx@gigix.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Aug 2015 00:02:53 +0200
Message-Id: <F6C97F59-9BC7-4AE0-8ADB-DD1ED37101CA@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/9qeF0CVlHwai9O08KKYlsQvB6oY>
Cc: Joel Halpern Direct <jmh.direct@joelhalpern.com>, Damien Saucez <damien.saucez@inria.fr>
Subject: [lisp] Standard Track
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:02:57 -0000

Hi,

As suggested by Terry Manderson during the last meeting, it is time for the WG 
to think to move away from the Internet Scalability issue and focus on the core
protocol technology. 

LISP has its merits, concerning routing scalability, proved by experimental work 
documented in the various RFC and drafts that the WG has produced so far. 
That work remains untouched. Yet, LISP provides advantages and benefits 
in contexts for which it has not been originally designed.

It would be worth for the WG to consider dropping the scalability aspects,
focus on the overlay technology itself, and possibly move the work
on standard track. 

If the WG decides to go that way, this will give the opportunity to re-work 
the core set of RFCs defining LISP, avoiding any reference to scalability,
and possibly enhancing the documents with the experience gathered so far.

Would be the WG in favour of such direction?

Joel & Luigi