ARIN Conversion: Template Instructions Now Available

[ginny listman]

Dawn,

My understanding of what Scott is proposing:

Query 1: An Org
Response 1: ALL POCs associated with the Org. This would include the
Administrative contact, as well as the multiple Technical contacts. Most
people will not be querying Orgs, but rather the actual resource.

Query 2: A resouce that has POCs associated with it
Response 2: Display only the resource POCs

Query 3: A resource that does NOT have POCs associated with it
Response 3: Display the Orgs Tech, NOC and Abuse contacts

Is this right, Scott?

I would go a step further and suggest that query 3 be broken into the
following:

Query 3A: A resource that does not have POCs associated with it, and the
Org has Abuse and/or NOC contacts
Response 3A: Display the Org Abuse and/or NOC

Query 3B: A resource that does not have POCs associated with it, and the
Org does not have Abuse and/or NOC
Response 3B: Display the Org Techs


Ginny

On Mon, 15 Jul 2002, Dawn Martin wrote:

> Scott,
>
> Are you saying that on any given record the organization would have to have
> at least 1 contact. If the organization decided to put additional POC's on
> the record the org. could decide not to have the admin listed on the record?
>
> If so, then the Admin contact could only be pulled up using a specific WHOIS
> query?
> Something like: whois -h whois.arin.net admin 157.130.0.0
>
> That would be fine with me, I think I have said before that if it was a
> separate
> entry that could be pulled up by savvy WHOIS folks it would be better.
>
> Dawn Martin
> WorldCom IP Planning & Policy Analyst
> dawn.martin at wcom.com
> (703)886-4746
>
>