Silvija Andrijic Dry (sdry | 10 Jul 2006 15:11
Picon
Favicon

Comments for draft-akhter-bmwg-mpls-meth-00.txt

Hi BMWG folks,
 
I reveiwed draft-akhter-bmwg-mpls-meth-00.txt and have couple of comments to the authors. Overall I thought draft looks good so far and going in the right direction:
 
1) Specify that this draft is applicable only to unicast traffic
2)  In all test cases specify throughput units to be used
3) Section 4.1.1 IGP Support:
  I haven't seen any tests related to control plane in the doc so not sure why are you imposing requirement for IGP to be used....perhaps MUST should be replaced with weaker word?
  Or is it that these type of test just haven't been added to the draft yet but are planned and hence MUST for OSPF and ISIS ?
4) Unidirectional imposition/disposition (sections 6.1.1 and 6.1.2):
  Your draft says in "Reporting format" subsection that max throughput should be measured as in RFC2432. However RFC2432 is  MC perf bench draft and there are multiple throughput types defined so you need to be more specific here. Or this was a typo and different RFC should of been quoted here ?
5) Section 6.4 " MPLS FW Negative Characterization"
  There needs to be more defintion on what is measured here or what pass criteria is or how to compare platfroms...i.e. there needs to be more description of what sentence ".......ensure that the DUT behaves appropriately" means.
Actually when I think about this one more I'm not even sure whether you should have some of these tests in this particular draft as they seem more of functional tests ? It is definately great set of tests that should normally be done but I'm just not sure whether they fit into this particular draft. I would be interested to see what wider audience thinks ?
 
 
Cheers,
 
Silvija
 
 
_______________________________________________
bmwg mailing list
bmwg <at> ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg
The IESG | 11 Jul 2006 02:39
Picon
Favicon

Document Action: 'Terminology for Benchmarking Network-layer Traffic Control Mechanisms' to Informational RFC

The IESG has approved the following document:

- 'Terminology for Benchmarking Network-layer Traffic Control Mechanisms '
   <draft-ietf-bmwg-dsmterm-13.txt> as an Informational RFC

This document is the product of the Benchmarking Methodology Working Group. 

The IESG contact persons are David Kessens and Dan Romascanu.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-dsmterm-13.txt

Technical Summary

 This document describes terminology for the benchmarking of                
 devices that implement traffic control based on IP precedence or           
 Diffserv code point criteria.  The terminology is to be applied            
 to measurements made on the data plane to evaluate IP traffic              
 control mechanisms.                                                        

 New terminology is needed because most existing measurements               
 assume the absence of congestion and only a single per-hop-                
 behavior.  This document introduces several new terms that will            
 allow measurements to be taken during periods of congestion.               

 Another key difference from existing terminology is the definition         
 of measurements as observed on egress as well as ingress of a              
 device/system under test.  Again, the existence of congestion              
 requires the addition of egress measurements as well as those              
 taken on ingress; without observing traffic leaving a                      
 device/system it is not possible to say whether traffic-control            
 mechanisms effectively dealt with congestion. 

 The principal measurements introduced in this document are vectors         
 for rate, delay, and jitter, all of which can be observed with or          
 without congestion of the DUT/SUT. 

Working Group Summary

 This document is a product of the BMWG WG.  The WG has consensus              
 to publish this document as an Informational RFC.

Protocol Quality

 This document was reviewed by David Kessens for the IESG.

_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

Al Morton | 13 Jul 2006 02:23
Picon
Favicon

Remote participants for the BMWG session

For folks who intend to participate remotely:

Please let me (not the whole list) know that you intend
to participate from a non-Montreal location.

The slides for all presentations are available now,
and the audio, jabber, and other info is available
on the IETF site under the current meeting page.

http://www3.ietf.org/meetings/text_conf.html

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=66

http://videolab.uoregon.edu/events/ietf/
for audio, we're in room 519 A

Al
Al Morton | 17 Jul 2006 15:01
Picon
Favicon

