<div dir="ltr"><div dir="ltr"><div>Interesting, indeed. It reminds me of my primary school times. We had fun going through the colour spectrum.</div><div><br></div><div>I am not a communication specialist, but I bet I am not the only one who didn't go through the torture of reading this from begin to end.<br></div><div><br></div><div>Boubakar</div><div><br></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 26, 2019 at 10:19 AM Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">Interesting… I found the format much more useful than previous reports. I like having direct links to the proposal pages inline and I find the color-coded outcomes quite useful for getting good data about the status of things at a quick glance.<div><br></div><div>Can you provide more specific objections or suggestions as to how you would like the format improved?</div><div><br></div><div>Owen</div><div><br><div><br><blockquote type="cite"><div>On Jun 25, 2019, at 03:14 , Boubakar Barry <<a href="mailto:boubakarbarry@gmail.com" target="_blank">boubakarbarry@gmail.com</a>> wrote:</div><br class="gmail-m_8192700445744735712Apple-interchange-newline"><div><div dir="ltr"><div dir="ltr"><div>Could these posts be more "friendly" in term of format? Not very appealing to me. I am having challenges reading this.</div><div><br></div><div>Boubakar</div><div><br></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 25, 2019 at 10:07 AM Moses Serugo <<a href="mailto:moses.serugo@gmail.com" target="_blank">moses.serugo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="color:rgb(0,0,153)"><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><span style="line-height:107%;color:rgb(117,117,117);background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial"><font face="arial, sans-serif">Dear PDWG members,</font></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><font face="arial, sans-serif"><span style="line-height:107%;color:rgb(117,117,117);background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial">Consequent to the discussions by the
PDWG community present at AFRINIC-30 during the Public Policy Meeting held on 19th June 2019 in Kampala Uganda, the following two policy proposals below have been
moved to “</span><span class="gmail-m_8192700445744735712gmail-m_5681044266777864703gmail-highlight"><b><span style="line-height:107%;color:rgb(117,117,117);background:rgb(255,255,204) none repeat scroll 0% 0%"><span rel="Last" style="box-sizing:border-box">Last</span></span></b></span><span style="line-height:107%;color:rgb(117,117,117);background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial"> </span><span class="gmail-m_8192700445744735712gmail-m_5681044266777864703gmail-highlight"><b><span style="line-height:107%;color:rgb(117,117,117);background:rgb(255,255,204) none repeat scroll 0% 0%"><span rel="Call" style="box-sizing:border-box">Call</span></span></b></span><span style="line-height:107%;color:rgb(117,117,117);background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial">”, starting today
25th June 2019.</span></font></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><font face="arial, sans-serif"><b>A) IPv6 PI Update (AFPUB-2018-V6-004) currently
CPM 6.8.2(v)</b></font></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><font face="arial, sans-serif"><b>B) AFPUB-2018-v4-001-DRAFT-01 (SL Update)</b><br></font></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><font face="arial, sans-serif"><br></font></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><font face="arial, sans-serif"><u><b>Decisions on policy proposals
discussed during the meeting</b><br></u></font></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><b style="font-family:arial,sans-serif"><br></b></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%"><b style="font-family:arial,sans-serif">AFRINIC Policy Development Process – bis</b><br></p><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:red">Back to list for
further discussion and refinement</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://www.afrinic.net/policy/proposals/2017-gen-002-d5" style="color:blue" target="_blank"><b>https://www.afrinic.net/policy/proposals/2017-gen-002-d5#proposal</b></a></font></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif">This proposal is a major
revision of the current Policy Development Process. Major highlights include:</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal">
</span>A clearer
mechanism for appeals and disputes.</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal">
</span>Introduction of
distinct phases in the policy proposal life cycle.</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal">
</span>More transparency
around consensus-gauging.</font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://afrinic.net/en/community/policy-development/policy-proposals/2313-ipv6-policy-and-references-update" style="color:blue" target="_blank"><b>Abuse</b></a><b>
Contact Policy Update</b></font></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:red">Back to list for
further discussion and refinement</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://afrinic.net/policy/2018-gen-001-d2" style="color:blue" target="_blank">https://afrinic.net/policy/2018-gen-001-d2</a></font></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif">Updates CPM 8.0 (Abuse Contact
Information) with the following key amendments: </font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal">
</span>Introduction of a
mandatory “abuse-c” attribute into inetnum, inet6num and aut-num whois database
objects for resources directly issued by AFRINIC. The value of this attribute
is an “abuse-mailbox”, which must be a valid e-mail address. </font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal">
</span>A mechanism is
proposed to validate the “abuse-mailbox” and report/escalate invalid or those
that are unresponsive.</font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Provisions for Resource Hijacking</font></b></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:red">Back to list for
further discussion and refinement</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://www.afrinic.net/policy/proposals/provisions-for-resource-hijacking" style="color:blue" target="_blank">https://www.afrinic.net/policy/proposals/provisions-for-resource-hijacking</a></font></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif">The proposal provides a
framework for recognizing that IP address hijacks are a policy violation within
the AFRINIC service region. A method to identify and report hijacks is proposed
and a pool of experts chosen from the community is instituted to investigate each reported case.</font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">IPv4 Inter-RIR Legacy Resource Transfers</font></b></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:red">Back to list for
further discussion and refinement</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://www.afrinic.net/policy/proposals/2019-v4-001-d1" style="color:blue" target="_blank">https://www.afrinic.net/policy/proposals/2019-v4-001-d1#proposal</a></font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>Establishes a
mechanism to allow transfers of <b>legacy</b> IPv4 space to/from other regions.
The intent is to align AFRINIC with an IPv4 address market that already exists
for which AFRICA is not currently part.</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>The author
fronted two Inter-RIR proposals with hope to withdraw one if the other passes
through. </font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><a href="https://www.afrinic.net/policy/proposals/2019-v4-002-d1" style="color:blue" target="_blank"><b><font face="arial, sans-serif">IPv4
Inter-RIR Resource Transfers (Comprehensive Scope)</font></b></a></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:red">Back to list for
further discussion and refinement</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://www.afrinic.net/policy/proposals/2019-v4-002-d1" style="color:blue" target="_blank"><b>https://www.afrinic.net/policy/proposals/2019-v4-002-d1</b></a></font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>Allows
establishing a mechanism to allow transfers of IPv4 space to/from other
regions. The intent is to align AFRINIC with an IPv4 address market that
already exists for which AFRICA is not currently part.</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>The author
fronted two Inter-RIR proposals with hope to withdraw one if the other passes
through. </font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font><span style="font-family:arial,sans-serif"> </span></p><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">IPv6 PI Clarification</font></b></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:rgb(0,176,80)">Last Call</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://www.afrinic.net/policy/proposals/2019-v6-001-d2" style="color:blue" target="_blank"><b>https://www.afrinic.net/policy/proposals/2019-v6-001-d2#proposal</b></a></font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal">
</span>Amends original
policy proposal “IPv6 PI Update” (AFPUB-2018-V6-004) currently CPM 6.8.2(v),
which requires that IPv6 PI space should be announced within 12 months of
getting it, and should not be disaggregated.</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal">
</span>This proposal
does not make it mandatory to announce the space, since there is no RFC1918
equivalent for IPv4, and cases like IXP peering LAN space doesn’t necessarily
have to be announced. If announced however, the condition to disaggregate it is
still in place. </font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">SL Update</font></b></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:rgb(0,176,80)">Last Call</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://afrinic.net/policy/proposals/2018-v4-001" style="color:blue" target="_blank"><b>https://afrinic.net/policy/proposals/2018-v4-001</b></a><b></b></font></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif">Proposes an update to CPM
5.4.7.2 which removes the Board’s power to replenish the (exhaustion) pool with
any IPv4 space available at the time (such as the /12 reserve in 5.4.7.1). The proposal also stipulates that the same
/12, if still unused by the time phase 2 space is exhausted, be automatically</font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font><b><font face="arial, sans-serif">Multihoming not required for ASN</font></b></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:red">Back to list for further
discussion and refinement</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://www.afrinic.net/policy/proposals/2019-asn-001-d2" style="color:blue" target="_blank"><b>https://www.afrinic.net/policy/proposals/2019-asn-001-d2</b></a></font></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif">Modifies CPM 7.4 by removing
7.4.2, a clause requiring requestors of ASNs to be multihomed (or demonstrate
plan thereof). Instead, the proposal sets the following criteria:</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>A unique routing
policy or</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>Interconnection
with one or more other ASNs which requires a globally unique ASN.</font></div><div style="margin:0in 0in 0.0001pt 0.5in"><font face="arial, sans-serif">•<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>An organization
will also be eligible if it can demonstrate that it will meet any of the above
criteria upon receiving an ASN (or within the following six months).</font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Internet Number Resources Review by AFRINIC</font></b></div><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Decision: <span style="color:red">Back to list for
further discussion and refinement</span></font></b></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"><a href="https://www.afrinic.net/policy/proposals/2016-gen-001-d8" style="color:blue" target="_blank"><b>https://www.afrinic.net/policy/proposals/2016-gen-001-d8</b></a></font></div><div style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif">The proposal introduces a
mechanism for AFRINIC to conduct reviews (or audits) for IPv4 number resources
issued to members, and recommends reclamation of resources that are found to be
in breach or not in compliance. </font></div><p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font face="arial, sans-serif"> </font></p><div style="margin:0in 0in 0.0001pt"><b><font face="arial, sans-serif">Clarification on temporary resource usage</font></b></div><div style="margin:0in 0in 8pt;line-height:107%">
<br class="gmail-m_8192700445744735712webkit-block-placeholder"></div><div style="margin:0in 0in 0.0001pt"><b><i><span style="color:rgb(196,89,17)"><font face="arial, sans-serif">This
proposal was withdrawn by authors just before it was discussed</font></span></i></b></div></div><div><div dir="ltr" class="gmail-m_8192700445744735712gmail-m_5681044266777864703gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div>Thanks & Regards,<br><br><b>Moses Serugo</b><br>PDWG Chair - AFRINIC<br>Tel: +256772212481<br>Email: <a href="mailto:moses.serugo@gmail.com" target="_blank">moses.serugo@gmail.com</a><br><br></div></div></div></div></div></div>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div></div>
_______________________________________________<br>RPD mailing list<br><a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br><a href="https://lists.afrinic.net/mailman/listinfo/rpd" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br></div></blockquote></div><br></div></div></blockquote></div></div>