Subject: [bmwg] Re: Updated:draft-sdry-bmwg-mvpnscale-03.txt

From: "Aamer Akhter (aakhter)" <[email-masked]>
Date: Thu, 6 Dec 2007 04:02:15 -0500

Hi Silvija/Maria/Yugi/Fernando,

I do like the breakdown in the test cases where common testcases are explictly identified. The draft continues to provide good guidance to network operators looking at this complicated technology. MVPN has many moving parts and the work takes this multi-variable environment and tries to make implementation comparisons possible. Unfortunatley it does take time for the test tool folks to package tests and I hope we can solidify this work for general avaliability. 

Thank-you for taking the time to put this together and keeping it moving forward.

Comments/questions:

= 6.2 Unicast Control Plane Setup 

Not sure if the reasoning given for the MUST for OSPF is correct. Even if OSPF was used, there is no guarantee the timers would be equivalent etc. I would suggest perhaps just documenting OSPF/ISIS and the timer values? 

For the SHOULD NOT for internet routes (I'm just assuming routes in the global table), can a reason be documented?

Does this cover IPv6 as well? Think it should be stated either way, and the 'internet/ipv4' phrase in 6.2 fixed if necessary. I see Rajiv and Gunter asked the same question, and I agree if the draft can be made agnostic, it would be very nice.

= 6.3 Multicast Control Plane Setup 

In all seriousness, I do appreciate the inline '(default MDTs)' translations from 'MI-PMSI' J. Thank-you.

'maximum Timer Interval between messages of 1/10th
   of a second.' Just curious, where is the interval number coming from?

=  6.4 Considerations for Number of Receivers behind remote PEs

'J/P' => join/prune
 
'does not perform efficient J/P suppression'. Is this effiency level defined?
 
= 6.6 Test Apparatus Considerations

The 80 J/P messages per PDU imply a minimum MTU. Can this be stated? Also I imagine, that setting the packing like this would have be doable on the test tool, is that something common?
 
= 7.2 Failure Recovery Testing Execution Methodology

In step 3, probably want to explicitly specify test-data multicast traffic, rather than just mcast.
 
= 9.1 "Empty" MVPNs Scale

I'm probably missing something here, but the two statements seem to be in conflict:
 
a)       Num_*G_C=Num_SG_C=2*Num_mVPN

b)  C-instances multicast routes and SI-PMSIs associated with given mVPN is negligible or zero in this test case.

== minor points

Noted a few 'should not' that were not capitalized.

Extremely minor point, but the first line in diagram in fig 1 doesn't seem to align properly

===================

"Silvija Andrijic Dry (sdry)" <[email-masked]> wrote in message news:<[email-masked]>...
Hi BMWG members,

We would like to solicit your feedback on the new version of MVPN
scalability benchmarking proposal:
http://www.ietf.org/internet-drafts/draft-sdry-bmwg-mvpnscale-03.txt

Note that in rev 03 we made couple of major changes based on feedback
from IETF68, namely:
- scope is modified to include both generic sections applicable to all
MVPN architectures specified in "draft-ietf- l3vpn-2547bis-mcast" and
sections specific to widely deployed "rosen-8" architecture 
- metric is changed to be architecture agnostic
- text is rewritten to address changed scope of the document

We are looking forward to the discussion in Vancouver. And for those of
you that won't be able to attend the meeting we would greatly appreciate
your comments sent to the mailing list.

Thanks,
Authors

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Friday, November 09, 2007 2:15 PM
To: [email-masked]
Subject: I-D ACTION:draft-sdry-bmwg-mvpnscale-03.txt 

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title		: Multicast VPN Scalability Benchmarking
	Author(s)	: S. Dry, et al.
	Filename	: draft-sdry-bmwg-mvpnscale-03.txt
	Pages		: 44
	Date		: 2007-11-9
	
Multicast VPN (MVPN) is a service deployed by VPN service providers 
   to enable their customers to use IP multicast applications over VPNs.

   With the increased popularity the scalability of deploying such a 
   service is becoming of a great interest. This document defines 
   standard metric and test methodology for characterizing and comparing

   control plane MVPN scalability of Provider Edge (PE) devices that 
   implement MVPN service.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-sdry-bmwg-mvpnscale-03.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-sdry-bmwg-mvpnscale-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-sdry-bmwg-mvpnscale-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

----------

_______________________________________________
bmwg mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/bmwg