Re: [lisp] draft-farinacci-lisp-crypto-01 - Call for WG Adoption

Dino Farinacci <farinacci@gmail.com> Sat, 06 December 2014 03:06 UTC

Return-Path: <farinacci@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 2A3AE1A8A95 for <lisp@ietfa.amsl.com>; Fri, 5 Dec 2014 19:06:52 -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 XBgGnLQQ_qan for <lisp@ietfa.amsl.com>; Fri, 5 Dec 2014 19:06:50 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BE911A8A94 for <lisp@ietf.org>; Fri, 5 Dec 2014 19:06:50 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id et14so1830254pad.29 for <lisp@ietf.org>; Fri, 05 Dec 2014 19:06:49 -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=VZB0PdzXGlOChLHr6UYA9jvm2RGyD+P6LGaH7Pj7QMQ=; b=Uz+4Mb84PAMM1PIbE8Qf7MiEtcFoeGaLx7h8jueWGDHzkwJRaO9NvV4ZznC0/InBBR OqhqYCYBK+pG/KyIMGuq6DHke3tXEAcX05Hai+gQeOdwpq3Re/FB91TU6hsPr814N1LS iKlxzL1AAtyeCiVGI+wSFa9uanGWbIYCxsonk6b9llaleHDC4ycRg7PBqxQCO/1wqvsD hMrhIBWXzGEEavd4cnH/gY4Teb2JCYxHPLKdR967d2+lOLrVLA/5C81CYmbc+ek0clms tKgJZMWa41RSGFIkOQQbAVpG1D5mXSGBtklE7O1RaViiLoty54JFts2Y9x+2Dx7B0RMU 5+bw==
X-Received: by 10.70.31.97 with SMTP id z1mr937835pdh.115.1417835209610; Fri, 05 Dec 2014 19:06:49 -0800 (PST)
Received: from [10.4.173.178] (mobile-166-171-249-159.mycingular.net. [166.171.249.159]) by mx.google.com with ESMTPSA id ae4sm30472310pad.16.2014.12.05.19.06.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Dec 2014 19:06:48 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (12B436)
In-Reply-To: <54822778.6050505@cisco.com>
Date: Fri, 5 Dec 2014 19:06:47 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFBC926D-FBCF-46DD-81AF-AF936D4B36DE@gmail.com>
References: <D35D7CD0-20E5-4210-8025-7C92441DD339@gigix.net> <5480B13C.4090203@cisco.com> <97DA0D20-84D3-4478-8F90-C033E67172CD@gmail.com> <5481DCB6.6070300@cisco.com> <B8414A88-F630-4FC3-A2FC-05235D78D483@gmail.com> <54822778.6050505@cisco.com>
To: Fabio Maino <fmaino@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/TzQ0ujxwnwb2UqWt3rPRN56WjCY
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] draft-farinacci-lisp-crypto-01 - Call for WG Adoption
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: Sat, 06 Dec 2014 03:06:52 -0000

> extension of the encap (as well as of the control plane, if needed) to address various LISP use cases.

I do like to see a list of requirements that requires changes to LISP encapsulation. 

LISP-GPE adds no new functionality. NSH can be done without packet encapsulation from any overlay protocol. 

> In my experience when customers see the benefit of overlays (LISP in my case) they tend jump on it... but you know this way better than me :-) It's our responsibility as a WG to clear up the confusion about encapsulations.

Well adding new encapsulation to the mix doesn't clear up confusion. It adds to it. 

Dino