IETF Logo Mail Archive

Re: [lisp] Way forward on 6830bis

Dino Farinacci <farinacci@gmail.com> Thu, 05 November 2015 02:43 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 2E86F1A1A7C for <lisp@ietfa.amsl.com>; Wed, 4 Nov 2015 18:43:56 -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 JlrtMTryurxc for <lisp@ietfa.amsl.com>; Wed, 4 Nov 2015 18:43:54 -0800 (PST)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (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 C2E051A1A5B for <lisp@ietf.org>; Wed, 4 Nov 2015 18:43:54 -0800 (PST)
Received: by pacdm15 with SMTP id dm15so47490241pac.3 for <lisp@ietf.org>; Wed, 04 Nov 2015 18:43:54 -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=ID94cPsOeIFOM85S7iWUY1iNiR8ijtWf0QUK7gaY5V8=; b=sSg7FI4WSXPJnm6MBWNUlDo+9D+sGBQFN8IcfSCYDx1VWKTX/734Hyp5Nl64gZC5zl lQFuAneA3wesGHpBQUvwySGS6S8BDx1VIvSv3c4lsPawnxTcXJk9il+p/OI9X0JBD6/R /xZJXQrvhhwC1XPhoZelylncsDwzt0EobaAz2p3DPqfO3zJYcVeKbnu0bW3t6EFtPnOW BLPeHSLVfQGdrhMcMLzCQrW1YXRRPInuG7ahl7Ob7BNqzjNlsas9dH/PF/wya4/rrZcF 34W6Stctr8mJ+9BRKVGgj83fxwTiBVFjbbzcFJgyTYEErRrj6rXHOfs5Q+jkBHylWXes acYg==
X-Received: by 10.66.62.225 with SMTP id b1mr921956pas.66.1446691434405; Wed, 04 Nov 2015 18:43:54 -0800 (PST)
Received: from t20010c4000003080eca5c6c4a913ab7d.v6.meeting.ietf94.jp (t20010c4000003080eca5c6c4a913ab7d.v6.meeting.ietf94.jp. [2001:c40:0:3080:eca5:c6c4:a913:ab7d]) by smtp.gmail.com with ESMTPSA id ku1sm4574153pbc.47.2015.11.04.18.43.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Nov 2015 18:43:53 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CA+YHcKFb_Axu2m4LS_cLGRsPS1h=fGUaXOmzkMZPzSKX+p-Cfg@mail.gmail.com>
Date: Wed, 04 Nov 2015 18:43:51 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <37B7213D-0640-460F-8583-0A4F413283D4@gmail.com>
References: <562E53EF.9070707@joelhalpern.com> <9181AA70-7967-4625-8F2A-981ED8C04724@gmail.com> <EE7AECD8-3EDB-407D-BACB-27EBDE8C88D3@gmail.com> <AC20FC57-849D-46D5-BB5D-69CE081016CB@gmail.com> <7F7F2396-CF00-4362-AA7A-A410B395C20A@gmail.com> <049DD8C5-0356-434A-A32C-EE8C4DF270FE@gmail.com> <CA+YHcKFb_Axu2m4LS_cLGRsPS1h=fGUaXOmzkMZPzSKX+p-Cfg@mail.gmail.com>
To: Alberto Rodriguez-Natal <arnatal@ac.upc.edu>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/5UaBtYRxfRiwOMJnEPXsWVdDnHo>
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] Way forward on 6830bis
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: Thu, 05 Nov 2015 02:43:56 -0000

> In that sense I think that we should ask ourselves the question, if I'm willing to use (for instance) VXLAN-GPE for encapsulation and LISP for the control-plane, which pieces of what is currently covered in RFC6830, RFC6833, etc, do I need to use? That is what for me should go into the "control-plane" document. The rest of the pieces of the LISP protocol that I didn't use since I had VXLAN-GPE, would be the "data-plane”.

Agree as well.

Dino

v2.23.0 | Report a Bug | By Email