Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-acceptown-community-01.txt

"Ilya Varlashkin" <Ilya.Varlashkin@de.easynet.net> Tue, 06 May 2008 11:05 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5297E3A6D64; Tue, 6 May 2008 04:05:25 -0700 (PDT)
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 67EA83A6A32 for <idr@core3.amsl.com>; Tue, 6 May 2008 04:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 PAaUR83sezfx for <idr@core3.amsl.com>; Tue, 6 May 2008 04:05:19 -0700 (PDT)
Received: from softy.ision.net (softy.ision.net [194.163.250.97]) by core3.amsl.com (Postfix) with ESMTP id A04843A6F8B for <idr@ietf.org>; Tue, 6 May 2008 04:05:18 -0700 (PDT)
Received: from paul.de.easynet.net ([195.180.208.152] helo=paul.adoffice.de.easynet.net) by softy.ision.net with esmtp (Exim 4.50) id 1JtKyx-0005YS-TY; Tue, 06 May 2008 13:05:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 06 May 2008 13:05:15 +0200
Message-ID: <7000E71D8C525042A815432358B2F1240138D477@paul.adoffice.local.de.easynet.net>
In-Reply-To: <A1F50CB516D211409DFD05D6B3CE6D300ED2856E@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-acceptown-community-01.txt
Thread-Index: Aciuy4OvU2oYSkWGS6Gg6XwRJbtl7QAm6cPg
References: <A1F50CB516D211409DFD05D6B3CE6D300ED2856E@KCCLUST06EVS1.ugd.att.com>
From: Ilya Varlashkin <Ilya.Varlashkin@de.easynet.net>
To: "UTTARO, JAMES, ATTLABS" <uttaro@att.com>, idr@ietf.org
Cc: "NGUYEN, HAN Q, ATTLABS" <hnguyen@att.com>, "LONGHITANO, ANTHONY C, ATTLABS" <aclonghitano@att.com>, "RAMSAROOP, JEEWAN P, ATTLABS" <jramsaroop@att.com>
Subject: Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-acceptown-community-01.txt
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0410538851=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Jim,
 
it's well understanable why you'd like to have ACCEPT_OWN capability.
However the problem you're trying to solve is more global than the
solution can address. ACCEPT_OWN may solve issue for some networks that
follow certain rules, but there will be still those with different
network design but similar problem and ACCEPT_OWN won't address their
needs (e.g. with client-to-client reflection disabled). Such networks
will then go on and design yet another solution for the same problem. 
 
I believe it's not optimum to modify core protocol functionality just to
address special case scenarios, in contrary - protocols should be more
generic. Couldn't the problem with building extranets solved in some way
that wouldn't require modification of the fundamental BGP functionality?
One such possibility could be to add a new address family to BGP that
would redistribute import/export policies among all routers within
arbitrary boundaries. This way you don't modify core protocol and people
could take advantage of new functionality without being forced to
redesign their networks.
 
Cheers,
iLya
 
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr