Dear Authors and All, I read through the document and have some comments:
1) If the correspondent node has only AAAA record, the communicate will fail (especially for the gateway based architecture). The document does not provide any mechanisms to handle this error. 2) Even if the correspondent node has both AAAA and A record, getaddrinfo() will prefer AAAA record (according to RFC3484 default rule). The communication fails again? 3) Another important scenario that this document is unable to support is the host to host communication. If the host is assigned the shared address, DNS response will return an overlapping IPv4 address, and communication will fail. I think many parts of the document need clarification regarding to these questions, so I do not think the document is fine enough. Thanks, Zhen China Mobile On Thu, Feb 4, 2010 at 1:04 AM, David Ward <[email protected]> wrote: > All - > > I'd like to start the WG LC on the draft "Dual-stack lite broadband > deployments post IPv4 exhaustion." It can be found here: > > http://tools.ietf.org/html/draft-ietf-softwire-dual-stack-lite-03 > > I call to your attention the significant restructuring of the document and > movement of informational material to appendices and clarifications > throughout. > > The LC will close 2010.02.18 at 1700 PST. Please send all comments to this > thread which includes all authors. > > Many thanks > > -DWard > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires > _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
