Re: [lisp] Questions about draft-saucez-lisp-itr-graceful-03

Damien Saucez <damien.saucez@inria.fr> Wed, 19 February 2014 08:39 UTC

Return-Path: <damien.saucez@inria.fr>
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 685FD1A0450 for <lisp@ietfa.amsl.com>; Wed, 19 Feb 2014 00:39:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548] 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 7xrYLxJmT2gN for <lisp@ietfa.amsl.com>; Wed, 19 Feb 2014 00:38:59 -0800 (PST)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by ietfa.amsl.com (Postfix) with ESMTP id 104241A0389 for <lisp@ietf.org>; Wed, 19 Feb 2014 00:38:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.97,504,1389740400"; d="scan'208";a="49611038"
Received: from faucon.inria.fr ([138.96.201.73]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 19 Feb 2014 09:38:54 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Damien Saucez <damien.saucez@inria.fr>
In-Reply-To: <20140218144825842648.087ffc67@sniff.de>
Date: Wed, 19 Feb 2014 09:38:54 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <7DFCF6EA-9F05-468D-B51F-7AB7DEC149C8@inria.fr>
References: <20140218144825842648.087ffc67@sniff.de>
To: Marc Binderberger <marc@sniff.de>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/t8UzZh0iA0yoUPDnrA8aPORFMn0
Cc: Clarence Filsfils <cf@cisco.com>, Luigi Iannone <luigi.iannone@telecom-paristech.fr>, LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] Questions about draft-saucez-lisp-itr-graceful-03
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: Wed, 19 Feb 2014 08:39:01 -0000

Hello Marc,

On 18 Feb 2014, at 23:48, Marc Binderberger <marc@sniff.de> wrote:

> Hello Damien/Olivier/Luigi/Clarence & LISP experts,
> 
> had a look at draft-saucez-lisp-itr-graceful-03. And wonder if there is 
> more to come?

Thank you for the interest.  We are indeed thinking on ways to extend
the document and provide more details on the ways the solutions could
be implemented.


> Somehow section 4 feels a bit "short".
> 
> What I mean: if you try to solve the problem of the _two_ cache-miss 
> storms - first on the 2nd ITR (ITR2) when your restarting ITR (ITR1) 
> goes down, then on the restarting ITR1 when it picks up traffic again - 
> then section 4 would probably need to talk about a permanent cache 
> synchronization (?). Unless you want to solve a planned restart only. 
> But for a failure of the ITR1 I don't see how the solution you describe 
> would work
> 
>   o  ITR cache synchronization: upon startup, the ITR synchronizes its
>      cache with the other ITRs in its synchronization set.  The ITR is
>      marked as available only after the cache is synchronized.
> 
> as ITR2 would trigger the cache-miss storm for the traffic after ITR1 
> failure.
> 
> Or if you want to solve only the cache-miss storm when ITR1 comes back 
> into the traffic stream then the ITR deflection has the advantage to 
> not require any cache-synchronization protocol, IMHO. The rate of 
> Map-Requests could be throttled to turn the storm into a breeze. The 
> method how to transport traffic to ITR2 could be one of many - a direct 
> LAN, GRE, Lisp.
> 
> 
> So my question in short: are you planning to add some words about a 
> permanent cache synchronization?
> 

For now we don't have acceptable techniques to keep caches
synchronised in a permanent way but I don't think it is a big issue as
the purpose of the document is to deal with planned restart of routers
meaning that we know exactly when the routeur will get down then up
(it is controlled by the operator).

If you have a solution to continuously synchronise ITRs caches, we
would be very happy to look at them and integrate them in the proposed
solution.

Thank you,

Damien Saucez

> 
> Thanks & Regards,
> Marc