Another issue related to the migration

Dear Colleagues,

"Lu, Ping" wrote:
> 
> Andrei,
>   The existing ripe2rpsl tool will automatically translate "AS-" to "ASN-"
> for the aut-num object and I think "ASN-" is more meaningful than "AS_".
>
If nobody objects against Ping's proposal, let's convert them to "ASN-".
I agree that "_" is a bit uncommon.

Regards,

Andrei

 
> Best Regards.
> 
> Ping Lu
> Cable & Wireless Global
> Network Tools and Analysis Group, USA
> W: +1-703-292-2359
> E: plu at cw.net
> 
> > -----Original Message-----
> > From: Andrei Robachevsky [mailto:andrei at ripe.net]
> > Sent: Thursday, March 29, 2001 11:10 AM
> > To: db-wg at ripe.net; routing-wg at ripe.net; Migration TF; lir-wg at ripe.net
> > Subject: Another issue related to the migration
> >
> >
> > Dear Colleagues,
> >
> > [Apologies for duplicate messages]
> >
> > One issue related to RIPE-181 to RPSL migration escaped our
> > attention and has
> > not been discussed. It is related to reserved prefixes that
> > cannot appear in
> > object names according to RPSL specification (RFC2622) which says:
> >
> > "Names starting with certain prefixes are reserved for
> > certain object types.
> > Names starting with "as-" are reserved for as set names.
> > Names starting with
> > "rs-" are reserved for route set names.  Names starting with
> > "rtrs-" are
> > reserved for router set names. Names starting with "fltr-"
> > are reserved for
> > filter set names. Names starting with "prng-" are reserved
> > for peering set
> > names."
> >
> > Unfortunately "as-name:" attribute is an object name in RPSL
> > and we have 133
> > aut-num objects with as-name starting with reserved 'AS-' prefix.
> >
> > Our suggestion how to deal with these objects is:
> >
> > 1. Send a message to the maintainers of these objects asking
> > them to change the
> > name to avoid conflict with RPSL specification.
> > 2. Give two-week notice period after which ripe-dbm will
> > convert non compliant
> > as-names using the following mapping: AS-ASNAME -> AS_ASNAME.
> >
> > This is more a "cosmetic" change as as-name is not even a
> > lookup key in the RIPE
> > Database.
> >
> > Your comments and suggestions are appreciated.
> >
> > Best regards,
> >
> >
> > Andrei Robachevsky
> > DB Group Manager
> > RIPE NCC
> >

-- 
Andrei Robachevsky
DB Group Manager
RIPE NCC