Re: as-set and origin as usage
-
To: Vesna Manojlovic BECHA@localhost
-
From: nicolas <henry.nicolas@localhost
-
Date: Mon, 13 Dec 2010 17:15:00 +0100
-
Cc: db-help@localhost
Hello,
Thanks a lot for this precise reply :)
Regards,
On Mon, 13 Dec 2010 16:48:53 +0100, Vesna Manojlovic BECHA@localhost
wrote:
> Hi Nicolas,
>
> On 12/13/10 3:47 PM, nicolas wrote:
>> Hello everybody,
>>
>> A few days ago I intended a RIPE RPSL training.
>> Now I'm writing a summary for my colleagues and there something I don't
>> remember perfectly, it's about the as-set object.
>>
>> Using an as-set object, I can either start its name with an origin as
or
>> directly put the name (ex. AS-Customers).
>> Under which circumstance should I specify the origin AS?
>
> You can choose to do it, if you like.
>
> The difference is: if you specify the name which starts with your AS,
> then you need to be able to pass the authentication of the maintainer of
> your AS number (aut-num object).
>
> That means that you are the only one able to create the as-set object
> AS12345:as-customers (if your AS number is AS12345)
>
> Otherwise, you need to find the unique name under the "as-" name-space
;-)
> (as-customers is taken...)
>
> ripe_ncc:becha:~ $ whois -r as-customers
> % This is the RIPE Database query service.
> % The objects are in RPSL format.
> %
> % Information related to 'AS-CUSTOMERS'
>
> as-set: AS-CUSTOMERS
> descr: WWWGBG and customer ASNs
> members: AS41136
> members: AS29602
> tech-c: WGS2-RIPE
> admin-c: WGS2-RIPE
> mnt-by: WWWGBG-MNT
> source: RIPE # Filtered
>
>> Thank you very much for your help,
>>
> Regards,
> Vesna