It appears to me (maybe others) that some of the basic
assumptions: mesh under or star networks are edge cases,
Geoff, why are you saying this?
mesh under is not an edge case. Mesh under with full, mostly-reliable
subnet-wide multicast *is* an edge case.
If you have a star network, you can run it this way, but why would you
want to wake up all nodes in a DAD?
that meshes
only use broadcast flooding,
Please do show me the mesh that has an efficient mostly-reliable
subnet-wide multicast.
that DAD is necessary,
Ah, good, let's discuss that! If we don't need DAD, we don't need
half of ND.
Leaving things out is always the best way to design things.
However, we wanted to be functionally compatible with ND.
and that RA/RS can't
be made to work on mesh under and route over network,
? We use RA/RS almost unmodified.
that anything more
than RA/RS are necessary are flawed.
?
I agree that finding some optimizations for 4861 would be good. Erik
and
Samita submitted an ID that had some suggestions for ND optimizations
not replacement.
Before we decided to actually start fixing the root of the problem,
this never came to a point where you could say "it works".
I'm not convinced that we need the complexity of white boards, new
ICMP
messages, more messages being transmitted to keep state alive,
turning a
stateless ND protocol into a stateful one.
6LoWPAN-ND is less complex than 4861-ND.
If 4861 won't work as is in a Route Over network (it does on mesh
under),
4861 works on mesh-under only in the fringe case mentioned above.
You still wouldn't *want* to cause all those subnet-wide multicasts.
then we need to find a way to fix it, but that doesn't mean we
have to go to the extreme of inventing something new (whiteboards,
nr/nc, 6AO, 6IO, 6SO, ...) and creating something that is incompatible
with existing infrastructure, devices, and management policies and
techniques.
Geoff, it would really help if you looked into the reasons why these
were "invented".
The actual node complexity goes down a lot with 6LoWPAN-ND.
BTW, management of a 6LoWPAN with no working DAD will be interesting,
to say the least.
Please do indicate what management policies and techniques are part of
the requirements.
Gruesse, Carsten
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
