On 1/22/2015 2:30 PM, Charlie Perkins wrote:
Hello Joe,
We aren't claiming that the effects described in the draft are new.
But they are relevant to IP.
I'm baffled as to how.
The doc starts off on the wrong foot by introducing a new term for
reachability - "detects"? IP doesn't "detect" anything; it communicates
between IP addresses. Either they're reachable or not. Reachability for
L2 subnets is determined by ARP or an emulated equivalent.
And IP doesn't care whether L2 had to forward or store that message as
part of that delivery. It simply is irrelevant to L3.
...
After reviewing PILC, I find that there is not much overlap with our
draft.
If you're expecting the same kind of obscure terminology, there wouldn't be.
What you're describing is an unstable set of unidirectional L2 paths,
and you want to call that an L2 network. It isn't.
I agree that PILC doesn't address unidirectional links, but most of IP
doesn't either. Unidirectional links inhibit most Internet protocols.
So if that's where you're going, it'd help to explain what you hope to
accomplish other than saying "don't try to use most Internet protocols
here".
The word "subnet" does not appear in our document, and that is
intentional. We were motivated to identify effects that really do
matter for multihop communications. Yes, these effects are due to
the characteristics of wireless media below IP, and IP does not need
to change in order to operate properly. But these effects do have an
impact on IP routing, and that was the main motivation for us to
develop the document. I think the effects are far more subtle and
worthy of careful explanation compared to simply unplugging an
Ethernet.
That may be true, but so far all the doc succeeds in describing is a
fundamentally broken L2 IMO. Whether that's what actually happens or
not, it's not very useful to consider it a single anything.
In fact, we do not propose any techniques for dealing with the
problems. Our intended scope is far, far narrower than the broad
scope of PILC.
It would help if you would start by using existing terminology and
explaining what you hope to achieve in this document - IN the draft itself.
Joe
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
