On 1/26/2015 5:33 AM, Dearlove, Christopher (UK) wrote:
Joe Touch
Regarding anthropomorphisms to avoid, they include:
detect
reaches
hears
The term you should be using is "can transfer an IP datagram to".
Not the same. If A can hear/detect B, that does not tell you that you
can transfer an IP datagram to. Opposite directions.
OK, to be more precise, "can receive an IP datagram from"
See for
exampleNHDP (RFC 6130), which uses one of those terms.
That doc is defining a routing protocol. You're trying to define a L2
network, AFAICT.
In the case of NHDP, "HEARS" is a routing protocol event when an IP
packet is received. See section 10.1.1 which explains that HELLO
messages occur in IP datagraph. Take that description and use it to
understand the meaning of HEARS, LINK, and SYMMETRIC LINK and you will
end up with the definitions I gave - despite the fact that
unidirectional link and bidirectional link are the common terms for what
that document redefines.
Note also that, strictly interpreted, NHDP creates a topology that might
never forward data packets. HEARS is defined in terms of receiving a
specific kind of IP datagram, rather than IP datagrams in general.
IMO, that's not useful. Even though that doc describes a routing
protocol, it could - and should - have used widely-used terms for it's
particulars.
Charles Perkins
Well, in [manet] we are dealing with routers to establish multihop
connectivity between endpoints.
That's an L2VPN.
A MANET is definitely not an L2VPN.
Agreed. MANETs don't need L3 devices for internal transit. If you don't
either, then why are you not just a MANET?
Joe
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
