IETF Logo Mail Archive

Re: [Idr] draft-l3vpn-legacy-rtc-00.txt

altonlo <altonlo@cisco.com> Fri, 29 July 2011 13:15 UTC

Return-Path: <altonlo@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B96121F8509 for <idr@ietfa.amsl.com>; Fri, 29 Jul 2011 06:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.266
X-Spam-Level:
X-Spam-Status: No, score=-5.266 tagged_above=-999 required=5 tests=[AWL=-2.667, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVtfHTHXsfzY for <idr@ietfa.amsl.com>; Fri, 29 Jul 2011 06:15:47 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id D1BF221F8500 for <idr@ietf.org>; Fri, 29 Jul 2011 06:15:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=altonlo@cisco.com; l=2746; q=dns/txt; s=iport; t=1311945347; x=1313154947; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=rD+/vUrElSQp/hXy3jFTNpl9V5XZKKxCfkNB+tLpDw4=; b=khyYS2WdJlggc7PqZ6KMhITn84gRcvUmBM8l70TJY6o/Q6Ag5Xqob07a KXafZOjrlJNLa2l6RxlM8Q0BLtuCXT9hKD1XUBARXE0tAG4818RGviP3P 65eui2N48Ed/+ifAF10MCsTMTu5hETJqZ989b0A5+xkVvtY5US5Qn2cbU 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EALKxMk6rRDoJ/2dsb2JhbAA0AQEBAQIBAQEBEQErAwE2CwUOAQkJD04SBjkBAQUPCCenRXeIfAShM55AhkEEh1qLIIUPhFuHGQ
X-IronPort-AV: E=Sophos;i="4.67,287,1309737600"; d="scan'208";a="7773942"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-2.cisco.com with ESMTP; 29 Jul 2011 13:15:43 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p6TDFhRu016782; Fri, 29 Jul 2011 13:15:43 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Jul 2011 06:15:42 -0700
Received: from 10.21.79.12 ([10.21.79.12]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Fri, 29 Jul 2011 13:15:42 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Fri, 29 Jul 2011 06:15:41 -0700
From: altonlo <altonlo@cisco.com>
To: Pedro Marques <pedro.r.marques@gmail.com>
Message-ID: <CA58008D.2B1A5%altonlo@cisco.com>
Thread-Topic: [Idr] draft-l3vpn-legacy-rtc-00.txt
Thread-Index: AcxN8Z1kyM0E/XJ6eUiB2enj2Tb1SQ==
In-Reply-To: <CAMXVrt7bxL+sOwCNNfS-8XUX+hXjdx9trwaaWmFzDk7Bc-UPrA@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Jul 2011 13:15:42.0804 (UTC) FILETIME=[9E784140:01CC4DF1]
Cc: Keyur Patel <keyupate@cisco.com>, idr@ietf.org
Subject: Re: [Idr] draft-l3vpn-legacy-rtc-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 29 Jul 2011 13:15:47 -0000

Hi Pedro,

Thanks for your reviews and comments.  Please see inline response.

Cheers,
-alton


On 7/28/11 8:54 PM, "Pedro Marques" <pedro.r.marques@gmail.com> wrote:

> Alton,
> I'd like to ask for a clarification as to whether you believe that the
> "Legacy PE Behavior" that is described in the draft is achievable by
> configuration alone, with no software changes to the PEs in question.
> For instance, can the communities that are defined in the draft be
> advertised by existing production software ?

The communities value is the following:

0xFFFF0002    ROUTE_FILTER_TRANSLATED_v4    [draft-l3vpn-legacy-rtc]
0xFFFF0003    ROUTE_FILTER_v4    [draft-l3vpn-legacy-rtc]
0xFFFF0004    ROUTE_FILTER_TRANSLATED_v6    [draft-l3vpn-legacy-rtc]
0xFFFF0005    ROUTE_FILTER_v6    [draft-l3vpn-legacy-rtc]

The existing production software in IOS and IOS-XR can be used without any
software upgrade.


> 
> If the procedure is based on configuration alone, it seems to be a
> potentially very error prone method. For instance, the RT filtering
> configuration could easily get out of sync with the actually VRF
> configuration, making this of doubtful operational value.

You've made a very good point and the configuration needs to planned.  This
scheme is not meant to replace RFC4684.  Instead, it offers the SP operators
a different migration path to RFC4684.

The "extra" configuration should be a one-to-one mapping to the VPN
membership (matching route-target value) on the legacy PE.  One suggestion
is to generate this configuration whenever a new VRF is provision in the
legacy PE.  We would like to hear feedback from the workgroup also.

> 
> If on the other hand one assumes that a software upgrade is required,
> these are not longer "Legacy PEs". In the latter case this proposal
> seems to be just a competing encoding for RFC4684.

Software upgrade is not required on the legacy PE
> 
> I think it is perfectly valid to propose an alternate encoding but i
> believe the document should be written as such and compare itself with
> the previous mechanism.

This is a very good feedback.  We will add your suggestion in next version.

> 
> regards,
>   Pedro.
> 
> On Thu, Jul 28, 2011 at 8:17 AM, altonlo <altonlo@cisco.com> wrote:
>> Hi,
>> 
>> We presented the following draft (Legacy PE RT Filtering) in IETF80 Prague
>> meeting.
>> 
>> http://tools.ietf.org/html/draft-l3vpn-legacy-rtc-00
>> 
>> And we are asking the IDR working group to accept this as a working group
>> document.
>> 
>> Thanks,
>> -alton
>> 
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>

v2.23.0 | Report a Bug | By Email