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 * *