The robot doesn't recognize these two templates yet. This will be fixed. Thanks for reporting it, 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@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@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 * *
At 17:37 09/11/01 +0100, Sabrina Waschke wrote: How then does one submit an ASN request without being trapped by the robot? -Hank
The robot doesn't recognize these two templates yet. This will be fixed. Thanks for reporting it, 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@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@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 * *
Hank Nussbacher <hank@att.net.il> writes: * At 17:37 09/11/01 +0100, Sabrina Waschke wrote: * * How then does one submit an ASN request without being trapped by the * robot? -Hank The robot gives warnings and the request is passed on to a hostmaster for processing. This is mentioned in the automatic response by the RIPE NCC Automatic Hostmaster Robot. However, if you have an error in your request (e.g. a mandatory field is missing in a maintainer template) you should correct this before resubmitting the request. If you want to bypass the syntax checking robot after it is gone through the robot once and received error messages, you can do so by re-sending the request and putting the keyword "NOAUTO " in the subject of your mail (please include a space at the end of the keyword). Please don't hesitate to contact <lir-help@ripe.net> if you have any further questions. Regards, Sabrina Waschke -- o------------------------------------------o | Sabrina Waschke sabrina@ripe.net | | Registration Services Operations Manager | | | | RIPE NCC tel +31 20 535 4444 | | www.ripe.net fax +31 20 535 4445 | o------------------------------------------o * >The robot doesn't recognize these two templates yet. This will be fixed. * >Thanks for reporting it, 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@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@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 * > * * > * *
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@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@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 * *
participants (2)
-
Hank Nussbacher -
Sabrina Waschke