Re: [Idr] Discussions about RT-Constrain //RE: IETF-78 IDR minutes

Robert Raszuk <raszuk@cisco.com> Mon, 06 September 2010 18:04 UTC

Return-Path: <raszuk@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 9B7513A6959 for <idr@core3.amsl.com>; Mon, 6 Sep 2010 11:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 1-2j-xw-8f9M for <idr@core3.amsl.com>; Mon, 6 Sep 2010 11:04:49 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id F29C43A694D for <idr@ietf.org>; Mon, 6 Sep 2010 11:04:47 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAO7JhExAaMHG/2dsb2JhbACTSI0qcaJngiMMAZhQhT0Eihg
X-IronPort-AV: E=Sophos;i="4.56,326,1280707200"; d="scan'208";a="584394292"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-6.cisco.com with ESMTP; 06 Sep 2010 18:05:15 +0000
Received: from [192.168.1.61] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o86I5DH9026470; Mon, 6 Sep 2010 18:05:14 GMT
Message-ID: <4C852D5E.4080306@cisco.com>
Date: Mon, 06 Sep 2010 20:05:18 +0200
From: Robert Raszuk <raszuk@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: lizhenqiang@chinamobile.com
References: <OFE1DAC013.1BD3F321-ON48257796.005C9D6D-48257796.005C9D76@china.mobile>
In-Reply-To: <OFE1DAC013.1BD3F321-ON48257796.005C9D6D-48257796.005C9D76@china.mobile>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: idr@ietf.org
Subject: Re: [Idr] Discussions about RT-Constrain //RE: IETF-78 IDR minutes
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@cisco.com
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: Mon, 06 Sep 2010 18:04:50 -0000

Hello Zhenqiang,

Many thx for your email. I have no doubt about your deployment case. In 
fact I think what you are planning to do does make sense.

But let's do not forget about the overall picture. RT-constrain's 
primary objective was to help automate inter-as VPNs. Later we have 
observed that it may also help to allow to store on RRs only those set 
of routes which are desired. The fact that it allows limit the amount of 
automated inbound filtering on the PEs is more or less the over all 
positive side effect :)

So RT-constrain in itself is an optimization. This draft would be an 
optimization to the optimization.

Reg the impact of IPv6 introduction how many VPN IPv6 routes are you 
concerned with ? Note that there are production IPv4 deployments with 
over 1 million IPv4 routes today and without rt-constrain deployed at all.

Are you concerned with the need to drop unnecessary routes on inbound RR 
-> PE (which is a very cheap operation) on those PEs which do not need 
them ? Or are you under impression that all PEs would need to store 
those routes even if those would not be needed .. the latter would be 
very easy to address without any protocol changes by your favorite BGP 
implementation.

Many thx,
R.


> Hi Robert and Jie,
>
> I am Zhenqiang Li from China Mobile. I think this draft is useful. We
> are now planning the IPv6 migration scheme. During the migration
> period, some sites of a specific service will introduce IPv6 first.
> These IPv6-enabled sites (still support IPv4) need to communicate
> with other sites belonging to this specific service, including both
> IPv6-enabled and IPv4-only sites. Because they are parts of one
> service, we want them to be in one VPN. Thus we give the IPv6 route
> the same RT as the IPv4 route of this service. By using the proposed
> scheme in this draft, we can control the IPv6 route distribution
> within the IPv6-enabled sites. This is also helpful to limit the
> potential impact of IPv6 introduction.
>
> Best Regards, Zhenqiang Li
> _______________________________________________ Idr mailing list
> Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
>