From plzak at arin.net Wed Mar 6 04:13:00 2002 From: plzak at arin.net (Ray Plzak) Date: Wed, 6 Mar 2002 04:13:00 -0500 Subject: FW: lame delegations in in-addr Message-ID: <001001c1c4ef$1f201a70$df82dfa9@ano> Forwarding this message from Evi Nemeth concerning lame delegations. Ray -----Original Message----- From: Evi Nemeth [mailto:evi at rupertsberg.cs.colorado.edu] Sent: Wednesday, March 06, 2002 4:09 AM To: plzak at arin.net Cc: evi at isc.org Subject: lame delegations in in-addr hi -- i suggest that arin consider a policy to try to clean up lame delegations in the in-addr.arpa zone. lame delegations are annoying, but for windows servers they are deadly because if all servers are lame win2k goes crazy and re-queries continually flooding the parent domain and often the roots. how about a policy that notifies a domain of their lame servers (via email to their whois contact perhaps) and monitors their continued lameness. if they ignore the mail or dont get it or dont care for 30 days and remain lame for 30 days, then put an empty zone file in the dns of the parent of the lame domain so that clients get an empty answer and can cache it. not sure of the privacy concerns but perhaps arin could maintain a web page of such lamers and a way for them to automatically fill in a web page, run a tool to prove they are no longer lame and have the empty file removed. -evi evi nemeth univ of colorado and caida and isc.org From ggm at apnic.net Wed Mar 6 23:59:47 2002 From: ggm at apnic.net (George Michaelson) Date: Thu, 07 Mar 2002 14:59:47 +1000 Subject: FW: lame delegations in in-addr In-Reply-To: Your message of "Wed, 06 Mar 2002 04:13:00 -0500." <001001c1c4ef$1f201a70$df82dfa9@ano> Message-ID: <26643.1015477187@apnic.net> Thanks for posting that Ray, I think its an issue we need to consider. I think we should aim to discuss this at the Las Vagas ARIN and get a substantive activity up to address lames, and non-delegated reverses. Is it too late to get something into the agenda? Big member communications/consent issues, but also good potential for community wide outcomes (reduction of traffic to roots, better DNS globally, training, improved secondary coverage) if it makes sense to progress it. cheers -George From plzak at arin.net Thu Mar 7 00:05:21 2002 From: plzak at arin.net (Ray Plzak) Date: Thu, 7 Mar 2002 00:05:21 -0500 Subject: FW: lame delegations in in-addr In-Reply-To: <26643.1015477187@apnic.net> Message-ID: <009501c1c595$afad3e50$df82dfa9@ano> George, This will be on the agenda for the Las Vegas meeting. Ray > -----Original Message----- > From: George Michaelson [mailto:ggm at apnic.net] > Sent: Thursday, March 07, 2002 12:00 AM > To: plzak at arin.net > Cc: dbwg at arin.net > Subject: Re: FW: lame delegations in in-addr > > > > Thanks for posting that Ray, I think its an issue we need to consider. > > I think we should aim to discuss this at the Las Vagas ARIN > and get a substantive activity up to address lames, and > non-delegated reverses. > > Is it too late to get something into the agenda? > > Big member communications/consent issues, but also good > potential for community wide outcomes (reduction of traffic > to roots, better DNS globally, training, improved secondary > coverage) if it makes sense to progress it. > > cheers > -George > From memsvcs at arin.net Fri Mar 8 10:30:50 2002 From: memsvcs at arin.net (Member Services) Date: Fri, 8 Mar 2002 10:30:50 -0500 (EST) Subject: Policy Proposal 2002-1 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN public policy and members meetings in Las Vegas, scheduled for April 7-10, 2002. All feedback received on the mailing lists about this policy proposal will be included in the discussions that will take place at the upcoming public policy meeting. ***** Policy Proposal 2002-1: Lame Delegations in IN-ADDR.ARPA It is proposed that ARIN actively identify lame servers on a regular basis and notify the ARIN point of contact (POC) of their findings. It is further proposed that ARIN monitor the status of those identified lame servers and remove all delegations that remain lame for a period of 30 days. ***** It is understood there are many issues that need to be discussed related to this policy proposal. Specifically: * How should the term "lame" be defined, as it relates to this proposed policy? * There has been recent discussion about the desire for WHOIS to more strictly reflect the delegations within IN-ADDR.ARPA. o Should lame delegations be identified in WHOIS, or simply removed? o If they are only flagged as lame, are they ever removed? o If they are removed, should ARIN publicly document removals? * How should the POCs of networks with lame servers be contacted by ARIN? * Should ARIN proactively or reactively conduct monitoring to identify lame delegations? This policy proposal discussion will take place on the database working group mailing list (dbwg at arin.net). Subscription information is available at http://www.arin.net/members/mailing.htm Richard Jimmerson Director of Operations American Registry for Internet Numbers From internetadmin at bestchecks.com Fri Mar 8 11:13:48 2002 From: internetadmin at bestchecks.com (internetadmin at bestchecks.com) Date: Fri, 8 Mar 2002 11:13:48 -0500 Subject: Policy Proposal 2002-1 Message-ID: Hopefully this is not off-subject, nor addressed earlier. In addition to monitoring for lame servers I would like to see ARIN also monitor and verify email addresses for the POC. As a user who forwards spam and DOS attempts to the originating block owner, I find that about 5% of the email addresses are invalid. Since email is the preferred method of contacting the block owner, it's important that the address be correct. So important in fact, that the delegation should be removed if the email address is found to be invalid or not working. The addresses should be checked at least monthly, and whenever a change is make to the database record. On another issue, although this may be a little late for the database implementation: has any provision been made for additional POC contacts in the database, like for violations of the AUP (i.e. an abuse email address)? I think it is inappropriate to send spam/malicious URL complaints to the NOC email address, but if this is the only address available for a less well-known block owner, this is where the complaints are sent to. -----Original Message----- From: Member Services [mailto:memsvcs at arin.net] Sent: Friday, March 08, 2002 10:31 AM To: arin-announce at arin.net; ppml at arin.net; dbwg at arin.net Subject: Policy Proposal 2002-1 ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN public policy and members meetings in Las Vegas, scheduled for April 7-10, 2002. All feedback received on the mailing lists about this policy proposal will be included in the discussions that will take place at the upcoming public policy meeting. ***** Policy Proposal 2002-1: Lame Delegations in IN-ADDR.ARPA It is proposed that ARIN actively identify lame servers on a regular basis and notify the ARIN point of contact (POC) of their findings. It is further proposed that ARIN monitor the status of those identified lame servers and remove all delegations that remain lame for a period of 30 days. ***** It is understood there are many issues that need to be discussed related to this policy proposal. Specifically: * How should the term "lame" be defined, as it relates to this proposed policy? * There has been recent discussion about the desire for WHOIS to more strictly reflect the delegations within IN-ADDR.ARPA. o Should lame delegations be identified in WHOIS, or simply removed? o If they are only flagged as lame, are they ever removed? o If they are removed, should ARIN publicly document removals? * How should the POCs of networks with lame servers be contacted by ARIN? * Should ARIN proactively or reactively conduct monitoring to identify lame delegations? This policy proposal discussion will take place on the database working group mailing list (dbwg at arin.net). Subscription information is available at http://www.arin.net/members/mailing.htm Richard Jimmerson Director of Operations American Registry for Internet Numbers From easmith at beatrice.rutgers.edu Fri Mar 8 12:09:51 2002 From: easmith at beatrice.rutgers.edu (Allen Smith) Date: Fri, 8 Mar 2002 12:09:51 -0500 Subject: Policy Proposal 2002-1 In-Reply-To: internetadmin@bestchecks.com "RE: Policy Proposal 2002-1" (Mar 8, 11:20am) References: Message-ID: <10203081209.ZM27291@beatrice.rutgers.edu> On Mar 8, 11:20am, internetadmin at bestchecks.com wrote: > Hopefully this is not off-subject, nor addressed earlier. It appears to be at least somewhat on-subject, given that if ARIN uses the contact addresses in the WHOIS database to do notifications of lame delegation problems, it will find out about invalid addresses. > In addition to monitoring for lame servers I would like to see ARIN also > monitor and verify email addresses for the POC. Strongly agreed. This can be unobtrusively done in many cases simply by making sure that there _is_ an email address and that the hostname resolves to an A record or an MX. Additional user-submitted information regarding WHOIS problems can be gotten through http://www.rfc-ignorant.org (and used for email or other blacklisting via ipwhois.rfc-ignorant.org). > As a user who forwards spam and DOS attempts to the originating block > owner, WHOIS contact addresses are also used for notifications of other network problems (if you think spam (UBE) isn't a network problem, try telling AT&T WorldNet that...), of course, including non-deliberate ones which nonetheless cause problems for others (a programming error resulting in an infinite loop in a network-accessing program, for instance). > I find that about 5% of the email addresses are invalid. Since email is > the preferred method of contacting the block owner, it's important that > the address be correct. So important in fact, that the delegation should > be removed if the email address is found to be invalid or not working. Agreed. > The addresses should be checked at least monthly, and whenever a change is > make to the database record. A full check - as in sending email to the address - should definitely be done whenever a change is made to the database record or whenever there are other indications of problems. I'm not sure whether an actual monthly email to every single contact address is a good idea when there are _not_ such indications of problems. > On another issue, although this may be a little late for the database > implementation: has any provision been made for additional POC contacts in > the database, like for violations of the AUP (i.e. an abuse email address)? > I think it is inappropriate to send spam/malicious URL complaints to the NOC > email address, but if this is the only address available for a less > well-known block owner, this is where the complaints are sent to. RPSL's differentiation between a tech-c and an admin-c address is useful in this regard. -Allen -- Allen Smith http://cesario.rutgers.edu/easmith/ September 11, 2001 A Day That Shall Live In Infamy II "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin From richardj at arin.net Fri Mar 8 13:17:56 2002 From: richardj at arin.net (Richard Jimmerson) Date: Fri, 8 Mar 2002 13:17:56 -0500 Subject: Policy Proposal 2002-1 In-Reply-To: Message-ID: <005901c1c6cd$b6132d70$ecfc95c0@cobalt> Thank you for our email. > In addition to monitoring for lame servers I would like to > see ARIN also monitor and verify email addresses for the POC. We would be glad to address this issue as a separate policy discussion. > has any provision been made for additional POC contacts in > the database, Yes. The new ARIN database to be released this June will include the ability to have multiple Technical, NOC, and Abuse contacts for all organizations and resources. There will also be a single Administrative POC for each organization. Future releases will include Billing and Member POCs. Best Regards, Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) > -----Original Message----- > From: dbwg-request at arin.net [mailto:dbwg-request at arin.net] On > Behalf Of internetadmin at bestchecks.com > Sent: Friday, March 08, 2002 11:14 AM > To: dbwg at arin.net > Subject: RE: Policy Proposal 2002-1 > > > Hopefully this is not off-subject, nor addressed earlier. > In addition to monitoring for lame servers I would like to > see ARIN also > monitor and verify email addresses for the POC. As a user > who forwards spam > and DOS attempts to the originating block owner, I find that > about 5% of the > email addresses are invalid. Since email is the preferred method of > contacting the block owner, it's important that the address > be correct. So > important in fact, that the delegation should be removed if the email > address is found to be invalid or not working. The addresses should be > checked at least monthly, and whenever a change is make to > the database > record. > > On another issue, although this may be a little late for the database > implementation: has any provision been made for additional > POC contacts in > the database, like for violations of the AUP (i.e. an abuse > email address)? > I think it is inappropriate to send spam/malicious URL > complaints to the NOC > email address, but if this is the only address available for a less > well-known block owner, this is where the complaints are sent to. > > -----Original Message----- > From: Member Services [mailto:memsvcs at arin.net] > Sent: Friday, March 08, 2002 10:31 AM > To: arin-announce at arin.net; ppml at arin.net; dbwg at arin.net > Subject: Policy Proposal 2002-1 > > > > ARIN welcomes feedback and discussion about the following policy > proposal in the weeks leading to the ARIN public policy and members > meetings in Las Vegas, scheduled for April 7-10, 2002. All feedback > received on the mailing lists about this policy proposal will be > included in the discussions that will take place at the > upcoming public > policy meeting. > > ***** > > Policy Proposal 2002-1: Lame Delegations in IN-ADDR.ARPA > > It is proposed that ARIN actively identify lame servers on a regular > basis and notify the ARIN point of contact (POC) of their > findings. It > is further proposed that ARIN monitor the status of those identified > lame servers and remove all delegations that remain lame for > a period of > 30 days. > > ***** > > It is understood there are many issues that need to be > discussed related > to this policy proposal. Specifically: > > * How should the term "lame" be defined, as it relates to > this proposed > policy? > > * There has been recent discussion about the desire for WHOIS to more > strictly reflect the delegations within IN-ADDR.ARPA. > > o Should lame delegations be identified in WHOIS, or simply removed? > o If they are only flagged as lame, are they ever removed? > o If they are removed, should ARIN publicly document removals? > > * How should the POCs of networks with lame servers be contacted by > ARIN? > > * Should ARIN proactively or reactively conduct monitoring to identify > lame delegations? > > > This policy proposal discussion will take place on the > database working > group mailing list (dbwg at arin.net). Subscription information is > available at http://www.arin.net/members/mailing.htm > > Richard Jimmerson > Director of Operations > American Registry for Internet Numbers > From dredd at megacity.org Mon Mar 11 21:18:03 2002 From: dredd at megacity.org (Derek Balling) Date: Mon, 11 Mar 2002 21:18:03 -0500 Subject: WHOIS data (recent discussion) Message-ID: I read Allen's message (which he forwarded to the RFC-Ignorant project's mailing list) about WHOIS policy proposals, etc. etc. As the "head stick wielder" for trying to bring lame POC info in line (and, I'd like to hope, more successful than random folks complaining to delegation-holders, which we've all seen via experience hasn't been very effective historically), I do have a vested interest in trying to help out wherever possible in this. What sort of help are we looking for here? :) D -- +---------------------+-----------------------------------------+ | dredd at megacity.org | "Thou art the ruins of the noblest man | | Derek J. Balling | That ever lived in the tide of times. | | | Woe to the hand that shed this costly | | | blood" - Julius Caesar Act 3, Scene 1 | +---------------------+-----------------------------------------+ From ginny at arin.net Tue Mar 12 11:00:20 2002 From: ginny at arin.net (ginny listman) Date: Tue, 12 Mar 2002 11:00:20 -0500 (EST) Subject: New Whois Display Format Message-ID: To coincide with the release of the new database and templates, ARIN has begun development of a new Whois, in a modular format. The Output Module will define the Whois display. It is our objective to keep the Whois display in a easily readable format, while accomodating machine queries by providing labels. The requirements outlined in this document are based on feedback from the community. To provide a usable tool, we are requesting additional comments at this time. Additionally, this format will be discussed at the Member Meeting taking place April 7-10 in Las Vegas. Ginny Listman Director of Engineering ARIN ***** WHOIS REQUIREMENTS I. Uses of Whois a. As a troubleshooting aid b. For Applications that use resource assignment information c. To show address space utilization d. In the future, to display routing objects II. Privacy a. The Whois database is a public resource. III. Formats a. The "default" format is returned when querying Whois without any flags, and there is a single record returned. For ease of use all items will include labels. If a field does not exist, for example if a POC is missing a email address, a label will not be displayed. Refer to the attached "Whois Examples" for samples. The four object will be displayed as follows: i. Point Of Contact - display all attributes of the POC Name: or Handle: Address: Phone: Phone: Email: Email: ii. Organization - list the organization and all associated POCs Org Name: Org ID: Org Address: Org Handle: Org Name: Org Phone: <*> Org Email: <*> Org Handle: Org Name: Org Phone: <*> Org Email: <*> Note: Organization POC functions include Admin, Tech, Abuse and NOC. iii. Autonomous System - list the organization, the autonomous system, POCs for the autonomous system, and POCs for the organization Org Name: Org ID: Org Address: AS Number: AS Handle: AS Name: AS Handle: AS Name: AS Phone: <*> AS Email: <*> Org Handle: Org Name: Org Phone: <*> Org Email: <*> Note: All POCs for the AS will be displayed. Only the organization's Tech, Abuse and NOC POCs will be displayed. iv. IPv4 Network - list the organization, the network, POCs for the network, POCs for the organization Org Name: Org ID: Org Address: CIDR Net Address: Network Range: Network Handle: Network Name: Can Sub-Delegate: IN-ADDR: IN-ADDR: Net Handle: Net Name: Net Phone: <*> Net Email: <*> Net Handle: Net Name: Net Phone: <*> Net Email: <*> Note: All POCs for the network will be displayed. Only the organization's Tech, Abuse and NOC POCs will be displayed. * Indicates that multiple phone numbers or email addresses exist, of which only the first is displayed. b. The "list" format is returned when querying Whois without specifying any flags, and there are multiple records returned. Labels are not included. The fields that are displayed are outlined below. i. Point Of Contact - last name, first name, middle name, handle, one email address, one office phone number ii. Organization - Organization name, Organization ID iii. Autonomous System - AS name, handle, AS number iiii. Network - network name, handle, either a single CIDR block or network range. c. In the future, we may provide the output in RPSL-like format. IV. Query by type. To narrow a search, a query can include a flag indicating the object type as follows: a. n will return only networks b. a will return only autonomous systems c. p will return only point-of-contacts d. o will return only organizations V. Query by attribute. To narrow a search, a query can also include a flag as follows: a. ! will return the single match of the specified handle b. @ will return the list of POCs with the specified domain name in the email address c. . will return a list of POCs, organizations, autonomous systems, and/or networks that start with the specified name VI. Additional features a. Sub-queries can be displayed using the % flag. The queried string must return a single record to provide sub-query information. The following objects have sub-query information: i. Networks - display the reassignment/reallocation information in list format, if data exists. ii. Organizations - display the organization's resources information in list format, if data exists. b. Parentage can be displayed using the * flag. The queried string must return a single record to provide parentage information. The following objects have parentage information: i. Networks - display the parentage in default format, if data exists. ii. Organizations - will be implemented in future releases. c. Other keywords i. = will show default displays for all matches, regardless of the number returned ii. HELP will display the help screen iii. . will show a list of all matches starting with the given string. iv. SUM will show list displays, even if there is only one match. d. The maximum number of records output is limited to 256. This may be revised in future versions. e. A future enhancement will include an relational lookup. For example, if a POC is queried, the resouces associated with the POC would be displayed. -------------- next part -------------- WHOIS EXAMPLES The following information is used as sample data. 1. Organization ABC ISP is registered with 5 POCs - DEF-ARIN as the administrative contact, ABC-TECH-ARIN and ABC-TECH2-ARIN as technical contacts, ABC-NOC-ARIN as a NOC contact and ABC-ABU-ARIN as an abuse contact. 2. ABC ISP has been assigned autonomous system 65000, and has ABUSE-ARIN as an abuse contact. 3. ABC ISP has been allocated two network blocks. The first 10.0.0.0/15 does not have any resource POCs associated with it. It has two IN-ADDR servers. 4. The second allocation 10.32.0.0/16 has SUP-ARIN as a technical contact and NOC2-ARIN as a NOC contact. It has 4 IN-ADDR servers. 5. ABC has reassigned 10.32.0.0-10.32.0.19 to XYZ ISP. XYZ has the minimal amount of POCs - XYZ-TECH-ARIN as the organizational technical and XYZ-ADMI-ARIN as the administrative. There are no POCs or IN-ADDR servers on the reallocation. Based on this information, the whois display would be as follows: 1. whois abc Org Name: ABC ISP Org ID: ABC Org Address: 132 Main Street Anytown, VA 22222 US Org Admin Handle: DEF-ARIN Org Admin Name: Foobar, Dwight E. Org Admin Phone: +1-999-999-7777 (Office) * Org Admin Email: foobar at example.net Org Tech Handle: ABC-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-999-999-9999 (Office) * Org Tech Email: tech at example.net Org Tech Handle: ABC-TECH2-ARIN Org Tech Name: Technical Support Manager Org Tech Phone: +1-999-999-8888 (Office) Org Tech Email: tech-mgr at example.net Org NOC Handle: ABC-NOC-ARIN Org NOC Name: Network Operations Center Org NOC Phone: +1-999-999-6666 (Office) * Org NOC Email: noc at example.net Org Abuse Handle: ABC-ABU-ARIN Org Abuse Name: Network Abuse Support Org Abuse Phone: +1-999-999-5555 (Office) * Org Abuse Email: abuse at example.net 2. whois 65000 Org Name: ABC ISP Org ID: ABC AS Number: 65000 AS Handle: AS65000 AS Name: ABC-ASN65000 AS Abuse Handle: ABUSE-ARIN AS Abuse Name: AS 65000 Abuse Support AS Abuse Phone: +1-703-000-0000 (Office) * AS Abuse Email: abuse-65000 at example.net Org Tech Handle: ABC-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-999-999-9999 (Office) * Org Tech Email: tech at example.net Org Tech Handle: ABC-TECH2-ARIN Org Tech Name: Technical Support Manager Org Tech Phone: +1-999-999-8888 (Office) Org Tech Email: tech-mgr at example.net Org NOC Handle: ABC-NOC-ARIN Org NOC Name: Network Operations Center Org NOC Phone: +1-999-999-6666 (Office) * Org NOC Email: noc at example.net Org Abuse Handle: ABC-ABU-ARIN Org Abuse Name: Network Abuse Support Org Abuse Phone: +1-999-999-5555 (Office) * Org Abuse Email: abuse at example.net 3. whois 10.0.0.0 Org Name: ABC ISP Org ID: ABC CIDR Net Address: 10.0.0.0/15 Network Range: 10.0.0.0-10.1.255.255 Network Handle: NET-10-0-0-0 Network Name: NETWORK-10 Can Sub-Delegate: Y IN-ADDR: ns.example.net IN-ADDR: ns2.example.net Org Tech Handle: ABC-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-999-999-9999 (Office) * Org Tech Email: tech at example.net Org Tech Handle: ABC-TECH2-ARIN Org Tech Name: Technical Support Manager Org Tech Phone: +1-999-999-8888 (Office) Org Tech Email: tech-mgr at example.net Org NOC Handle: ABC-NOC-ARIN Org NOC Name: Network Operations Center Org NOC Phone: +1-999-999-6666 (Office) * Org NOC Email: noc at example.net Org Abuse Handle: ABC-ABU-ARIN Org Abuse Name: Network Abuse Support Org Abuse Phone: +1-999-999-5555 (Office) * Org Abuse Email: abuse at example.net 4. whois 10.32.0.0 NETWORK-10.32 (NET-10-32-0-0) 10.32.0.0/16 NET-10-32-RE (NET-10-32-0-0-2) 10.32.0.0-10.32.0.19 5. whois NET-10-32-0-0-2 Org Name: XYZ ISP Org ID: XYZ CIDR Net Address: 10.32.0.0/28, 10.32.0.19/30 Network Range: 10.32.0.0-10.32.0.19 Network Handle: NET-10-32-0-0-2 Network Name: NET-10-32-RE Can Sub-Delegate: N Org Tech Handle: XYZ-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-777-777-7777 (Office) * Org Tech Email: tech-xyz at example.net 6. whois ABC-NOC-ARIN Name: Network Operations Center Handle: ABC-NOC-ARIN Address: ABC ISP 132 Main Street Anytown, VA 22222 US Phone: +1-999-999-6666 (Office) Phone: +1-888-888-8888 (Mobile) Phone: +1-777-777-7777 (Fax) Email: noc at example.net From huberman at gblx.net Tue Mar 12 11:35:16 2002 From: huberman at gblx.net (David R Huberman) Date: Tue, 12 Mar 2002 09:35:16 -0700 (MST) Subject: New Whois Display Format In-Reply-To: Message-ID: First off, the examples look fantastic. THe utility of the new layout is excellent. Question: For downstream reassignments: 1) Can upstreams put themselves in the ORG ID? 2) Can upstream designate their POC handle(s) for reassignment? (Meaning ABC delegating to XYZ puts ABC contact handle in for XYZ reassignment record.) 3) Can downstream org put NOC/Abuse/Tech/Admin contacts into their ORG ID for display in their reassigned netblocks? I just want to be clear on these. THe answers seem obvious, but... :> /david *--------------------------------* | Global Crossing API | | Manager, Global IP Addressing | | (703) 627-5800 | | huberman at gblx.net | *--------------------------------* From markk at netsol.com Tue Mar 12 14:12:30 2002 From: markk at netsol.com (Mark Kosters) Date: Tue, 12 Mar 2002 14:12:30 -0500 Subject: New Whois Display Format In-Reply-To: References: Message-ID: <20020312191230.GA9960@slam.admin.cto.netsol.com> Hi Ginny Thanks for doing this. I'm glad to see whois being improved on. I do have a couple of questions: 1) Is there going to be support for a IPv6 object? 2) Will there be support for query wildcards? 3) Do we really want to keep on using the magic characters "!", "*", ".", and "@"? The only one that has caught on is "!". 4) Should we have keywords for format displays? Thanks, Mark On Tue, Mar 12, 2002 at 11:00:20AM -0500, ginny listman wrote: > To coincide with the release of the new database and templates, ARIN has > begun development of a new Whois, in a modular format. The Output Module > will define the Whois display. It is our objective to keep the Whois > display in a easily readable format, while accomodating machine queries > by providing labels. > > The requirements outlined in this document are based on feedback from the > community. To provide a usable tool, we are requesting additional comments > at this time. Additionally, this format will be discussed at the Member > Meeting taking place April 7-10 in Las Vegas. > > Ginny Listman > Director of Engineering > ARIN > > ***** > > WHOIS REQUIREMENTS > > I. Uses of Whois > a. As a troubleshooting aid > b. For Applications that use resource assignment information > c. To show address space utilization > d. In the future, to display routing objects > > II. Privacy > a. The Whois database is a public resource. > > III. Formats > a. The "default" format is returned when querying Whois without any flags, > and there is a single record returned. For ease of use all items will > include labels. If a field does not exist, for example if a POC is > missing a email address, a label will not be displayed. Refer to the > attached "Whois Examples" for samples. The four object will be displayed > as follows: > > i. Point Of Contact - display all attributes of the POC > > Name: or > Handle: > Address: country code> > Phone: > Phone: > Email: > Email: > > ii. Organization - list the organization and all associated POCs > > Org Name: > Org ID: > Org Address: > > Org Handle: > Org Name: > Org Phone: <*> > Org Email: <*> > > Org Handle: > Org Name: > Org Phone: <*> > Org Email: <*> > > Note: Organization POC functions include Admin, Tech, Abuse and NOC. > > iii. Autonomous System - list the organization, the autonomous system, > POCs for the autonomous system, and POCs for the organization > > Org Name: > Org ID: > Org Address: > > AS Number: > AS Handle: > AS Name: > > AS Handle: > AS Name: > AS Phone: <*> > AS Email: <*> > > Org Handle: > Org Name: > Org Phone: <*> > Org Email: <*> > > Note: All POCs for the AS will be displayed. Only the organization's > Tech, Abuse and NOC POCs will be displayed. > > iv. IPv4 Network - list the organization, the network, POCs for the > network, POCs for the organization > > Org Name: > Org ID: > Org Address: > > CIDR Net Address: > Network Range: > Network Handle: > Network Name: > Can Sub-Delegate: > IN-ADDR: > IN-ADDR: > > Net Handle: > Net Name: > Net Phone: <*> > Net Email: <*> > > Net Handle: > Net Name: > Net Phone: <*> > Net Email: <*> > > Note: All POCs for the network will be displayed. Only the > organization's Tech, Abuse and NOC POCs will be displayed. > > * Indicates that multiple phone numbers or email addresses exist, > of which only the first is displayed. > > b. The "list" format is returned when querying Whois without specifying any > flags, and there are multiple records returned. Labels are not included. > The fields that are displayed are outlined below. > i. Point Of Contact - last name, first name, middle name, handle, one > email address, one office phone number > ii. Organization - Organization name, Organization ID > iii. Autonomous System - AS name, handle, AS number > iiii. Network - network name, handle, either a single CIDR block or network > range. > > c. In the future, we may provide the output in RPSL-like format. > > IV. Query by type. To narrow a search, a query can include a flag indicating > the object type as follows: > a. n will return only networks > b. a will return only autonomous systems > c. p will return only point-of-contacts > d. o will return only organizations > > V. Query by attribute. To narrow a search, a query can also include a flag > as follows: > a. ! will return the single match of the specified handle > b. @ will return the list of POCs with the specified domain name > in the email address > c. . will return a list of POCs, organizations, autonomous systems, > and/or networks that start with the specified name > > VI. Additional features > a. Sub-queries can be displayed using the % flag. The queried string > must return a single record to provide sub-query information. The > following objects have sub-query information: > i. Networks - display the reassignment/reallocation information in > list format, if data exists. > ii. Organizations - display the organization's resources information > in list format, if data exists. > b. Parentage can be displayed using the * flag. The queried string > must return a single record to provide parentage information. The > following objects have parentage information: > i. Networks - display the parentage in default format, if data exists. > ii. Organizations - will be implemented in future releases. > c. Other keywords > i. = will show default displays for all matches, > regardless of the number returned > ii. HELP will display the help screen > iii. . will show a list of all matches starting with the > given string. > iv. SUM will show list displays, even if there is only > one match. > d. The maximum number of records output is limited to 256. This may be > revised in future versions. > e. A future enhancement will include an relational lookup. For example, if > a POC is queried, the resouces associated with the POC would be > displayed. Content-Description: Whois Examples > WHOIS EXAMPLES > > The following information is used as sample data. > > 1. Organization ABC ISP is registered with 5 POCs - DEF-ARIN as the > administrative contact, ABC-TECH-ARIN and ABC-TECH2-ARIN as technical > contacts, ABC-NOC-ARIN as a NOC contact and ABC-ABU-ARIN as an abuse contact. > 2. ABC ISP has been assigned autonomous system 65000, and has ABUSE-ARIN as > an abuse contact. > 3. ABC ISP has been allocated two network blocks. The first 10.0.0.0/15 > does not have any resource POCs associated with it. It has two IN-ADDR servers. > 4. The second allocation 10.32.0.0/16 has SUP-ARIN as a technical contact and > NOC2-ARIN as a NOC contact. It has 4 IN-ADDR servers. > 5. ABC has reassigned 10.32.0.0-10.32.0.19 to XYZ ISP. XYZ has the minimal > amount of POCs - XYZ-TECH-ARIN as the organizational technical and XYZ-ADMI-ARIN > as the administrative. There are no POCs or IN-ADDR servers on the reallocation. > > Based on this information, the whois display would be as follows: > > 1. whois abc > Org Name: ABC ISP > Org ID: ABC > Org Address: 132 Main Street > Anytown, VA 22222 > US > > Org Admin Handle: DEF-ARIN > Org Admin Name: Foobar, Dwight E. > Org Admin Phone: +1-999-999-7777 (Office) * > Org Admin Email: foobar at example.net > > Org Tech Handle: ABC-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-999-999-9999 (Office) * > Org Tech Email: tech at example.net > > Org Tech Handle: ABC-TECH2-ARIN > Org Tech Name: Technical Support Manager > Org Tech Phone: +1-999-999-8888 (Office) > Org Tech Email: tech-mgr at example.net > > Org NOC Handle: ABC-NOC-ARIN > Org NOC Name: Network Operations Center > Org NOC Phone: +1-999-999-6666 (Office) * > Org NOC Email: noc at example.net > > Org Abuse Handle: ABC-ABU-ARIN > Org Abuse Name: Network Abuse Support > Org Abuse Phone: +1-999-999-5555 (Office) * > Org Abuse Email: abuse at example.net > > 2. whois 65000 > Org Name: ABC ISP > Org ID: ABC > > AS Number: 65000 > AS Handle: AS65000 > AS Name: ABC-ASN65000 > > AS Abuse Handle: ABUSE-ARIN > AS Abuse Name: AS 65000 Abuse Support > AS Abuse Phone: +1-703-000-0000 (Office) * > AS Abuse Email: abuse-65000 at example.net > > Org Tech Handle: ABC-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-999-999-9999 (Office) * > Org Tech Email: tech at example.net > > Org Tech Handle: ABC-TECH2-ARIN > Org Tech Name: Technical Support Manager > Org Tech Phone: +1-999-999-8888 (Office) > Org Tech Email: tech-mgr at example.net > > Org NOC Handle: ABC-NOC-ARIN > Org NOC Name: Network Operations Center > Org NOC Phone: +1-999-999-6666 (Office) * > Org NOC Email: noc at example.net > > Org Abuse Handle: ABC-ABU-ARIN > Org Abuse Name: Network Abuse Support > Org Abuse Phone: +1-999-999-5555 (Office) * > Org Abuse Email: abuse at example.net > > 3. whois 10.0.0.0 > Org Name: ABC ISP > Org ID: ABC > > CIDR Net Address: 10.0.0.0/15 > Network Range: 10.0.0.0-10.1.255.255 > Network Handle: NET-10-0-0-0 > Network Name: NETWORK-10 > Can Sub-Delegate: Y > IN-ADDR: ns.example.net > IN-ADDR: ns2.example.net > > Org Tech Handle: ABC-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-999-999-9999 (Office) * > Org Tech Email: tech at example.net > > Org Tech Handle: ABC-TECH2-ARIN > Org Tech Name: Technical Support Manager > Org Tech Phone: +1-999-999-8888 (Office) > Org Tech Email: tech-mgr at example.net > > Org NOC Handle: ABC-NOC-ARIN > Org NOC Name: Network Operations Center > Org NOC Phone: +1-999-999-6666 (Office) * > Org NOC Email: noc at example.net > > Org Abuse Handle: ABC-ABU-ARIN > Org Abuse Name: Network Abuse Support > Org Abuse Phone: +1-999-999-5555 (Office) * > Org Abuse Email: abuse at example.net > > 4. whois 10.32.0.0 > NETWORK-10.32 (NET-10-32-0-0) 10.32.0.0/16 > NET-10-32-RE (NET-10-32-0-0-2) 10.32.0.0-10.32.0.19 > > 5. whois NET-10-32-0-0-2 > Org Name: XYZ ISP > Org ID: XYZ > > CIDR Net Address: 10.32.0.0/28, 10.32.0.19/30 > Network Range: 10.32.0.0-10.32.0.19 > Network Handle: NET-10-32-0-0-2 > Network Name: NET-10-32-RE > Can Sub-Delegate: N > > Org Tech Handle: XYZ-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-777-777-7777 (Office) * > Org Tech Email: tech-xyz at example.net > > 6. whois ABC-NOC-ARIN > Name: Network Operations Center > Handle: ABC-NOC-ARIN > Address: ABC ISP > 132 Main Street > Anytown, VA 22222 > US > Phone: +1-999-999-6666 (Office) > Phone: +1-888-888-8888 (Mobile) > Phone: +1-777-777-7777 (Fax) > Email: noc at example.net -- Mark Kosters markk at netsol.com Verisign Applied Research From dbarger at swbell.net Tue Mar 12 14:26:34 2002 From: dbarger at swbell.net (Dave Barger) Date: Tue, 12 Mar 2002 13:26:34 -0600 Subject: New Whois Display Format In-Reply-To: Message-ID: <5.0.0.25.2.20020312131946.00a645a8@postoffice.swbell.net> Very, Very nice. The labels will make parsing through the output much easier. Question: Currently, when doing a Whois query, and the netblock is not found, Whois will display the info for the ISP's large netblock allocation from which the netblock originates. Will the format of this output change? This is important, in that our automation looks for the "NON-PORTABLE" character string on the page as an indication that a netblock has no specific Whois entry. Thanks. ---------------------------------- Dave Barger Director - Network Engineering IP Management SBC Internet Services ---------------------------------- At 10:00 AM 3/12/2002, ginny listman wrote: >To coincide with the release of the new database and templates, ARIN has >begun development of a new Whois, in a modular format. The Output Module >will define the Whois display. It is our objective to keep the Whois >display in a easily readable format, while accomodating machine queries >by providing labels. > >The requirements outlined in this document are based on feedback from the >community. To provide a usable tool, we are requesting additional comments >at this time. Additionally, this format will be discussed at the Member >Meeting taking place April 7-10 in Las Vegas. > >Ginny Listman >Director of Engineering >ARIN > >***** > > WHOIS REQUIREMENTS > >I. Uses of Whois > a. As a troubleshooting aid > b. For Applications that use resource assignment information > c. To show address space utilization > d. In the future, to display routing objects > >II. Privacy > a. The Whois database is a public resource. > >III. Formats > a. The "default" format is returned when querying Whois without any > flags, > and there is a single record returned. For ease of use all items will > include labels. If a field does not exist, for example if a POC is > missing a email address, a label will not be displayed. Refer to the > attached "Whois Examples" for samples. The four object will be > displayed > as follows: > > i. Point Of Contact - display all attributes of the POC > > Name: or > Handle: > Address: country code> > Phone: > Phone: > Email: > Email: > > ii. Organization - list the organization and all associated POCs > > Org Name: > Org ID: > Org Address: > > Org Handle: > Org Name: > Org Phone: <*> > Org Email: <*> > > Org Handle: > Org Name: > Org Phone: <*> > Org Email: <*> > > Note: Organization POC functions include Admin, Tech, Abuse and NOC. > > iii. Autonomous System - list the organization, the autonomous system, > POCs for the autonomous system, and POCs for the organization > > Org Name: > Org ID: > Org Address: > > AS Number: > AS Handle: > AS Name: > > AS Handle: > AS Name: > AS Phone: <*> > AS Email: <*> > > Org Handle: > Org Name: > Org Phone: <*> > Org Email: <*> > > Note: All POCs for the AS will be displayed. Only the organization's > Tech, Abuse and NOC POCs will be displayed. > > iv. IPv4 Network - list the organization, the network, POCs for the > network, POCs for the organization > > Org Name: > Org ID: > Org Address: > > CIDR Net Address: > Network Range: > Network Handle: > Network Name: > Can Sub-Delegate: > IN-ADDR: > IN-ADDR: > > Net Handle: > Net Name: > Net Phone: <*> > Net Email: <*> > > Net Handle: > Net Name: > Net Phone: <*> > Net Email: <*> > > Note: All POCs for the network will be displayed. Only the > organization's Tech, Abuse and NOC POCs will be displayed. > > * Indicates that multiple phone numbers or email addresses exist, > of which only the first is displayed. > > b. The "list" format is returned when querying Whois without > specifying any > flags, and there are multiple records returned. Labels are not > included. > The fields that are displayed are outlined below. > i. Point Of Contact - last name, first name, middle name, handle, one > email address, one office phone number > ii. Organization - Organization name, Organization ID > iii. Autonomous System - AS name, handle, AS number > iiii. Network - network name, handle, either a single CIDR block or > network > range. > > c. In the future, we may provide the output in RPSL-like format. > >IV. Query by type. To narrow a search, a query can include a flag indicating > the object type as follows: > a. n will return only networks > b. a will return only autonomous systems > c. p will return only point-of-contacts > d. o will return only organizations > >V. Query by attribute. To narrow a search, a query can also include a flag > as follows: > a. ! will return the single match of the specified handle > b. @ will return the list of POCs with the specified domain > name > in the email address > c. . will return a list of POCs, organizations, autonomous systems, > and/or networks that start with the specified name > >VI. Additional features > a. Sub-queries can be displayed using the % flag. The queried string > must return a single record to provide sub-query information. The > following objects have sub-query information: > i. Networks - display the reassignment/reallocation information in > list format, if data exists. > ii. Organizations - display the organization's resources information > in list format, if data exists. > b. Parentage can be displayed using the * flag. The queried string > must return a single record to provide parentage information. The > following objects have parentage information: > i. Networks - display the parentage in default format, if data exists. > ii. Organizations - will be implemented in future releases. > c. Other keywords > i. = will show default displays for all matches, > regardless of the number returned > ii. HELP will display the help screen > iii. . will show a list of all matches starting with the > given string. > iv. SUM will show list displays, even if there is only > one match. > d. The maximum number of records output is limited to 256. This may be > revised in future versions. > e. A future enhancement will include an relational lookup. For > example, if > a POC is queried, the resouces associated with the POC would be > displayed. > WHOIS EXAMPLES > >The following information is used as sample data. > >1. Organization ABC ISP is registered with 5 POCs - DEF-ARIN as the >administrative contact, ABC-TECH-ARIN and ABC-TECH2-ARIN as technical >contacts, ABC-NOC-ARIN as a NOC contact and ABC-ABU-ARIN as an abuse contact. >2. ABC ISP has been assigned autonomous system 65000, and has ABUSE-ARIN as >an abuse contact. >3. ABC ISP has been allocated two network blocks. The first 10.0.0.0/15 >does not have any resource POCs associated with it. It has two IN-ADDR >servers. >4. The second allocation 10.32.0.0/16 has SUP-ARIN as a technical contact and >NOC2-ARIN as a NOC contact. It has 4 IN-ADDR servers. >5. ABC has reassigned 10.32.0.0-10.32.0.19 to XYZ ISP. XYZ has the minimal >amount of POCs - XYZ-TECH-ARIN as the organizational technical and >XYZ-ADMI-ARIN >as the administrative. There are no POCs or IN-ADDR servers on the >reallocation. > >Based on this information, the whois display would be as follows: > >1. whois abc > Org Name: ABC ISP > Org ID: ABC > Org Address: 132 Main Street > Anytown, VA 22222 > US > > Org Admin Handle: DEF-ARIN > Org Admin Name: Foobar, Dwight E. > Org Admin Phone: +1-999-999-7777 (Office) * > Org Admin Email: foobar at example.net > > Org Tech Handle: ABC-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-999-999-9999 (Office) * > Org Tech Email: tech at example.net > > Org Tech Handle: ABC-TECH2-ARIN > Org Tech Name: Technical Support Manager > Org Tech Phone: +1-999-999-8888 (Office) > Org Tech Email: tech-mgr at example.net > > Org NOC Handle: ABC-NOC-ARIN > Org NOC Name: Network Operations Center > Org NOC Phone: +1-999-999-6666 (Office) * > Org NOC Email: noc at example.net > > Org Abuse Handle: ABC-ABU-ARIN > Org Abuse Name: Network Abuse Support > Org Abuse Phone: +1-999-999-5555 (Office) * > Org Abuse Email: abuse at example.net > >2. whois 65000 > Org Name: ABC ISP > Org ID: ABC > > AS Number: 65000 > AS Handle: AS65000 > AS Name: ABC-ASN65000 > > AS Abuse Handle: ABUSE-ARIN > AS Abuse Name: AS 65000 Abuse Support > AS Abuse Phone: +1-703-000-0000 (Office) * > AS Abuse Email: abuse-65000 at example.net > > Org Tech Handle: ABC-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-999-999-9999 (Office) * > Org Tech Email: tech at example.net > > Org Tech Handle: ABC-TECH2-ARIN > Org Tech Name: Technical Support Manager > Org Tech Phone: +1-999-999-8888 (Office) > Org Tech Email: tech-mgr at example.net > > Org NOC Handle: ABC-NOC-ARIN > Org NOC Name: Network Operations Center > Org NOC Phone: +1-999-999-6666 (Office) * > Org NOC Email: noc at example.net > > Org Abuse Handle: ABC-ABU-ARIN > Org Abuse Name: Network Abuse Support > Org Abuse Phone: +1-999-999-5555 (Office) * > Org Abuse Email: abuse at example.net > >3. whois 10.0.0.0 > Org Name: ABC ISP > Org ID: ABC > > CIDR Net Address: 10.0.0.0/15 > Network Range: 10.0.0.0-10.1.255.255 > Network Handle: NET-10-0-0-0 > Network Name: NETWORK-10 > Can Sub-Delegate: Y > IN-ADDR: ns.example.net > IN-ADDR: ns2.example.net > > Org Tech Handle: ABC-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-999-999-9999 (Office) * > Org Tech Email: tech at example.net > > Org Tech Handle: ABC-TECH2-ARIN > Org Tech Name: Technical Support Manager > Org Tech Phone: +1-999-999-8888 (Office) > Org Tech Email: tech-mgr at example.net > > Org NOC Handle: ABC-NOC-ARIN > Org NOC Name: Network Operations Center > Org NOC Phone: +1-999-999-6666 (Office) * > Org NOC Email: noc at example.net > > Org Abuse Handle: ABC-ABU-ARIN > Org Abuse Name: Network Abuse Support > Org Abuse Phone: +1-999-999-5555 (Office) * > Org Abuse Email: abuse at example.net > >4. whois 10.32.0.0 > NETWORK-10.32 (NET-10-32-0-0) 10.32.0.0/16 > NET-10-32-RE (NET-10-32-0-0-2) 10.32.0.0-10.32.0.19 > >5. whois NET-10-32-0-0-2 > Org Name: XYZ ISP > Org ID: XYZ > > CIDR Net Address: 10.32.0.0/28, 10.32.0.19/30 > Network Range: 10.32.0.0-10.32.0.19 > Network Handle: NET-10-32-0-0-2 > Network Name: NET-10-32-RE > Can Sub-Delegate: N > > Org Tech Handle: XYZ-TECH-ARIN > Org Tech Name: Technical Support > Org Tech Phone: +1-777-777-7777 (Office) * > Org Tech Email: tech-xyz at example.net > >6. whois ABC-NOC-ARIN > Name: Network Operations Center > Handle: ABC-NOC-ARIN > Address: ABC ISP > 132 Main Street > Anytown, VA 22222 > US > Phone: +1-999-999-6666 (Office) > Phone: +1-888-888-8888 (Mobile) > Phone: +1-777-777-7777 (Fax) > Email: noc at example.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jiml at mrtg.noc.adelphia.net Tue Mar 12 14:31:20 2002 From: jiml at mrtg.noc.adelphia.net (James W. Laferriere) Date: Tue, 12 Mar 2002 14:31:20 -0500 (Eastern Standard Time) Subject: New Whois Display Format In-Reply-To: <20020312191230.GA9960@slam.admin.cto.netsol.com> Message-ID: Hello All , On Tue, 12 Mar 2002, Mark Kosters wrote: > Hi Ginny > Thanks for doing this. I'm glad to see whois being improved on. > I do have a couple of questions: > 1) Is there going to be support for a IPv6 object? > 2) Will there be support for query wildcards? > 3) Do we really want to keep on using the magic characters "!", "*", ".", and > "@"? The only one that has caught on is "!". I'll register a vote for we keep them . JimL > 4) Should we have keywords for format displays? > > Thanks, > Mark James W. Laferriere Research Engineer jlaferriere at adelphia.net 814.260.3697 Voice 814.260.3760 Fax From ginny at arin.net Tue Mar 12 15:37:31 2002 From: ginny at arin.net (ginny listman) Date: Tue, 12 Mar 2002 15:37:31 -0500 (EST) Subject: New Whois Display Format In-Reply-To: Message-ID: On Tue, 12 Mar 2002, David R Huberman wrote: > First off, the examples look fantastic. THe utility of the new layout is > excellent. > > Question: For downstream reassignments: > > 1) Can upstreams put themselves in the ORG ID? Only if they plan on using the reassigned networks for internal purposes. > 2) Can upstream designate their POC handle(s) for > reassignment? (Meaning ABC delegating to XYZ puts > ABC contact handle in for XYZ reassignment record.) If you are reassigning to an end user, and there are no inaddr servers, POC information is not required. In fact, we would recommend that you use the reassign-simple template, where POCs are not permitted - defaults to the upstream's. The reason ARIN would need POC information is if the downstream can further sub-delegate, or if they have inaddr servers. We (and probably the community) would want to deal directly with those responsible for the network. Therefore, the POCs should be from the downstream organization. > 3) Can downstream org put NOC/Abuse/Tech/Admin contacts > into their ORG ID for display in their reassigned > netblocks? Absolutely. > > I just want to be clear on these. THe answers seem obvious, but... :> > > /david > > > *--------------------------------* > | Global Crossing API | > | Manager, Global IP Addressing | > | (703) 627-5800 | > | huberman at gblx.net | > *--------------------------------* > From ginny at arin.net Tue Mar 12 16:28:26 2002 From: ginny at arin.net (ginny listman) Date: Tue, 12 Mar 2002 16:28:26 -0500 (EST) Subject: New Whois Display Format In-Reply-To: <20020312191230.GA9960@slam.admin.cto.netsol.com> Message-ID: On Tue, 12 Mar 2002, Mark Kosters wrote: > Hi Ginny > > Thanks for doing this. I'm glad to see whois being improved on. > I do have a couple of questions: > > 1) Is there going to be support for a IPv6 object? Yes. Although we haven't outlined an example, IPv6 objects will be displayed in a similar fashion as IPv4 objects. > 2) Will there be support for query wildcards? The initial release will support the "magic" characters you speak of below. We will consider any enhancements recommended by the membership that will improve the usefulness of Whois. > 3) Do we really want to keep on using the magic characters "!", "*", ".", and > "@"? The only one that has caught on is "!". We can do some analysis as to how frequently these characters have been used. However, we will be making improvements that should increase their usefulness. For example, ARIN currently does not have the ability to show parentage (* flag). The new version will. > 4) Should we have keywords for format displays? > I'm not sure if I understand the question. The initial has = for default and SUM for list display. Other formats are out of scope for this release. > Thanks, > Mark > > On Tue, Mar 12, 2002 at 11:00:20AM -0500, ginny listman wrote: > > To coincide with the release of the new database and templates, ARIN has > > begun development of a new Whois, in a modular format. The Output Module > > will define the Whois display. It is our objective to keep the Whois > > display in a easily readable format, while accomodating machine queries > > by providing labels. > > > > The requirements outlined in this document are based on feedback from the > > community. To provide a usable tool, we are requesting additional comments > > at this time. Additionally, this format will be discussed at the Member > > Meeting taking place April 7-10 in Las Vegas. > > > > Ginny Listman > > Director of Engineering > > ARIN > > > > ***** > > > > WHOIS REQUIREMENTS > > > > I. Uses of Whois > > a. As a troubleshooting aid > > b. For Applications that use resource assignment information > > c. To show address space utilization > > d. In the future, to display routing objects > > > > II. Privacy > > a. The Whois database is a public resource. > > > > III. Formats > > a. The "default" format is returned when querying Whois without any flags, > > and there is a single record returned. For ease of use all items will > > include labels. If a field does not exist, for example if a POC is > > missing a email address, a label will not be displayed. Refer to the > > attached "Whois Examples" for samples. The four object will be displayed > > as follows: > > > > i. Point Of Contact - display all attributes of the POC > > > > Name: or > > Handle: > > Address: > country code> > > Phone: > > Phone: > > Email: > > Email: > > > > ii. Organization - list the organization and all associated POCs > > > > Org Name: > > Org ID: > > Org Address: > > > > Org Handle: > > Org Name: > > Org Phone: <*> > > Org Email: <*> > > > > Org Handle: > > Org Name: > > Org Phone: <*> > > Org Email: <*> > > > > Note: Organization POC functions include Admin, Tech, Abuse and NOC. > > > > iii. Autonomous System - list the organization, the autonomous system, > > POCs for the autonomous system, and POCs for the organization > > > > Org Name: > > Org ID: > > Org Address: > > > > AS Number: > > AS Handle: > > AS Name: > > > > AS Handle: > > AS Name: > > AS Phone: <*> > > AS Email: <*> > > > > Org Handle: > > Org Name: > > Org Phone: <*> > > Org Email: <*> > > > > Note: All POCs for the AS will be displayed. Only the organization's > > Tech, Abuse and NOC POCs will be displayed. > > > > iv. IPv4 Network - list the organization, the network, POCs for the > > network, POCs for the organization > > > > Org Name: > > Org ID: > > Org Address: > > > > CIDR Net Address: > > Network Range: > > Network Handle: > > Network Name: > > Can Sub-Delegate: > > IN-ADDR: > > IN-ADDR: > > > > Net Handle: > > Net Name: > > Net Phone: <*> > > Net Email: <*> > > > > Net Handle: > > Net Name: > > Net Phone: <*> > > Net Email: <*> > > > > Note: All POCs for the network will be displayed. Only the > > organization's Tech, Abuse and NOC POCs will be displayed. > > > > * Indicates that multiple phone numbers or email addresses exist, > > of which only the first is displayed. > > > > b. The "list" format is returned when querying Whois without specifying any > > flags, and there are multiple records returned. Labels are not included. > > The fields that are displayed are outlined below. > > i. Point Of Contact - last name, first name, middle name, handle, one > > email address, one office phone number > > ii. Organization - Organization name, Organization ID > > iii. Autonomous System - AS name, handle, AS number > > iiii. Network - network name, handle, either a single CIDR block or network > > range. > > > > c. In the future, we may provide the output in RPSL-like format. > > > > IV. Query by type. To narrow a search, a query can include a flag indicating > > the object type as follows: > > a. n will return only networks > > b. a will return only autonomous systems > > c. p will return only point-of-contacts > > d. o will return only organizations > > > > V. Query by attribute. To narrow a search, a query can also include a flag > > as follows: > > a. ! will return the single match of the specified handle > > b. @ will return the list of POCs with the specified domain name > > in the email address > > c. . will return a list of POCs, organizations, autonomous systems, > > and/or networks that start with the specified name > > > > VI. Additional features > > a. Sub-queries can be displayed using the % flag. The queried string > > must return a single record to provide sub-query information. The > > following objects have sub-query information: > > i. Networks - display the reassignment/reallocation information in > > list format, if data exists. > > ii. Organizations - display the organization's resources information > > in list format, if data exists. > > b. Parentage can be displayed using the * flag. The queried string > > must return a single record to provide parentage information. The > > following objects have parentage information: > > i. Networks - display the parentage in default format, if data exists. > > ii. Organizations - will be implemented in future releases. > > c. Other keywords > > i. = will show default displays for all matches, > > regardless of the number returned > > ii. HELP will display the help screen > > iii. . will show a list of all matches starting with the > > given string. > > iv. SUM will show list displays, even if there is only > > one match. > > d. The maximum number of records output is limited to 256. This may be > > revised in future versions. > > e. A future enhancement will include an relational lookup. For example, if > > a POC is queried, the resouces associated with the POC would be > > displayed. > > Content-Description: Whois Examples > > WHOIS EXAMPLES > > > > The following information is used as sample data. > > > > 1. Organization ABC ISP is registered with 5 POCs - DEF-ARIN as the > > administrative contact, ABC-TECH-ARIN and ABC-TECH2-ARIN as technical > > contacts, ABC-NOC-ARIN as a NOC contact and ABC-ABU-ARIN as an abuse contact. > > 2. ABC ISP has been assigned autonomous system 65000, and has ABUSE-ARIN as > > an abuse contact. > > 3. ABC ISP has been allocated two network blocks. The first 10.0.0.0/15 > > does not have any resource POCs associated with it. It has two IN-ADDR servers. > > 4. The second allocation 10.32.0.0/16 has SUP-ARIN as a technical contact and > > NOC2-ARIN as a NOC contact. It has 4 IN-ADDR servers. > > 5. ABC has reassigned 10.32.0.0-10.32.0.19 to XYZ ISP. XYZ has the minimal > > amount of POCs - XYZ-TECH-ARIN as the organizational technical and XYZ-ADMI-ARIN > > as the administrative. There are no POCs or IN-ADDR servers on the reallocation. > > > > Based on this information, the whois display would be as follows: > > > > 1. whois abc > > Org Name: ABC ISP > > Org ID: ABC > > Org Address: 132 Main Street > > Anytown, VA 22222 > > US > > > > Org Admin Handle: DEF-ARIN > > Org Admin Name: Foobar, Dwight E. > > Org Admin Phone: +1-999-999-7777 (Office) * > > Org Admin Email: foobar at example.net > > > > Org Tech Handle: ABC-TECH-ARIN > > Org Tech Name: Technical Support > > Org Tech Phone: +1-999-999-9999 (Office) * > > Org Tech Email: tech at example.net > > > > Org Tech Handle: ABC-TECH2-ARIN > > Org Tech Name: Technical Support Manager > > Org Tech Phone: +1-999-999-8888 (Office) > > Org Tech Email: tech-mgr at example.net > > > > Org NOC Handle: ABC-NOC-ARIN > > Org NOC Name: Network Operations Center > > Org NOC Phone: +1-999-999-6666 (Office) * > > Org NOC Email: noc at example.net > > > > Org Abuse Handle: ABC-ABU-ARIN > > Org Abuse Name: Network Abuse Support > > Org Abuse Phone: +1-999-999-5555 (Office) * > > Org Abuse Email: abuse at example.net > > > > 2. whois 65000 > > Org Name: ABC ISP > > Org ID: ABC > > > > AS Number: 65000 > > AS Handle: AS65000 > > AS Name: ABC-ASN65000 > > > > AS Abuse Handle: ABUSE-ARIN > > AS Abuse Name: AS 65000 Abuse Support > > AS Abuse Phone: +1-703-000-0000 (Office) * > > AS Abuse Email: abuse-65000 at example.net > > > > Org Tech Handle: ABC-TECH-ARIN > > Org Tech Name: Technical Support > > Org Tech Phone: +1-999-999-9999 (Office) * > > Org Tech Email: tech at example.net > > > > Org Tech Handle: ABC-TECH2-ARIN > > Org Tech Name: Technical Support Manager > > Org Tech Phone: +1-999-999-8888 (Office) > > Org Tech Email: tech-mgr at example.net > > > > Org NOC Handle: ABC-NOC-ARIN > > Org NOC Name: Network Operations Center > > Org NOC Phone: +1-999-999-6666 (Office) * > > Org NOC Email: noc at example.net > > > > Org Abuse Handle: ABC-ABU-ARIN > > Org Abuse Name: Network Abuse Support > > Org Abuse Phone: +1-999-999-5555 (Office) * > > Org Abuse Email: abuse at example.net > > > > 3. whois 10.0.0.0 > > Org Name: ABC ISP > > Org ID: ABC > > > > CIDR Net Address: 10.0.0.0/15 > > Network Range: 10.0.0.0-10.1.255.255 > > Network Handle: NET-10-0-0-0 > > Network Name: NETWORK-10 > > Can Sub-Delegate: Y > > IN-ADDR: ns.example.net > > IN-ADDR: ns2.example.net > > > > Org Tech Handle: ABC-TECH-ARIN > > Org Tech Name: Technical Support > > Org Tech Phone: +1-999-999-9999 (Office) * > > Org Tech Email: tech at example.net > > > > Org Tech Handle: ABC-TECH2-ARIN > > Org Tech Name: Technical Support Manager > > Org Tech Phone: +1-999-999-8888 (Office) > > Org Tech Email: tech-mgr at example.net > > > > Org NOC Handle: ABC-NOC-ARIN > > Org NOC Name: Network Operations Center > > Org NOC Phone: +1-999-999-6666 (Office) * > > Org NOC Email: noc at example.net > > > > Org Abuse Handle: ABC-ABU-ARIN > > Org Abuse Name: Network Abuse Support > > Org Abuse Phone: +1-999-999-5555 (Office) * > > Org Abuse Email: abuse at example.net > > > > 4. whois 10.32.0.0 > > NETWORK-10.32 (NET-10-32-0-0) 10.32.0.0/16 > > NET-10-32-RE (NET-10-32-0-0-2) 10.32.0.0-10.32.0.19 > > > > 5. whois NET-10-32-0-0-2 > > Org Name: XYZ ISP > > Org ID: XYZ > > > > CIDR Net Address: 10.32.0.0/28, 10.32.0.19/30 > > Network Range: 10.32.0.0-10.32.0.19 > > Network Handle: NET-10-32-0-0-2 > > Network Name: NET-10-32-RE > > Can Sub-Delegate: N > > > > Org Tech Handle: XYZ-TECH-ARIN > > Org Tech Name: Technical Support > > Org Tech Phone: +1-777-777-7777 (Office) * > > Org Tech Email: tech-xyz at example.net > > > > 6. whois ABC-NOC-ARIN > > Name: Network Operations Center > > Handle: ABC-NOC-ARIN > > Address: ABC ISP > > 132 Main Street > > Anytown, VA 22222 > > US > > Phone: +1-999-999-6666 (Office) > > Phone: +1-888-888-8888 (Mobile) > > Phone: +1-777-777-7777 (Fax) > > Email: noc at example.net > > > -- > > Mark Kosters markk at netsol.com Verisign Applied Research > From cathym at arin.net Tue Mar 12 16:57:18 2002 From: cathym at arin.net (Cathy Murphy) Date: Tue, 12 Mar 2002 16:57:18 -0500 (EST) Subject: New Whois Display Format In-Reply-To: <5.0.0.25.2.20020312131946.00a645a8@postoffice.swbell.net> Message-ID: On Tue, 12 Mar 2002, Dave Barger wrote: > Question: > > Currently, when doing a Whois query, and the netblock is not found, > Whois will display the info for the ISP's large netblock allocation from > which the netblock originates. > > Will the format of this output change? This is important, in that our > automation looks for the "NON-PORTABLE" character string on the page as > an indication that a netblock has no specific Whois entry. Yes, the format will change somewhat, but mostly on newer records. That information is currently inserted based on an instruction in the ISP network request template, and a comment is added to the network registration record if the requestor indicates that the addresses are to be "non-portable". So, all existing records containing this comment will retain this comment and will show up in a query for the network registration record. However, the new templates will no longer ask for this item of information. During the template re-design process, it was decided that the whole notion of portability was being misunderstood. New network requests can still insert this into the comment field if they so choose, but we are now providing another mechanism to determine the type of address space being issued or sub-delegated. Each network registration record will now contain the label "Can Sub-Delegate:", followed by Y for yes or N for no. All ARIN allocations and reallocation SWIPs will indicate that those addresses can be further sub-delegated. All ARIN end-user assignments and reassignment SWIPs will indicate no sub-delegation. Hope this clarifies the situation. Thanks for your feedback. Regards, Cathy Murphy Principal Software Engineer American Registry for Internet Numbers (ARIN) +1 703 227 9875 From richardj at arin.net Wed Mar 13 11:06:31 2002 From: richardj at arin.net (Richard Jimmerson) Date: Wed, 13 Mar 2002 11:06:31 -0500 Subject: WHOIS data (recent discussion) In-Reply-To: Message-ID: <004c01c1caa9$0a419b00$ecfc95c0@cobalt> Hello Derek, Thank you for your email. > What sort of help are we looking for here? :) This issue has been added to the agenda of the upcoming ARIN public policy meeting. After receiving the initial feedback at the meeting regarding this issue, there will also be discussion on ARIN's public policy and database working group mailing lists. The help needed here is community feedback at the public policy meeting and on the ARIN mailing lists. Thank you again for your interest. Best Regards, Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) > -----Original Message----- > From: dbwg-request at arin.net [mailto:dbwg-request at arin.net] On > Behalf Of Derek Balling > Sent: Monday, March 11, 2002 9:18 PM > To: dbwg at arin.net > Subject: WHOIS data (recent discussion) > > > I read Allen's message (which he forwarded to the RFC-Ignorant > project's mailing list) about WHOIS policy proposals, etc. etc. > > As the "head stick wielder" for trying to bring lame POC info in line > (and, I'd like to hope, more successful than random folks complaining > to delegation-holders, which we've all seen via experience hasn't > been very effective historically), I do have a vested interest in > trying to help out wherever possible in this. > > What sort of help are we looking for here? :) > > D > > > -- > +---------------------+-----------------------------------------+ > | dredd at megacity.org | "Thou art the ruins of the noblest man | > | Derek J. Balling | That ever lived in the tide of times. | > | | Woe to the hand that shed this costly | > | | blood" - Julius Caesar Act 3, Scene 1 | > +---------------------+-----------------------------------------+ > From ginny at arin.net Thu Mar 21 13:55:21 2002 From: ginny at arin.net (ginny listman) Date: Thu, 21 Mar 2002 13:55:21 -0500 (EST) Subject: Whois Update Message-ID: Based on feedback, the Whois Requirements Document has been modified/ clarified in the following ways: 1. When displaying a network, the "Network Range" is displayed before the "CIDR Notation". 2. Displays that contain postal addresses, will have a "Country Code" label. This applies to the Org and POC objects. 3. All objects can have comments. The "Comments" will be displayed for the queried object only. For example, when querying a network, only the network's comments will be displayed. If there are comments on the Org or POC, they will not be displayed for this query. 4. Like the current version of WHOIS, the "Last Updated:" will appear for each query. 5. Like the current version of WHOIS, the "Database last updated" will appear for each query. 6. The "Registration Date:" will be displayed for each object. 7. Although not explicitly stated, WHOIS will not accept queries containing a CIDR prefix. However, if there is enough demand from the community, it will be added as a feature in the future. 8. There was some discussion as to whether or not whois should be using meta-characters (@ ! * % . =) for flags. We have done some analysis of which of these flags have been used, and actually all of them are being used. And as suspected, the bang (!) is the most frequently used one. We will be releasing the stats to the list sometime next week. 9. The new database structure introduces the new org object, that contains the organization name and address, and is based on the maintainer ID. Since an existing system permits a maintainer to have multiple resources with different names and addresses, the WHOIS display may contain multiple names/addresses. These duplicate name/address records will be part of the cleanup project to take place immediately following conversion. 10. To aid in cleanup, when querying an AS or network that has an org record with multiple name/addresses, the display will contain a note indicating that cleanup is necessary. 11. The network display will include 'Upstream Network Handle' if appropriate. 12. Networks displayed in the list format will include the Org Name. 13. Autonomous systems displayed in the list format will include the Org Name. 14. The default display of networks and autonomous systems does NOT include the Org Address. 15. There will be a separate display for Customer records. (See example #6) 16. Since there are some AS blocks in the database, the label has been changed to AS Number[s], where the 's' will be display only if there is a range. 17. Although not explicitly stated, the new whois will no longer accept name server as a valid query. -------------- next part -------------- WHOIS SERVER REQUIREMENTS I. Uses of Whois a. As a troubleshooting aid b. For applications that use resource assignment information c. To show address space utilization d. In the future, to display routing objects II. Privacy a. The Whois database is a public resource. III. Formats a. The "default" format is displayed when querying Whois without any flags, and there is a single record returned. For ease of use all items will include labels. If a field does not exist, for example if a POC is missing an email address, a label will not be displayed. Refer to the attached "Whois Examples" for samples. The five objects will be displayed as follows: i. Point Of Contact - display all attributes of the POC Name: or Handle: Company Name: Address: Country Code: Phone: Phone: Email: Email: Comments: Registration Date: Last Updated: ii. Organization - list the organization and all associated POCs Org Name: Org ID: Org Address: Country Code: Comments: Registration Date: Last Updated: Org Handle: Org Name: Org Phone: <*> Org Email: <*> Org Handle: Org Name: Org Phone: <*> Org Email: <*> Note: Organization POC functions include Admin, Tech, Abuse and NOC. iii. Customer - list the customer Customer Name: Customer Number: Customer Address: Country Code: Comments: Registration Date: Last Updated: Note: Customers do not have POCs. iv. Autonomous System - list the organization, the autonomous system, POCs for the autonomous system, and POCs for the organization Org Name: Org ID: AS Number[s]: AS Name: AS Handle: Comments: Registration Date: Last Updated: AS Handle: AS Name: AS Phone: <*> AS Email: <*> Org Handle: Org Name: Org Phone: <*> Org Email: <*> Note: All POCs for the AS will be displayed. Only the organization's Tech, Abuse and NOC POCs will be displayed. v. Organization IPv4 Network - list the organization, the network, POCs for the network, POCs for the organization Org Name: Org ID: Network Range: CIDR Notation: Network Name: Network Handle: Upstream Network Handle: Can Sub-Delegate: IN-ADDR: IN-ADDR: Comments: Registration Date: Last Updated: Net Handle: Net Name: Net Phone: <*> Net Email: <*> Org Handle: Org Name: Org Phone: <*> Org Email: <*> Note: All POCs for the network will be displayed. Only the organization's Tech, Abuse and NOC POCs will be displayed. vi. Customer IPv4 Network - list the customer, the network Customer Name: Customer Number: Network Range: CIDR Notation: Network Name: Network Handle: Upstream Network Handle: Can Sub-Delegate: Comments: Registration Date: Last Updated: Note: Customer records will not contain POCs. *Indicates that multiple phone numbers or email addresses exist, of which only the first is displayed. b. The "list" format is returned when querying Whois without specifying any flags, and there are multiple records returned. Labels are not included. The fields that are displayed are outlined below. i. Point Of Contact - last, first and middle name or role name, handle, one email address, one office phone number ii. Organization - organization name, organization ID iii. Customer - customer name, customer number iv. Autonomous System - organization name, AS name, handle, AS number v. Network - organization name, network name, handle, either a single CIDR block or network range. c. In the future, we may provide the output in RPSL-like, or other formats. IV. Query by type. To narrow a search, a query can include one of the listed flags (either upper or lower case) to indicate the object type as follows: a. a will return only autonomous systems b. c will return only customers c. n will return only networks d. o will return only organizations e. p will return only point-of-contacts V. Query by attribute. To narrow a search, a query can also include a flag as follows: a. ! will return the single match of the specified handle b. @ will return the list of POCs with the specified domain name in the email address c. . will return a list of POCs, organizations, autonomous systems, and/or networks that start with the specified name VI. Additional features a. Sub-queries can be displayed using the % flag. The queried string must return a single record to provide sub-query information. The following objects have sub-query information: i. Networks - display the reassignment/reallocation information in list format, if data exists. ii. Organizations - display the organization's resources information in list format, if data exists. b. Parentage can be displayed using the * flag. The queried string must return a single record to provide parentage information. The following objects have parentage information: i. Networks - display the parentage in default format, if data exists. ii. Organizations - will be implemented in future releases. c. Other keywords i. = will show default displays for all matches, regardless of the number returned ii. HELP will display the help screen iii. . will show a list of all matches starting with the given string. iv. SUM will show list displays, even if there is only one match. d. The maximum number of records output is limited to 256. This may be revised in future versions. e. A future enhancement will include a relational lookup. For example, if a POC is queried, the resources associated with the POC would be displayed. -------------- next part -------------- WHOIS EXAMPLES The following information is used as sample data. 1. Organization ABC ISP is registered with 5 POCs - DEF-ARIN as the administrative contact, ABC-TECH-ARIN and ABC-TECH2-ARIN as technical contacts, ABC-NOC-ARIN as a NOC contact and ABC-ABU-ARIN as an abuse contact. 2. ABC ISP has been assigned autonomous system number 65000, and has ABUSE-ARIN as a resource abuse contact. 3. ABC ISP has been allocated two network blocks. The first 10.0.0.0/15 does not have any resource POCs associated with it. It has two IN-ADDR servers. 4. The second allocation 10.32.0.0/17 has SUP-ARIN as a technical contact and NOC2-ARIN as a NOC contact. It has 4 IN-ADDR name servers. 5. ABC has reallocated 10.32.0.0-10.32.0.19 to XYZ ISP. XYZ has the minimal amount of POCs - XYZ-TECH-ARIN as the organizational technical and XYZ-ADMI-ARIN as the administrative. There are no POCs or IN-ADDR name servers on the reallocation. 6. XYZ has reassigned 10.32.0.0-10.32.0.7 to Customer Joe User. Since it was SWIPed with a reassign simple, no POCs or inaddrs are allowed. Based on this information, the whois display would be as follows: 1. whois abc Org Name: ABC ISP Org ID: ABC Org Address: 132 Main Street Anytown, VA 22222 Country Code: US Registration Date: 1999-01-07 Last Updated: 2001-12-30 Org Admin Handle: DEF-ARIN Org Admin Name: Foobar, Dwight E. Org Admin Phone: +1-999-999-7777 (Office) * Org Admin Email: foobar at example.net Org Tech Handle: ABC-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-999-999-9999 (Office) * Org Tech Email: tech at example.net Org Tech Handle: ABC-TECH2-ARIN Org Tech Name: Technical Support Manager Org Tech Phone: +1-999-999-8888 (Office) Org Tech Email: tech-mgr at example.net Org NOC Handle: ABC-NOC-ARIN Org NOC Name: Network Operations Center Org NOC Phone: +1-999-999-6666 (Office) * Org NOC Email: noc at example.net Org Abuse Handle: ABC-ABU-ARIN Org Abuse Name: Network Abuse Support Org Abuse Phone: +1-999-999-5555 (Office) * Org Abuse Email: abuse at example.net 2. whois 65000 Org Name: ABC ISP Org ID: ABC AS Number: 65000 AS Name: ABC-ASN65000 AS Handle: AS65000 Registration Date: 2000-05-24 Last Updated: 2001-06-12 AS Abuse Handle: ABUSE-ARIN AS Abuse Name: AS 65000 Abuse Support AS Abuse Phone: +1-703-000-0000 (Office) * AS Abuse Email: abuse-65000 at example.net Org Tech Handle: ABC-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-999-999-9999 (Office) * Org Tech Email: tech at example.net Org Tech Handle: ABC-TECH2-ARIN Org Tech Name: Technical Support Manager Org Tech Phone: +1-999-999-8888 (Office) Org Tech Email: tech-mgr at example.net Org NOC Handle: ABC-NOC-ARIN Org NOC Name: Network Operations Center Org NOC Phone: +1-999-999-6666 (Office) * Org NOC Email: noc at example.net Org Abuse Handle: ABC-ABU-ARIN Org Abuse Name: Network Abuse Support Org Abuse Phone: +1-999-999-5555 (Office) * Org Abuse Email: abuse at example.net 3. whois 10.0.0.0 Org Name: ABC ISP Org ID: ABC Network Range: 10.0.0.0-10.1.255.255 CIDR Notation: 10.0.0.0/15 Network Name: NETWORK-10 Network Handle: NET-10-0-0-0 Can Sub-Delegate: Y IN-ADDR: ns.example.net IN-ADDR: ns2.example.net Registration Date: 2001-10-30 Last Updated: 2001-10-30 Org Tech Handle: ABC-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-999-999-9999 (Office) * Org Tech Email: tech at example.net Org Tech Handle: ABC-TECH2-ARIN Org Tech Name: Technical Support Manager Org Tech Phone: +1-999-999-8888 (Office) Org Tech Email: tech-mgr at example.net Org NOC Handle: ABC-NOC-ARIN Org NOC Name: Network Operations Center Org NOC Phone: +1-999-999-6666 (Office) * Org NOC Email: noc at example.net Org Abuse Handle: ABC-ABU-ARIN Org Abuse Name: Network Abuse Support Org Abuse Phone: +1-999-999-5555 (Office) * Org Abuse Email: abuse at example.net 4. whois 10.32.0.0 ABC ISP (NET-10-32-0-0) NETWORK-10.32 10.32.0.0/17 XYZ ISP (NET-10-32-0-0-2) NET-10-32-RE 10.32.0.0-10.32.0.19 Joe User (NET-10-32-0-0-3) NET-JOE-USER 10.32.0.0/29 5. whois NET-10-32-0-0-2 Org Name: XYZ ISP Org ID: XYZ Network Range: 10.32.0.0-10.32.0.19 CIDR Notation: 10.32.0.0/28, 10.32.0.19/30 Network Name: NET-10-32-RE Network Handle: NET-10-32-0-0-2 Upstream Network Handle: NET-10-32-0-0 Can Sub-Delegate: Y Registration Date: 2000-10-10 Last Updated: 2001-11-03 Org Tech Handle: XYZ-TECH-ARIN Org Tech Name: Technical Support Org Tech Phone: +1-777-777-7777 (Office) * Org Tech Email: tech-xyz at example.net 6. whois NET-10-32-0-0-3 Customer Name: Joe User Customer Number: 43432 Network Range: 10.32.0.0-10.32.0.7 CIDR Notation: 10.32.0.0/29 Network Name: NET-JOE-USER Network Handle: NET-10-32-0-0-3 Upstream Network Handle: NET-10-32-0-0-2 Can Sub-Delegate: N Registration Date: 2001-10-31 Last Updated: 2001-11-03 7. whois ABC-NOC-ARIN Name: Network Operations Center Handle: ABC-NOC-ARIN Company Name: ABC ISP Address: 132 Main Street Anytown, VA 22222 Country Code: US Phone: +1-999-999-6666 (Office) Phone: +1-888-888-8888 (Mobile) Phone: +1-777-777-7777 (Fax) Email: noc at example.net Registration Date: 1998-06-09 Last Updated: 2000-11-21 From richardj at arin.net Fri Mar 29 17:23:32 2002 From: richardj at arin.net (Richard Jimmerson) Date: Fri, 29 Mar 2002 17:23:32 -0500 Subject: FW: ARIN Database and Template Transition Message-ID: <000901c1d770$5c5c33e0$93fc95c0@cobalt> The following events related to ARIN's database and template transition are scheduled for the upcoming ARIN IX meeting (April 7-10): * 2002 Templates Tutorial covering the new ARIN templates and database * Getting a Jump Start on Your Org ID Information session describing your transition to the new ARIN database * Database Working Group (DBWG) Meeting Report and discussion session that will cover items related to the new database and templates More information about these events and other agenda items for the ARIN IX meeting are available at: http://www.arin.net/membership/meetings/arin_ix/agenda.html Definitions of the new templates and point of contact (POC) types are now available at: http://www.arin.net/library/training/2002_templates/ Regards, Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) -----Original Message----- From: Richard Jimmerson [mailto:richardj at arin.net] Sent: Tuesday, February 12, 2002 4:08 PM To: 'arin-announce at arin.net'; 'ppml at arin.net'; 'dbwg at arin.net' Subject: ARIN Database and Template Transition ARIN will transition to a new database and templates in June of 2002. Over the past year, ARIN has developed requirements for the new database with input from members of the ARIN user community at ARIN meetings and on the DB Working Group mailing list, dbwg at arin.net. A training program describing the new database and templates is currently under development. This training program will be offered in person at the upcoming ARIN meeting in April, and on-line for those who are unable to attend the meeting. Training will focus primarily on the new objects of the ARIN database and the newly designed templates. The newly designed templates are available now at: ftp://ftp.arin.net/pub/new-templates/ The templates incorporate the comments submitted via the DB Working Group with the efforts of Registration Services and Engineering Departments. ARIN is providing these templates well in advance of the conversion, and is encouraging those ISPs that have auto-generated SWIPs to revise those scripts, and submit templates as beta tests. ARIN will solicit beta testers from the community for the new database and templates. Participation will be open to all interested parties. More information about beta testing will soon become available. Regards, Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN)