[ietf79-tech] AS290

[Jim Martin]

Leon,
	I've attached the letter from Interop that has worked for us in the past. Let me know if there's more we can do to help...

	- Jim

On Oct 22, 2010, at 7:51 AM, Joel Jaeggli wrote:

> Ask them if they'll accept a LOA from the holder of record.
> the prefix is used with other OriginAS in the normal course of operations.
> 
> If that fails, then email Ruediger Volk rv at nic.dtag.de and explain the
> situation.
> 
> On 10/21/10 8:35 PM, Xiaoliang Zhao wrote:
>> 130.129.0.0 record in ARIN reads an empty origin AS. Deutch Telecom
>> won't take it unless origin AS=290 or our AS#. Any idea on how to
>> resolve this?
>> 
>> xzhao at xzhao-desktop:~$ whois -h whois.arin.net <http://whois.arin.net>
>> 130.129.0.0
>> ...
>> NetRange:       130.129.0.0 - 130.129.255.255
>> CIDR:           130.129.0.0/16 <http://130.129.0.0/16>
>> OriginAS:
>> 
>> (we can start using 290 from next monday, right? just a safety check)
>> 
>> thanks,
>> Leon
>> 
>> On Wed, Oct 13, 2010 at 4:27 PM, Jim Martin <jim at daedelus.com
>> <mailto:jim at daedelus.com>> wrote:
>> 
>>    On Oct 13, 2010, at 1:08 AM, Xiaoliang Zhao <xzhao at cernet.edu.cn
>>    <mailto:xzhao at cernet.edu.cn>> wrote:
>> 
>>>    Great, thanks for clarification, Jim. I will make sure no AS290
>>>    from us after Oct. 15th.
>>> 
>>>    We have no problem using private AS, but just to clarify:
>>> 
>>>    1) we can use 130.129/16 anytime, right?
>> 
>>     Yes ... Feel free to advertise it anytime. 
>> 
>>>    2) our ISP can be origin AS for 130.129/16, (probably need
>>>    register to irr), yes?
>>> 
>> 
>>    No problem. If you need help making the RIPE changes, just yell.
>>    Alternatively, just ask either of the RIPE guys from Maastricht for
>>    help. 
>> 
>>    - Jim
>> 
>>>    thanks,
>>>    Leon
>>> 
>>>    On Wed, Oct 13, 2010 at 3:19 PM, Jim Martin <
>>>    <mailto:jim at daedelus.com>jim at daedelus.com
>>>    <mailto:jim at daedelus.com>> wrote:
>>> 
>>>        Leon,
>>>               OK, I have a bit of clarity on the use of AS290 now. It
>>>        will be being used for Interop New York from October 15th
>>>        through the 24th. If you want to use it now until the end of
>>>        Thursday, feel free. After that, please don't advertise using
>>>        it until the Morning of the 25th. In the mean time, perhaps
>>>        you could advertise using a private AS to the lab
>>>        infrastructure, and then just strip the AS on the way out?
>>>        Sorry for the hassle, but since it actually does belong to
>>>        Interop and they have a show running, they obviously have
>>>        priority.
>>> 
>>>               - Jim
>>> 
>>>        On Oct 12, 2010, at 9:21 PM, Xiaoliang Zhao wrote:
>>> 
>>>>> I'm confused. Are you actually advertising the block with
>>>        AS290 even though we specifically asked you not to? I don't
>>>        see it on
>>>>> routeviews, so we may be ok, but PLEASE, don't advertise
>>>        anywhere yet.
>>>> 
>>>> my apologies.. I'm too eager for success :) Now, it is stopped.
>>>> 
>>>> just a heads-up: we may need your help to deal with Deutch
>>>        Telecom. They are our ISP's provider and refused to take
>>>        AS290/130.129 from us because it is not in RADB or something
>>>        similar. more details will follow once i heard from our ISP.
>>>> 
>>>> thanks,
>>>> Leon
>>> 
>>> 
>> 
>> 
>> 
>> _______________________________________________
>> ietf79-tech mailing list
>> ietf79-tech at daedelus.com
>> http://www.daedelus.com/mailman/listinfo/ietf79-tech

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 130.129 Authorization.pdf
Type: application/pdf
Size: 61359 bytes
Desc: not available
Url : http://www.daedelus.com/pipermail/ietf79-tech/attachments/20101022/09793b8d/attachment-0001.pdf 
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3675 bytes
Desc: not available
Url : http://www.daedelus.com/pipermail/ietf79-tech/attachments/20101022/09793b8d/attachment-0001.bin