Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acceptown-community-01.txt
Jeffrey Haas <jhaas@pfrc.org> Tue, 06 May 2008 11:15 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 DE3AB28C0E9; Tue, 6 May 2008 04:15:28 -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 042023A6B40 for <idr@core3.amsl.com>; Tue, 6 May 2008 04:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 IQsbBk-4tCDo for <idr@core3.amsl.com>; Tue, 6 May 2008 04:15:25 -0700 (PDT)
Received: from manos.scc.mi.org (manos.scc.mi.org [204.11.140.250]) by core3.amsl.com (Postfix) with ESMTP id 5FA0F3A68E0 for <idr@ietf.org>; Tue, 6 May 2008 04:15:25 -0700 (PDT)
Received: by manos.scc.mi.org (Postfix, from userid 1025) id 8A7064E4DA; Tue, 6 May 2008 07:15:23 -0400 (EDT)
Date: Tue, 06 May 2008 07:15:23 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "UTTARO, JAMES, ATTLABS" <uttaro@att.com>
Message-ID: <20080506111523.GA9122@scc.mi.org>
References: <A1F50CB516D211409DFD05D6B3CE6D300ED2856E@KCCLUST06EVS1.ugd.att.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <A1F50CB516D211409DFD05D6B3CE6D300ED2856E@KCCLUST06EVS1.ugd.att.com>
User-Agent: Mutt/1.5.9i
Cc: idr@ietf.org, "LONGHITANO, ANTHONY C, ATTLABS" <aclonghitano@att.com>, "RAMSAROOP, JEEWAN P, ATTLABS" <jramsaroop@att.com>, "NGUYEN, HAN Q, ATTLABS" <hnguyen@att.com>
Subject: Re: [Idr] Fwd: I-D ACTION: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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
Jim, On Mon, May 05, 2008 at 11:17:29AM -0500, UTTARO, JAMES, ATTLABS wrote: > I wanted to take an opportunity to discuss the rationale for this draft. Thanks for taking the time to go over this. > Why is this draft so powerful? With this draft the SP can simply manage > routing information from central location. That may be an admirable goal but it has a bit more scope than may make many people comfortable, including me. In your offered example of managing VPNs this is reasonable, although IMO only weakly so. However, since this is a general community rather than a different form of an extended community, this has semantics that might be hazardous under misconfiguration to non-VPN infrastructure. The argument has been made that under proper implementation that it wouldn't be dangerous. I'll just leave it that I'm skeptical. At least two modifications to the protocol mechanism suggest themselves to me: 1. Add a configuration knob that says "accept this route with route-target and ignore originator". 2. A new version of the route-target extended community that has the "accept this with your own originator" semantics. Both of these options limit the scope of this feature to the VPN case. > In order to create a VPN > stitch, the SP simply applies RTs to facilitate the stitch and reflects > to all PEs. In order to deliver these services from a central location ( > RR, etc... ) we need to be able to reflect a route back to the PE that > originated it. This is due to the fact the the two VPNs being stitched > may reside on the same PE. I think one of the things I find unfortunate here is that this feature shouldn't be necessary. The code path for sending your BGP routes could simply reflect them internally back to your router as an "incoming route" when a route-target of interest is being appended on an outbound basis. Having been involved in an implementation that did this, it's certainly possible even if the code path is awkward. -- Jeff _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
- [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acceptow… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Ilya Varlashkin
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Ilya Varlashkin
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Enke Chen
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Enke Chen
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Enke Chen
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd:I-D ACTION:draft-pmohapat-idr-accep… Robert Raszuk
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Danny McPherson
- Re: [Idr] Fwd:I-D ACTION:draft-pmohapat-idr-accep… Danny McPherson
- Re: [Idr] Fwd:I-D ACTION:draft-pmohapat-idr-accep… John G. Scudder
- Re: [Idr] Fwd:I-D ACTION:draft-pmohapat-idr-accep… Brian Dickson
- Re: [Idr] Fwd:I-D ACTION:draft-pmohapat-idr-accep… Robert Raszuk
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… UTTARO, JAMES, ATTLABS
- Re: [Idr] Fwd:I-D ACTION:draft-pmohapat-idr-accep… Danny McPherson
- [Idr] Route reflectors [was: Re: Fwd:I-D ACTION:d… John G. Scudder
- Re: [Idr] Route reflectors [was: Re: Fwd:I-D ACTI… Brian Dickson
- Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-accep… Ilya Varlashkin
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Jeffrey Haas
- Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-accep… UTTARO, JAMES, ATTLABS
- Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-accep… Danny McPherson
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-accep… Jim Guichard (jguichar)
- Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-accep… Ilya Varlashkin
- Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-accep… John G. Scudder
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Jeffrey Haas
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Jim Guichard (jguichar)
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… UTTARO, JAMES, ATTLABS
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Jeffrey Haas
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Jeffrey Haas
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Jeffrey Haas
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… John G. Scudder
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… Jeffrey Haas
- Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acce… David Ward
- Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-accep… Pradosh Mohapatra (pmohapat)
- [Idr] draft-pmohapat-softwire-lb-00.txt Pradosh Mohapatra (pmohapat)