RE: Differentiated Routing, not only plain rambo-SPF

"Ayyasamy, Senthilkumar (UMKC-Student)" <saq66@umkc.edu> Mon, 05 August 2002 18:32 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26145 for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:32:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20605; Mon, 5 Aug 2002 14:26:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20579 for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:26:49 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25720 for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:25:36 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905); Mon, 5 Aug 2002 13:26:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 05 Aug 2002 13:26:46 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2526@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8qrS9RFP22RL5QkCgVgbVRxxWIQAAkdNY
From: "Ayyasamy, Senthilkumar (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>, Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: "Naidu, Venkata" <Venkata.Naidu@marconi.com>, jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net, routing-discussion@ietf.org
X-OriginalArrivalTime: 05 Aug 2002 18:26:47.0222 (UTC) FILETIME=[A8686D60:01C23CAD]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA20580
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

>  -> - scalability: Since you are maintaining multiple Routing
> -> tables, doing at line rate is pretty difficult and hence
> -> doesnt scale well.
> I agree with you here. Yes! there are performance and
> scalability problems if we go for DiffRouting in a
> hop-by-hop fashion. Then you have to maintain
> different route tables, line rate forwarding issues etc etc.
>
> That is why we went for source routing (using MPLS-TE).
> That effectively solved the problem of maintaining
> multiple routing tables. Connection-less to connection-oriented
> move (with small fixed length label lookup) solved the
> problem of line rate forwarding (directly or indirectly).
> 
>  Now we are moving towards MPLS-TE with DiffServ.
who told you diffserv-aware MPLS -TE scalable? 
Section 4.4 and 3.1 of http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-reqts-05.txt clearly points out the scalability problems.
  

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion