[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OSPF] Questions regarding draft-ietf-ospf-manet-or-00.txt
Abhay,
I have a few more comments that are mostly editorial.
First, I would like to correct my suggested definition of an
overlapping relay to the following:
"An adjacent neighbor is considered an overlapping relay for a
speaker if it has an adjacent neighbor that is not equal to
the speaker itself."
Another possible definition of an overlapping relay (which I think
is used in Boeing's GTNETS code) is:
"A bidirectional neighbor is considered an overlapping relay for a
speaker if it has an adjacent neighbor that is not equal to the
speaker itself."
The existing definition of overlapping relay from Section 3.3.2 is:
"A neighbor is considered an overlapping relay for a speaker if it can
reach a node in the two-hop neighborhood of the neighbor, i.e., if it
has one-hop neighbors."
I think "neighborhood of the neighbor" should be
"neighborhood of the speaker".
Note that the definition of "two-hop neighborhood", i.e., "those
nodes that are neighbors of the speaker's one-hop neighbors", implies
that the speaker can be in its own two-hop neighborhood, which is
why I excluded "the speaker itself" in my suggested definitions.
(However, this probably will not affect flooding operation.)
In Section 3.3.3 (Terminology), the 5th bullet is:
o N2: A subset of 2-hop FULL neighbors excluding the nodes only
reachable by members of N.
I think N2 is the subset of 2-hop FULL neighbors excluding the
1-hop neighbors, i.e., excluding members of N.
However, the 2nd bullet already defines the 2-hop FULL neighbors
to exclude the 1-hop neighbors:
o 2-hop FULL neighbors: The list of 2-hop neighbors of the node that
are FULL and that can be reached from direct neighbors, excluding
any directly connected neighbors.
Richard
_______________________________________________
OSPF mailing list
OSPF at ietf.org
https://www.ietf.org/mailman/listinfo/ospf