somnath.chatterjee01 at gmail.com
Wed Mar 21 04:41:29 PDT 2012
1>In Section 4.1.1 two statements can be found which is ambiguous.
In first paragraph
"The M bit MUST be zero."
and in sixth paragraph
"The M bit MUST be zero for a known unicast ping."
I think the ping tool should not be limited to unicast use only and
should be allowed to be sent on distribution tree when used for
multidestination frames/unknown unicast. It would be good to include
excerpts from draft-yizhou-trill-multi-destination-ping in this OAM
draft which talks about multi-destination ping, jitters etc.
2> It would be good if RBridges that implement TRILL- OAM does not
decrement Hop count by more than one for OAM/Channel messages only.
This would help us limiting the max hop count used for traceroute to
be equal to the diameter of the campus.
3> If my understanding is correct there is no way to distinguish
between pings reply and unicast traceroute reply(other than the error
replies). An user may use both the tool concurrently or with minimal
time gap. As such it would be hard to distinguish between the replies
only with sequence number. I would suggest to use some unique
identifier to differentiate between the two types of messages.
4> In Section 22.214.171.124
". . . various forms of ECMP hashing based on fields such as MAC
addresses, IP addresses, and/or TCP/UDP port numbers."
Vlans may be added to the fields list.
5> In Section 126.96.36.199
Editorial changes for "One cannot use the diemater of the network . .
." should be replaced by
"One cannot use the diameter of the network/campus"
More information about the rbridge