I-D Action: draft-saucez-lisp-itr-graceful-01.txt

internet-drafts@ietf.org Wed, 26 December 2012 13:55 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-saucez-lisp-itr-graceful-01.txt
Message-ID: <20121226135531.24862.99414.idtracker@ietfa.amsl.com>
Date: Wed, 26 Dec 2012 05:55:31 -0800
Precedence: list
Reply-To: internet-drafts@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title           : LISP ITR Graceful Restart
	Author(s)       : Damien Saucez
                          Olivier Bonaventure
                          Luigi Iannone
                          Clarence Filsfils
	Filename        : draft-saucez-lisp-itr-graceful-01.txt
	Pages           : 12
	Date            : 2012-12-26

Abstract:
   The Locator/ID Separation Protocol (LISP) is a map-and-encap
   mechanism to enable the communication between hosts identified with
   their Endpoint IDentifier (EID) over the Internet where EIDs are not
   routable.  To do so, packets toward EIDs are encapsulated in packets
   with routing locators (RLOCs) to form dynamic tunnels.  An Ingress
   Tunnel Router (ITR) that encapsulates EID packets determines tunnel
   endpoints via mappings that associate EIDs to RLOCs.  Before
   encapsulating a packet, the ITR queries the mapping system to obtain
   the mapping associated to the EID of the packet it must encapsulate.
   Such mapping is cached by the ITR in its local EID-to-RLOC cache for
   any subsequent encapsulation for the same EID.  LISP is scalable
   because the EID-to-RLOC cache of an ITR, which is initially empty, is
   populated progressively according to the traffic going through the
   ITR.  However, after an ITR is restarted, e.g., for maintenance
   reason, its cache is empty which means that all packets that are re-
   routed to the freshly restarted ITR will cause cache misses and a
   potentially high loss rate.  In this draft, we present mechanisms to
   reduce the negative impact on traffic caused by the restart of an ITR
   in a LISP network.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-saucez-lisp-itr-graceful

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-saucez-lisp-itr-graceful-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-saucez-lisp-itr-graceful-01


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-saucez-lisp-itr-graceful-01.txt internet-drafts