Hi,
δΊ 2011/10/31 13:36, Washam Fan ει:
Hi the authors,
I have 2 comments on this draft so far.
1. Appendix A gives an example how to generate a IPv4-translatable
address delegated to a CPE, but miss the part how a CPE derive a IPv4
prefix, address, or shared address from a given delegated
IPv4-translatable address. At least, I think the s bits can not be
derived without extra provisioning.
The CPE need to get configuration parameters via DHCPv6.
2. It seems to me native IPv6 addresses and IPv4-translatable
addresses share the same prefix. Then how a CPE identify a IPv6 packet
arriving at the WAN-facing interface is a native one or a translated
one?
Since IPv4-translatable address is a /128 inside /64, when the
configuration parameters are given (see above), the routing can guide
the translated packets to the translation API.
xing
Thanks,
washam
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
