I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Please wait for direction from your document shepherd
or AD before posting a new version of the draft.
Document: draft-ietf-bmwg-protection-meth-12.txt
Methodology for benchmarking MPLS protection mechanisms
Reviewer: Joel M. Halpern
Review Date: 12-November-2012
IETF LC End Date: 20-March-2012
IESG Telechat date: 15-November-2012
Summary: This document is almost ready for publication as an
Informational RFC.
This reviewer notes with thanks that a number of his concerns from the
March review have been well-addressed.
Major Comments:
Section 5.7 is still internally inconsistent. It says that "It is
suggested that there be three or more traffic streams..." in the first
paragraph. The second paragraph then begins "At least 16 flows should
be used, ..." I have compared the definitions in RFC 4689, and I can
not see how 3 streams (A group of packets treated as a single entity by
the traffic receiver) can be 16 flows (one or more packets sharing a
common intended pair of ingress and egress interfaces.) I suspect that
the issue is what traffic receiver is intended. Is the intent that
there be at least 3 LSPs with 16 or more flows running through them?
Minor Comments:
In section 5.1 "some" failure events are listed. It is unclear whether
this list is the ones to be tested for, or just "some" events. I think
it is intended to be comprehensive, so why "some".
I presume that the use of the term Layer2 VC in section 6 is intended to
refer to a pt-to-pt layer2 VPN component. Is there an existing document
where that term is used that way? Could it be referenced?
For that matter, since the number of labels is the same in the Layer3
cases and the Layer2 cases, could the Layer2 cases be omitted without
loss of generality?
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
