Re: [Gen-art] Gen-ART review of draft-ietf-softwire-bgp-te-attribute-03.txt
"Hamid Ould-Brahim" <hbrahim@nortel.com> Mon, 15 December 2008 22:36 UTC
Return-Path: <gen-art-bounces@ietf.org>
X-Original-To: gen-art-archive@optimus.ietf.org
Delivered-To: ietfarch-gen-art-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B2753A6989; Mon, 15 Dec 2008 14:36:03 -0800 (PST)
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FD853A69B1 for <gen-art@core3.amsl.com>; Mon, 15 Dec 2008 14:36:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z2s0h+TloPFO for <gen-art@core3.amsl.com>; Mon, 15 Dec 2008 14:36:01 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id D0D233A6989 for <gen-art@ietf.org>; Mon, 15 Dec 2008 14:36:00 -0800 (PST)
Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com [47.129.230.95]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id mBFMZn203123; Mon, 15 Dec 2008 22:35:50 GMT
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 15 Dec 2008 17:35:47 -0500
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D1791C242@zcarhxm0.corp.nortel.com>
In-Reply-To: <494695FE.2040505@ericsson.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Gen-ART review of draft-ietf-softwire-bgp-te-attribute-03.txt
Thread-Index: Acle2+BPg4rYOhBGSzKEK/c36iMjlgAJsyYw
References: <494695FE.2040505@ericsson.com>
From: Hamid Ould-Brahim <hbrahim@nortel.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, General Area Review Team <gen-art@ietf.org>, draft-ietf-softwire-bgp-te-attribute@tools.ietf.org
Cc: softwire-ads@tools.ietf.org, Yakov Rekhter <yakov@juniper.net>, softwire-chairs@tools.ietf.org, Don Fedyk <dwfedyk@nortel.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-bgp-te-attribute-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org
Hi Suresh, See inline under <<<[Hamid]...>>> -----Original Message----- From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com] Sent: Monday, December 15, 2008 12:38 PM To: General Area Review Team; draft-ietf-softwire-bgp-te-attribute@tools.ietf.org Cc: softwire-ads@tools.ietf.org; softwire-chairs@tools.ietf.org Subject: Gen-ART review of draft-ietf-softwire-bgp-te-attribute-03.txt I am the assigned Gen-ART reviewer for draft-ietf-softwire-bgp-te-attribute-03.txt For background on Gen-ART, please see the FAQ at <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>. Please resolve these comments along with any other Last Call comments you may receive. Summary: This draft is almost ready for publication as Proposed Standard but I have a few comments. Major ===== Section 5: Impact on scalability * This document states that "Use of Traffic Engineering Attribute does not increase the number of routes" but I am not sure if this is true. Say I have a route 200.0.2.0/24 with a TE attribute field X and a route 200.0.3.0/24 with TE attribute field Y. Without the TE attribute these could have been aggregated to a 200.0.2.0/23, but with the attribute, they cannot be. Am I reading this wrong? <<<[Hamid] Actually this was discussed before. The draft recommends that when the routes carry different TE information (even if they share all other attributes and next hop then these routes will be advertised in different BGP update messages. So in this specific case BGP will have to send two different BGP update messages. When looking at a single BGP update message with TE information, the statement above is correct. >>>> Minor ===== Section 3 * This document does not define whether Switching Capability-specific information is included when the switching cap field is set to Fiber Switch Capable (FSC) <<<[Hamid] Yes. In fact here we are not doing anything different than what is being done in RFC4203 (OSPF-TE). Thanks for the input. Hamid.>>> Cheers Suresh _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen-ART review of draft-ietf-softwire-b… Suresh Krishnan
- Re: [Gen-art] Gen-ART review of draft-ietf-softwi… Hamid Ould-Brahim