<html>
Very, Very nice. The labels will make parsing through the
output<br>
much easier.<br>
<br>
Question:<br>
<br>
Currently, when doing a Whois query, and the netblock is not found, Whois
will<br>
display the info for the ISP's large netblock allocation from which the
netblock<br>
originates.<br>
<br>
Will the format of this output change? This is important, in that
our automation<br>
looks for the "NON-PORTABLE" character string on the page as an
indication<br>
that a netblock has no specific Whois entry.<br>
<br>
Thanks.<br>
----------------------------------<br>
Dave Barger<br>
Director - Network Engineering IP Management<br>
SBC Internet Services<br>
----------------------------------<br>
<br>
At 10:00 AM 3/12/2002, ginny listman wrote:<br>
<blockquote type=cite class=cite cite>To coincide with the release of the
new database and templates, ARIN has<br>
begun development of a new Whois, in a modular format. The Output
Module<br>
will define the Whois display. It is our objective to keep the
Whois<br>
display in a easily readable format, while accomodating machine
queries<br>
by providing labels.<br>
<br>
The requirements outlined in this document are based on feedback from
the<br>
community. To provide a usable tool, we are requesting additional
comments <br>
at this time. Additionally, this format will be discussed at the
Member<br>
Meeting taking place April 7-10 in Las Vegas.<br>
<br>
Ginny Listman<br>
Director of Engineering<br>
ARIN<br>
<br>
*****<br>
<br>
WHOIS
REQUIREMENTS<br>
<br>
I. Uses of Whois<br>
a. As a troubleshooting aid<br>
b. For Applications that use resource assignment
information<br>
c. To show address space utilization<br>
d. In the future, to display routing objects<br>
<br>
II. Privacy<br>
a. The Whois database is a public resource.<br>
<br>
III. Formats<br>
a. The "default" format is returned when querying
Whois without any flags, <br>
and there is a single record returned. For
ease of use all items will<br>
include labels. If a field does not exist,
for example if a POC is <br>
missing a email address, a label will not
be displayed. Refer to the <br>
attached "Whois Examples" for
samples. The four object will be displayed <br>
as follows:<br>
<br>
i. Point Of Contact - display all
attributes of the POC<br>
<br>
Name: <last name,
first name, middle name> or <role account><br>
Handle: <point of
contact handle><br>
Address:
<organization name, street address, city, state, zip, <br>
country code><br>
Phone: <phone number,
phone extension, phone type><br>
Phone: <phone number,
phone extension, phone type><br>
Email: <email
address><br>
Email: <email
address><br>
<br>
ii. Organization - list the organization and all
associated POCs<br>
<br>
Org Name:
<organization name><br>
Org ID: <organization
ID, formerly maintainer ID><br>
Org Address: <street
address, city, state, zip, country code><br>
<br>
Org <POC function>
Handle: <POC handle><br>
Org <POC function>
Name: <POC name><br>
Org <POC function>
Phone: <POC office phone number><*><br>
Org <POC function>
Email: <POC email address><*><br>
<br>
Org <POC function>
Handle: <POC handle><br>
Org <POC function>
Name: <POC name><br>
Org <POC function>
Phone: <POC office phone number><*><br>
Org <POC function>
Email: <POC email address><*><br>
<br>
Note: Organization POC
functions include Admin, Tech, Abuse and NOC.<br>
<br>
iii. Autonomous System - list the organization, the
autonomous system,<br>
POCs for the autonomous
system, and POCs for the organization<br>
<br>
Org Name:
<organization name><br>
Org ID: <organization
ID, formerly maintainer ID><br>
Org Address: <street
address, city, state, zip, country code><br>
<br>
AS Number:
<autonomous system number><br>
AS Handle:
<autonomous system handle><br>
AS Name: <autonomous
system name><br>
<br>
AS <POC function>
Handle: <POC handle><br>
AS <POC function>
Name: <POC name><br>
AS <POC function>
Phone: <POC office phone number><*><br>
AS <POC function>
Email: <POC email address><*><br>
<br>
Org <POC function>
Handle: <POC handle><br>
Org <POC function>
Name: <POC name><br>
Org <POC function>
Phone: <POC office phone number><*><br>
Org <POC function>
Email: <POC email address><*><br>
<br>
Note: All POCs for the
AS will be displayed. Only the organization's<br>
Tech, Abuse and NOC POCs
will be displayed.<br>
<br>
iv. IPv4 Network - list the organization, the
network, POCs for the<br>
network, POCs for the
organization<br>
<br>
Org Name:
<organization name><br>
Org ID: <organization
ID, formerly maintainer ID><br>
Org Address: <street
address, city, state, zip, country code><br>
<br>
CIDR Net Address:
<network address in CIDR format><br>
Network Range:
<network address range><br>
Network Handle:
<network handle><br>
Network Name:
<network name><br>
Can Sub-Delegate:
<Y/N><br>
IN-ADDR: <in-addr
server name><br>
IN-ADDR: <in-addr
server name><br>
<br>
Net <POC function>
Handle: <POC handle><br>
Net <POC function>
Name: <POC name><br>
Net <POC function>
Phone: <POC office phone number><*><br>
Net <POC function>
Email: <POC email address><*><br>
<br>
Net <POC function>
Handle: <POC handle><br>
Net <POC function>
Name: <POC name><br>
Net <POC function>
Phone: <POC office phone number><*><br>
Net <POC function>
Email: <POC email address><*><br>
<br>
Note: All POCs for the
network will be displayed. Only the <br>
organization's Tech,
Abuse and NOC POCs will be displayed.<br>
<br>
* Indicates that
multiple phone numbers or email addresses exist,<br>
of which
only the first is displayed.<br>
<br>
b. The "list" format is returned when querying
Whois without specifying any <br>
flags, and there are multiple records
returned. Labels are not included.<br>
The fields that are displayed are outlined
below.<br>
i. Point Of Contact - last name, first
name, middle name, handle, one <br>
email address, one
office phone number<br>
ii. Organization - Organization name,
Organization ID<br>
iii. Autonomous System - AS name, handle, AS
number<br>
iiii. Network - network name, handle, either a single CIDR
block or network<br>
range.<br>
<br>
c. In the future, we may provide the output in RPSL-like
format.<br>
<br>
IV. Query by type. To narrow a search, a query can include a flag
indicating<br>
the object type as follows:<br>
a. n <query string> will return only networks<br>
b. a <query string> will return only autonomous
systems<br>
c. p <query string> will return only
point-of-contacts<br>
d. o <query string> will return only
organizations<br>
<br>
V. Query by attribute. To narrow a search, a query can also include a
flag<br>
as follows:<br>
a. ! <handle> will return the single match of the
specified handle<br>
b. @ <DNS name> will return the list of POCs with the
specified domain name<br>
in the email address<br>
c. . <name> will return a list of POCs, organizations,
autonomous systems,<br>
and/or networks that start with the
specified name<br>
<br>
VI. Additional features<br>
a. Sub-queries can be displayed using the % flag. The
queried string<br>
must return a single record to provide
sub-query information. The<br>
following objects have sub-query
information:<br>
i. Networks - display the
reassignment/reallocation information in<br>
list format, if data
exists.<br>
ii. Organizations - display the organization's
resources information<br>
in list format, if data
exists.<br>
b. Parentage can be displayed using the * flag. The
queried string<br>
must return a single record to provide
parentage information. The<br>
following objects have parentage
information:<br>
i. Networks - display the parentage in
default format, if data exists.<br>
ii. Organizations - will be implemented in
future releases.<br>
c. Other keywords<br>
i. = <query string> will show
default displays for all matches, <br>
regardless of the number
returned<br>
ii. HELP will display the help screen<br>
iii. <query string>. will show a list of all
matches starting with the<br>
given string.<br>
iv. SUM <query string> will show list
displays, even if there is only<br>
one match.<br>
d. The maximum number of records output is limited to
256. This may be<br>
revised in future versions.<br>
e. A future enhancement will include an relational
lookup. For example, if<br>
a POC is queried, the resouces associated
with the POC would be <br>
displayed.<br>
WHOIS EXAMPLES<br>
<br>
The following information is used as sample data.<br>
<br>
1. Organization ABC ISP is registered with 5 POCs - DEF-ARIN as the
<br>
administrative contact, ABC-TECH-ARIN and ABC-TECH2-ARIN as
technical <br>
contacts, ABC-NOC-ARIN as a NOC contact and ABC-ABU-ARIN as an abuse
contact.<br>
2. ABC ISP has been assigned autonomous system 65000, and has ABUSE-ARIN
as <br>
an abuse contact.<br>
3. ABC ISP has been allocated two network blocks. The first
10.0.0.0/15<br>
does not have any resource POCs associated with it. It has two
IN-ADDR servers.<br>
4. The second allocation 10.32.0.0/16 has SUP-ARIN as a technical contact
and<br>
NOC2-ARIN as a NOC contact. It has 4 IN-ADDR servers.<br>
5. ABC has reassigned 10.32.0.0-10.32.0.19 to XYZ ISP. XYZ has the
minimal<br>
amount of POCs - XYZ-TECH-ARIN as the organizational technical and
XYZ-ADMI-ARIN<br>
as the administrative. There are no POCs or IN-ADDR servers on the
reallocation.<br>
<br>
Based on this information, the whois display would be as follows:<br>
<br>
1. whois abc<br>
Org Name: ABC ISP<br>
Org ID: ABC<br>
Org Address: 132 Main Street<br>
Anytown, VA 22222<br>
US<br>
<br>
Org Admin Handle: DEF-ARIN<br>
Org Admin Name: Foobar, Dwight E.<br>
Org Admin Phone: +1-999-999-7777 (Office) *<br>
Org Admin Email: foobar@example.net<br>
<br>
Org Tech Handle: ABC-TECH-ARIN<br>
Org Tech Name: Technical Support<br>
Org Tech Phone: +1-999-999-9999 (Office) *<br>
Org Tech Email: tech@example.net<br>
<br>
Org Tech Handle: ABC-TECH2-ARIN<br>
Org Tech Name: Technical Support Manager<br>
Org Tech Phone: +1-999-999-8888 (Office)<br>
Org Tech Email: tech-mgr@example.net<br>
<br>
Org NOC Handle: ABC-NOC-ARIN<br>
Org NOC Name: Network Operations Center<br>
Org NOC Phone: +1-999-999-6666 (Office) *<br>
Org NOC Email: noc@example.net<br>
<br>
Org Abuse Handle: ABC-ABU-ARIN<br>
Org Abuse Name: Network Abuse Support<br>
Org Abuse Phone: +1-999-999-5555 (Office) *<br>
Org Abuse Email: abuse@example.net<br>
<br>
2. whois 65000<br>
Org Name: ABC ISP<br>
Org ID: ABC<br>
<br>
AS Number: 65000<br>
AS Handle: AS65000<br>
AS Name: ABC-ASN65000<br>
<br>
AS Abuse Handle: ABUSE-ARIN<br>
AS Abuse Name: AS 65000 Abuse Support<br>
AS Abuse Phone: +1-703-000-0000 (Office) *<br>
AS Abuse Email: abuse-65000@example.net<br>
<br>
Org Tech Handle: ABC-TECH-ARIN<br>
Org Tech Name: Technical Support<br>
Org Tech Phone: +1-999-999-9999 (Office) *<br>
Org Tech Email: tech@example.net<br>
<br>
Org Tech Handle: ABC-TECH2-ARIN<br>
Org Tech Name: Technical Support Manager<br>
Org Tech Phone: +1-999-999-8888 (Office)<br>
Org Tech Email: tech-mgr@example.net<br>
<br>
Org NOC Handle: ABC-NOC-ARIN<br>
Org NOC Name: Network Operations Center<br>
Org NOC Phone: +1-999-999-6666 (Office) *<br>
Org NOC Email: noc@example.net<br>
<br>
Org Abuse Handle: ABC-ABU-ARIN<br>
Org Abuse Name: Network Abuse Support<br>
Org Abuse Phone: +1-999-999-5555 (Office) *<br>
Org Abuse Email: abuse@example.net<br>
<br>
3. whois 10.0.0.0<br>
Org Name: ABC ISP<br>
Org ID: ABC<br>
<br>
CIDR Net Address: 10.0.0.0/15<br>
Network Range: 10.0.0.0-10.1.255.255<br>
Network Handle: NET-10-0-0-0<br>
Network Name: NETWORK-10<br>
Can Sub-Delegate: Y<br>
IN-ADDR: ns.example.net<br>
IN-ADDR: ns2.example.net<br>
<br>
Org Tech Handle: ABC-TECH-ARIN<br>
Org Tech Name: Technical Support<br>
Org Tech Phone: +1-999-999-9999 (Office) *<br>
Org Tech Email: tech@example.net<br>
<br>
Org Tech Handle: ABC-TECH2-ARIN<br>
Org Tech Name: Technical Support Manager<br>
Org Tech Phone: +1-999-999-8888 (Office)<br>
Org Tech Email: tech-mgr@example.net<br>
<br>
Org NOC Handle: ABC-NOC-ARIN<br>
Org NOC Name: Network Operations Center<br>
Org NOC Phone: +1-999-999-6666 (Office) *<br>
Org NOC Email: noc@example.net<br>
<br>
Org Abuse Handle: ABC-ABU-ARIN<br>
Org Abuse Name: Network Abuse Support<br>
Org Abuse Phone: +1-999-999-5555 (Office) *<br>
Org Abuse Email: abuse@example.net<br>
<br>
4. whois 10.32.0.0<br>
NETWORK-10.32
(NET-10-32-0-0)
10.32.0.0/16<br>
NET-10-32-RE
(NET-10-32-0-0-2)
10.32.0.0-10.32.0.19<br>
<br>
5. whois NET-10-32-0-0-2<br>
Org Name: XYZ ISP<br>
Org ID: XYZ<br>
<br>
CIDR Net Address: 10.32.0.0/28, 10.32.0.19/30<br>
Network Range: 10.32.0.0-10.32.0.19<br>
Network Handle: NET-10-32-0-0-2<br>
Network Name: NET-10-32-RE<br>
Can Sub-Delegate: N<br>
<br>
Org Tech Handle: XYZ-TECH-ARIN<br>
Org Tech Name: Technical Support<br>
Org Tech Phone: +1-777-777-7777 (Office) *<br>
Org Tech Email: tech-xyz@example.net<br>
<br>
6. whois ABC-NOC-ARIN<br>
Name: Network Operations Center<br>
Handle: ABC-NOC-ARIN<br>
Address: ABC ISP<br>
132 Main Street<br>
Anytown, VA 22222<br>
US<br>
Phone: +1-999-999-6666 (Office)<br>
Phone: +1-888-888-8888 (Mobile)<br>
Phone: +1-777-777-7777 (Fax)<br>
Email: noc@example.net </blockquote>
<x-sigsep><p></x-sigsep>
<b><br>
</b></html>