Search RPD Archives
[rpd] Public Policy Meeting Draft Agenda for AfriNIC 31
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Sat Jun 8 07:07:50 UTC 2019
I will like to take the oportunity to ask eveyone to read the proposals. Time is short, so it will not be possible to do a complete "text" presentation of every proposal if we want to have discussion time.
More below, in-line.
El 8/6/19 1:51, "Owen DeLong" <owen at delong.com> escribió:
Thanks, Dewole, for putting this together.
> 09:00 – 09:10 Welcome, Introduction & Agenda Overview
> 09:10 – 09:20 The AFRINIC PDP
> 09:20 – 10:45 Policy Development Update from other RIRs
> 09:45 – 10:00 Policy Implementation Experience Report
> 10:00 - 10:30 Multihoming not required for ASN
Support as written. Hopefully this one will not bring up significant controversy. A similar policy is already in place in at least 3 other RIRs. (Not sure about LACNIC).
-> Same for LACNIC.
Not sure why this policy gets a 1/2 hour slot while more controversial policies below get 15 minutes each.
-> I agree it can be shorter, but as Dewole said, order can be changed, so I guess if we finish before with this one, we can move on to the next one or another that can fit in the available time. Also note that the two policies that get 15 minutes, will be presented in a single 30 minutes slot. Single presentation, single discussion. I guess it was showed in the agenda that way to avoid confusing people, instead of:
11:00 – 11:30 IPv4 Inter-RIR Resource Transfers (both proposals)
> 10:30 – 11:00 BREAK
> 11:00 – 11:15 IPv4 Inter-RIR Legacy Resource Transfers
> 11:15 – 11:30 IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)
I don’t see any reason to treat transfers of legacy resources separate from non-legacy. In fact, IMHO, any resource which is transferred should require that the new owner receive it as non-legacy status. Legacy status is an accident of history, not a privilege to be retained by subsequent registrants.
-> Fully agree and I will explain this in my presentation. It was also explained in the email when the proposals were introduced in the list.
> 11:30 - 12:00 SL-Update
Still oppose. Grounds previously stated.
> 12:00 - 12:30 IPv6 PI Clarification
Mostly neutral. Not opposed, slight support, but consider it mostly unnecessary.
-> I believe your maybe confused here with something else ? You're also a co-author! There is a major problem with the actual policy: The text states that the space must be announced or returned. This is a non-sense for cases such as IXPs. The other point is clarifying end-user vs end-site.
> 12:30 - 14:00 LUNCH
> 14:00 – 14:30 Abuse Contact Policy Update
Some concerns here, but mostly neutral.
-> There is a new version that has been sent a few days ago, so just waiting for publication. It hopefully clarify your concerns and those in the impact analysis. Basically, it is the same as implemented in ARIN and APNIC.
> 14:30 – 15:00 Internet Number Resources review by AFRINIC
Still opposed. Grounds stated previously.
> 15:00 - 15:30 Provisions for Resource Hijacking
Opposed. Grounds stated previously.
> 15:30 – 16:00 BREAK
> 16:00 – 16:30 Clarification on temporary resource usage
Mostly neutral. Not opposed, slight support, but consider it mostly a no-op.
> 16:30 – 17:00 AFRINIC Policy Development Process Bis
Opposed. Grounds stated previously.
> 17:00 - 17:30 Open Policy Microphone
RPD mailing list
RPD at afrinic.net
IPv4 is over
Are you ready for the new Internet ?
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.
More information about the RPD