Re: [OSPF] OSPF Topology Transparent Zone (TTZ) Next Steps

Peter Psenak <ppsenak@cisco.com> Tue, 09 July 2013 20:21 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC42521F9DB5 for <ospf@ietfa.amsl.com>; Tue, 9 Jul 2013 13:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DTsxWH466tYd for <ospf@ietfa.amsl.com>; Tue, 9 Jul 2013 13:21:49 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 728A221F9DB4 for <ospf@ietf.org>; Tue, 9 Jul 2013 13:21:49 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from stew-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r69KLgO0005836 for <ospf@ietf.org>; Tue, 9 Jul 2013 22:21:42 +0200 (CEST)
Received: from ams-ppsenak-8717.cisco.com (ams-ppsenak-8717.cisco.com [10.55.51.200]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r69KLeXD027587; Tue, 9 Jul 2013 22:21:40 +0200 (CEST)
Message-ID: <51DC70D4.8000001@cisco.com>
Date: Tue, 09 Jul 2013 22:21:40 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Huaimo Chen <huaimo.chen@huawei.com>
References: <94A203EA12AECE4BA92D42DBFFE0AE471993A4@eusaamb101.ericsson.se> <38B62731-B738-4FCE-B7D9-80F17244AFCB@juniper.net> <5316A0AB3C851246A7CA5758973207D4451E2F00@dfweml509-mbx.china.huawei.com>
In-Reply-To: <5316A0AB3C851246A7CA5758973207D4451E2F00@dfweml509-mbx.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] OSPF Topology Transparent Zone (TTZ) Next Steps
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 20:21:54 -0000

Huaimo,

OSPF has the concept of areas, which allows you to scale if needed. ABR 
part is also the most complex part of the OSPF protocol and TTZ is of 
the same if not higher complexity.

I do not believe current area architecture has reached its scaling 
limits which would require an introduction of the new protocol mechanism.

In short, you need to find some other applicability of the TTZ, scaling 
is simply not the relevant one.

my 2c,
Peter

On 9.7.2013 21:33, Huaimo Chen wrote:
> Hi Hannes,
>
>      Thanks for your comments!
>      See my responses in line below.
>
> Best Regards,
> Huaimo
> -----Original Message-----
> From: ospf-bounces@ietf.org [mailto:ospf-bounces@ietf.org] On Behalf Of Hannes Gredler
> Sent: Tuesday, July 09, 2013 1:21 PM
> To: Acee Lindem
> Cc: OSPF List
> Subject: Re: [OSPF] OSPF Topology Transparent Zone (TTZ) Next Steps
>
> scaling a link-state protocols route-calculation path (SPF and RIB-Walk) to support 1000s of nodes is an already solved problem.
> solving it again, (just different this time) is of limited use ...
>
> [Huaimo] How about 10,000s or 100,000s of nodes?
>
>
> quite contrary - i fail to see how *hiding* information (i.e. nodes and links along with their TE attributes) does not break some of the TE eco-system that has been built around link-state IGPs. i am particularly interested how  TE use-cases requiring admission-control and pre-emption play with TTZ.
>
> [Huaimo] Regarding to TE, we are working on it and have some solutions.
>
>
> /hannes
>
> On Jul 6, 2013, at 9:09 PM, Acee Lindem wrote:
>
>> As WG chair, I'd like to initiate a discussion on this technology. We've had it presented at the last couple IETFs and there are varying opinions on its usefulness.
>> For reference:
>>
>>   Base Document: http://www.ietf.org/id/draft-chen-ospf-ttz-05.txt
>>   Applicability: http://www.ietf.org/id/draft-chen-ospf-ttz-app-03.txt
>
>
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
>
>