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]/
[ncc-services-wg] ASDOT data conversion in the RIPE Database
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] Implementation of ASPLAIN Format
- Next message (by thread): [ncc-services-wg] Update to RIPE Database software
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Thu Mar 19 16:58:23 CET 2009
Dear Colleagues,
The RIPE NCC is preparing for the implementation of RFC5396, which
defines the representation of all AS Numbers in the ASPLAIN format.
The RIPE NCC will start using the ASPLAIN format on 25 March 25 2009.
On this day the RIPE NCC will convert any existing ASDOT data in the
RIPE Database into ASPLAIN equivalent data.
There are two ways we will do this:
- If the primary key of the object contains an ASDOT, for example
"aut-num: AS8.0", then the object will be deleted and re-created.
- If the object contains a reference to an ASDOT, for example
"import: from AS8.0", then the object will be modified.
All objects altered in any way will have a "remarks:" attribute and an
extra "changed:" attribute added. Notifications will be sent to the
maintainers of the data for each update.
The maintainers of the data do not need to do anything regarding this
change. The conversion can only be done as part of the software
upgrade. But if you are responsible for any ASDOT data we would ask
that you check the data after the conversion is complete.
Regards,
Denis Walker
Business Analyst
RIPE NCC
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] Implementation of ASPLAIN Format
- Next message (by thread): [ncc-services-wg] Update to RIPE Database software
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]