Re: [Pce] Virtual Network Topology (VNT) changes and IP layer routing loops

JP Vasseur <jvasseur@cisco.com> Wed, 07 June 2006 14:33 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnz5x-0000Li-V4 for ccamp-archive@ietf.org; Wed, 07 Jun 2006 10:33:17 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fnz5w-0000BA-Gg for ccamp-archive@ietf.org; Wed, 07 Jun 2006 10:33:17 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1FnytZ-000BaX-Dt for ccamp-data@psg.com; Wed, 07 Jun 2006 14:20:29 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_ABUSE,SPF_PASS autolearn=no version=3.1.1
Received: from [171.68.10.86] (helo=sj-iport-4.cisco.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <jvasseur@cisco.com>) id 1FnytY-000BaK-KZ for ccamp@ops.ietf.org; Wed, 07 Jun 2006 14:20:28 +0000
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-4.cisco.com with ESMTP; 07 Jun 2006 07:20:28 -0700
X-IronPort-AV: i="4.05,217,1146466800"; d="scan'208"; a="1821146865:sNHT37595082"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k57EKRa9021686; Wed, 7 Jun 2006 07:20:28 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k57EKRIs021666; Wed, 7 Jun 2006 10:20:27 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Jun 2006 10:20:27 -0400
Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Jun 2006 10:20:26 -0400
In-Reply-To: <44845914.3090207@grotto-networking.com>
References: <44845914.3090207@grotto-networking.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <97684F9F-453A-435C-95FA-96778779D9C6@cisco.com>
Cc: ccamp@ops.ietf.org, pce@ietf.org
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [Pce] Virtual Network Topology (VNT) changes and IP layer routing loops
Date: Wed, 07 Jun 2006 10:20:22 -0400
To: Greg Bernstein <gregb@grotto-networking.com>
X-Mailer: Apple Mail (2.750)
X-OriginalArrivalTime: 07 Jun 2006 14:20:26.0675 (UTC) FILETIME=[85A97030:01C68A3D]
DKIM-Signature: a=rsa-sha1; q=dns; l=2413; t=1149690028; x=1150554028; c=relaxed/simple; s=sjdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:JP=20Vasseur=20<jvasseur@cisco.com> |Subject:Re=3A=20[Pce]=20Virtual=20Network=20Topology=20(VNT)=20changes=20and=20I P=20layer=20routing=20loops; X=v=3Dcisco.com=3B=20h=3D4WLiFWjDUNLvTOSsgm7b6ade6MA=3D; b=Pf843R8r0aQsi9LZR4oqi8AhT+1SmubLcC1hLrc5B9WXNUe6kFtAiuWy/nwzKWnjArB33m2L bLO7CQIXX5dCGuuUrUDZdEAHlbEuWnDFTrhoGiCDQRsyRaSpDx89MePZ;
Authentication-Results: sj-dkim-2.cisco.com; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com verified; );
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

Hi Greg,

Thanks for your note. I just wanted to add that this is no different  
from IGP Link weight tuning and off-line algorithms/heuristics  
computing link costs already take such constraint into account. One  
can expect an PCE implementation for VNT computation to also take  
such constraint into account.

Cheers,

JP.

On Jun 5, 2006, at 12:17 PM, Greg Bernstein wrote:

> Hi folks, in drafts draft-ietf-ccamp-gmpls-mln-reqs-00.txt and  
> draft-ietf-pce-inter-layer-frwk-00.txt the concepts of multi-layer  
> and multi-region networking are defined and discussed.
> An important case is when the IP layer rests directly upon a  
> "virtual network topology" layer that we will desire to change via  
> GMPLS signaling. Changes to the IP layer VNT can produce "transient  
> IP layer routing loops" also known as "micro loops" which can last  
> 100's of mili seconds or more.  Hence any time we change a  
> connection between IP layer routers via GMPLS we can cause  
> significant outages compared to the recovery times that we set out  
> to achieve with GMPLS fast reroute and other mechanisms such as SDH  
> APS (rings and linear).
>
> At the Routing working group, Alex's draft draft-ietf-rtgwg- 
> microloop-analysis-01.txt provides some analysis and a method to  
> reduce the impact (duration too) of the transient loops.  More  
> recently the drafts:
> (1) draft-bryant-shand-lf-applicability-01.txt
> (2) draft-bryant-shand-lf-conv-frmwk-02.txt
> (3) draft-francois-ordered-fib-01.txt
> Address this problem more generally including in (3) a method that  
> guarantee loop free convergence.
>
> The problem is that these have generated very little interest at  
> the RTG WG and may not move forward.  This area is not within PCE  
> or CCAMPs charter but can have an impact on the adoption of GMPLS  
> in multi-layer/region networking. If you're interested please take  
> a look and comment to the RTG WG.  Note I wasn't involved with  
> writing these, but came across them when considering the effects of  
> GMPLS changes on the IP layer VNT.
>
> Thanks
>
> Greg B.
>
> -- 
> ===================================================
> Dr Greg Bernstein, Grotto Networking (510) 573-2237
>
>
>
> _______________________________________________
> Pce mailing list
> Pce@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/pce