[RPKI-Discuss] the case for ASPA objects

Wed Apr 8 06:31:17 UTC 2026

Hi Mukom,

Thanks for the email.

 > My colleague Yogesh will share the testing timeline and participation
 > details with the community within the next 2 weeks.

looking forward to this, and i believe i'm not alone.

 > MyAFRINIC v1 is the critical constraint because we've reached its
 > architectural limits. Trying to extend it further makes it more
 > fragile
 > and puts registry operations at risk. That's why we decided to replace
 > it entirely with MyAFRINIC 2.0.

So I was wondering a bit for how long we've heard about this 2.0
And from a google search the AI answer mislead me saying "2022".
While the same search had a link to
https://www.afrinic.net/ast/pdf/agmm/2013/af18-agmm-OperationsReport-COO.pdf
which says since June 2013 we hear about MyAfriNIC2.0

I trust that there were some moving goalposts along the way, but I just 
can't avoid feeling that it's "been a long time".

This is the view from the other side of the table.

PS:
https://status.afrinic.net/notices/2oqqaqurvbtjedsr-service-degradation-notice
has no updates for 3 days *and* the statement "Updates will be shared as 
progress is made". So we have to conclude that there's no progress?

Regards,
Frank

On 4/6/2026 1:27 PM, Mukom wrote:
> Hi Frank,
> 
> 
> 
> Thank you for raising this again.
> You're right to push on it, and you're right that this is overdue.
> 
> Here's where things stand and what we're doing about it.
> 
> MyAFRINIC v1 is the critical constraint because we've reached its 
> architectural limits. Trying to extend it further makes it more fragile 
> and puts registry operations at risk. That's why we decided to replace 
> it entirely with MyAFRINIC 2.0.
> 
> 100% of our development capacity is focused on delivering MyAFRINIC 2.0 
> as the foundation that can support the capabilities members need — 
> including delegated RPKI, ASPA, and everything else the community is 
> asking for. We're subordinating everything else to that goal.
> 
> We do however have working code for RPKI delegated mode that we will be 
> opening up for member testing. This lets us validate requirements and 
> refine the implementation now, so that when MyAFRINIC 2.0 launches, 
> delegated mode — and subsequently ASPA and other features based on 
> member needs — can follow in structured, near-term releases (v2.1, v2.2) 
> rather than starting from scratch.
> 
> 
> My colleague Yogesh will share the testing timeline and participation 
> details with the community within the next 2 weeks.
> 
> To your procedural question: this does not need a Working Group 
> discussion. Delegated RPKI and ASPA support are operational capabilities 
> that fall squarely within AFRINIC's mandate. Where the Working Group 
> will be valuable is in helping us prioritize features for the post- 
> launch roadmap.
> 
> To your offer to mobilize members: we welcome it. What would be most 
> valuable right now is member input into the MyAFRINIC 2.0 development 
> process itself, so that we build the right foundation from the start.
> 
> We thus appreciate the tireless work you've been doing on that forum, 
> and it is even more critical now.
> 
> I recognize this timeline may not match the urgency you and other 
> members feel. I share that frustration. What I can commit to is 
> transparency on progress and including resource members in the design 
> process so that MyAFRINIC 2.0 launches without limitations that might 
> hamper future developments.
> 
> 
> Thank you for your continued engagement.
> 
> 
> 
> 
> 
> --
> 
> Mukom Akong T.  |  @perfexcellent
> 
> 
> ------------------------------------------------------------------------------------------------------------------------------------------
> “When you work, you are the FLUTE through whose lungs the whispering of 
> the hours turns to MUSIC" - Kahlil Gibran
> -------------------------------------------------------------------------------------------------------------------------------------------
> On 2 Apr 2026 at 22:18 +0400, Frank Habicht <geier at geier.ne.tz>, wrote:
>> Dear AfriNIC staff and members,
>>
>> It has come to my attention that some people feel that we need more
>> public outrage that AfriNIC still doesn't support delegated mode RPKI.
>>
>> That's mostly because some members wish to create ASPA records and with
>> the AfriNIC-hosted solution this is still not possible - in my
>> understanding, to be corrected.
>>
>> Maybe they are right.
>>
>> I tried to find public statements with timelines.
>> at [1] on slide 23, I found "July 2011".
>>
>> I probably didn't search well enough for more...
>>
>> the address rpki-help at afrinic.net has received a detailed request from a
>> member on January 5th.
>>
>> I can represent 4 members asking you to provide a solution to members
>> for the creation of ASPA objects. Best by enabling both methods, of 
>> course.
>>
>> I consider volunteering to get you a list of many more members who do
>> have the need for that and want to officially support AfriNIC moving
>> more quickly to accomplish this.
>>
>> How many do we need?
>>
>> I would hope that it is well known that this is a request for the
>> betterment and positive development of routing security.
>>
>> Which I believe to be withing the mandate of AfriNIC.
>>
>> I have seen messages that this could be a request to be "discussed"
>> within an AfriNIC Working Group. Does anybody at AfriNIC think that any
>> discussion is needed? Or would you just like to provide be above
>> requested number?
>>
>> Personally, I believe this is more a topic for a staff meeting at
>> AfriNIC than for a Working Group... Mostly because it's 2026.
>>
>> In the meantime, can others please help me with the public outrage?
>>
>> Thanks,
>> Frank Habicht
>> ORG-SL71-AFRINIC
>>
>>
>> [1]
>> https://meeting.afrinic.net/afrinic-13/images/stories/ 
>> af13_presentation/AF-13-24/10-RPKI-AFRINIC-13-simplified.pdf
>>