IETF Logo Mail Archive

Re: [lisp] I-D Action: draft-ietf-lisp-introduction-05.txt - Decoupling

Albert Cabellos <albert.cabellos@gmail.com> Mon, 20 October 2014 13:08 UTC

Return-Path: <albert.cabellos@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 3A2CB1A870C for <lisp@ietfa.amsl.com>; Mon, 20 Oct 2014 06:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.899
X-Spam-Level: *
X-Spam-Status: No, score=1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FB_CIALIS_LEO3=3.899, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 eRzgc40vukv1 for <lisp@ietfa.amsl.com>; Mon, 20 Oct 2014 06:08:45 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1A651A8710 for <lisp@ietf.org>; Mon, 20 Oct 2014 06:08:43 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id tp5so4631959ieb.14 for <lisp@ietf.org>; Mon, 20 Oct 2014 06:08:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=qvelcY8vrv/7KZWVFJ28LOPZAMq0T6reJAuCCpPRxtQ=; b=V9gQv7Bp9tgXURFp0JrceTuXRJyaSyNoIHz+YJ2jM1KctTXKRYeGa4PUopj+C+Q3pB RqArzPG65CafcSW48LhwbnbkGk3+eAu8+Vj+E5VWMtY2psM8Rtqer0SEH4W+lKkS9mtJ BknY8YT3Ga7WWxxmgpOitR9lcGYUU2BaYWFR3VW49m8yGU+Ly8mEg5660hYl+DGnAWe/ 5lYsEzpoiBaWUm9E9tw8rkxAbe8OmAcdBdbkTTs8NY3R0mazxkOekd70xHr/Ridhb+Xo 6sfLMascEu1+xPFHeI6Rw7roE4i/iHqOxgSVnLge30Pho9FlnXdUZDeJgXVbatisWCd6 i3xA==
MIME-Version: 1.0
X-Received: by 10.107.30.136 with SMTP id e130mr29003032ioe.9.1413810523127; Mon, 20 Oct 2014 06:08:43 -0700 (PDT)
Received: by 10.107.35.73 with HTTP; Mon, 20 Oct 2014 06:08:43 -0700 (PDT)
In-Reply-To: <66955a49886045589ca568d9166968c9@CO1PR05MB442.namprd05.prod.outlook.com>
References: <da742ef87a964895b755294837b989f4@CO1PR05MB442.namprd05.prod.outlook.com> <5194B6B9-0F51-47EF-AC33-155F47399AA4@gmail.com> <8b220ca159a447a194d19dc536db3f0c@CO1PR05MB442.namprd05.prod.outlook.com> <E321E09E-18AB-4149-A7D8-0AC27366F985@gmail.com> <8A3FAEEC-98D6-4E32-AB12-7B8E3418752C@gigix.net> <CA+YHcKF-f-q8k0=dRNjhVW2oJzJ=rJfdNau8G9KSN=yiNJENQA@mail.gmail.com> <95F2B24F-854A-4A09-8FB1-EF1025DE2A5F@cisco.com> <66955a49886045589ca568d9166968c9@CO1PR05MB442.namprd05.prod.outlook.com>
Date: Mon, 20 Oct 2014 15:08:43 +0200
Message-ID: <CAGE_Qex4MJLP-VeBT5j+CBXjxoC6cKhjb3pGMoxBSbN915ciiQ@mail.gmail.com>
From: Albert Cabellos <albert.cabellos@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/m280noBl20wWZ03BDRaDpQKCFTI
Cc: "lisp@ietf.org" <lisp@ietf.org>, Damien Saucez <damien.saucez@inria.fr>
Subject: Re: [lisp] I-D Action: draft-ietf-lisp-introduction-05.txt - Decoupling
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: acabello@ac.upc.edu
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: Mon, 20 Oct 2014 13:08:46 -0000

Hi Ron,

Clearly isolation must not be undersood in strict terms, otherwise
fully isolating the control from the data-plane results in a useless
architecture. This is also what I understand from your comment.

This means that "isolation" must be understood as a degree, "to which
degree are the control and the data-plane isolated?" As such, a
"degree" is not fundamental to an architecture and -in my view- not a
design principle.

Albert



On Sun, Oct 12, 2014 at 12:54 AM, Ronald Bonica <rbonica@juniper.net> wrote:
> Folks,
>
> Thanks for the good dialog regarding "decoupling" and "isolation". So far, I glean the following from the email thread:
>
> - LISP decouples the forwarding and control plane, so draft-ietf-lisp-introduction is correct
> - LISP does not isolate the control plane from the forwarding plane, so RFC 6830 is also correct
>
> Because both statements are correct and architecturally significant, they *both* should appear in Section 2.1 of draft-ietf-lisp-introduction. Ideally, these two statements should be juxtaposed to one another in order to highlight the difference between "isolation" and "decoupling".
>
> Each statement should include:
>         1)  A title (i.e., Decoupled data and control-plane, Non-isolation between data and control plane)
>         2)  A sentence or two explaining what it means to be decoupled or non-isolated
>         3) A cost/benefit statement
>
>                                                                                       Ron
>
>
>> -----Original Message-----
>> From: lisp [mailto:lisp-bounces@ietf.org] On Behalf Of Darrel Lewis
>> (darlewis)
>> Sent: Wednesday, October 08, 2014 2:07 PM
>> To: Alberto Rodriguez-Natal
>> Cc: Damien Saucez; lisp@ietf.org
>> Subject: Re: [lisp] I-D Action: draft-ietf-lisp-introduction-05.txt - Decoupling
>>
>>
>> On Oct 8, 2014, at 1:34 AM, Alberto Rodriguez-Natal <arnatal@ac.upc.edu>
>> wrote:
>>
>> >
>> >
>> > On Wed, Oct 8, 2014 at 10:28 AM, Luigi Iannone <ggx@gigix.net> wrote:
>> > Hi,
>> >
>> > I think is fair to state in the intro document that data- and control- planes
>> are "decoupled" in LISP because their instantiation may run on different
>> boxes, but they are not "isolated" because LISP data plane can trigger control
>> plane activity.
>> >
>> > I think this is an excellent way to describe it.
>>
>> Agreed.
>>
>> -Darrel
>>
>>
>> >
>> > Alberto
>> >
>> > _______________________________________________
>> > lisp mailing list
>> > lisp@ietf.org
>> > https://www.ietf.org/mailman/listinfo/lisp
>>
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email