<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 7, 2020, at 10:52 , Noah <<a href="mailto:noah@neo.co.tz" class="">noah@neo.co.tz</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class=""><br class="">Hey Owen</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><br class=""><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Fri, 7 Feb 2020, 05:20 Owen DeLong, <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word; line-break: after-white-space;" class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Feb 6, 2020, at 06:00 , gregoire.ehoumi via RPD <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer" class="">rpd@afrinic.net</a>> wrote:</div><br class=""><div class=""><div dir="auto" class=""><div dir="auto" class="">Hi Nishal,<br class=""><br class="">I am glad to finally see some conversations on these topics and thanks for your contributions.<br class=""><br class="">The RPD is indeed the appropriate forum to discuss these issues as it is directly related to the management, distribution and usage of the INRs.<br class=""><br class="">Your reaction to the cochairs unbelievable decision on the AS0 ROAs proposal did not go unnoticed and I see you mentioning AS0 ROA as one of the solution to the problem being discussed here, as relates to continued routing of<span class="Apple-converted-space"> </span><b class="">hijacked prefixes</b><span class="Apple-converted-space"> </span>as bogons.<br class=""><br class="">How could one understand the Co-Chairs decision about the AS0 ROA in this context without giving the impression that the rot has set in and that there seems to exist some cover-up game going on?<br class=""></div></div></div></blockquote><div class=""><br class=""></div>While I don’t entirely agree with the Co-Chairs determination on this item, I will say that there was some appearance of controversy within the community over the proposal and I think their conclusion is arguably legitimate.</div></div></blockquote></div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Could you spell out the said controversy. I have gone through the archives and I have watched the PPM videos and dont see nothing.</div></div></div></blockquote><div><br class=""></div>There was one commenter who appeared to feel that there was insufficient time between the withdrawal of an AS0 ROA and the issuance of addresses to a registrant.</div><div><br class=""></div><div>There were some other commenters who had objections that I don’t recall the details, but didn’t really seem to reflect an understanding of what an AS0 ROA for space not issued by the RIR would do or didn’t understand that these AS0 ROAs would only be issued for space that was not issued to a registrant, but was under control of AfriNIC itself. As such, I confess I didn’t try to keep a strong memory of the details of the objections as I considered them non-relevant.</div><div><br class=""><blockquote type="cite" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div dir="auto" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word; line-break: after-white-space;" class=""><div class="">The co-chairs aren’t there to pass value judgment on the merits of the proposal. They are there to guide and moderate the discussion, help the community explore the issues, help the authors develop well written implementable policy, and ultimately to decide whether the community has come to consensus in favor of the proposed policy.</div></div></blockquote></div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">The co-chairs would do the working group some service if they came out to specifically clarify their controversial conclusion on this proposal.</div></div></blockquote><div><br class=""></div>Agreed. My point is that they should not express support or opposition to the proposal itself or an opinion as to whether the proposal is “a good idea” or “a gift from the bad-idea fairy”.</div><div><br class=""></div><div>Owen</div><div><br class=""></div></body></html>