<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">Hi Gert, thanks for your clarification! But you still get my point, do you? If a prefix was assigned to an entity other than the one that is advertising the prefix, for example: 80.187.128.0/22 Announcing: Deutsche Telekom AG (AS3320) Assigned: T-Mobile Deutschland GmbH (AS44178) The information (original prefix receiver) is stored in the RIPE DB, right? It could be compared to what we see via BGP. I am aware that a single entity can have multiple AS numbers, but when different entities are "involved", more transparency would be great. Or am i missing something here? BR, Simon On 29.06.22 10:54, Gert Doering wrote: </div> <blockquote type="cite" cite="mid:YrwTQ7rWYd3qURa0@Space.Net"> <pre class="moz-quote-pre" wrap="">Hi, On Wed, Jun 29, 2022 at 10:30:22AM +0200, Simon Brandt via ripe-atlas wrote: </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">Another example would be a multi ASN company which announces all prefixes from a single ASN via BGP, even though the prefixes are assigned to various AS numbers. Since the RIRs do have the information, to which AS a specific prefix is assigned to, </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> prefixes are not assigned to "AS" numbers, ever. prefixes are assigned to entities, as are AS numbers. ROAs and/or route(6): objects are used to tie both together - and it's in the authority of the network (prefix) holder to state which AS is allowed and expected to announce a given prefix, not the RIR. Repeat: the RIR has no say in "which AS is tied a prefix". Gert Doering -- NetMaster </pre> </blockquote> </body> </html>