RIPE-227?

Hank,

The robot has now been fixed and recognizes all templates when using the 
correct titles including the '#'.

Please do *NOT* remove the template titles as presented on the request 
form(s). The robot will not recognize the form and set it to a lower priority.

As I said in my previous message the robot gave a warning (not an error) for 
the templates #[ANNOUNCED ADDRESS RANGES]# and #[PEERING CONTACTS]# and the 
requests were immediately forwarded to a hostmaster for processing. Requests 
containing errors should be corrected and resent, the keyword NOAUTO can be 
used to bypass the robot.

Kind regards,

Sabrina Waschke

-- 

o------------------------------------------o
| Sabrina Waschke         sabrina at ripe.net |
| Registration Services Operations Manager |
|                                          |
| RIPE NCC             tel +31 20 535 4444 |
| www.ripe.net         fax +31 20 535 4445 |
o------------------------------------------o
 Hank Nussbacher <hank at att.net.il> writes:
 * At 17:37 09/11/01 +0100, Sabrina Waschke wrote:
 * 
 * >The robot doesn't recognize these two templates yet. This will be fixed.
 * >Thanks for reporting it, Hank.
 * 
 * So I stripped off the template tags and resubmitted and got back:
 * 
 * >PLEASE NOTE:
 * >This ticket has *NOT* been identified as a request for IP
 * >addresses or AS numbers.
 * >We will handle this message with lower priority than a request for IP
 * >addresses / AS numbers. If your mail in fact is a request for IP
 * >addresses / AS numbers, there are most likely missing / incorrect
 * >fields in your mail. Please make sure to correct and complete your
 * >request so that we can give it appropriate priority.
 * 
 * So if I submit with ASN template tags, your robot flags it as an error and 
 * returns it.  If I strip off the ASN tags then it gets sent to a lower 
 * priority queue.  What is the magic sequence that will allow my ASN request 
 * to enter a normal queue?
 * 
 * -Hank
 * 
 * 
 * 
 * 
 * >FYI:
 * >The RIPE NCC Database and Software Department are working on a whois
 * >library which will be able to parse and validate whois objects of any
 * >type - that will include multi-line fields, and strictly adhere to the
 * >internal format of the objects in the whois DB.
 * >
 * >Kind regards,
 * >
 * >Sabrina Waschke
 * >
 * >--
 * >
 * >o------------------------------------------o
 * >| Sabrina Waschke         sabrina at ripe.net |
 * >| Registration Services Operations Manager |
 * >|                                          |
 * >| RIPE NCC             tel +31 20 535 4444 |
 * >| www.ripe.net         fax +31 20 535 4445 |
 * >o------------------------------------------o
 * >
 * >  Hank Nussbacher <hank at att.net.il> writes:
 * >  * Does anyone know if the RIPE robot supports RIPE-227 templates?  This
 * >  * fairly new template (Oct 2, 2001) for ASN requests.  The robot saw it
 * >  * as  of the 'RIPE147' type and then proceeded to flag as warnings:
 * >  *
 * >  * >-ANNOUNCED ADDRESS RANGES-
 * >  * >
 * >  * >
 * >  * >Warning #1
 * >  * >
 * >  * >Template was not recognised and *not* processed. Please
 * >  * >check your spelling!
 * >  * >
 * >  * >
 * >  * >-PEERING CONTACTS-
 * >  * >
 * >  * >
 * >  * >Warning #2
 * >  * >
 * >  * >Template was not recognised and *not* processed. Please
 * >  * >check your spelling!
 * >  *
 * >  * So either the template as listed in RIPE-227 is wrong or the robot is 
 * > broken
 * >  * .
 * >  *
 * >  * Thanks,
 * >  * Hank
 * >  *
 * >  *
 *