[address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs

On 06/27/13 13:42, Gert Doering wrote:
> On Wed, Jun 26, 2013 at 08:50:29PM +0300, Andrey Semenchuk wrote:
>> I saw no information inside proposal to remove the objects that
>> referenced to deleted ASN - it's just removing a broken references
>> inside those objects. So, deleting of the broken references is the way
>> to provide integrity to RIPE's database - nothing additional.
> You can't remove the reference to an ASN from a route:/route6: object - you
> have to remove the whole object.
let me to correct myself: "I saw no information inside proposal to 
remove the *resource* objects that
referenced to deleted ASN". Any route object is illegal since the ASN 
does not exists.
As it seems to me, there're two solutions:
- to delete illegal resource;
- to replace reference inside those objects to the placeholder ASN

The first solution is more correct

RFC1786:
=========
The value of the origin attribute will be an AS reference of the form 
AS1234 referring to an aut-num object.  It represents the AS injecting 
this route into the routing mesh.
=========

RIPE-252:
=========
1.2.16  route

... The "route:" attribute is the address prefix of the route and the 
"origin:" attribute is the AS number of the AS that originates the route 
into the interAS routing system.  ...
=========

No ASN - no route object.


-- 
Best wishes,
Andrey Semenchuk

Trifle Internet Service Provider
(056) 731-99-11
www.trifle.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20130627/86217a2c/attachment.html>