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

[AfriNIC-rpd] Staff Comments & Implementation Impact Analysis for Policy - Abuse Contact Information in the AfriNIC Service Region (AFPUB-2010-GEN-006)

Mukom Akong T. tamon at afrinic.net
Fri Jan 14 13:35:39 SAST 2011


Staff Comments & Implementation Impact Analysis for
Abuse Contact Information in the AfriNIC Service Region
Policy  (AFPUB-2010-GEN-006)
-------------------------------------------------------------------------------------


1.0 Introduction

The comments herein are from the AfriNIC Technical Operations Area in
general and the Member Services, Software Engineering and Database units
in particular. The impact of this policy proposal to any internal
procedures and processes relating to Internet Number Resource
Management, software sources and back-end databases will be analyzed.

2.0 Actions arising from the proposal

The final version of this proposal that reached concensus at the
AfriNIC-13 public policy meeting in Sandton, South Africa, November
2010, is at:

http://www.afrinic.net/docs/policies/AFPUB-2010-GEN-006.htm

Key actions points from the proposal:

a. Create a new or use an already existing whois database object that
will be referenced in all objects of type:

	inetnum
	inet6num
	aut-num
	
It is envisaged that each object above will be modified to include an
extra optional attribute that could be called “abuse-c”, and that it
would be a reference to a normal person or role object.


b. The object should conform to the following:

Can be referenced once in an inetnum, inet6num and aut-num
Contains two mandatory attributes named below, whose value must be that
of a valid e-mail address.
	
	e-mail
	abuse-mailbox

c. This object must be able to be queried through the normal whois query
process. (Although this has not been explicitly mentioned, I guess that
the attributes above would be both normal and inverse lookup keys. The
primary lookup key would be the object-id, such as a “nic-hdl”, while
other lookup keys would be defined as appropriate).

d. Currently, the “abuse-mailbox” attribute is an optional requirement
in the following whois database objects:

	person
	role
	organization


3.0 Impact to Internal Processes

3.1 New Membership Process

Addition of detailed abuse contact information to the new membership
(online) form. This will have to be the data that is required to
populate all the attributes necessary for creating the prospective
member’s person or role object that will be used as an “abuse-c”.

3.2 Resource Request Evaluation

When processing additional resource requests for existing members, we
shall ask the member to either create a person object that will be
referenced as an “abuse-c”, or provide us with the information necessary
to create the object in the whois database. This is the only foreseeable
long-term impact to the internal number resource evaluation process.

4.0 Other Areas of Impact

4.1 MyAfriNIC

Changes must be made in MyAfriNIC to allow inclusion of the “abuse-c”
attribute when working with (IPv4/IPV6 PA and PI assignments,
allocations, sub-allocations, PA assignments and ASNs).

4.2 The whois server

Please see 2.0 above.

4.3 Training Material

This change will need to be added to current training material.

4.4 Resource Requests

Sections in the resource requests where existing whois database object
templates are referenced will have to be updated accordingly. This is
partly catered for in the work to be done under MyAfriNIC.

4.5 Website

Online whois database help and reference pages will need to be updated
to include content about the “abuse-c” attribute.



4.6 Staff Training

The staff interfacing with members for 1st level support (IP Analysts,
Membership Liaison Officer) will need general introductory training on
the use of the “abuse-c” attribute.


4.7 Internal Collaboration Tools [Wiki/E-Groupware]

The relevant documents for various internal guidelines and procedures
(on internet resource management and the new-membership process) will
need to be updated.


5.0 Implementation of the proposal

With the current (human) resource constraint in the Technical Operations
Area and ongoing parallel activities, it is envisaged that it will take
AfriNIC staff approximately 60 days to fully implement the policy and
incorporate it into our internal business processes.

It is also to be noted that the long-term general impact to AfriNIC
internal business processes as a result of ratification of this policy
proposal is minimal – See 6.0 below.


6.0 Categorization of “impact” scenarios.


a. Minimal: Will be implemented with no impact to ongoing projects and
activities, human resources and budget. Till take  0-3 months.

b. Moderate: May require additional human resources and updates to
network infrastructure. Could impact the budget to be implemented. Will
take 3-6 months.

c. Critical: Implementation of the policy requires major overhaul of
company infrastructure, human resources and business processes. Will
grossly impact the budget and will be implemented in 6-12 months or more.







--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
Mukom Akong T.
www.afrinic.net | p: +230 403 5100   |   f: +230 466 6758
Skype/Twitter: perfexcellent   | LinkedIn: mu.linkedin.com/in/perfexcellent

“When you work you are a flute through whose heart the whispering of the
hours turns to music.“

                                                - Kahlil Gibran


More information about the rpd mailing list