Search RPD Archives
[AFRINIC-rpd] Re: AFPUB-2012-V4-001-DRAFT-02
dogwallah at gmail.com
Wed Jun 19 12:39:56 UTC 2013
Apologies that I can't be with you in person this week (or even remotely).
I do not see any support (or even any opposition) on this proposal.
This proposal forces people to register their assignments in order to
get reverse delegation in the AFRINIC Database.
If there is no consensus that this is the way to rectify the problem
of getting people to register their assignments, I would be happy to
withdraw this proposal and perhaps the time scheduled for this
proposal can be spent discussing other ways to solve the problem?
I leave it in the capable hands of the WG co-chairs to lead this discussion.
Best Regards to all in Lusaka,
On Mon, Dec 17, 2012 at 3:12 PM, McTim <dogwallah at gmail.com> wrote:
> Ladies and Gents,
> Please find my revisions to the "No Reverse" proposal below, taking
> into account all of your concerns (I hope):
> Unique identifier: AFPUB-2012-DNS-001-DRAFT-02
> Draft Policy Name: No Reverse Unless Assigned
> Author: Tim McGinnis (McTim) mctimconsulting at gmail.com
> Related Policies: None
> Obsoletes: None
> Submission Date: November 30th, 2012
> Amends: AFPUB-2005-v4-001
> Summary of the Problem Being Addressed by this Policy Proposal
> The purpose of a Public Network Information Database such as the AfriNIC
> Database is so that contact information about public networks is made public
> by registering assignments as they are made in the database. It is the author's
> experience that AfriNIC members are not as diligent about registering
> assignments of IPv4 space as they could be.
> AFPUB-2005-v4-001 says, inter alia:
> 9.5 Validity of an assignment
> Assignments remain valid as long as the original criteria on
> which the assignment was based are still in place and the assignment
> is registered in the
> AfriNIC whois database. An assignment is therefore invalid if it is
> not registered
> in the database and if the purpose for which it was registered has
> changed or no longer holds.
> This proposal is an enforcement mechanism of that long-standing policy.
> Summary of How this Proposal Addresses the Problem
> This proposal limits LIRs and End-Users from obtaining reverse
> delegation (rDNS) from AfriNIC unless the address space is assigned or
> sub-allocated in the
> AfriNIC Database.
> 3.1 AfriNIC will no longer grant reverse delegation of IP address
> space that it administers unless an assignment or sub-allocation of
> the specific address space is
> registered appropriately in the AfriNIC Database.
> For a /24 reverse delegation, at least one assignment or
> sub-allocation must be registered in the AfriNIC Database
> for that specific /24. the entire /24 does not have to be assigned in
> order for the reverse delegation to be allowed.
> 3.2 AfriNIC will contact those LIRs who currently have reverse DNS for
> allocations, but have not registered any assignments or
> sub-allocations under those allocations to remind them of the above
> text from AFPUB-2005-v4-001. It is envisioned that this will be done
> using MyAfriNIC and email, but specific details will be left to the
> Secretariat staff to implement. These LIRs will have 12 (twelve)
> months from the date of the reminder to register their assignments or
> 3.3 AfriNIC may remove reverse delegation of any LIRs allocation
> beginning 12 (twelve) months from the date of the reminder.
> Please discuss as needed.
More information about the RPD