RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence-motivation-00.txt
"Samir Vapiwala \(svapiwal\)" <svapiwal@cisco.com> Wed, 25 April 2007 13:14 UTC
Return-path: <bmwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HghKC-000261-C1; Wed, 25 Apr 2007 09:14:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HghKB-00025v-M7 for bmwg@ietf.org; Wed, 25 Apr 2007 09:14:23 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HghKA-00043z-RE for bmwg@ietf.org; Wed, 25 Apr 2007 09:14:23 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 25 Apr 2007 09:14:23 -0400
X-IronPort-AV: i="4.14,450,1170651600"; d="scan'208,217"; a="58573216:sNHT118861708"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3PDEMCw000376; Wed, 25 Apr 2007 09:14:22 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3PDDolm019288; Wed, 25 Apr 2007 13:14:22 GMT
Received: from xmb-rtp-214.amer.cisco.com ([64.102.31.75]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Apr 2007 09:14:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence-motivation-00.txt
Date: Wed, 25 Apr 2007 09:14:12 -0400
Message-ID: <C14B21C3CFBE6F4C81665B29F9880D3E0363F6AE@xmb-rtp-214.amer.cisco.com>
In-Reply-To: <FD67EDC57CDCC04DA8CA0B795AAC01F30361A212@xmb-rtp-215.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence-motivation-00.txt
thread-index: AceB0LtnaBcSPRFlRt60G3Zvys2IdAAYHsWgAUIFhjA=
From: "Samir Vapiwala (svapiwal)" <svapiwal@cisco.com>
To: "Andrey Kiselev (ankisele)" <ankisele@cisco.com>, bmwg@ietf.org
X-OriginalArrivalTime: 25 Apr 2007 13:14:13.0271 (UTC) FILETIME=[9E579A70:01C7873B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=18768; t=1177506862; x=1178370862; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=svapiwal@cisco.com; z=From:=20=22Samir=20Vapiwala=20\(svapiwal\)=22=20<svapiwal@cisco.com> |Subject:=20RE=3A=20[bmwg]=20draft-vapiwala-bmwg-rsvpte-convergence-motiv ation-00.txt |Sender:=20 |To:=20=22Andrey=20Kiselev=20\(ankisele\)=22=20<ankisele@cisco.com>, =20<b mwg@ietf.org>; bh=it+jPRctk8HhO0Fy+BYwZaG4iD3Xk266LJJvGzIBmAE=; b=FwtjyLgNo7Nn6/Zgg150xydMY3zRP0o2L0ov0EaU0XKw2t6Cj+EBg9C1gPsuaJUdAcsvQNdO unnsvjZ+7EYRC1nEbROSWymwX5ZzhQ4o7lz8qzvpF9fiGzt0Uk5qHTkE;
Authentication-Results: rtp-dkim-2; header.From=svapiwal@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 75ac86d24bd0a3cd8a26e327ae61143e
Cc: Rajiv Papneja <rpapneja@isocore.com>
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1098189375=="
Errors-To: bmwg-bounces@ietf.org
Hi Andery Thanks for reviewing and supporting this work item, we appreciate it. pls see comments inline ________________________________ From: Andrey Kiselev (ankisele) Sent: Friday, April 20, 2007 6:07 PM To: Samir Vapiwala (svapiwal); bmwg@ietf.org Cc: Rajiv Papneja; Karu Ratnam (kratnam) Subject: RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence-motivation-00.txt Hi Authors, I reviewed the document, and I believe there is a need in standard for benchmarking MPLS TE convergence. I was even surprised these items have not been standardized yet. I have a few comments and questions on the document. 1. You use terms MPLS TE convergence and RSVP TE convergence interchangingly through the document. However, most items in section 3 are also applicable to classic RSVP. Are there any existing documents on classic RSVP convergence? I think we should draw a line somewhere between MPLS TE convergence and RSVP convergence. There may be a space for a separate document, covering classic RSVP benchmarking. SV- we will correct the terms use in above draft we'll use RSVP-TE. You are right it will be separate classic RSVP and RSVP-TE draft, There is already terminology draft for classic RSVP as "draft-ietf-bmwg-benchres-term-08.txt" and authors are already working on Methodology draft which will get published soon. In addition you would see separate term and meth documents for RSVP-TE 2. page 4 paragraph 3.3: RSVP rate-limit parameter definitely will impact MPLS TE convergence, but how it applies to benchmarking? It is user-configurable, and can be set to any value. SV- we will list out suggested rate-limit values for scalability in methodology draft. if vendor does not support configurable rate-limit option then one can use default. 3. All factors listed in section 3 come either from RSVP, or system limitations. Should it be something else in this list, like explicit vs. dynamic paths or certain RSVP timers? SV - Explicit or dynamic should not impact convergence because both needs to run CSPF... I'm not aware of any other rsvp timer that could can impact convergence of RSVP-TE, We would like to ask this question to the BMWG list if are missing anything here. 4. Section 4 MPLS TE Scalability and Convergence Performance cases: What cases in section 4 are actually related to scalability? I would add some case which would allow us to get this scalability number MAX x for number of lsps. Should we also consider somehow number of nodes on the path between headend and tailend? SV - All the cases in section 4 will impact scalability and convergence. Section 5 suggests x number of lsp to be tested with every scenario defined in section 4. In reference to the no. of number of hops, section 4.8 measures the latency of signal lsp in scale network. results from that can be extrapolated for network of any size. We'll be happy to hear better ideas from BMWG list if any. 5. page 5 paragraph 4.6, 4.7: I would rephrase headers as "Convergence with RSVP Authentication..." Otherwise it may be IGP authentication, LDP authentication, etc. SV- Convergence with RSVP Authentication sounds better and it eliminates confusion, we'll change that. 6. page 6 paragraph 5.1: Just curious - why wouldn't we start from 1 LSP? SV - Testcase 4.8 covers 1 lsp convergence in scaled network, The granularity of measurements for large numbers of lsp will be coarser and like not a usable for 1 or few numbers of lsp. Thanks Authors Thank you, Andrey ________________________________ From: Samir Vapiwala (svapiwal) Sent: Wednesday, April 18, 2007 11:47 AM To: bmwg@ietf.org Cc: Rajiv Papneja; Samir Vapiwala (svapiwal) Subject: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence-motivation-00.txt Hi folks, We would like to seek your opinion on motivation draft that we have recently published addressing the MPLS TE Convergence benchmarking. This document describes the motivation for benchmarking MPLS traffic engineering (TE) convergence using RSVP-TE as an underlying signaling protocol. This document further provides an overview of the proposed work item and we plan to produce a separate methodology and terminology document if there is enough interest in the area. Kindly review the motivation document that has been recently posted in the internet-draft directory- http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-convergen ce-motivation-00.txt <http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-converge nce-motivation-00.txt> . We look forward to hearing your feedback and comments. Thanks Authors
_______________________________________________ bmwg mailing list bmwg@ietf.org https://www1.ietf.org/mailman/listinfo/bmwg
- [bmwg] draft-vapiwala-bmwg-rsvpte-convergence-mot… Samir Vapiwala (svapiwal)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Andrey Kiselev (ankisele)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Samir Vapiwala (svapiwal)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Raveesh Janardan (rjanarda)
- [bmwg] Re: draft-vapiwala-bmwg-rsvpte-convergence… Aamer Akhter (aakhter)
- RE: [bmwg] Re: draft-vapiwala-bmwg-rsvpte-converg… Karu Ratnam (kratnam)
- RE: [bmwg] Re: draft-vapiwala-bmwg-rsvpte-converg… Aamer Akhter (aakhter)
- RE: [bmwg] Re: draft-vapiwala-bmwg-rsvpte-converg… Karu Ratnam (kratnam)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Rajiv Papneja
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Esa Salahuddin (esalahud)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Rajiv Papneja
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Esa Salahuddin (esalahud)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Rajiv Papneja
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Esa Salahuddin (esalahud)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Al Morton
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Esa Salahuddin (esalahud)
- Re: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Curtis Villamizar
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Samir Vapiwala (svapiwal)
- RE: [bmwg] draft-vapiwala-bmwg-rsvpte-convergence… Esa Salahuddin (esalahud)