Hi Sascha, I have the feeling this goes right against the "spirit" of the definition of an AS (as of RFC1930, and RIPE-140) - I believe your customer should register his own AS (or you should do it for him), to make things proper. However, I'm not at all sure of these assertions, so if you hear otherwise I will be very interested to know! Cheers, jvv "Sascha E. Pollok" wrote:
Dear Colleagues,
we are currently announcing several prefixes to our three upstream providers. One of our customers is willing to buy a flatrate from another upstream. That customers has a /24 assignment out of a /19 that we announce.
Is it ok to announce that /24 prefix to the new upstream so that we'll have the following route-objects:
route: 213.128.128.0/19 descr: IPHH-BLOCK-B origin: AS12731 notify: guardian@iphh.net mnt-by: AS12731-MNT
route: 213.128.140.0/24 descr: IPHH-BLOCK-B origin: AS12731 notify: guardian@iphh.net mnt-by: AS12731-MNT
Our aut-num object would look like this:
aut-num: AS12731 descr: Internet Port Hamburg descr: Global AS Routing-Policy as-in: from AS1270 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS3300 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS5409 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS8852 100 accept AS-GINKO AND NOT {0.0.0.0/0} as-in: from AS13003 100 accept AS13003 AND NOT {0.0.0.0/0} as-out: to AS1270 announce AS-IPHH as-out: to AS3300 announce AS-IPHH as-out: to AS5409 announce AS-IPHH as-out: to AS8852 announce NONE as-out: to AS13003 announce AS-IPHH as-out: to ASxxxx announce {213.128.140.0/24}
Would that be ok?
Regards, Sascha
--- Sascha E. Pollok Internet Port Hamburg Technical Staff / Network Operations Grosse Reichenstrasse 27 D-20457 Hamburg Germany Tel. +49 (0)40 37 49 19-0 Fax +49 (0)40 37 49 19-29 Email: sp@iphh.de ICQ #38955239
-- Jos� Vieira Vilela Funda��o para a Computa��o Cient�fica Nacional