Dear Raymond, Colleagues, Thanks for that kind reminder and of course, also a thank you to those who have already submitted comments or approached us with feedback directly. Just to explain where we are, process wise, from the perspective of the RIPE NCC. We have been tracking this work item in ITU Study Group 20 for a while now. People might also still remember our first response to the Liaison we received from the ITU back in 2016, in which we already highlighted the need for this kind of document to be based on operational experience and have it be subject to review by the RIR communities. In a more recent note, following the Liaison that we forwarded to you, which included the draft Recommendation, we have welcomed the Study Group’s decision to accept your invite to come and present at RIPE 76. Further we have committed ourselves to provide a report after this meeting, containing an aggregate of all of the commented received on this list an during the session next week. Once submitted as a reply to the Liaison Statement, we will continue our work in Study Group 20 and follow up in their meetings regarding the input from the RIPE community and how to best reflect that feedback in the ongoing Work Item and the drat Recommendation. As such, we would very much appreciate your collective expertise in reviewing this draft, especially comparing it to existing deployment scenarios and past experience in designing and building IPv6 networks. We are happy to take those comments and feedback back into ITU’s Study Group 20 and the discussions around this draft recommendation. But for the process, it would be beneficial if we can refer to those comments with reference to a public record, such as the archives of this mailing list. In relation to deadlines, the original Liaison mentioned a deadline of 1 June 2018. We still plan on honouring that date and submit a record of the feedback back to ITU no later than May 31st. Regards, Marco Hogewoning -- External Relations - RIPE NCC