[Isis-wg] Split area may interrupt services) draft-chen-isis-ttz-02

Huaimo Chen <huaimo.chen@huawei.com> Wed, 29 April 2015 21:24 UTC

Return-Path: <huaimo.chen@huawei.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id B25791A079D for <isis-wg@ietfa.amsl.com>; Wed, 29 Apr 2015 14:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id TxI2_iZZZjQT for <isis-wg@ietfa.amsl.com>; Wed, 29 Apr 2015 14:24:04 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E64AB1A0068 for <isis-wg@ietf.org>; Wed, 29 Apr 2015 14:24:03 -0700 (PDT)
Received: from (EHLO lhreml404-hub.china.huawei.com) ([]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRZ13249; Wed, 29 Apr 2015 21:24:02 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com ( by lhreml404-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Wed, 29 Apr 2015 22:24:01 +0100
Received: from SJCEML701-CHM.china.huawei.com ([]) by SJCEML702-CHM.china.huawei.com ([]) with mapi id 14.03.0158.001; Wed, 29 Apr 2015 14:23:56 -0700
From: Huaimo Chen <huaimo.chen@huawei.com>
To: "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Split area may interrupt services) draft-chen-isis-ttz-02
Thread-Index: AQHQgsLM8Xr4xTQ9J0qrNLYGHpYDNA==
Date: Wed, 29 Apr 2015 21:23:56 +0000
Message-ID: <5316A0AB3C851246A7CA5758973207D44E381E94@SJCEML701-CHM.china.huawei.com>
References: <E3164327BB56B14B9162ABA2F0078A5B20DB89EB@SJEXCHMB06.corp.ad.broadcom.com>
In-Reply-To: <E3164327BB56B14B9162ABA2F0078A5B20DB89EB@SJEXCHMB06.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_5316A0AB3C851246A7CA5758973207D44E381E94SJCEML701CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/UmmRRSxSy8JTrfXnDfDDamxTFTM>
Subject: [Isis-wg] Split area may interrupt services) draft-chen-isis-ttz-02
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Apr 2015 21:24:06 -0000

Hi Everyone,

Some service interruptions may occur while splitting a network running ISIS into more areas.

   During IETF 92 in Dallas, someone said that this issue could be resolved in some ways in ISIS when I presented ISIS TTZ (draft-chen-isis-ttz-02) which solves this issue. But this seems not always true. That is that "there may be service interruptions while splitting the network into more ISIS areas."

    In ISIS, when splitting a part of level 2 network area into a new level 1 area, the routing in the new area will be changed. A change for a route to a destination will cause service interruptions if there are services going through that route. Before splitting, every router in the level 2 network area has the same topology and uses this topology to compute the route (shortest path) to a destination. After splitting, every router in the new area (except for the edge routers) does not have the original level 2 network topology, it just uses the topology of its level 1 area to compute a shortest path to each of the edge routers of the area and selects an edge router that is closest to it. For every destination outside of the area, it just uses the path (or next hop) to that edge router.  For a destination, if this path (or next hop) is different from the original one, then there is a route change.

Best Regards,