Dear Lorezon， Many Thanks for your reviewer comments! Please see the replies below and the attached draft revision version.
Best Regards,
Jun Bi
Comments from Lorenzo Colitti
I skimmed the draft. It looks well-written, and it addresses an important
problem which I think is probably solved in (different?) proprietary ways on
various implementations in the field today. I'm not very familiar with the AD
sponsorship process, so not sure what the has to happen from a process
perspective. But I think the document requires further review, especially given
that it's making statements about very widely-deployed scenarios (IPv6 over
wifi). Should the document be adopted by a WG such as 6man or v6ops? If not, it
should definitely be reviewed by those WGs.
As a concrete example, here are some things that need to be resolved before the
document advances:
1. The proposed scheme relies on DAD packets to create mapping entries. That
means that if a DAD packet is lost (which can happen even though 802.11 employs
retransmissions at L2), a station could have an IPv6 address that doesn't work
with no indication that it's not working. This is basically a non-recoverable
outage. Perhaps the document should specify another solution instead, e.g., it
could say that mapping entries could be created when a wired station receives a
solicited NA response from a wireless station.
Reply:
Thank you very much for your comment. We’ve already discussed about this
issue in Section 3.3:
Data packets MAY also trigger the establishment of new IP-MAC binding
entries. Data packet with non-bound source IP address with a limited
rate is collected to handle DAD message loss in SLAAC procedure,
which can be quite frequent in wireless network. The detail of the
procedure is specified in Section 4.
And we also have related security discussions in Section 7.1.
2. The document says that the lifetime of SLAAC addresses is the address
lifetime, but the network has no way of knowing what the address lifetime is
because it depends on which RA(s) the host has received.
Reply:
As we already discussed in Section 3.1.1 and 3.3, the binding entries come
from DHCP/ND snooping which is the same as that in wired network specified in
RFC6620 and RFC7513. Thus the lifetime of SLAAC addresses are learnt by
snooping RA messages sent to hosts.
draft-bi-savi-wlan-16.txt
Description: Binary data
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