2nd WG Last Call on Address Hash and Bit Stuffing Draft (05)

BMWG:

A WG Last Call period for the Internet-Draft on

"Hash and Stuffing: Overlooked Factors in Network Device Benchmarking"

will be open from 17 July 2006 through 14 August 2006.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-hash-stuffing-05.txt

A WG Last Call (ending 3 Feb 2006) was issued on version 04
of this draft.  Version 05 addresses comments from
the previous Last Call, the cross-area review, and the ensuing discussion.
In particular, attention should be paid to material in the new
Appendices (B and C).

Please express your opinion on whether or not this Internet-Draft
should be given to the Area Directors for consideration in
progressing the Draft to an Informational RFC.  Send your comments
to this list or acmorton <at> att.com.
Al Morton | 17 Jul 2006 15:31
Picon
Favicon

WG Last Call on Accelerated Stress Benchmarking Drafts

BMWG:

A WG Last Call period for the Internet-Drafts on

Terminology for Accelerated Stress Benchmarking
Methodology Guidelines for Accelerated Stress Benchmarking

will be open from 17 July 2006 through 28 August 2006 (6 weeks).

URLs for these Internet-Drafts are:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-acc-bench-term-09.txt
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-acc-bench-meth-05.txt

These versions incorporate comments resulting from implementation.
The authors believe that all comments from the working group
have been addressed, dating back to June 2003 when version 00
of the terminology draft was published.

These drafts are entering the BMWG Last Call Process. See
http://www1.ietf.org/mail-archive/web/bmwg/current/msg00846.html
At this time, we are seeking volunteers to complete the
BMWG Last Call Review Template in the message of 4/27/04
titled, "Refinements to the BMWG Last Call Process".
Volunteers should contact acmorton <at> att.com
A copy of the template is available here:
http://home.comcast.net/~acmacm/IDcheck/LastCallTemplate.txt

Whether or not you decide to volunteer for the directed review,
please *read* and express your opinion on whether or not this
Internet-Draft should be given to the Area Directors for
consideration as an Informational RFC.  Send your comments
to this list or acmorton <at> att.com 
sporetsky | 17 Jul 2006 15:46

RE: WG Last Call on Accelerated Stress Benchmarking Drafts

Hi BMWG-ers,

When reviewing these documents, please keep in mind an excellent suggestion
from Scott Bradner that he made following the BMWG meeting in Montreal last
week.  The Instability Conditions as currently explained in the Methodology
are applied simultaneously.  While this is useful because it increases the
probability of measuring degraded performance, it is difficult to identify
which instability condition, or combination of instability conditions,
actually caused the degraded performance.  Scott's suggestion was therefore
to apply instability conditions in serial fashion to facilitate isolation of
performance degradation to a specific instability condition.  The authors
intend in the next revision to add a test case for this.

Scott

-----Original Message-----
From: Al Morton [mailto:acmorton <at> att.com]
Sent: Monday, July 17, 2006 9:31 AM
To: bmwg <at> ietf.org
Subject: [bmwg] WG Last Call on Accelerated Stress Benchmarking Drafts

BMWG:

A WG Last Call period for the Internet-Drafts on

Terminology for Accelerated Stress Benchmarking
Methodology Guidelines for Accelerated Stress Benchmarking

will be open from 17 July 2006 through 28 August 2006 (6 weeks).

URLs for these Internet-Drafts are:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-acc-bench-term-09.txt
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-acc-bench-meth-05.txt

These versions incorporate comments resulting from implementation.
The authors believe that all comments from the working group
have been addressed, dating back to June 2003 when version 00
of the terminology draft was published.

These drafts are entering the BMWG Last Call Process. See
http://www1.ietf.org/mail-archive/web/bmwg/current/msg00846.html
At this time, we are seeking volunteers to complete the
BMWG Last Call Review Template in the message of 4/27/04
titled, "Refinements to the BMWG Last Call Process".
Volunteers should contact acmorton <at> att.com
A copy of the template is available here:
http://home.comcast.net/~acmacm/IDcheck/LastCallTemplate.txt

Whether or not you decide to volunteer for the directed review,
please *read* and express your opinion on whether or not this
Internet-Draft should be given to the Area Directors for
consideration as an Informational RFC.  Send your comments
to this list or acmorton <at> att.com 

_______________________________________________
bmwg mailing list
bmwg <at> ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg
Al Morton | 17 Jul 2006 23:09
Picon
Favicon

Draft Minutes from BMWG <at> IETF-66

BMWG:

Thanks to a truly expert contribution by our note-taker
Tim Alexander, we already have minutes from our session
posted on the meeting materials site:
https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=66

Comments or requests for clarification are welcome now through
August 11, 2006.  In particular:

- if you think some critical detail was left out of the summary,
   please indicate it.

- if you volunteered to review a document (and your name isn't listed),
   let me know.

Also note that our new Supplementary web page is available now:
http://home.comcast.net/~acmacm/BMWG/
and any suggestions on this material are welcome.

Al
bmwg co-chair
sporetsky | 17 Jul 2006 23:32

RE: Draft Minutes from BMWG <at> IETF-66

Great job Tom!

-----Original Message-----
From: Al Morton [mailto:acmorton <at> att.com]
Sent: Monday, July 17, 2006 5:10 PM
To: bmwg <at> ietf.org
Subject: [bmwg] Draft Minutes from BMWG  <at>  IETF-66

BMWG:

Thanks to a truly expert contribution by our note-taker
Tim Alexander, we already have minutes from our session
posted on the meeting materials site:
https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=66

Comments or requests for clarification are welcome now through
August 11, 2006.  In particular:

- if you think some critical detail was left out of the summary,
   please indicate it.

- if you volunteered to review a document (and your name isn't listed),
   let me know.

Also note that our new Supplementary web page is available now:
http://home.comcast.net/~acmacm/BMWG/
and any suggestions on this material are welcome.

Al
bmwg co-chair

_______________________________________________
bmwg mailing list
bmwg <at> ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg
Romascanu, Dan (Dan | 19 Jul 2006 00:01
Favicon

SIP Performance Metrics


I am cross-posting the bmwg and sipping wg lists on purpose.   

There seem to be quite a lot of commonality between the following
Internet-Drafts:

-
http://www.ietf.org/internet-drafts/draft-malas-performance-metrics-03.t
xt
-
http://www.ietf.org/internet-drafts/draft-poretsky-sip-bench-term-01.txt

It would be nice if the authors of the two drafts would work together to
make sure that SIP performance metrics are being defined in one place
(in the IETF at least) and the same definitions are being used for SIP
performance measurement and benchmarking.

Regards,

Dan
Daryl Malas | 19 Jul 2006 00:11

Re: SIP Performance Metrics

This communication and work is taking place to make sure the efforts are
complimentary (and relative to the specific working groups) and do not
overlap.  The differences were discussed in Montreal, but to recap...the
work in Sipping is end-to-end and the work in BMWG is single DUT.

Thanks..--Daryl

On Wed, 2006-07-19 at 01:01 +0300, Romascanu, Dan (Dan) wrote:
> I am cross-posting the bmwg and sipping wg lists on purpose.   
> 
> There seem to be quite a lot of commonality between the following
> Internet-Drafts:
> 
> -
> http://www.ietf.org/internet-drafts/draft-malas-performance-metrics-03.t
> xt
> -
> http://www.ietf.org/internet-drafts/draft-poretsky-sip-bench-term-01.txt
>  
> It would be nice if the authors of the two drafts would work together to
> make sure that SIP performance metrics are being defined in one place
> (in the IETF at least) and the same definitions are being used for SIP
> performance measurement and benchmarking.
> 
> Regards,
> 
> Dan
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors <at> cs.columbia.edu for questions on current sip
> Use sip <at> ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sip <at> ietf.org for new developments of core SIP


Gmane