[rbridge] Minor issue in draft-touch-trill-rbridge-arch-00a.txt
erik.nordmark at sun.com
Tue Nov 8 16:59:29 PST 2005
| /| \
| / N \
| / \
* * *
* * *
* * *
\ / | \
\ / N N
Figure 3 Reorganized RBridge Ethernet link subnet
Since there might be a hub or bridge between e.g. r4 and r7 that they
can't see (in addition to the hub it could also be a bridge which
doesn't speak BSTP). Thus I think the RBridges must assume that the path
between any pair of them might have nodes/stations attached, just as in
the r7-r9 path.
I think this makes the "inside" vs. "outside" definitions not very
helpful in terms of understanding the toplogy; we have paths between
RBridges which carry encapsulated frames, but for those we also have a
designated forwarder which sends unencapsulated frames out, in order to
handle the r7,r9,b8 type topology above.
For instance, I think an RBridge must treat all its ports as external.
In addition, a port would also be internal when the discovery protocol
finds that there are other RBridges directly reachable over that port.
More information about the rbridge