Thomas, Totally agree. Around the day I published our document, I contacted the Chairs of 6man and also contacted a v6ops Chair to discuss resolving the two documents. I and Wes would have totally worked with Rajiv to resolve the two documents issue. However, during last week Rajiv was out on PTO and this week he is away too. That is why closing the issue has taken time. The draft-asati-01 does not have a workable solution yet. See
http://www.ietf.org/mail-archive/web/ipv6/current/msg14828.html The email in the URL above also proposes a path moving forward for one document in 6man. See other questions asked of the draft-asati that haven't been closed yet. http://www.ietf.org/mail-archive/web/v6ops/current/msg10411.html That is why we wrote our document because we need a solution ASAP for broadband network DAD loop back issues. Hemant -----Original Message----- From: Thomas Narten [mailto:nar...@us.ibm.com] Sent: Tuesday, October 18, 2011 6:15 AM To: Hemant Singh (shemant) Cc: Tassos Chatzithomaoglou; IPv6 WG Mailing List Subject: Re: FW: New Version Notification for draft-hsingh-6man-enhanced-dad-01.txt The WG should produce one single document, not two. This is pretty simple stuff here and we don't need 2 documents, each only 5 pages long. Indeed, I think it's sort of unfortunate that we have started out with two competing documents, for no good reason that I can see. Its not like the proposed approaches are different. Per previous mailing list discussion, the problem and solution are pretty straightforward. Let's ensure that one document gets published quickly. Thomas -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
