Re: [bmwg] Comments on draft-ietf-bmwg-basic-convergence

"UTTARO, JAMES" <ju1738@att.com> Thu, 29 May 2014 14:20 UTC

Return-Path: <ju1738@att.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 265021A6F56 for <bmwg@ietfa.amsl.com>; Thu, 29 May 2014 07:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.85
X-Spam-Level:
X-Spam-Status: No, score=-4.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5U5xNU1lk3Q1 for <bmwg@ietfa.amsl.com>; Thu, 29 May 2014 07:20:18 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 756E21A6F41 for <bmwg@ietf.org>; Thu, 29 May 2014 07:20:17 -0700 (PDT)
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.1-0) with ESMTP id d1247835.2ae607a78940.5057418.00-2446.14082677.nbfkord-smmo06.seg.att.com (envelope-from <ju1738@att.com>); Thu, 29 May 2014 14:20:13 +0000 (UTC)
X-MXL-Hash: 5387421d0b080e57-14d4c7dcc29a3df6ca19dbca2f6da22b3671d072
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.1-0) over TLS secured channel with ESMTP id 71247835.0.5057333.00-1955.14082428.nbfkord-smmo06.seg.att.com (envelope-from <ju1738@att.com>); Thu, 29 May 2014 14:20:10 +0000 (UTC)
X-MXL-Hash: 5387421a4bc879c9-58e99d2b8e6b40b7f063ed1311279a577275f036
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s4TEK5YM011759; Thu, 29 May 2014 10:20:06 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s4TEJv36011587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 May 2014 10:20:00 -0400
Received: from MISOUT7MSGHUB9A.ITServices.sbc.com (MISOUT7MSGHUB9A.itservices.sbc.com [144.151.223.62]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Thu, 29 May 2014 14:19:46 GMT
Received: from MISOUT7MSGUSRCD.ITServices.sbc.com ([169.254.4.251]) by MISOUT7MSGHUB9A.ITServices.sbc.com ([144.151.223.62]) with mapi id 14.03.0174.001; Thu, 29 May 2014 10:19:45 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: 'Rajiv Papneja' <Rajiv.Papneja@huawei.com>, "'bmwg@ietf.org'" <bmwg@ietf.org>
Thread-Topic: Comments on draft-ietf-bmwg-basic-convergence
Thread-Index: Ac9JzvHItEzNWPW6QPmwJmOz4pIs5AcbO1aABUNHP3A=
Date: Thu, 29 May 2014 14:19:44 +0000
Message-ID: <B17A6910EEDD1F45980687268941550F06D380C5@MISOUT7MSGUSRCD.ITServices.sbc.com>
References: <B17A6910EEDD1F45980687268941550F06362868@MISOUT7MSGUSR9I.ITServices.sbc.com> <52B0D42F4BADB144B850705C4549F6EA21491AFC@dfweml703-chm.china.huawei.com>
In-Reply-To: <52B0D42F4BADB144B850705C4549F6EA21491AFC@dfweml703-chm.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.91.76.243]
Content-Type: multipart/alternative; boundary="_000_B17A6910EEDD1F45980687268941550F06D380C5MISOUT7MSGUSRCD_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=Kpj6LxqN c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a]
X-AnalysisOut: [=cBTeQoVI2ekA:10 a=ofMgfj31e3cA:10 a=lB4lNuC3LbQA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=zQP7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=i0EeH86SA]
X-AnalysisOut: [AAA:8 a=48vgC7mUAAAA:8 a=OiZMrtSzT3ZvjuTyVuUA:9 a=wPNLvfGT]
X-AnalysisOut: [eEIA:10 a=hPjdaMEvmhQA:10 a=lZB815dzVvQA:10 a=xkVxmyi4VMz6]
X-AnalysisOut: [tzeQ:21 a=OewV-UU7Hdgt9In5:21 a=yMhMjlubAAAA:8 a=SSmOFEACA]
X-AnalysisOut: [AAA:8 a=XIpJDxpoAge5YHnezU8A:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4]
X-AnalysisOut: [-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=C93-BYJG2Sr]
X-AnalysisOut: [hnMYJ:21 a=lIFYXmPZwxN0PErR:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <ju1738@att.com>
X-SOURCE-IP: [144.160.229.24]
Archived-At: http://mailarchive.ietf.org/arch/msg/bmwg/lgZOL2Vx9dhNu089Ex84pl_LteA
Cc: "MORTON JR., AL" <acmorton@att.com>
Subject: Re: [bmwg] Comments on draft-ietf-bmwg-basic-convergence
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 May 2014 14:20:24 -0000

Rajiv,

                I think I can help with some of the scenarios.. Maybe we can meet on the phone and discuss over the next couple of weeks.

Jim Uttaro

From: Rajiv Papneja [mailto:Rajiv.Papneja@huawei.com]
Sent: Wednesday, May 21, 2014 6:45 PM
To: UTTARO, JAMES; bmwg@ietf.org
Cc: MORTON JR., AL
Subject: RE: Comments on draft-ietf-bmwg-basic-convergence

Hi James,

First of all thank you so much for your valuable comments and my sincere apologies for the delay in responding to your comments. Please see inline:


From: bmwg [mailto:bmwg-bounces@ietf.org] On Behalf Of UTTARO, JAMES
Sent: Thursday, March 27, 2014 11:12 AM
To: bmwg@ietf.org<mailto:bmwg@ietf.org>
Cc: MORTON JR., AL
Subject: [bmwg] Comments on draft-ietf-bmwg-basic-convergence

Meta Comments.

A picture showing the T0 failure T1 failure detection T3 Control Plane Detects T3 Control Plane Converged T4 Forwarding Plan Converged would be a useful addition to the reporting format.
[rp] <Do you want us to include these as reporting parameters in the reporting matrix?  We only define data plane convergence methodology in this document.


You should indicate your sampling interval.
[rp] We do suggest that the user defines the sampling intervals  but do not recommend any values in the work

As part of the route distribution it should be made clear the various leaf to node ratios you recommend.
[rp] We do recommend the route mixture in section 4.2 which is by using the internet routing table that has a good distribution of route prefixes. Also in testcases we recommend multiple iterations with a varying number of routes and route mixtures to get a complete characterization

This goes way back for me but in the late 90s we used routers that prioritized other protocols/processes over BGP, so part of our convergence testing would be to stress out multiple protocols and get data on how BGP convergence may be affected. It is important when doing this benchmarking to simulate the real world design and behavior..


Section 1

Will VPNV4 be included in subsequent drafts?  Many of our designs are built around providing a quickly converging BGP Control Plane for our VPN customers.
<rp> Yes, this is what we have been considering. We certainly welcome you participating in extending this work to include BGP based services

Section 1.4


"To ensure uniformity of the results all optional
   parameters SHOULD be disabled and all settings SHOULD be changed to
   default, these may include BGP timers as well."


We modify the default parameters to enhance convergence.. It may be useful to solicit from SPs and others what the settings are and use that as a baseline.
<rp> Yes, certainly. We emphasis reporting matrix to include initial conditions (for example, in section 4.4,  recommendations on using the timers). We present a unified methodology and initial conditions that can be defined based on user requirements ( for example -various SP requirements). We also recommend some basic settings 4.4, however we would welcome a typical example from you!

Section 5.1


"Running tests with a varying number of routes and route mixtures is

   important to get a full characterization of a single peer."



I did not see it but having multiple peers with varying route mixtures is an important point. For this type of testing the results change dramatically based on workload profile.

[rp]  we agree with you here, and we recommend multiple peer scenarios in the section 4.1. We also provide the flexibility for the user to document the number of peers should be included in the testing per each user requirement. We will however clarify the importance of using route mixtures for multiple peers.





Section 5.2.1



An interesting addl case of interest would be when both links hot in a load balanced manner. We use this configuration quite a bit and a result of interest would be how long to reprogram the FIB and point the ½ number of entries using RR1 to be re-programmed to use RR2. This is a function of the vendor/platform software design and how it deals with FIB entries ( We hope for indirection )

[rp] If I understand the scenario correctly, I believe this scenario is covered in section 5.2.3.


Section 5.8

Does this address both GR and LLGR?
[rp] currently we only considered GR. The LLGR work we plan on considering it for future extensions/drafts when we include other Address-families