The AUP is the same for both systems. The intent of each system is different however. If you are intending to do massive scripting of any sort, we prefer (and appreciate) that traffic going to the batch pool. This is for two (main) reasons
1) Verisign registry allows certain types of traffic to go to certain of their registry pools. Regular traffic for regular registrations, and "batch" pool for massive scripting - typically against name dropped. We've mimicked this architecture by placing a system outside of our normal pool. 2) The two different types of traffic have two different kinds of effects on our system. By allowing you to point your traffic at two systems, we can provision accordingly. I.E. the rr-n1-tor system for regular traffic is designed and setup in such a way that normal traffic across all systems is best provisioned and handled. The batch pool is typically used for data gathering from the RWI and attempting to get dropped names (primarily from Verisign, but for CIRA's TBR as well, etc). It's tweaked to handle this traffic. By isolating the traffic we allow the best service in both systems, can get more realistic usage data from each system (instead of having data from one type of traffic obfuscating the other). The intent of the AUP is to disincent resellers from abusing our systems in any way. The general guidelines are something to keep in mind regardless of which system you're using. It's our way of saying "This is what we suggest, please keep these things in mind, if you're naughty or affect system performance we have recourse to remedy the situation" Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] > Sent: September 11, 2002 8:12 AM > To: [EMAIL PROTECTED] > Subject: Re: Batch.opensrs.net > > > What about the AUP for the batch pool? > > I've found two answers as well: > > 1. Some of the actions that will not be tolerated (...) - processing > commands in excess of 3 transactions per second, repetitive or otherwise > > 2. Requesting a name more than once every 5 minutes is considered abuse > > Nothing is stated about difference of the two pools. > > Thanks. > Andrew. > > > ----- Original Message ----- > From: "Charles Daminato" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Wednesday, September 11, 2002 4:05 PM > Subject: RE: Batch.opensrs.net > > > > You've gotten two different answers ;) > > > > Our batch.opensrs.net system goes to Verisign's batch pool. > > > > The rr-n1-tor.opensrs.net system goes to Verisign's guarantee pool. > > > > Charles Daminato > > OpenSRS Product Manager > > Tucows Inc. - [EMAIL PROTECTED] > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] > > > Sent: September 10, 2002 5:37 PM > > > To: [EMAIL PROTECTED] > > > Subject: Batch.opensrs.net > > > > > > > > > Hello all, > > > > > > I was looking for the information concerning batch pool, > > > batch.opensrs.net, and found very few on the OpenSRS web site. Can > > > anyone describe the acceptable usage limits for this pool. > > > > > > Also, does OpenSRS forward these requests to the Verisign's batch > pool > > > or it uses the guarantee pool? > > > > > > Regards, > > > Andrew Ivanov > > > > > >
