This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
RPSL - what is going on?
- Previous message (by thread): RIPE-181 to RPSL Migration; Phase 2.
- Next message (by thread): RPSL - what is going on?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hank Nussbacher
hank at att.net.il
Wed May 23 13:38:09 CEST 2001
I've gone through all the RPSL pages listed at: http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html and am starting to wonder if its me that can't work with RPSL or everyone else. The documents on that page above have no consistency. Some are PDF, some are HTML. Response time for getting a response to a reported problem is about 5-7 days. There is no page of bugs found and what is still a bug and what has been fixed (ala Cisco Release Notes). For example, I lost 5 days when I couldn't create a nic-hdl. Turns out I was sending it in as "nic-hdl: auto-1" and there is a bug where lower case "auto-1" doesn't work and one has to use all uppercase. Now I have lost a day on fixing up an aut-num. I am trying to send in an update as follows: >export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736 > > >***Error: valid lines start with attribute names, spaces or # I have tried with the export tag on one line as well as split on two lines as follows: export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736 I just can't get auto-rpsl to accept the export tags. Sorry for the crossposting but I am wondering whether I am the only one who is hitting all these problems? Thanks, Hank
- Previous message (by thread): RIPE-181 to RPSL Migration; Phase 2.
- Next message (by thread): RPSL - what is going on?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]