Re: [Idr] draft-rosen-idr-aigp-00

"Pradosh Mohapatra (pmohapat)" <pmohapat@cisco.com> Tue, 24 March 2009 17:49 UTC

Return-Path: <pmohapat@cisco.com>
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4B4728C31B for <idr@core3.amsl.com>; Tue, 24 Mar 2009 10:49:19 -0700 (PDT)
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 UjxIGNnx-240 for <idr@core3.amsl.com>; Tue, 24 Mar 2009 10:49:18 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 220EE28C320 for <idr@ietf.org>; Tue, 24 Mar 2009 10:49:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,413,1233532800"; d="scan'208";a="145966706"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 24 Mar 2009 17:49:53 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n2OHnr4F005157; Tue, 24 Mar 2009 10:49:53 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id n2OHnrq8018417; Tue, 24 Mar 2009 17:49:53 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Mar 2009 10:49:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Mar 2009 10:49:51 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5408EB8472@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <49C906E6.9030904@raszuk.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Idr] draft-rosen-idr-aigp-00
Thread-Index: Acmsm7L3MGVe+K30S6urNqBjcuHlagABoHGw
References: <49C906E6.9030904@raszuk.net>
From: "Pradosh Mohapatra (pmohapat)" <pmohapat@cisco.com>
To: robert@raszuk.net, idr <idr@ietf.org>
X-OriginalArrivalTime: 24 Mar 2009 17:49:53.0108 (UTC) FILETIME=[EF99B140:01C9ACA8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1568; t=1237916993; x=1238780993; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pmohapat@cisco.com; z=From:=20=22Pradosh=20Mohapatra=20(pmohapat)=22=20<pmohapat @cisco.com> |Subject:=20RE=3A=20[Idr]=20draft-rosen-idr-aigp-00 |Sender:=20; bh=zNc9Xb8dgsrLRfnSd6QrQVeLxKFhNhgFIq4HrObJt04=; b=cBmjFGVC/mk+nIMyNgjjSCTnHv05AWmth+FpildpPITYcfUGkJfn91VAc8 606XxFUHHkrr/7GlaOBdcLvFC/fn9FVBe3ec2peF+oEPN3LBVeU30sWS2JB0 JSY2/L6LSJ;
Authentication-Results: sj-dkim-3; header.From=pmohapat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Subject: Re: [Idr] draft-rosen-idr-aigp-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2009 17:49:19 -0000

Hi Robert,

Thanks for the comments. Inline:

| I would like to support the suggestion made yesterday by Enke 
| Chen, Keyur Patel and Danny which suggested to make a good 
| analysis for using MED + Cost Community which are an already 
| existing tools to achieve the same functionality as the draft 
| proposed via a definition of a new AIGP attribute.

Here are the replies I made during the WG discussion for these
questions:

1) MED alone is not a good tool since the MED comparison step
   is after AS_PATH length comparison.
2) Cost community is an extended community which is optional
   transitive. We want to make the attribute non-
   transitive to restrict its scope of propagation.

- Pradosh

| 
| In fact the problem described in the draft is a very good 
| example where practical problem can be solved using the above 
| two solutions combined together.
| 
| It can be a very good motivation for restarting work on cost 
| community itself which were last posted 
| draft-retana-bgp-custom-decision-00. There are apparently 
| practical cases which this draft has a potential to solve and 
| IMHO there is a saving to implement something once and then 
| reuse for various applications as opposed to implementing 
| separate attributes which would at the end result in more 
| burden to BGP and deployment difficulties.
| 
| Cheers,
| R.
| 
| _______________________________________________
| Idr mailing list
| Idr@ietf.org
| https://www.ietf.org/mailman/listinfo/idr
|