Dear Samita
I went over the draft and gladly find many similarities with 'IPv6
over 802.16' work. For example, an Access Router in PAN (PAN
coordinator) has the complete list of all the (link-local) addresses
on the link' and WiMAX AR (ASN GW) is also an omniscient AR. It seems
that we think along the similar line.
Kindly find my in-line comments.
Sec 3.
2. When the host initializes its network it multicasts one or a few
Neighbor Solicitation messages to the all-router IPv6 multicast
Typo. sub/ Neighbor/ Router.
Sec 5.1.
The lowpan nodes MUST include a Sender Link-layer Address option in
the Router Solicitation, since this then allows the router to unicast
a Router Advertisement in response.
The above is possible only after DAD is completed, which results in
delay. How about including 'Tentative Option' instead?
Since every host sends a RS when it attaches to the PAN and there is
a single router for the PAN (the PAN co-ordinator), this router will
observe the arrival of all the IPv6 link local addresses
This may not be so. Allow me an example. When a host attaches to a
network, while performing DAD, it may receive an unsolicited
(periodic) RA. Then the host would not send an RS. Also the host may
generate a new (link-local) address while staying at the same link for
the privacy reason. Then it would simply configure a new address
without sending an RS.
How about monitoring the incoming DAD NS to generate the list instead?
That's the approach WiMAX takes right now.
Sec 5.2.
Firstly, it might very well be possible to increase the default time
significantly as long as the hosts can use some other mechanism to
detect when the router (the PAN co-ordinator) disappears.
We also try to increase the maximum of MaxRtrAdvInterval.
Sec 7.
Should nodes in LowPan network use duplicate address
detection Avoiding duplicate address detection will save broadcast
signaling in the PAN-since 802.15.4 does not have multicast
capabilities.
I have difficulty understanding the above. Kindly clarify.
Sec 11
It is assumed that the node knows the router's IPv6 address on the
link.
Usually this is not possible for 802.16/ WiMAX.
The node sends a Router Solicitation message directly to the
router's link-local address.
In WiMAX, the node sends an RS with all-router multicast destination
address. However, WiMAX specific forwarding mechanism ensures that the
RS is delivered to the AR in unicast.
This RS message MUST carry sender's
link-layer address (SLLA) option.
If the RS is sent before completing DAD, it can't carry SLAA. In that
case it may carry Tentative Option.
The
default periodic interval should be set by the link-layer technology
specific requirements.
In WiMAX, it may not be efficient to send RA every 30 mins (current
Max MaxRtrAdvInt) I learned that, in cellular environments, mobile
stations remain idle for the majority of time. (Even it's not
unthinkable to spend more than 90% of time in idling mode
contemplating my own cellular phone usage.) So WiMAX developers are
not happy at the prospect of having to page and awaken 90% of dormant
nodes for every 30 mins.
This causes the router
to both forward the packet to the target and send a Redirect message
back to the sender. The redirect can include the L2 address for the
target,
In WiMAX, the router would not send a Redirect message. Usually L2
address is not used for data forwarding inside a link. In WiMAX, an MS
has only an AR, a default router, as its on-link neighbor.
The router
sends router redirects for the target on-link IP address to the
sender node A. The router redirect carries the target link-layer
address option.
As I wrote the above, an MS has only its AR as its on-link neighbor in
its Neighbor Cache. So I don't think it's necessary for AR to relay an
address resolution query.
I wish the above helps.
Thanks for your kind consideration.
Best Regards
JinHyeock
_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan
