2 questions
David R Huberman
huberman at gblx.net
Thu Dec 21 16:10:35 EST 2000
> Private (not displayed in whois): Billing, Membership and Administrative
-------
* Billing POCs are held by ARIN billing upon the establishment of a new
registering organization, correct? An e-mail to billing at arin.net can
help effect changes to the registered billing POC, correct?
* Membership POCs are held by ARIN Member Services also upon the
establishment of a new registered organization, correct? An e-mail
to memsvcs at arin.net can help effect changes to the registered
membership POC, correct?
* Administrative POCs are not well defined here. ARIN's RSG has historic
records of correspondence between ARIN and a given customer. I cannot
think of any existing mechanism that allows the customer to define to
ARIN whom the administrative POC is for that organization's
registrations. Such a system seems to be a good idea. Joe Schmo runs
Global Crossing IP addressing for x many years. Joe Schmo leaves GBLX.
On the way out, Joe Schmo updates ARIN's records to designate John
Doe as the administrative contact to whom ARIN can turn with questions.
> Public (displayed in whois): Technical, NOC and Abuse
------
* It seems to be that RPSL already defines these POCs quite well. ARIN
would do well to model multiple POC listings after RPSL. Within each
WHOIS registration would contain a mandatory technical contact, which
can be filled by a role account AND/OR a individual handle, and an
abuse contact, also filled by either a role or individual handle.
> The next question is, is there a need to ever have more than one of any
> type of POC?
* Rather than thinking about it as "Technical, NOC, Abuse" it seems to
be more flexible to think of it as tech-c: and abuse:. This allows
registrants to put information into tech-c: as they desire.
To answer your question, yes. Global Crossing could, for example, put
IA12-ORG-ARIN into tech-c: for its address registrations but could
put IA12-ORG-ARIN *and* an individual handle into its AS registration
to assist in inter-provider communication.
/david
More information about the Dbwg
mailing list