From memsvcs at arin.net Thu Jul 11 14:58:38 2002 From: memsvcs at arin.net (Member Services) Date: Thu, 11 Jul 2002 14:58:38 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available Message-ID: In February of this year, ARIN released the new templates to be used after the conversion taking place on August 9, 2002. We have now modified those templates to include the instructions. These instructions should provide any guidance necessary to correctly complete a template. Please note that some of these templates make references to websites that will not be modified or posted until after conversion. The templates can be found at: ftp://ftp.arin.net/pub/new-templates/ If you have any questions regarding these templates and/or the database conversion, please address your questions to jumpstart at arin.net. Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) From Scott.Whipple at cox.com Fri Jul 12 11:45:53 2002 From: Scott.Whipple at cox.com (Whipple, Scott (CCI-Atlanta)) Date: Fri, 12 Jul 2002 11:45:53 -0400 Subject: ARIN Conversion: Template Instructions Now Available Message-ID: I think the templates and instructions look very good. I have a couple questions. 1. Can you submit more then one netmod.txt, reassign-simple.txt and net-name-change.txt? a. If you can does End of Template have to be remove like on the old swip template? b. If not can this become an option? 2. On the old swip template you didn't need to compete all fields when deleting a reassignment/reallocation. When returning or removing on the new netmod and reassign-simple what are the minimum fields that need to be completed? If anyone is reading these mailing lists please post some questions. The conversion is coming up on us soon and there must be things out there we are missing or not thinking of. Scott Whipple Cox Communications -----Original Message----- From: Member Services [mailto:memsvcs at arin.net] Sent: Thursday, July 11, 2002 11:59 AM To: arin-announce at arin.net; dbwg at arin.net Subject: ARIN Conversion: Template Instructions Now Available In February of this year, ARIN released the new templates to be used after the conversion taking place on August 9, 2002. We have now modified those templates to include the instructions. These instructions should provide any guidance necessary to correctly complete a template. Please note that some of these templates make references to websites that will not be modified or posted until after conversion. The templates can be found at: ftp://ftp.arin.net/pub/new-templates/ If you have any questions regarding these templates and/or the database conversion, please address your questions to jumpstart at arin.net. Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) From ginny at arin.net Fri Jul 12 12:09:44 2002 From: ginny at arin.net (ginny listman) Date: Fri, 12 Jul 2002 12:09:44 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: On Fri, 12 Jul 2002, Whipple, Scott (CCI-Atlanta) wrote: > I think the templates and instructions look very good. I have a couple > questions. > > 1. Can you submit more then one netmod.txt, reassign-simple.txt and > net-name-change.txt? ARIN will impose the same limit that exist today, 10 per email. > a. If you can does End of Template have to be remove like on the old > swip template? > b. If not can this become an option? The END OF TEMPLATE is required for ALL templates. If you include 10 templates in a file, there must be 10 END OF TEMPLATE lines. The reason for this is that the last field on most of the templates is "Public Comments". This field can be multi-lined. If the END OF TEMPLATE is not included, it will include everything up until the END OF TEMPLATE is reached. The result of omitting this line, is to have a second template not be processed and be a Public Comment for the first. > > 2. On the old swip template you didn't need to compete all fields when > deleting a reassignment/reallocation. When returning or removing on the > new netmod and reassign-simple what are the minimum fields that need to > be completed? > This is something that should be incorporated into the instructions of the template. ARIN will make the modifications to the necessary templates, and post the revisions. > If anyone is reading these mailing lists please post some questions. > The conversion is coming up on us soon and there must be things out > there we are missing or not thinking of. > > Scott Whipple > Cox Communications > Ginny Listman Director of Engineering ARIN From dawn.martin at wcom.com Fri Jul 12 16:22:12 2002 From: dawn.martin at wcom.com (Dawn Martin) Date: Fri, 12 Jul 2002 16:22:12 -0400 Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: <000d01c229e1$cf1893b0$8bde2799@wcomnet.com> I have a couple of questions: 1)Can a Resource Tech POC complete ALL aspects of SWIPing? In the tutorial, it only says that they can do allocations? 2)Was it ever figured out exactly what contacts were going to be published in WHOIS? 3)In the replies from the new templates is ARIN going to completely change the subject line? It would be nice if they could just add their ticket number and nothing else. Dawn Martin WorldCom -----Original Message----- From: dbwg-request at arin.net [mailto:dbwg-request at arin.net]On Behalf Of Whipple, Scott (CCI-Atlanta) Sent: Friday, July 12, 2002 11:46 AM To: Member Services; arin-announce at arin.net; dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available I think the templates and instructions look very good. I have a couple questions. 1. Can you submit more then one netmod.txt, reassign-simple.txt and net-name-change.txt? a. If you can does End of Template have to be remove like on the old swip template? b. If not can this become an option? 2. On the old swip template you didn't need to compete all fields when deleting a reassignment/reallocation. When returning or removing on the new netmod and reassign-simple what are the minimum fields that need to be completed? If anyone is reading these mailing lists please post some questions. The conversion is coming up on us soon and there must be things out there we are missing or not thinking of. Scott Whipple Cox Communications -----Original Message----- From: Member Services [mailto:memsvcs at arin.net] Sent: Thursday, July 11, 2002 11:59 AM To: arin-announce at arin.net; dbwg at arin.net Subject: ARIN Conversion: Template Instructions Now Available In February of this year, ARIN released the new templates to be used after the conversion taking place on August 9, 2002. We have now modified those templates to include the instructions. These instructions should provide any guidance necessary to correctly complete a template. Please note that some of these templates make references to websites that will not be modified or posted until after conversion. The templates can be found at: ftp://ftp.arin.net/pub/new-templates/ If you have any questions regarding these templates and/or the database conversion, please address your questions to jumpstart at arin.net. Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) From ginny at arin.net Mon Jul 15 11:40:23 2002 From: ginny at arin.net (ginny listman) Date: Mon, 15 Jul 2002 11:40:23 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: <000d01c229e1$cf1893b0$8bde2799@wcomnet.com> Message-ID: On Fri, 12 Jul 2002, Dawn Martin wrote: > I have a couple of questions: > > 1)Can a Resource Tech POC complete ALL aspects of SWIPing? In the tutorial, > it only says that > they can do allocations? Yes, a Resource Tech can complete all aspects of SWIPing. In which tutorial does it say they can only allocate? > > 2)Was it ever figured out exactly what contacts were going to be published > in WHOIS? No. Although there was concern expressed at the April 2002 Member Meeting regarding publishing the Administrative and/or Technical contacts, it needs to be discussed further on the list. I posted information regarding the Administrative contact http://www.arin.net/mailing_lists/dbwg/0256.html There was only one response. I believe that once we release the new WHOIS and people have the opportunity to see and review what is displayed, this topic will resurface. For now the new WHOIS will display the following: Entity POCs Displayed ====== ============== org All organization POCs including Admin, Tech, NOC and Abuse resouce All resource POCs and all organization POCs BUT Admin > > 3)In the replies from the new templates is ARIN going to completely change > the subject line? It > would be nice if they could just add their ticket number and nothing else. > It is our intention to only append the ticket number to the subject line, and nothing else. > > Dawn Martin > WorldCom > Ginny Listman Director of Engineering ARIN From dawn.martin at wcom.com Mon Jul 15 13:30:06 2002 From: dawn.martin at wcom.com (Dawn Martin) Date: Mon, 15 Jul 2002 13:30:06 -0400 Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: <001401c22c25$435bd8a0$8bde2799@wcomnet.com> Thanks Ginny, for #1 the URL is: http://www.arin.net/library/training/2002_templates/index.html# for the resource Tech POC. Everyone else, (OK anyone else) doesn't anyone have anything to say about your name being put in WHOIS with ALL of your records??? I can only say for me that I don't want my name to show up. Anyone... Bueller... Bueller... Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Monday, July 15, 2002 11:40 AM To: Dawn Martin Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available On Fri, 12 Jul 2002, Dawn Martin wrote: > I have a couple of questions: > > 1)Can a Resource Tech POC complete ALL aspects of SWIPing? In the tutorial, > it only says that > they can do allocations? Yes, a Resource Tech can complete all aspects of SWIPing. In which tutorial does it say they can only allocate? > > 2)Was it ever figured out exactly what contacts were going to be published > in WHOIS? No. Although there was concern expressed at the April 2002 Member Meeting regarding publishing the Administrative and/or Technical contacts, it needs to be discussed further on the list. I posted information regarding the Administrative contact http://www.arin.net/mailing_lists/dbwg/0256.html There was only one response. I believe that once we release the new WHOIS and people have the opportunity to see and review what is displayed, this topic will resurface. For now the new WHOIS will display the following: Entity POCs Displayed ====== ============== org All organization POCs including Admin, Tech, NOC and Abuse resouce All resource POCs and all organization POCs BUT Admin > > 3)In the replies from the new templates is ARIN going to completely change > the subject line? It > would be nice if they could just add their ticket number and nothing else. > It is our intention to only append the ticket number to the subject line, and nothing else. > > Dawn Martin > WorldCom > Ginny Listman Director of Engineering ARIN From ginny at arin.net Mon Jul 15 13:50:08 2002 From: ginny at arin.net (ginny listman) Date: Mon, 15 Jul 2002 13:50:08 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: <001401c22c25$435bd8a0$8bde2799@wcomnet.com> Message-ID: dawn> 1)Can a Resource Tech POC complete ALL aspects of SWIPing? In the dawn> tutorial, it only says that they can do allocations? ginny> Yes, a Resource Tech can complete all aspects of SWIPing. In which ginny> tutorial does it say they can only allocate? dawn> Thanks Ginny, for #1 the URL is: dawn> http://www.arin.net/library/training/2002_templates/index.html# for dawn> the resource Tech POC. Aha, found it. Only allocations can swip, not swip only allocations. I will see about changing the wording to make this clearer. Ginny From Scott.Whipple at cox.com Mon Jul 15 14:15:18 2002 From: Scott.Whipple at cox.com (Whipple, Scott (CCI-Atlanta)) Date: Mon, 15 Jul 2002 14:15:18 -0400 Subject: ARIN Conversion: Template Instructions Now Available Message-ID: Hi Dawn. I'm assuming you're going to be the Admin tech for WorldCom. I think I would like to see ALL Org contacts being separated from the resources unless there is no resource POC specified. If there is a POC listed on a resource, that is obviously how that ISP wants to be contacted if there is a problem with that network. If there is no resource POC associated with a particular network, then I think how Ginny has it below would be fine. I think if we associate all the POC's except the admin we are going to be getting way more data then we want. Our answers could end up being bulky and difficult to fish and find what you really want. I would guess ARIN's whois for the majority is used to find out what organization an IP address is registered too and then secondly for who is responsible for it. If you want to know who all the POC are for that organization then you can do a second query. If an organization is savvy enough to take the time and associate a resource tech with there resources, then their Org POC's don't ever need to be shown unless the Org is actually queried. Ginny. The way I would like to see the POC's listed differs slightly from what ARIN has now. Is this still open for conversation before conversion, or is this a closed issue because of lack of community input? Scott Whipple Cox Communications -----Original Message----- From: Dawn Martin [mailto:dawn.martin at wcom.com] Sent: Monday, July 15, 2002 10:30 AM To: 'ginny listman' Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Thanks Ginny, for #1 the URL is: http://www.arin.net/library/training/2002_templates/index.html# for the resource Tech POC. Everyone else, (OK anyone else) doesn't anyone have anything to say about your name being put in WHOIS with ALL of your records??? I can only say for me that I don't want my name to show up. Anyone... Bueller... Bueller... Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Monday, July 15, 2002 11:40 AM To: Dawn Martin Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available On Fri, 12 Jul 2002, Dawn Martin wrote: > I have a couple of questions: > > 1)Can a Resource Tech POC complete ALL aspects of SWIPing? In the tutorial, > it only says that > they can do allocations? Yes, a Resource Tech can complete all aspects of SWIPing. In which tutorial does it say they can only allocate? > > 2)Was it ever figured out exactly what contacts were going to be published > in WHOIS? No. Although there was concern expressed at the April 2002 Member Meeting regarding publishing the Administrative and/or Technical contacts, it needs to be discussed further on the list. I posted information regarding the Administrative contact http://www.arin.net/mailing_lists/dbwg/0256.html There was only one response. I believe that once we release the new WHOIS and people have the opportunity to see and review what is displayed, this topic will resurface. For now the new WHOIS will display the following: Entity POCs Displayed ====== ============== org All organization POCs including Admin, Tech, NOC and Abuse resouce All resource POCs and all organization POCs BUT Admin > > 3)In the replies from the new templates is ARIN going to completely change > the subject line? It > would be nice if they could just add their ticket number and nothing else. > It is our intention to only append the ticket number to the subject line, and nothing else. > > Dawn Martin > WorldCom > Ginny Listman Director of Engineering ARIN From dawn.martin at wcom.com Mon Jul 15 15:13:53 2002 From: dawn.martin at wcom.com (Dawn Martin) Date: Mon, 15 Jul 2002 15:13:53 -0400 Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: <000601c22c33$c299f8a0$8bde2799@wcomnet.com> Scott, Are you saying that on any given record the organization would have to have at least 1 contact. If the organization decided to put additional POC's on the record the org. could decide not to have the admin listed on the record? If so, then the Admin contact could only be pulled up using a specific WHOIS query? Something like: whois -h whois.arin.net admin 157.130.0.0 That would be fine with me, I think I have said before that if it was a separate entry that could be pulled up by savvy WHOIS folks it would be better. Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: dbwg-request at arin.net [mailto:dbwg-request at arin.net]On Behalf Of Whipple, Scott (CCI-Atlanta) Sent: Monday, July 15, 2002 2:15 PM To: dawn.martin at wcom.com; ginny listman Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Hi Dawn. I'm assuming you're going to be the Admin tech for WorldCom. I think I would like to see ALL Org contacts being separated from the resources unless there is no resource POC specified. If there is a POC listed on a resource, that is obviously how that ISP wants to be contacted if there is a problem with that network. If there is no resource POC associated with a particular network, then I think how Ginny has it below would be fine. I think if we associate all the POC's except the admin we are going to be getting way more data then we want. Our answers could end up being bulky and difficult to fish and find what you really want. I would guess ARIN's whois for the majority is used to find out what organization an IP address is registered too and then secondly for who is responsible for it. If you want to know who all the POC are for that organization then you can do a second query. If an organization is savvy enough to take the time and associate a resource te! ch with there resources, then their Org POC's don't ever need to be shown unless the Org is actually queried. Ginny. The way I would like to see the POC's listed differs slightly from what ARIN has now. Is this still open for conversation before conversion, or is this a closed issue because of lack of community input? Scott Whipple Cox Communications -----Original Message----- From: Dawn Martin [mailto:dawn.martin at wcom.com] Sent: Monday, July 15, 2002 10:30 AM To: 'ginny listman' Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Thanks Ginny, for #1 the URL is: http://www.arin.net/library/training/2002_templates/index.html# for the resource Tech POC. Everyone else, (OK anyone else) doesn't anyone have anything to say about your name being put in WHOIS with ALL of your records??? I can only say for me that I don't want my name to show up. Anyone... Bueller... Bueller... Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Monday, July 15, 2002 11:40 AM To: Dawn Martin Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available On Fri, 12 Jul 2002, Dawn Martin wrote: > I have a couple of questions: > > 1)Can a Resource Tech POC complete ALL aspects of SWIPing? In the tutorial, > it only says that > they can do allocations? Yes, a Resource Tech can complete all aspects of SWIPing. In which tutorial does it say they can only allocate? > > 2)Was it ever figured out exactly what contacts were going to be published > in WHOIS? No. Although there was concern expressed at the April 2002 Member Meeting regarding publishing the Administrative and/or Technical contacts, it needs to be discussed further on the list. I posted information regarding the Administrative contact http://www.arin.net/mailing_lists/dbwg/0256.html There was only one response. I believe that once we release the new WHOIS and people have the opportunity to see and review what is displayed, this topic will resurface. For now the new WHOIS will display the following: Entity POCs Displayed ====== ============== org All organization POCs including Admin, Tech, NOC and Abuse resouce All resource POCs and all organization POCs BUT Admin > > 3)In the replies from the new templates is ARIN going to completely change > the subject line? It > would be nice if they could just add their ticket number and nothing else. > It is our intention to only append the ticket number to the subject line, and nothing else. > > Dawn Martin > WorldCom > Ginny Listman Director of Engineering ARIN From ginny at arin.net Tue Jul 16 14:30:30 2002 From: ginny at arin.net (ginny listman) Date: Tue, 16 Jul 2002 14:30:30 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available (fwd) Message-ID: This message didn't make it to the list. (Lee, are you subscribed under a different email address?) ---------- Forwarded message ---------- Date: Mon, 15 Jul 2002 14:07:39 -0400 (EDT) From: Lee Howard To: Dawn Martin Cc: 'ginny listman' , dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available > Entity POCs Displayed > ====== ============== > org All organization POCs including Admin, Tech, NOC and Abuse > resouce All resource POCs and all organization POCs BUT Admin Speaking as the Administrative contact for WorldCom, I don't want my name and contact information appearing in WHOIS. I already get a couple of abuse/security/spam/hacker compaints a day because my name appears on some route objects in the RADB. I ask the community for its sympathy--can anyone imagine being the lone human whose name shows up for all UUNET records? I also don't want all Tech POCs to appear. We have hundreds of people who could allocate and SWIP; I don't want somebody to be able to see the name of every UUNET engineer just by doing a WHOIS. The bait is too strong for recruiters or social engineering hacks. Any legitimate use of WHOIS can be directed to a NOC, Help or Abuse role account, which we staff 24x7. I personally am not responsive 24x7. If other organizations do not have such role accounts, they are welcome to list individuals as their NOC or Abuse contacts. That's my opinion as a potential Admin contact, and the manager of a large group of potential Tech contacts. Lee On Mon, 15 Jul 2002, Dawn Martin wrote: > Date: Mon, 15 Jul 2002 13:30:06 -0400 > From: Dawn Martin > To: 'ginny listman' > Cc: dbwg at arin.net > Subject: RE: ARIN Conversion: Template Instructions Now Available > > Thanks Ginny, for #1 the URL is: > http://www.arin.net/library/training/2002_templates/index.html# for the > resource Tech POC. > > Everyone else, > > (OK anyone else) doesn't anyone have anything to say about your > name being put in WHOIS with ALL of your records??? I can only say > for me that I don't want my name to show up. > > Anyone... > > Bueller... > > Bueller... > > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > > -----Original Message----- > From: ginny listman [mailto:ginny at arin.net] > Sent: Monday, July 15, 2002 11:40 AM > To: Dawn Martin > Cc: dbwg at arin.net > Subject: RE: ARIN Conversion: Template Instructions Now Available > > > > > On Fri, 12 Jul 2002, Dawn Martin wrote: > > > I have a couple of questions: > > > > 1)Can a Resource Tech POC complete ALL aspects of SWIPing? In the > tutorial, > > it only says that > > they can do allocations? > > Yes, a Resource Tech can complete all aspects of SWIPing. In which > tutorial does it say they can only allocate? > > > > > 2)Was it ever figured out exactly what contacts were going to be published > > in WHOIS? > > No. Although there was concern expressed at the April 2002 Member Meeting > regarding publishing the Administrative and/or Technical contacts, it > needs to be discussed further on the list. I posted information regarding > the Administrative contact > http://www.arin.net/mailing_lists/dbwg/0256.html > > There was only one response. I believe that once we release the new WHOIS > and people have the opportunity to see and review what is displayed, this > topic will resurface. For now the new WHOIS will display the following: > > Entity POCs Displayed > ====== ============== > org All organization POCs including Admin, Tech, NOC and Abuse > resouce All resource POCs and all organization POCs BUT Admin > > > > > 3)In the replies from the new templates is ARIN going to completely change > > the subject line? It > > would be nice if they could just add their ticket number and nothing > else. > > > > It is our intention to only append the ticket number to the subject line, > and nothing else. > > > > > Dawn Martin > > WorldCom > > > > Ginny Listman > Director of Engineering > ARIN > From ginny at arin.net Tue Jul 16 14:41:24 2002 From: ginny at arin.net (ginny listman) Date: Tue, 16 Jul 2002 14:41:24 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: On Mon, 15 Jul 2002, Whipple, Scott (CCI-Atlanta) wrote: > Ginny. The way I would like to see the POC's listed differs slightly > from what ARIN has now. Is this still open for conversation before > conversion, or is this a closed issue because of lack of community > input? > > Scott Whipple > Cox Communications > > The topic of displaying POCs is still open for discussion. We will consider a different format for the August 12 release. Also, we are willing to change the display after this initial release. However, we will only change the format when there is significant input from the community to do so. I imagine by the October meeting, people will have had enough time to review the new WHOIS and will be ready to discuss different displays. Ginny From ginny at arin.net Tue Jul 16 15:28:54 2002 From: ginny at arin.net (ginny listman) Date: Tue, 16 Jul 2002 15:28:54 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: <000601c22c33$c299f8a0$8bde2799@wcomnet.com> Message-ID: Dawn, My understanding of what Scott is proposing: Query 1: An Org Response 1: ALL POCs associated with the Org. This would include the Administrative contact, as well as the multiple Technical contacts. Most people will not be querying Orgs, but rather the actual resource. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3: A resource that does NOT have POCs associated with it Response 3: Display the Orgs Tech, NOC and Abuse contacts Is this right, Scott? I would go a step further and suggest that query 3 be broken into the following: Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Ginny On Mon, 15 Jul 2002, Dawn Martin wrote: > Scott, > > Are you saying that on any given record the organization would have to have > at least 1 contact. If the organization decided to put additional POC's on > the record the org. could decide not to have the admin listed on the record? > > If so, then the Admin contact could only be pulled up using a specific WHOIS > query? > Something like: whois -h whois.arin.net admin 157.130.0.0 > > That would be fine with me, I think I have said before that if it was a > separate > entry that could be pulled up by savvy WHOIS folks it would be better. > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > From Scott.Whipple at cox.com Tue Jul 16 15:53:05 2002 From: Scott.Whipple at cox.com (Whipple, Scott (CCI-Atlanta)) Date: Tue, 16 Jul 2002 15:53:05 -0400 Subject: ARIN Conversion: Template Instructions Now Available Message-ID: Yes that is what I'm suggesting. I'm also willing to go a little farther on the Org query and lean toward what Lee said. Eliminate the the Admin from ever showing up in a whois query. I don't think we can eliminate the Org techs from showing up unless there is an abuse/noc contact, and from what I think I remember abuse/noc contacts are not required to complete an Org template but the Org tech is required. Because we have to have some contacts showing up for our resources if a company doesn't create an abuse/noc POC we have to list at least the Org Tech contacts. These are my new compromised suggestions. Query 1: An Org Response 1: Only includes abuse or noc contacts unless no abuse/noc contacts are listed, then org techs are listed. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Scott -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Tuesday, July 16, 2002 12:29 PM To: Dawn Martin Cc: Whipple, Scott (CCI-Atlanta); dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Dawn, My understanding of what Scott is proposing: Query 1: An Org Response 1: ALL POCs associated with the Org. This would include the Administrative contact, as well as the multiple Technical contacts. Most people will not be querying Orgs, but rather the actual resource. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3: A resource that does NOT have POCs associated with it Response 3: Display the Orgs Tech, NOC and Abuse contacts Is this right, Scott? I would go a step further and suggest that query 3 be broken into the following: Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Ginny On Mon, 15 Jul 2002, Dawn Martin wrote: > Scott, > > Are you saying that on any given record the organization would have to have > at least 1 contact. If the organization decided to put additional POC's on > the record the org. could decide not to have the admin listed on the record? > > If so, then the Admin contact could only be pulled up using a specific WHOIS > query? > Something like: whois -h whois.arin.net admin 157.130.0.0 > > That would be fine with me, I think I have said before that if it was a > separate > entry that could be pulled up by savvy WHOIS folks it would be better. > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > From dawn.martin at wcom.com Tue Jul 16 16:42:20 2002 From: dawn.martin at wcom.com (Dawn Martin) Date: Tue, 16 Jul 2002 16:42:20 -0400 Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: <004401c22d09$490dc530$8bde2799@wcomnet.com> I have two thoughts here: 1) The Org records should have at least 1 contact. Why can't the Org decide which & who that contact should be. If the other information we provide is proprietary, why can't the company decide that. ARIN can keep some information private, that could be the folks that are allowed to SWIP and the folks that are allowed to request IPs and change the org information (org. techs & admin techs). I think Lee already voiced my opinion in this, that I don't want my name or the name of several hundred employees listed on all of our resources. For one it would make for a really long lookup. 2) I would really like to see some sample WHOIS outputs. It if very difficult to decide who is going to be where without some samples. I'm just going around in circle's guessing what is going to be put on each record. Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] Sent: Tuesday, July 16, 2002 3:53 PM To: ginny listman; Dawn Martin Cc: dbwg at arin.net; lee.howard at wcom.com Subject: RE: ARIN Conversion: Template Instructions Now Available Yes that is what I'm suggesting. I'm also willing to go a little farther on the Org query and lean toward what Lee said. Eliminate the the Admin from ever showing up in a whois query. I don't think we can eliminate the Org techs from showing up unless there is an abuse/noc contact, and from what I think I remember abuse/noc contacts are not required to complete an Org template but the Org tech is required. Because we have to have some contacts showing up for our resources if a company doesn't create an abuse/noc POC we have to list at least the Org Tech contacts. These are my new compromised suggestions. Query 1: An Org Response 1: Only includes abuse or noc contacts unless no abuse/noc contacts are listed, then org techs are listed. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Scott -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Tuesday, July 16, 2002 12:29 PM To: Dawn Martin Cc: Whipple, Scott (CCI-Atlanta); dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Dawn, My understanding of what Scott is proposing: Query 1: An Org Response 1: ALL POCs associated with the Org. This would include the Administrative contact, as well as the multiple Technical contacts. Most people will not be querying Orgs, but rather the actual resource. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3: A resource that does NOT have POCs associated with it Response 3: Display the Orgs Tech, NOC and Abuse contacts Is this right, Scott? I would go a step further and suggest that query 3 be broken into the following: Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Ginny On Mon, 15 Jul 2002, Dawn Martin wrote: > Scott, > > Are you saying that on any given record the organization would have to have > at least 1 contact. If the organization decided to put additional POC's on > the record the org. could decide not to have the admin listed on the record? > > If so, then the Admin contact could only be pulled up using a specific WHOIS > query? > Something like: whois -h whois.arin.net admin 157.130.0.0 > > That would be fine with me, I think I have said before that if it was a > separate > entry that could be pulled up by savvy WHOIS folks it would be better. > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 3508 bytes Desc: not available URL: From David.Poch at telus.com Tue Jul 16 17:51:13 2002 From: David.Poch at telus.com (David Poch) Date: Tue, 16 Jul 2002 15:51:13 -0600 Subject: FW: new template question Message-ID: <047E727188F5D31184170001FA7E51A208F7D814@ex4.ent.agt.ab.ca> If an existing end user 'assignment' includes an end user POC does the NET-Mod template need to be used to remove the assignment? Also, can Netmod be used to remove simple 'assignments' (ones that do not contain in-addrs or POC for the end user organization). -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Wednesday, May 15, 2002 1:52 PM To: geoffrey camps Cc: dbwg at arin.net Subject: RE: new template question You must use the Net-Mod to modify/remove an allocation or a reassigment that has POCs and/or inaddrs (reassign detail). Ginny On Wed, 15 May 2002, geoffrey camps wrote: > Ok, so can Reassign-Simple be used to Modify/Delete an 'allocation', or do > we have to use Net-Mod? > > -gc > > -----Original Message----- > From: dbwg-request at arin.net [mailto:dbwg-request at arin.net]On Behalf Of > ginny listman > Sent: Wednesday, May 15, 2002 11:07 AM > To: Todd Caine > Cc: dbwg at arin.net > Subject: Re: new template question > > > Yes. In the current SWIP template the '(A)allocate (S)assign:' field has > cause problems, mostly because assign and allocate both begin with 'A'. > For clarity, we have created separate templates. > > Ginny > > On Wed, 15 May 2002, Todd Caine wrote: > > > > > Is it also true that Reassign-Simple and Reassign-Detailed are only to be > used for > > End-User "assignments" and the Reallocate template is only to be used for > > allocations to ISP that will be reassigning the address space to their > customers? > > > > ginny listman wrote: > > > > > Geoffrey, > > > > > > You are correct. As a beta tester, I'll be sure to let you know when and > > > where you can send your test templates. > > > > > > Ginny Listman > > > Director of Engineering > > > ARIN > > > > > > On Wed, 15 May 2002, geoffrey camps wrote: > > > > > > > I need a quick sanity check regarding the new templates that are > replacing > > > > the SWIP template. I am working on converting our current SWIP script > to > > > > reflect the new template design. Previously, the SWIP template could > be > > > > used to create, modify, or delete an assignment or allocation. > However, the > > > > new templates have specific purposes and I want to be sure that I have > them > > > > correct: > > > > > > > > Reassign-Simple: New, Modify, Delete > > > > Net-Mod: Modify, Delete > > > > Reassign-Detailed: New > > > > Reallocate: New > > > > > > > > Any comments or clarification would be appreciated. > > > > > > > > > > > > Geoffrey Camps > > > > Network Engineer > > > > Exodus, a Cable and Wireless Service > > > > Delivering the Internet promise > > > > www.exodus.net > > > > gcamps at exodus.net > > > > > > > > -- > > Todd Caine > > Software Engineer > > Electric Lightwave, Inc. > > tcaine at eli.net > > > > > > From Scott.Whipple at cox.com Wed Jul 17 09:30:32 2002 From: Scott.Whipple at cox.com (Whipple, Scott (CCI-Atlanta)) Date: Wed, 17 Jul 2002 09:30:32 -0400 Subject: ARIN Conversion: Template Instructions Now Available Message-ID: Dawn, I think if you used my last proposal you can accomplish what you're looking for. The Admin and org tech would never be seen as long as you had an abuse/noc contact on your org ID. If you don't want all your engineers to be listed you can set up an additional org tech that's a role account for all your engineers or you can list them all out as individuals now that there is no limit for the amount of POC's. The point is they would never be seen as long as you have an abuse/noc contact. If you're worried about having all your employees listed on resources just set up a role account that they all have access to or a few different role accounts giving access to who you want for what you want. This will still give them the ability to add or delete reassignments. I think the 3 of us are saying basically the same thing. Scott -----Original Message----- From: Dawn Martin [mailto:dawn.martin at wcom.com] Sent: Tuesday, July 16, 2002 1:42 PM To: Whipple, Scott (CCI-Atlanta) Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available I have two thoughts here: 1) The Org records should have at least 1 contact. Why can't the Org decide which & who that contact should be. If the other information we provide is proprietary, why can't the company decide that. ARIN can keep some information private, that could be the folks that are allowed to SWIP and the folks that are allowed to request IPs and change the org information (org. techs & admin techs). I think Lee already voiced my opinion in this, that I don't want my name or the name of several hundred employees listed on all of our resources. For one it would make for a really long lookup. 2) I would really like to see some sample WHOIS outputs. It if very difficult to decide who is going to be where without some samples. I'm just going around in circle's guessing what is going to be put on each record. Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] Sent: Tuesday, July 16, 2002 3:53 PM To: ginny listman; Dawn Martin Cc: dbwg at arin.net; lee.howard at wcom.com Subject: RE: ARIN Conversion: Template Instructions Now Available Yes that is what I'm suggesting. I'm also willing to go a little farther on the Org query and lean toward what Lee said. Eliminate the the Admin from ever showing up in a whois query. I don't think we can eliminate the Org techs from showing up unless there is an abuse/noc contact, and from what I think I remember abuse/noc contacts are not required to complete an Org template but the Org tech is required. Because we have to have some contacts showing up for our resources if a company doesn't create an abuse/noc POC we have to list at least the Org Tech contacts. These are my new compromised suggestions. Query 1: An Org Response 1: Only includes abuse or noc contacts unless no abuse/noc contacts are listed, then org techs are listed. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Scott -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Tuesday, July 16, 2002 12:29 PM To: Dawn Martin Cc: Whipple, Scott (CCI-Atlanta); dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Dawn, My understanding of what Scott is proposing: Query 1: An Org Response 1: ALL POCs associated with the Org. This would include the Administrative contact, as well as the multiple Technical contacts. Most people will not be querying Orgs, but rather the actual resource. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3: A resource that does NOT have POCs associated with it Response 3: Display the Orgs Tech, NOC and Abuse contacts Is this right, Scott? I would go a step further and suggest that query 3 be broken into the following: Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Ginny On Mon, 15 Jul 2002, Dawn Martin wrote: > Scott, > > Are you saying that on any given record the organization would have to have > at least 1 contact. If the organization decided to put additional POC's on > the record the org. could decide not to have the admin listed on the record? > > If so, then the Admin contact could only be pulled up using a specific WHOIS > query? > Something like: whois -h whois.arin.net admin 157.130.0.0 > > That would be fine with me, I think I have said before that if it was a > separate > entry that could be pulled up by savvy WHOIS folks it would be better. > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > From dawn.martin at wcom.com Wed Jul 17 09:47:15 2002 From: dawn.martin at wcom.com (Dawn Martin) Date: Wed, 17 Jul 2002 09:47:15 -0400 Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: <000b01c22d98$7674a4f0$8bde2799@wcomnet.com> Hey Scott, It is not the set-up of the role accounts but a copy of every SWIP/netmod template being sent to everyone on the list every time something is sent out or received. At that point I'm sure people would just start ignoring it and deleting those emails assuming it was for someone else. It would make it difficult for the sender to ensure that their SWIP was actually processed. I agree though that we are all saying the same thing about at least having one contact, I just want some of the contact information that I provide to ARIN to be for their eyes only. Dawn -----Original Message----- From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] Sent: Wednesday, July 17, 2002 9:31 AM To: dawn.martin at wcom.com Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Dawn, I think if you used my last proposal you can accomplish what you're looking for. The Admin and org tech would never be seen as long as you had an abuse/noc contact on your org ID. If you don't want all your engineers to be listed you can set up an additional org tech that's a role account for all your engineers or you can list them all out as individuals now that there is no limit for the amount of POC's. The point is they would never be seen as long as you have an abuse/noc contact. If you're worried about having all your employees listed on resources just set up a role account that they all have access to or a few different role accounts giving access to who you want for what you want. This will still give them the ability to add or delete reassignments. I think the 3 of us are saying basically the same thing. Scott -----Original Message----- From: Dawn Martin [mailto:dawn.martin at wcom.com] Sent: Tuesday, July 16, 2002 1:42 PM To: Whipple, Scott (CCI-Atlanta) Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available I have two thoughts here: 1) The Org records should have at least 1 contact. Why can't the Org decide which & who that contact should be. If the other information we provide is proprietary, why can't the company decide that. ARIN can keep some information private, that could be the folks that are allowed to SWIP and the folks that are allowed to request IPs and change the org information (org. techs & admin techs). I think Lee already voiced my opinion in this, that I don't want my name or the name of several hundred employees listed on all of our resources. For one it would make for a really long lookup. 2) I would really like to see some sample WHOIS outputs. It if very difficult to decide who is going to be where without some samples. I'm just going around in circle's guessing what is going to be put on each record. Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] Sent: Tuesday, July 16, 2002 3:53 PM To: ginny listman; Dawn Martin Cc: dbwg at arin.net; lee.howard at wcom.com Subject: RE: ARIN Conversion: Template Instructions Now Available Yes that is what I'm suggesting. I'm also willing to go a little farther on the Org query and lean toward what Lee said. Eliminate the the Admin from ever showing up in a whois query. I don't think we can eliminate the Org techs from showing up unless there is an abuse/noc contact, and from what I think I remember abuse/noc contacts are not required to complete an Org template but the Org tech is required. Because we have to have some contacts showing up for our resources if a company doesn't create an abuse/noc POC we have to list at least the Org Tech contacts. These are my new compromised suggestions. Query 1: An Org Response 1: Only includes abuse or noc contacts unless no abuse/noc contacts are listed, then org techs are listed. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Scott -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Tuesday, July 16, 2002 12:29 PM To: Dawn Martin Cc: Whipple, Scott (CCI-Atlanta); dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Dawn, My understanding of what Scott is proposing: Query 1: An Org Response 1: ALL POCs associated with the Org. This would include the Administrative contact, as well as the multiple Technical contacts. Most people will not be querying Orgs, but rather the actual resource. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3: A resource that does NOT have POCs associated with it Response 3: Display the Orgs Tech, NOC and Abuse contacts Is this right, Scott? I would go a step further and suggest that query 3 be broken into the following: Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Ginny On Mon, 15 Jul 2002, Dawn Martin wrote: > Scott, > > Are you saying that on any given record the organization would have to have > at least 1 contact. If the organization decided to put additional POC's on > the record the org. could decide not to have the admin listed on the record? > > If so, then the Admin contact could only be pulled up using a specific WHOIS > query? > Something like: whois -h whois.arin.net admin 157.130.0.0 > > That would be fine with me, I think I have said before that if it was a > separate > entry that could be pulled up by savvy WHOIS folks it would be better. > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 4284 bytes Desc: not available URL: From brmandal at att.com Wed Jul 17 13:31:15 2002 From: brmandal at att.com (Mandal, Barbara R, ALCNS) Date: Wed, 17 Jul 2002 13:31:15 -0400 Subject: beta testing Message-ID: <62DA45D4963FA747BA1B253E266760F9031A9610@OCCLUST04EVS1.ugd.att.com> We've sent numerous templates to betamaster at arin.net since July 2 and haven't gotten any responses. Is anyone successfully testing? Barbara Mandal IP Systems and Applications Services AT&T From gcamps at exodus.net Wed Jul 17 13:38:50 2002 From: gcamps at exodus.net (geoffrey camps) Date: Wed, 17 Jul 2002 10:38:50 -0700 Subject: beta testing In-Reply-To: <62DA45D4963FA747BA1B253E266760F9031A9610@OCCLUST04EVS1.ugd.att.com> Message-ID: We're experiencing the same thing. -gc -----Original Message----- From: dbwg-request at arin.net [mailto:dbwg-request at arin.net]On Behalf Of Mandal, Barbara R, ALCNS Sent: Wednesday, July 17, 2002 10:31 AM To: dbwg at arin.net Subject: beta testing We've sent numerous templates to betamaster at arin.net since July 2 and haven't gotten any responses. Is anyone successfully testing? Barbara Mandal IP Systems and Applications Services AT&T From ginny at arin.net Wed Jul 17 14:07:52 2002 From: ginny at arin.net (ginny listman) Date: Wed, 17 Jul 2002 14:07:52 -0400 (EDT) Subject: beta testing In-Reply-To: Message-ID: Barbara and Geoffrey, I apologize for the delay. We had some technical difficulties that have since been resolved. I've just spoken with the testers, and they will get through all the beta templates by the end of the day. Thank you for volunteering to be a beta tester. Ginny Director of Engineering ARIN On Wed, 17 Jul 2002, geoffrey camps wrote: > We're experiencing the same thing. > > -gc > > -----Original Message----- > From: dbwg-request at arin.net [mailto:dbwg-request at arin.net]On Behalf Of > Mandal, Barbara R, ALCNS > Sent: Wednesday, July 17, 2002 10:31 AM > To: dbwg at arin.net > Subject: beta testing > > > We've sent numerous templates to betamaster at arin.net since July 2 and > haven't gotten any responses. Is anyone successfully testing? > > Barbara Mandal > IP Systems and Applications Services > AT&T > From dbarger at swbell.net Wed Jul 17 14:35:46 2002 From: dbarger at swbell.net (Dave Barger) Date: Wed, 17 Jul 2002 13:35:46 -0500 Subject: beta testing In-Reply-To: References: Message-ID: <5.0.0.25.2.20020717133353.00a68bf0@postoffice.swbell.net> Ginny, Whois queries to beta.arin.net are failing for me. Whois -h beta.arin.net ###.###.###.### Should this work?? Thanks. Dave Barger Director - Engineering IP Management SBC Internet Services At 01:07 PM 7/17/2002, ginny listman wrote: >Barbara and Geoffrey, > >I apologize for the delay. We had some technical difficulties that have >since been resolved. I've just spoken with the testers, and they will get >through all the beta templates by the end of the day. Thank you for >volunteering to be a beta tester. > >Ginny >Director of Engineering >ARIN > >On Wed, 17 Jul 2002, geoffrey camps wrote: > > > We're experiencing the same thing. > > > > -gc > > > > -----Original Message----- > > From: dbwg-request at arin.net [mailto:dbwg-request at arin.net]On Behalf Of > > Mandal, Barbara R, ALCNS > > Sent: Wednesday, July 17, 2002 10:31 AM > > To: dbwg at arin.net > > Subject: beta testing > > > > > > We've sent numerous templates to betamaster at arin.net since July 2 and > > haven't gotten any responses. Is anyone successfully testing? > > > > Barbara Mandal > > IP Systems and Applications Services > > AT&T > > e" ------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ginny at arin.net Wed Jul 17 14:41:07 2002 From: ginny at arin.net (ginny listman) Date: Wed, 17 Jul 2002 14:41:07 -0400 (EDT) Subject: beta testing In-Reply-To: <5.0.0.25.2.20020717133353.00a68bf0@postoffice.swbell.net> Message-ID: You have to specify port 4344. Depending on your whois client this may be simple or difficult. The other option is to telnet, as in: telnet beta.arin.net 4344 Then enter your query. Ginny On Wed, 17 Jul 2002, Dave Barger wrote: > Ginny, > > Whois queries to beta.arin.net are failing for me. > > Whois -h beta.arin.net ###.###.###.### > > Should this work?? > Thanks. > > Dave Barger > Director - Engineering IP Management > SBC Internet Services > > > At 01:07 PM 7/17/2002, ginny listman wrote: > >Barbara and Geoffrey, > > > >I apologize for the delay. We had some technical difficulties that have > >since been resolved. I've just spoken with the testers, and they will get > >through all the beta templates by the end of the day. Thank you for > >volunteering to be a beta tester. > > > >Ginny > >Director of Engineering > >ARIN > > > >On Wed, 17 Jul 2002, geoffrey camps wrote: > > > > > We're experiencing the same thing. > > > > > > -gc > > > > > > -----Original Message----- > > > From: dbwg-request at arin.net [mailto:dbwg-request at arin.net]On Behalf Of > > > Mandal, Barbara R, ALCNS > > > Sent: Wednesday, July 17, 2002 10:31 AM > > > To: dbwg at arin.net > > > Subject: beta testing > > > > > > > > > We've sent numerous templates to betamaster at arin.net since July 2 and > > > haven't gotten any responses. Is anyone successfully testing? > > > > > > Barbara Mandal > > > IP Systems and Applications Services > > > AT&T > > > > > e" > ------------------------ > From brmandal at att.com Mon Jul 22 20:43:46 2002 From: brmandal at att.com (Mandal, Barbara R, ALCNS) Date: Mon, 22 Jul 2002 20:43:46 -0400 Subject: beta testing Message-ID: <62DA45D4963FA747BA1B253E266760F9032AFAD2@OCCLUST04EVS1.ugd.att.com> Help! With less than three weeks until cutover, we still haven't received any responses to the templates we submitted. Can you tell us if any of the responses have changed or are they the same as with the old templates? Barbara Mandal INSTAR Systems Engineering (732) 420-2368 From richardj at arin.net Tue Jul 23 12:05:44 2002 From: richardj at arin.net (Richard Jimmerson) Date: Tue, 23 Jul 2002 12:05:44 -0400 Subject: beta testing In-Reply-To: <62DA45D4963FA747BA1B253E266760F9032AFAD2@OCCLUST04EVS1.ugd.att.com> Message-ID: <010401c23262$cd164dd0$c9fc95c0@cobalt> Hello Barbara, Thank you for your message. One of your beta submissions was processed on July 17, and the other yesterday. Someone from the beta testing team will be contacting you today. If anyone else on this list is participating in beta testing and is having difficulties receiving responses, please send email to hostmaster at arin.net or call ARIN registration services at (703) 227-0660, as they will be able to put you in direct contact with a member of the beta testing team. 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 Mandal, Barbara R, ALCNS > Sent: Monday, July 22, 2002 8:44 PM > To: dbwg at arin.net > Subject: beta testing > > > Help! With less than three weeks until cutover, we still > haven't received any responses to the templates we submitted. > Can you tell us if any of the responses have changed or are > they the same as with the old templates? > > Barbara Mandal > INSTAR Systems Engineering > (732) 420-2368 > From Scott.Whipple at cox.com Tue Jul 23 15:42:11 2002 From: Scott.Whipple at cox.com (Whipple, Scott (CCI-Atlanta)) Date: Tue, 23 Jul 2002 15:42:11 -0400 Subject: ARIN Conversion: Template Instructions Now Available Message-ID: Hello Ginny, Would you say there has been enough input on this thread to make any changes to what ARIN is planning? Scott -----Original Message----- From: Dawn Martin [mailto:dawn.martin at wcom.com] Sent: Wednesday, July 17, 2002 6:47 AM To: Whipple, Scott (CCI-Atlanta) Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Hey Scott, It is not the set-up of the role accounts but a copy of every SWIP/netmod template being sent to everyone on the list every time something is sent out or received. At that point I'm sure people would just start ignoring it and deleting those emails assuming it was for someone else. It would make it difficult for the sender to ensure that their SWIP was actually processed. I agree though that we are all saying the same thing about at least having one contact, I just want some of the contact information that I provide to ARIN to be for their eyes only. Dawn -----Original Message----- From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] Sent: Wednesday, July 17, 2002 9:31 AM To: dawn.martin at wcom.com Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Dawn, I think if you used my last proposal you can accomplish what you're looking for. The Admin and org tech would never be seen as long as you had an abuse/noc contact on your org ID. If you don't want all your engineers to be listed you can set up an additional org tech that's a role account for all your engineers or you can list them all out as individuals now that there is no limit for the amount of POC's. The point is they would never be seen as long as you have an abuse/noc contact. If you're worried about having all your employees listed on resources just set up a role account that they all have access to or a few different role accounts giving access to who you want for what you want. This will still give them the ability to add or delete reassignments. I think the 3 of us are saying basically the same thing. Scott -----Original Message----- From: Dawn Martin [mailto:dawn.martin at wcom.com] Sent: Tuesday, July 16, 2002 1:42 PM To: Whipple, Scott (CCI-Atlanta) Cc: dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available I have two thoughts here: 1) The Org records should have at least 1 contact. Why can't the Org decide which & who that contact should be. If the other information we provide is proprietary, why can't the company decide that. ARIN can keep some information private, that could be the folks that are allowed to SWIP and the folks that are allowed to request IPs and change the org information (org. techs & admin techs). I think Lee already voiced my opinion in this, that I don't want my name or the name of several hundred employees listed on all of our resources. For one it would make for a really long lookup. 2) I would really like to see some sample WHOIS outputs. It if very difficult to decide who is going to be where without some samples. I'm just going around in circle's guessing what is going to be put on each record. Dawn Martin WorldCom IP Planning & Policy Analyst dawn.martin at wcom.com (703)886-4746 -----Original Message----- From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] Sent: Tuesday, July 16, 2002 3:53 PM To: ginny listman; Dawn Martin Cc: dbwg at arin.net; lee.howard at wcom.com Subject: RE: ARIN Conversion: Template Instructions Now Available Yes that is what I'm suggesting. I'm also willing to go a little farther on the Org query and lean toward what Lee said. Eliminate the the Admin from ever showing up in a whois query. I don't think we can eliminate the Org techs from showing up unless there is an abuse/noc contact, and from what I think I remember abuse/noc contacts are not required to complete an Org template but the Org tech is required. Because we have to have some contacts showing up for our resources if a company doesn't create an abuse/noc POC we have to list at least the Org Tech contacts. These are my new compromised suggestions. Query 1: An Org Response 1: Only includes abuse or noc contacts unless no abuse/noc contacts are listed, then org techs are listed. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Scott -----Original Message----- From: ginny listman [mailto:ginny at arin.net] Sent: Tuesday, July 16, 2002 12:29 PM To: Dawn Martin Cc: Whipple, Scott (CCI-Atlanta); dbwg at arin.net Subject: RE: ARIN Conversion: Template Instructions Now Available Dawn, My understanding of what Scott is proposing: Query 1: An Org Response 1: ALL POCs associated with the Org. This would include the Administrative contact, as well as the multiple Technical contacts. Most people will not be querying Orgs, but rather the actual resource. Query 2: A resouce that has POCs associated with it Response 2: Display only the resource POCs Query 3: A resource that does NOT have POCs associated with it Response 3: Display the Orgs Tech, NOC and Abuse contacts Is this right, Scott? I would go a step further and suggest that query 3 be broken into the following: Query 3A: A resource that does not have POCs associated with it, and the Org has Abuse and/or NOC contacts Response 3A: Display the Org Abuse and/or NOC Query 3B: A resource that does not have POCs associated with it, and the Org does not have Abuse and/or NOC Response 3B: Display the Org Techs Ginny On Mon, 15 Jul 2002, Dawn Martin wrote: > Scott, > > Are you saying that on any given record the organization would have to have > at least 1 contact. If the organization decided to put additional POC's on > the record the org. could decide not to have the admin listed on the record? > > If so, then the Admin contact could only be pulled up using a specific WHOIS > query? > Something like: whois -h whois.arin.net admin 157.130.0.0 > > That would be fine with me, I think I have said before that if it was a > separate > entry that could be pulled up by savvy WHOIS folks it would be better. > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > From ginny at arin.net Wed Jul 24 07:49:51 2002 From: ginny at arin.net (ginny listman) Date: Wed, 24 Jul 2002 07:49:51 -0400 (EDT) Subject: ARIN Conversion: Template Instructions Now Available In-Reply-To: Message-ID: On the list there were comments from 3 people from 2 companies. I have also received a few comments off-list. I don't think this is a fair representation of the community. There is 12 weeks between release and the Public Policy and Member Meeting. That should be enough time for people to see the changes and get a better feel for what they want. I believe WHOIS output will be a topic for the agenda. Ginny On Tue, 23 Jul 2002, Whipple, Scott (CCI-Atlanta) wrote: > Hello Ginny, > > Would you say there has been enough input on this thread to make any changes to what ARIN is planning? > > Scott > > -----Original Message----- > From: Dawn Martin [mailto:dawn.martin at wcom.com] > Sent: Wednesday, July 17, 2002 6:47 AM > To: Whipple, Scott (CCI-Atlanta) > Cc: dbwg at arin.net > Subject: RE: ARIN Conversion: Template Instructions Now Available > > > Hey Scott, > > It is not the set-up of the role accounts but a copy of every SWIP/netmod template > being sent to everyone on the list every time something is sent out or received. At > that point I'm sure people would just start ignoring it and deleting those emails > assuming it was for someone else. It would make it difficult for the sender to > ensure that their SWIP was actually processed. > > I agree though that we are all saying the same thing about at least having one contact, > I just want some of the contact information that I provide to ARIN to be for their eyes > only. > > Dawn > > > -----Original Message----- > From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] > Sent: Wednesday, July 17, 2002 9:31 AM > To: dawn.martin at wcom.com > Cc: dbwg at arin.net > Subject: RE: ARIN Conversion: Template Instructions Now Available > > > Dawn, > > I think if you used my last proposal you can accomplish what you're looking for. The Admin and org tech would never be seen as long as you had an abuse/noc contact on your org ID. If you don't want all your engineers to be listed you can set up an additional org tech that's a role account for all your engineers or you can list them all out as individuals now that there is no limit for the amount of POC's. The point is they would never be seen as long as you have an abuse/noc contact. If you're worried about having all your employees listed on resources just set up a role account that they all have access to or a few different role accounts giving access to who you want for what you want. This will still give them the ability to add or delete reassignments. I think the 3 of us are saying basically the same thing. > > Scott > > -----Original Message----- > From: Dawn Martin [mailto:dawn.martin at wcom.com] > Sent: Tuesday, July 16, 2002 1:42 PM > To: Whipple, Scott (CCI-Atlanta) > Cc: dbwg at arin.net > Subject: RE: ARIN Conversion: Template Instructions Now Available > > > I have two thoughts here: > > 1) The Org records should have at least 1 contact. Why can't the Org decide which & > who that contact should be. If the other information we provide is proprietary, > why can't the company decide that. ARIN can keep some information private, that > could be the folks that are allowed to SWIP and the folks that are allowed to > request IPs and change the org information (org. techs & admin techs). I think > Lee already voiced my opinion in this, that I don't want my name or the name of > several hundred employees listed on all of our resources. For one it would make for > a really long lookup. > > 2) I would really like to see some sample WHOIS outputs. It if very difficult to decide > who is going to be where without some samples. I'm just going around in circle's > guessing what is going to be put on each record. > > Dawn Martin > WorldCom IP Planning & Policy Analyst > dawn.martin at wcom.com > (703)886-4746 > > > -----Original Message----- > From: Whipple, Scott (CCI-Atlanta) [mailto:Scott.Whipple at cox.com] > Sent: Tuesday, July 16, 2002 3:53 PM > To: ginny listman; Dawn Martin > Cc: dbwg at arin.net; lee.howard at wcom.com > Subject: RE: ARIN Conversion: Template Instructions Now Available > > > Yes that is what I'm suggesting. I'm also willing to go a little farther on the Org query and lean toward what Lee said. Eliminate the the Admin from ever showing up in a whois query. I don't think we can eliminate the Org techs from showing up unless there is an abuse/noc contact, and from what I think I remember abuse/noc contacts are not required to complete an Org template but the Org tech is required. Because we have to have some contacts showing up for our resources if a company doesn't create an abuse/noc POC we have to list at least the Org Tech contacts. These are my new compromised suggestions. > > Query 1: An Org > Response 1: Only includes abuse or noc contacts unless no abuse/noc contacts are listed, then org techs are listed. > > Query 2: A resouce that has POCs associated with it > Response 2: Display only the resource POCs > > Query 3A: A resource that does not have POCs associated with it, and the > Org has Abuse and/or NOC contacts > Response 3A: Display the Org Abuse and/or NOC > > Query 3B: A resource that does not have POCs associated with it, and the > Org does not have Abuse and/or NOC > Response 3B: Display the Org Techs > > Scott > > > -----Original Message----- > From: ginny listman [mailto:ginny at arin.net] > Sent: Tuesday, July 16, 2002 12:29 PM > To: Dawn Martin > Cc: Whipple, Scott (CCI-Atlanta); dbwg at arin.net > Subject: RE: ARIN Conversion: Template Instructions Now Available > > > Dawn, > > My understanding of what Scott is proposing: > > Query 1: An Org > Response 1: ALL POCs associated with the Org. This would include the > Administrative contact, as well as the multiple Technical contacts. Most > people will not be querying Orgs, but rather the actual resource. > > Query 2: A resouce that has POCs associated with it > Response 2: Display only the resource POCs > > Query 3: A resource that does NOT have POCs associated with it > Response 3: Display the Orgs Tech, NOC and Abuse contacts > > Is this right, Scott? > > I would go a step further and suggest that query 3 be broken into the > following: > > Query 3A: A resource that does not have POCs associated with it, and the > Org has Abuse and/or NOC contacts > Response 3A: Display the Org Abuse and/or NOC > > Query 3B: A resource that does not have POCs associated with it, and the > Org does not have Abuse and/or NOC > Response 3B: Display the Org Techs > > > Ginny > > On Mon, 15 Jul 2002, Dawn Martin wrote: > > > Scott, > > > > Are you saying that on any given record the organization would have to have > > at least 1 contact. If the organization decided to put additional POC's on > > the record the org. could decide not to have the admin listed on the record? > > > > If so, then the Admin contact could only be pulled up using a specific WHOIS > > query? > > Something like: whois -h whois.arin.net admin 157.130.0.0 > > > > That would be fine with me, I think I have said before that if it was a > > separate > > entry that could be pulled up by savvy WHOIS folks it would be better. > > > > Dawn Martin > > WorldCom IP Planning & Policy Analyst > > dawn.martin at wcom.com > > (703)886-4746 > > > > > From ebohlin at uu.net Wed Jul 24 18:41:15 2002 From: ebohlin at uu.net (Einar Bohlin) Date: Wed, 24 Jul 2002 18:41:15 -0400 Subject: netnames, logic, cust net updates Message-ID: <20020724184115.A27165@uu.net> Hi, With the new templates netnames will no longer need to be unique. Are they then required? Can we put "customer-net" on each and every reassignment we do? The following is pretty rare, but can one of our downstreams still reassign an entire reallocation? I mean if we reallocate a /23, can they reallocate or reassign the /23? What eliminates the confusion that might occur with the networks only being described by the net range? By the way, we plan to do this: reallocate to downstream ISPs reassign-detailed to some customers reassign simple to many customers and netmod to delete all three of the above. Is this going to work for assigning nets and getting them back? I'll beta this, but am I on the right track here for coding purposes? We currently have customer nets with one contact. Often our customers want us to update that contact to a new one. Can we do this with the new templates? How? Example, if I reallocate a /22 to a downstream and in the process create an org, and an org poc, and the org poc is wrong, will I as the upstream be able to replace the org poc on the org? Regards, Einar Bohlin IP Planning Analyst WorldCom, Inc. Phone: USA 703 886-7362 email: einar.bohlin at wcom.com From ginny at arin.net Thu Jul 25 09:45:50 2002 From: ginny at arin.net (ginny listman) Date: Thu, 25 Jul 2002 09:45:50 -0400 (EDT) Subject: netnames, logic, cust net updates In-Reply-To: <20020724184115.A27165@uu.net> Message-ID: On Wed, 24 Jul 2002, Einar Bohlin wrote: > Hi, > > With the new templates netnames will no longer need to > be unique. Are they then required? Can we put > "customer-net" on each and every reassignment we do? The purpose of this field is to allow you to specify a secondary identifier, e.g., one that you might use for internal tracking, to facilitate whois queries. If you use the same identifier, it will make it difficult to query by netname, but there is nothing preventing you from doing this. > > The following is pretty rare, but can one of our > downstreams still reassign an entire reallocation? I > mean if we reallocate a /23, can they reallocate or > reassign the /23? What eliminates the confusion > that might occur with the networks only being > described by the net range? > ARIN will still allow the full reassignment of a network block. There will be a 'Parent Handle' displayed in WHOIS that will provide the necessary clarification. > By the way, we plan to do this: > > reallocate to downstream ISPs > reassign-detailed to some customers > reassign simple to many customers > and > netmod to delete all three of the above. > > Is this going to work for assigning nets and getting > them back? I'll beta this, but am I on the right > track here for coding purposes? > Yes, it should work this way. You can use a netmod to remove all reassignments, but can not delete a reallocate or reassign-detailed with a reassign-simple template. > We currently have customer nets with one contact. > Often our customers want us to update that contact to > a new one. Can we do this with the new templates? > How? Example, if I reallocate a /22 to > a downstream and in the process create an org, and an > org poc, and the org poc is wrong, will I as the > upstream be able to replace the org poc on the org? > When reallocating a network block, you are suppose to provide different POCs, thereby delegating responsibility for that network to someone else and, therefore the downstream is suppose to manage that information. Since only the Admin is authorized to change POCs on the org, it would mean you would have to be the Admin to do this. However, if you want to change the POCs on the resources, you could establish yourself as an alternate Tech contact on the org. I suggest that if you plan to do something like this, that you establish the downstream org prior to submitting the reallocate template. Then on the reallocate template you should only provide the Org ID. Ginny Listman Director of Engineering ARIN From ginny at arin.net Fri Jul 26 15:03:07 2002 From: ginny at arin.net (ginny listman) Date: Fri, 26 Jul 2002 15:03:07 -0400 (EDT) Subject: Beta WHOIS v0.3 Released Message-ID: ARIN has release Beta WHOIS version 0.3. This version has updated many of the known bugs, as well as implemented some new features. For full details, review the WHOIS Beta website at: http://www.arin.net/tools/whois_update.html Although, the help screen has been written, displaying it has not been implemented in the software. There are some differences from the WHOIS document that was posted to the list in March. I have included it below. I encourage everyone to read it, discover the new features of WHOIS and give it a test. Ginny Listman Director of Engineering ARIN ******************** ARIN's WHOIS service provides a mechanism for finding contact and registration information for resources registered with ARIN. ARIN's database contains IP addresses, autonomous system (AS) numbers, organizations or customers that are associated with these resources, and related Points of Contact (POC). ARIN's WHOIS will NOT locate any domain-related information, or any information relating to military networks. Please use whois.internic.net to locate domain information, and whois.nic.mil for military network information. Many operating systems provide a WHOIS utility. To conduct a query from the command line, the format is: whois -h hostname identifier e.g. whois -h whois.arin.net To obtain a more specific response, you may conduct a search by using certain flags. Many of these flags can be combined to indicate the desired output. Flags must be separated from each other and from the search term by a space. Your results will vary depending on the refinements you apply in your search. Listed below are the flags currently available; you may only use one flag from each flag-type in a query (i.e. one record type, one attribute, etc.). Query-by-record-type: --------------------- To limit your query to a specific record type, include one of the following flags: n Network address space a Autonomous systems p Points of contact o Organizations c End-user customers Query-by-attribute: ------------------- To limit your query to a specific record attribute, include one of the following flags: @ Searches for matches by the domain-portion of an email address ! Searches for matches by handle or id . Searches for matches by name Searches that retrieve a single record will display the full record. Searches that retrieve more than one record will be displayed in list output. Display flags: -------------- To modify the way that the query results display, include one of the following flags: + Shows detailed (aka 'full' output) display for EACH match - Show summary only (aka 'list' output), even if single match returned The + flag cannot be used with the sub-query feature described below. Record hierarchy: ----------------- Records in the ARIN WHOIS database have hierarchical relationship with other records. To display those related records, use the following flags: < Displays the record related up the hierarchy. For a network, display the supernet, or parent network in detailed (full) format. > Displays the record(s) related down the hierarchy. For a network, display the subdelegation(s), or subnets, below the network, in summary (list) format. For an organization or customer, display the resource(s) registered to that organization or customer, in summary (list) format. Wild card queries: ------------------ WHOIS supports wild card queries. This feature is only supported as a trailing character option. To take advantage of this append the query with an asterisk (*). This can also be used in combination with any flags defined above. Other helpful hints: -------------------- To guarantee matching only a single record, look it up by its handle using a handle-only search. In the record summary line, the handle is shown in parenthesis after the name. When using a handle to conduct a search for POC information, be sure to add the -ARIN extension. Queries that return more than 256 results will stop displaying data after the 256th result. You may want to narrow your search criteria or add flags to your query to limit the results. To search on an individual's name, you may enter the last name, or to further restrict results, use the last name and first name, separated by a comma. For example: Smith, John. From jiml at mrtg.noc.adelphia.net Fri Jul 26 15:15:54 2002 From: jiml at mrtg.noc.adelphia.net (James W. Laferriere) Date: Fri, 26 Jul 2002 15:15:54 -0400 (Eastern Daylight Time) Subject: Beta WHOIS v0.3 Released In-Reply-To: Message-ID: Hello Ginny , Please place the url: for the new versions in each announcement . Saves me a tad bit of searching each time . Tia , JimL On Fri, 26 Jul 2002, ginny listman wrote: > ARIN has release Beta WHOIS version 0.3. This version has updated many of > the known bugs, as well as implemented some new features. For full > details, review the WHOIS Beta website at: > http://www.arin.net/tools/whois_update.html > > Although, the help screen has been written, displaying it has not been > implemented in the software. There are some differences from the WHOIS > document that was posted to the list in March. I have included it below. I > encourage everyone to read it, discover the new features of WHOIS and give > it a test. > > Ginny Listman > Director of Engineering > ARIN > > ******************** > > ARIN's WHOIS service provides a mechanism for finding contact and registration > information for resources registered with ARIN. ARIN's database contains IP > addresses, autonomous system (AS) numbers, organizations or customers that are > associated with these resources, and related Points of Contact (POC). > > ARIN's WHOIS will NOT locate any domain-related information, or any information > relating to military networks. Please use whois.internic.net to locate domain > information, and whois.nic.mil for military network information. > > Many operating systems provide a WHOIS utility. To conduct a query from the > command line, the format is: > whois -h hostname identifier e.g. whois -h whois.arin.net > > To obtain a more specific response, you may conduct a search by using certain > flags. Many of these flags can be combined to indicate the desired output. > Flags must be separated from each other and from the search term by a space. > Your results will vary depending on the refinements you apply in your search. > Listed below are the flags currently available; you may only use one flag from > each flag-type in a query (i.e. one record type, one attribute, etc.). > > > Query-by-record-type: > --------------------- > To limit your query to a specific record type, include one of the following > flags: > n Network address space > a Autonomous systems > p Points of contact > o Organizations > c End-user customers > > > Query-by-attribute: > ------------------- > To limit your query to a specific record attribute, include one of the > following flags: > @ Searches for matches by the domain-portion of an email > address > ! Searches for matches by handle or id > . Searches for matches by name > > Searches that retrieve a single record will display the full record. Searches > that retrieve more than one record will be displayed in list output. > > > Display flags: > -------------- > To modify the way that the query results display, include one of the > following flags: > + Shows detailed (aka 'full' output) display for EACH match > - Show summary only (aka 'list' output), even if single match > returned > > The + flag cannot be used with the sub-query feature described below. > > > Record hierarchy: > ----------------- > Records in the ARIN WHOIS database have hierarchical relationship with other > records. To display those related records, use the following flags: > > < Displays the record related up the hierarchy. For a network, > display the supernet, or parent network in detailed (full) > format. > > Displays the record(s) related down the hierarchy. For a network, > display the subdelegation(s), or subnets, below the network, in > summary (list) format. For an organization or customer, display > the resource(s) registered to that organization or customer, in > summary (list) format. > > > Wild card queries: > ------------------ > WHOIS supports wild card queries. This feature is only supported as a trailing > character option. To take advantage of this append the query with an asterisk > (*). This can also be used in combination with any flags defined above. > > > Other helpful hints: > -------------------- > To guarantee matching only a single record, look it up by its handle using a > handle-only search. In the record summary line, the handle is shown in > parenthesis after the name. > > When using a handle to conduct a search for POC information, be sure to add > the -ARIN extension. > > Queries that return more than 256 results will stop displaying data after the > 256th result. You may want to narrow your search criteria or add flags to your > query to limit the results. > > To search on an individual's name, you may enter the last name, or to further > restrict results, use the last name and first name, separated by a comma. For > example: Smith, John. > James W. Laferriere Research Engineer jlaferriere at adelphiacom.net 814.260.3697 Voice 814.260.3760 Fax From cathym at arin.net Fri Jul 26 15:46:39 2002 From: cathym at arin.net (Cathy Murphy) Date: Fri, 26 Jul 2002 15:46:39 -0400 (EDT) Subject: Beta WHOIS v0.3 Released In-Reply-To: Message-ID: On Fri, 26 Jul 2002, James W. Laferriere wrote: > > Hello Ginny , Please place the url: for the new versions in each > announcement . Saves me a tad bit of searching each time . Tia , JimL Thanks for the suggestion Jim. So that the rest of you don't have to dig through the website, beta whois is available at: beta.arin.net port 4344 TIA for testing! Cathy Murphy Principal Software Engineer American Registry for Internet Numbers (ARIN) > On Fri, 26 Jul 2002, ginny listman wrote: > > > ARIN has release Beta WHOIS version 0.3. This version has updated many of > > the known bugs, as well as implemented some new features. For full > > details, review the WHOIS Beta website at: > > http://www.arin.net/tools/whois_update.html > > > > Although, the help screen has been written, displaying it has not been > > implemented in the software. There are some differences from the WHOIS > > document that was posted to the list in March. I have included it below. I > > encourage everyone to read it, discover the new features of WHOIS and give > > it a test. > > > > Ginny Listman > > Director of Engineering > > ARIN > > > > ******************** > > > > ARIN's WHOIS service provides a mechanism for finding contact and registration > > information for resources registered with ARIN. ARIN's database contains IP > > addresses, autonomous system (AS) numbers, organizations or customers that are > > associated with these resources, and related Points of Contact (POC). > > > > ARIN's WHOIS will NOT locate any domain-related information, or any information > > relating to military networks. Please use whois.internic.net to locate domain > > information, and whois.nic.mil for military network information. > > > > Many operating systems provide a WHOIS utility. To conduct a query from the > > command line, the format is: > > whois -h hostname identifier e.g. whois -h whois.arin.net > > > > To obtain a more specific response, you may conduct a search by using certain > > flags. Many of these flags can be combined to indicate the desired output. > > Flags must be separated from each other and from the search term by a space. > > Your results will vary depending on the refinements you apply in your search. > > Listed below are the flags currently available; you may only use one flag from > > each flag-type in a query (i.e. one record type, one attribute, etc.). > > > > > > Query-by-record-type: > > --------------------- > > To limit your query to a specific record type, include one of the following > > flags: > > n Network address space > > a Autonomous systems > > p Points of contact > > o Organizations > > c End-user customers > > > > > > Query-by-attribute: > > ------------------- > > To limit your query to a specific record attribute, include one of the > > following flags: > > @ Searches for matches by the domain-portion of an email > > address > > ! Searches for matches by handle or id > > . Searches for matches by name > > > > Searches that retrieve a single record will display the full record. Searches > > that retrieve more than one record will be displayed in list output. > > > > > > Display flags: > > -------------- > > To modify the way that the query results display, include one of the > > following flags: > > + Shows detailed (aka 'full' output) display for EACH match > > - Show summary only (aka 'list' output), even if single match > > returned > > > > The + flag cannot be used with the sub-query feature described below. > > > > > > Record hierarchy: > > ----------------- > > Records in the ARIN WHOIS database have hierarchical relationship with other > > records. To display those related records, use the following flags: > > > > < Displays the record related up the hierarchy. For a network, > > display the supernet, or parent network in detailed (full) > > format. > > > Displays the record(s) related down the hierarchy. For a network, > > display the subdelegation(s), or subnets, below the network, in > > summary (list) format. For an organization or customer, display > > the resource(s) registered to that organization or customer, in > > summary (list) format. > > > > > > Wild card queries: > > ------------------ > > WHOIS supports wild card queries. This feature is only supported as a trailing > > character option. To take advantage of this append the query with an asterisk > > (*). This can also be used in combination with any flags defined above. > > > > > > Other helpful hints: > > -------------------- > > To guarantee matching only a single record, look it up by its handle using a > > handle-only search. In the record summary line, the handle is shown in > > parenthesis after the name. > > > > When using a handle to conduct a search for POC information, be sure to add > > the -ARIN extension. > > > > Queries that return more than 256 results will stop displaying data after the > > 256th result. You may want to narrow your search criteria or add flags to your > > query to limit the results. > > > > To search on an individual's name, you may enter the last name, or to further > > restrict results, use the last name and first name, separated by a comma. For > > example: Smith, John. > > > > James W. Laferriere > Research Engineer > jlaferriere at adelphiacom.net > 814.260.3697 Voice > 814.260.3760 Fax > From jiml at mrtg.noc.adelphia.net Fri Jul 26 15:54:22 2002 From: jiml at mrtg.noc.adelphia.net (James W. Laferriere) Date: Fri, 26 Jul 2002 15:54:22 -0400 (Eastern Daylight Time) Subject: Beta WHOIS v0.3 Released In-Reply-To: Message-ID: Hello Cathy , My Bad , I saw all the words 'Code' in the original and ass-u-me'd that it was another release of the Daemon or Client . Again Sorry , JimL On Fri, 26 Jul 2002, Cathy Murphy wrote: > On Fri, 26 Jul 2002, James W. Laferriere wrote: > > Hello Ginny , Please place the url: for the new versions in each > > announcement . Saves me a tad bit of searching each time . Tia , JimL > Thanks for the suggestion Jim. So that the rest of you don't have to dig > through the website, beta whois is available at: > beta.arin.net port 4344 > TIA for testing! > Cathy Murphy > Principal Software Engineer > American Registry for Internet Numbers (ARIN) > > On Fri, 26 Jul 2002, ginny listman wrote: > > > ARIN has release Beta WHOIS version 0.3. This version has updated many of > > > the known bugs, as well as implemented some new features. For full > > > details, review the WHOIS Beta website at: > > > http://www.arin.net/tools/whois_update.html > > > Although, the help screen has been written, displaying it has not been > > > implemented in the software. There are some differences from the WHOIS > > > document that was posted to the list in March. I have included it below. I > > > encourage everyone to read it, discover the new features of WHOIS and give > > > it a test. > > > Ginny Listman > > > Director of Engineering > > > ARIN James W. Laferriere Research Engineer jlaferriere at adelphiacom.net 814.260.3697 Voice 814.260.3760 Fax From cathym at arin.net Tue Jul 30 10:55:49 2002 From: cathym at arin.net (Cathy Murphy) Date: Tue, 30 Jul 2002 10:55:49 -0400 (EDT) Subject: Beta Web Whois Interface Released Message-ID: ARIN has release a web interface to its beta WHOIS server. The interface is available via: http://www.arin.net/tools/new_whois_help.html The newer interface provides more targeted links in its response. Take it for a test drive and let us know what you think! As always, bug reports are welcome. Regards, Cathy Murphy Principal Software Engineer American Registry for Internet Numbers (ARIN) From internetadmin at bestchecks.com Wed Jul 31 21:05:16 2002 From: internetadmin at bestchecks.com (internetadmin) Date: Wed, 31 Jul 2002 21:05:16 -0400 Subject: Eager to see you Message-ID: <200208010105.g7115Cx09831@mx0.n0c.net> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: your.exe Type: audio/x-midi Size: 92167 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_over[1].jpg Type: application/octet-stream Size: 4552 bytes Desc: not available URL: