<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 06/27/13 13:42, Gert Doering wrote:
<blockquote cite="mid:20130627104235.GW2706@Space.Net" type="cite">
<pre wrap="">On Wed, Jun 26, 2013 at 08:50:29PM +0300, Andrey Semenchuk wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
You can't remove the reference to an ASN from a route:/route6: object - you
have to remove the whole object.</pre>
</blockquote>
let me to correct myself: "I saw no information inside proposal to
remove the <b>resource</b> objects that <br>
referenced to deleted ASN". Any route object is illegal since the
ASN does not exists. <br>
As it seems to me, there're two solutions:<br>
- to delete illegal resource;<br>
- to replace reference inside those objects to the placeholder ASN<br>
<br>
The first solution is more correct<br>
<br>
RFC1786: <br>
=========<br>
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.<br>
=========<br>
<br>
RIPE-252:<br>
=========<br>
1.2.16 route<br>
<br>
... 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. ...<br>
=========<br>
<br>
No ASN - no route object. <br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Best wishes,
Andrey Semenchuk
Trifle Internet Service Provider
(056) 731-99-11
<a class="moz-txt-link-abbreviated" href="http://www.trifle.net">www.trifle.net</a></pre>
</body>
</html>