Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] Report on AFRINIC-28 Public Policy Meeting

Dewole Ajao dewole at forum.org.ng
Mon Jun 4 13:00:53 UTC 2018



Good day PDWG, 




We apologize for the uncharacteristic delay in sharing this report. 

For the policy proposals that reached last call, individual announcements will follow shortly. 




All policy proposals are at https://afrinic.net/community/policy-development/policy-proposals 




Thank you. 

Dewole Ajao & Sami Salih 

PDWG Co-Chairs 




Please find below the highlights of the AFRINIC-28 Public Policy Meeting held during AIS-18 in Dakar, Senegal on Wednesday May 9, 2018. 

–----------- 

Policy Proposal text discussed: IPv6 Policy & References Update 

ID: AFPUB-2018-V6-001-DRAFT01 

Summary: 

Seeks to delete redundant text, clean up references and clarify the concept of utilization (all in relation to IPv6). 

Session Video starts at: [ https://youtu.be/pWTApl4QHfY?t=6196 |   ] 

[ https://youtu.be/pWTApl4QHfY?t=6196 | https://youtu.be/pWTApl4QHfY?t=6196 ] 

Playlist Video: [ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=f95qT5Np3Mo |   ] 

[ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=f95qT5Np3Mo | https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=f95qT5Np3Mo ] 

Community-proposed text updates: None 

Updated version of proposal text based on community feedback: Not Applicable 

PPM outcome: 

Based on strong PDWG support, absence of opposition, no recommendations to update proposal text, co-chairs moved the policy proposal to last call. 


-------------------- 

Policy Proposal text discussed: Internet Number Resources Review by AFRINIC 

ID: AFPUB-2016-GEN-001-DRAFT06 

Summary: 

Seeks to set out procedures for reviewing Internet Number resources allocated/assigned to AFRINIC members. 

Session video starts at: [ https://youtu.be/pWTApl4QHfY?t=7223 |   ] 

[ https://youtu.be/pWTApl4QHfY?t=7223 | https://youtu.be/pWTApl4QHfY?t=7223 ] 

Playlist video: [ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=l-1jo2d8Qes |   ] 

[ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=l-1jo2d8Qes | https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=l-1jo2d8Qes ] 

Community-proposed text updates: NIL 

Updated version of proposal text based on community feedback: None yet 

PPM outcome: 

Objections include cost concerns, potential for abuse in targeting of companies, questioning the need for such a policy since provisions already exist in AFRINIC documentation for staff to work with, etc. As a result of both strong opposition and strong support for the policy proposal for a variety of reasons expressed online and at the PPM, co-chairs returned the proposal to the rpd list for further discussion and refinement. 

Co-chairs also suggested that the community discuss further to see if there are better ways for AFRINIC to tackle the perceived/observed problem of irresponsible use of (or fraudulent applications for) Internet numbering resources. 


----------- 

Policy Proposal text discussed: Policy Development Process – bis 

ID: AFPUB-2017-GEN-002-DRAFT03 

Summary: 

Changes to the Policy Development Process (PDP) are required to go through the PDP. This proposal seeks to introduce new definitions, guidelines and operational procedures for the PDP. 

Session video starts at: [ https://youtu.be/pWTApl4QHfY?t=16050 |   ] 

[ https://youtu.be/pWTApl4QHfY?t=16050 | https://youtu.be/pWTApl4QHfY?t=16050 ] 

Playlist video: 

[ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=2d9UB9PVuFA | https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=2d9UB9PVuFA ] 

Community-proposed text updates: Not applicable 

Updated version of proposal text based on community feedback: None yet 

PPM outcome: 

Some feedback from the community included removal of absolutes, inclusion of additional definitions, addition of time for co-chairs to make consensus calls, more explicit text to take the contributions on RPD into consideration, addressing the subjectivity (based on individual perspective) of “minor” or “major” issues/objections, co-chairs as editors, CEO as chair, Council of Elders inclusion, allowing anonymous proposers, etc. 


Authors expressed willingness to continue engagement to move the policy proposal forward. As a result of so many areas requiring discussion, co-chairs returned the proposal to the RPD list for further discussion and refinement. 


----------- 

Policy Proposal text discussed: IPv4 Soft Landing - bis 

ID: AFPUB-2016-V4-001-DRAFT07 

Summary: Proposal seeks to replace the current IPv4 soft-landing policy 

Session video starts at: 

[ https://youtu.be/pWTApl4QHfY?t=20130 | https://youtu.be/pWTApl4QHfY?t=20130 ] 

Playlist video: 

[ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=2iN-ipRuYvU | https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=2iN-ipRuYvU ] 

Community-proposed text updates: Not applicable 

Updated version of proposal text based on community feedback: None yet 


PPM outcome: 

Authors requested clarity from the PDWG Appeal Committee on whatever inconsistencies they observed in order to determine the way forward. Opponents of the policy proposal referred authors to their appeal document to view the issues considered “never addressed”. Because there are pending discussions surrounding the policy proposal, co-chairs returned the proposal to the RPD list for further discussion and refinement. 


--------- 

Policy Proposal text discussed: Clarification on IPv6 sub-assignments 

ID: AFPUB-2018-V6-002-DRAFT01 

Summary: IPv6 and indeed IPv4 assignments commonly involve use-cases related to VPNs, point-to-point links and other devices not owned by the resource holder. These use-cases are actually quite common despite being explicitly prohibited by the current policy text. This proposal seeks to clarify by adding text at the bottom of the section that says such genuine instances of sub-assignment are indeed permitted. 




Session video starts at: 

[ https://youtu.be/pWTApl4QHfY?t=20967 | https://youtu.be/pWTApl4QHfY?t=20967 ] 

Playlist video: 

[ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=pdOWMbpOKRw | https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=pdOWMbpOKRw ] 


Community-proposed text updates: 

Updated version of proposal text based on community feedback: 




PPM outcome: 

There was good discussion on the proposal including some in relation to the wording and potential application to cover IPv4. Most of the feedback was positive even though some of it pointed to a lack of understanding of the proposal. As a result of the text-related feedback to which there was no conclusive modification, co-chairs sent the policy proposal back to the rpd mailing list for further discussion and refinement. 


--------- 

Policy Proposal text discussed: IPv6 Initial Allocation Update 

ID: AFPUB-2018-V6-003-DRAFT01 

Summary: 

Proposal seeks to delete redundant text, add text to show services can be provided to entities not explicitly named, add requirement to announce received space within a certain time frame, loosen justification for addressing plans to include the entire size and scope of the organization regardless of whether the infrastructure for it is currently in place, introduce a provision for rectification of size of initial allocations in the cases where the resource holders discover at deployment time that they actually need more IPv6 space than initially allocated. 




Session video starts at: 

[ https://youtu.be/pWTApl4QHfY?t=23949 | https://youtu.be/pWTApl4QHfY?t=23949 ] 

Playlist video: 

[ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=0fvfiIIieis | https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=0fvfiIIieis ] 

Community-proposed text updates: 

Removal of requirement to announce allocated IP address space within a specific time frame. 

Updated version of proposal text based on community feedback: Not yet published 




PPM outcome: 

Staff confirmed that some of the issues raised are already being dealt with in similar manner operationally and welcome the proposed policy text. Contributions included suggestions to use the policy proposal to enforce allocation alignment along nibble boundaries (an option the author chose not to deal with in order not to make the proposal more complex), remove requirements to announce space (an option the author agreed to). 

Based on strong PDWG support, absence of opposition, and consensus to update proposal text, co-chairs moved the policy proposal to last call. 



--------- 

Policy Proposal text discussed: IPv6 PI Update 

ID: AFPUB-2018-V6-004-DRAFT01 


Summary: 

Proposal seeks to simplify the provision of IPv6 address space to end users by decoupling IPv6 from IPv4 assignment qualification requirements, documenting the need to justify subsequent assignments, and introducing clause to allow rectification of assignments in the event that initial assignments are found inadequate at deployment time. 

Session video starts at: 

[ https://youtu.be/pWTApl4QHfY?t=25928 | https://youtu.be/pWTApl4QHfY?t=25928 ] 

Playlist video: 

[ https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=JNyB7vDMCGI | https://www.youtube.com/watch?list=PLLJRUWAm1GCbhFkvJldw4dBeQ6j85H6En&v=JNyB7vDMCGI ] 

Community-proposed text updates: None 

Updated version of proposal text based on community feedback: Not applicable 

PPM outcome: 

Contributions included one (opposed to current version of proposal) which suggested leaving the current requirement to meet same qualifications as IPv4 until IPv6 qualification criteria are defined. In spite of the singular objection, co-chairs moved the policy proposal to last call as there was no movement in the direction of text changes in the proposal. 



Other discussions in the room to continue on RPD 


Staff pointed out that assigned PAs are being registered on AFRINIC WHOIS database in the name of entities that are not in fact customers of the resource holders. Cases in point are actually in the names of organizations outside the AFRINIC region who have complained to AFRINIC because they are not using those resources. To clarify, such WHOIS entries carry the misleading information in the comments fields. As these occurrences are showing up with legacy space holders, the more direct question to the community is “how do we deal with legacy space holders and others putting fraudulent data in our WHOIS?” 


A community member pointed out that staff assessment of policy proposals should be made available at least 4 weeks in advance of the PPM to give authors and the PDWG time to act on the feedback before the PPM. Further clarification from the member seemed to sugges that staff should give their analysis within a week of receiving a new policy proposal. 


A community member suggested that it may be time for another review of the CPM to fix any references that may have broken in the insertion of new sections. It was suggested that staff do the review and present the results before the community for transparent adoption. 


A community member signified intention to propose a policy about abuse-c 


A community member made a call to all present to remember that the PDWG is responsible to all 1 billion African people in the management of the organization AFRINIC and the resources entrusted to it; members were enjoined to be very vigilant to avoid the failure of AFRINIC. 


A community member commented on remote participation and requested that transcripts of chat sessions be added to documentation/archives of PPM. 


A community member made further comments regarding the need for PDWG members to engage better on policy proposals well before the PPM. He reminded that the PPM being on Wednesday gives room for members to meet on Monday and Tuesday probably in sub working-groups for a more fruitful PPM on Wednesday. 


Co-chairs raised the issue of mailing list moderation (esp. Code of conduct violations) and called for volunteers that would like to assist in looking out for violations and moderating the mailing lists. In earlier discussion, it was pointed out that those who feel they are attacked in the course of discussions may contact the co-chairs directly with specific details of what they consider to be personal attacks or other code of conduct violation for necessary action. 




#end 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20180604/772dcda0/attachment-0001.html>


More information about the RPD mailing list