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

[rpd] Last Call | Decisions on policy proposals discussed during the meeting

Owen DeLong owen at delong.com
Wed Jun 26 10:22:39 UTC 2019


+1

Owen


> On Jun 25, 2019, at 04:28 , Frank Habicht <geier at geier.ne.tz> wrote:
> 
> I agree.
> Frank
> 
> On 25/06/2019 13:42, JORDI PALET MARTINEZ via RPD wrote:
>> In my opinion, it should be clearly defined up-front. Otherwise “legally
>> speaking”, it creates “procedural indefension”.
>> 
>>  
>> 
>> Both, people supporting and people objecting to any policy proposal must
>> know “a priori” the terms.
>> 
>>  
>> 
>> Regards,
>> 
>> Jordi
>> 
>> @jordipalet
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> El 25/6/19 12:38, "Moses Serugo" <moses.serugo at gmail.com
>> <mailto:moses.serugo at gmail.com <mailto:moses.serugo at gmail.com>>> escribió:
>> 
>>  
>> 
>> Hello Jordi,
>> 
>>  
>> 
>> The last call period is at least two weeks from today but can be any
>> maximum based of feedback received and reactions from the community.
>> 
>>  
>> 
>> Regards,
>> 
>> Moses
>> 
>>  
>> 
>> On Tue, Jun 25, 2019, 1:26 PM JORDI PALET MARTINEZ
>> <jordi.palet at consulintel.es <mailto:jordi.palet at consulintel.es> <mailto:jordi.palet at consulintel.es <mailto:jordi.palet at consulintel.es>>> wrote:
>> 
>>    Hi Moses,
>> 
>>     
>> 
>>    Thanks a lot for your quick reaction on this and for the good
>>    summary to the community.
>> 
>>     
>> 
>>    One clarification that is needed from your side, if you don’t mind.
>> 
>>     
>> 
>>    For the two policy proposals that reached consensus and had started
>>    the last-call period today, is it a default/minimum two-weeks ?
>> 
>>     
>> 
>>    My opinion is tha two-weeks is sufficient considering that in both
>>    proposals, neither in the list or in the meeting, there was any
>>    opossition (if I recall correctly), but it is neccesary to clearly
>>    state it in the “last-call” announcement from a procedural point of
>>    view.
>> 
>>     
>> 
>>    Regards,
>> 
>>    Jordi
>> 
>>    @jordipalet
>> 
>>     
>> 
>>     
>> 
>>     
>> 
>>    El 25/6/19 12:10, "Moses Serugo" <moses.serugo at gmail.com <mailto:moses.serugo at gmail.com>
>>    <mailto:moses.serugo at gmail.com <mailto:moses.serugo at gmail.com>>> escribió:
>> 
>>     
>> 
>>    Dear PDWG members,
>> 
>>    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 “*Last* *Call*”, starting today 25th June 2019.
>> 
>>    *A) IPv6 PI Update (AFPUB-2018-V6-004) currently CPM 6.8.2(v)*
>> 
>>    *B) AFPUB-2018-v4-001-DRAFT-01 (SL Update)*
>> 
>>     
>> 
>>    *_Decisions on policy proposals discussed during the meeting_*
>> 
>>     
>> 
>>    *AFRINIC Policy Development Process – bis*
>> 
>>    *Decision:  **Back to list for further discussion and refinement*
>> 
>>    *https://www.afrinic.net/policy/proposals/2017-gen-002-d5#proposal* <https://www.afrinic.net/policy/proposals/2017-gen-002-d5#proposal*>
>>    <https://www.afrinic.net/policy/proposals/2017-gen-002-d5 <https://www.afrinic.net/policy/proposals/2017-gen-002-d5>>
>> 
>>    This proposal is a major revision of the current Policy Development
>>    Process. Major highlights include:
>> 
>>    •       A clearer mechanism for appeals and disputes.
>> 
>>    •       Introduction of distinct phases in the policy proposal life
>>    cycle.
>> 
>>    •       More transparency around consensus-gauging.
>> 
>>     
>> 
>>     
>> 
>>    *Abuse*
>>    <https://afrinic.net/en/community/policy-development/policy-proposals/2313-ipv6-policy-and-references-update <https://afrinic.net/en/community/policy-development/policy-proposals/2313-ipv6-policy-and-references-update>>*Contact
>>    Policy Update*
>> 
>>    *Decision:  **Back to list for further discussion and refinement*
>> 
>>    https://afrinic.net/policy/2018-gen-001-d2 <https://afrinic.net/policy/2018-gen-001-d2>
>> 
>>    Updates CPM 8.0 (Abuse Contact Information) with the following key
>>    amendments: 
>> 
>>    •       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.
>> 
>>    •       A mechanism is proposed to validate the “abuse-mailbox” and
>>    report/escalate invalid or those that are unresponsive.
>> 
>>     
>> 
>>     
>> 
>>    *Provisions for Resource Hijacking*
>> 
>>    *Decision:  **Back to list for further discussion and refinement*
>> 
>>    https://www.afrinic.net/policy/proposals/provisions-for-resource-hijacking <https://www.afrinic.net/policy/proposals/provisions-for-resource-hijacking>
>> 
>>    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.
>> 
>>     
>> 
>>     
>> 
>>    *IPv4 Inter-RIR Legacy Resource Transfers*
>> 
>>    *Decision:  **Back to list for further discussion and refinement*
>> 
>>    https://www.afrinic.net/policy/proposals/2019-v4-001-d1#proposal <https://www.afrinic.net/policy/proposals/2019-v4-001-d1#proposal>
>>    <https://www.afrinic.net/policy/proposals/2019-v4-001-d1 <https://www.afrinic.net/policy/proposals/2019-v4-001-d1>>
>> 
>>    •  Establishes a mechanism to allow transfers of *legacy* 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.
>> 
>>    •   The author fronted two Inter-RIR proposals with hope to withdraw
>>    one if the other passes through.
>> 
>>     
>> 
>>     
>> 
>>    *IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)*
>>    <https://www.afrinic.net/policy/proposals/2019-v4-002-d1 <https://www.afrinic.net/policy/proposals/2019-v4-002-d1>>
>> 
>>    *Decision:  **Back to list for further discussion and refinement*
>> 
>>    *https://www.afrinic.net/policy/proposals/2019-v4-002-d1* <https://www.afrinic.net/policy/proposals/2019-v4-002-d1*>
>> 
>>    •   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.
>> 
>>    •  The author fronted two Inter-RIR proposals with hope to withdraw
>>    one if the other passes through.
>> 
>>      
>> 
>>    *IPv6 PI Clarification*
>> 
>>    *Decision:  **Last Call*
>> 
>>    *https://www.afrinic.net/policy/proposals/2019-v6-001-d2#proposal* <https://www.afrinic.net/policy/proposals/2019-v6-001-d2#proposal*>
>>    <https://www.afrinic.net/policy/proposals/2019-v6-001-d2 <https://www.afrinic.net/policy/proposals/2019-v6-001-d2>>
>> 
>>    •       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.
>> 
>>    •       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.
>> 
>>     
>> 
>>    *SL Update*
>> 
>>    *Decision:  **Last Call*
>> 
>>    *https://afrinic.net/policy/proposals/2018-v4-001* <https://afrinic.net/policy/proposals/2018-v4-001*>
>> 
>>    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
>> 
>>     
>> 
>>     *Multihoming not required for ASN*
>> 
>>    *Decision:  **Back to list for further discussion and refinement*
>> 
>>    *https://www.afrinic.net/policy/proposals/2019-asn-001-d2* <https://www.afrinic.net/policy/proposals/2019-asn-001-d2*>
>> 
>>    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:
>> 
>>    •   A unique routing policy or
>> 
>>    •   Interconnection with one or more other ASNs which requires a
>>    globally unique ASN.
>> 
>>    •  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).
>> 
>>     
>> 
>>     
>> 
>>    *Internet Number Resources Review by AFRINIC*
>> 
>>    *Decision:  **Back to list for further discussion and refinement*
>> 
>>    *https://www.afrinic.net/policy/proposals/2016-gen-001-d8* <https://www.afrinic.net/policy/proposals/2016-gen-001-d8*>
>> 
>>    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.
>> 
>>     
>> 
>>    *Clarification on temporary resource usage*
>> 
>>    */This proposal was withdrawn by authors just before it was discussed/*
>> 
>>     
>> 
>>    Thanks & Regards,
>> 
>>    *Moses Serugo*
>>    PDWG Chair - AFRINIC
>>    Tel: +256772212481
>>    Email: moses.serugo at gmail.com <mailto:moses.serugo at gmail.com> <mailto:moses.serugo at gmail.com <mailto:moses.serugo at gmail.com>>
>> 
>>    _______________________________________________ RPD mailing list
>>    RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:RPD at afrinic.net <mailto:RPD at afrinic.net>>
>>    https://lists.afrinic.net/mailman/listinfo/rpd
>> 
>> 
>>    **********************************************
>>    IPv4 is over
>>    Are you ready for the new Internet ?
>>    http://www.theipv6company.com
>>    The IPv6 Company
>> 
>>    This electronic message contains information which may be privileged
>>    or confidential. The information is intended to be for the exclusive
>>    use of the individual(s) named above and further non-explicilty
>>    authorized disclosure, copying, distribution or use of the contents
>>    of this information, even if partially, including attached files, is
>>    strictly prohibited and will be considered a criminal offense. If
>>    you are not the intended recipient be aware that any disclosure,
>>    copying, distribution or use of the contents of this information,
>>    even if partially, including attached files, is strictly prohibited,
>>    will be considered a criminal offense, so you must reply to the
>>    original sender to inform about this communication and delete it.
>> 
>> 
>> **********************************************
>> IPv4 is over
>> Are you ready for the new Internet ?
>> http://www.theipv6company.com
>> The IPv6 Company
>> 
>> This electronic message contains information which may be privileged or
>> confidential. The information is intended to be for the exclusive use of
>> the individual(s) named above and further non-explicilty authorized
>> disclosure, copying, distribution or use of the contents of this
>> information, even if partially, including attached files, is strictly
>> prohibited and will be considered a criminal offense. If you are not the
>> intended recipient be aware that any disclosure, copying, distribution
>> or use of the contents of this information, even if partially, including
>> attached files, is strictly prohibited, will be considered a criminal
>> offense, so you must reply to the original sender to inform about this
>> communication and delete it.
>> 
>> 
>> _______________________________________________
>> RPD mailing list
>> RPD at afrinic.net
>> https://lists.afrinic.net/mailman/listinfo/rpd
>> 
> 
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net <mailto:RPD at afrinic.net>
> https://lists.afrinic.net/mailman/listinfo/rpd <https://lists.afrinic.net/mailman/listinfo/rpd>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20190626/7c8983b0/attachment-0001.html>


More information about the RPD mailing list