[IPv6-wien] Fwd: NCC#2013041338 IPv6 prefix 2a02:60::/29 allocated to at.funkfeuer

Erich N. Pekarek (spam-protected)
Mon Apr 8 15:12:21 CEST 2013


Hallo Aaron!

On 2013-04-08 14:55, L. Aaron Kaplan wrote:
> Hi!
>
> So, jetzt haben wir ein (v6) /29 ;-)
> Es gehen sich somit mehrere /32 aus.
Das sind gute Nachrichten! Danke!
Ich denke, dass uns das weiterbringen wird und neue Perspektiven eröffnet.

> Viel Spass.
:)
> Backbone wiki wurde upgedated.
Super, Danke!

> lg,
> a.
>
LG
Erich
>
> Begin forwarded message:
>
>> From: RIPE NCC Hostmaster <(spam-protected)>
>> Subject: NCC#2013041338 IPv6 prefix 2a02:60::/29 allocated to at.funkfeuer
>> Date: April 8, 2013 2:47:51 PM GMT+02:00
>> To: "L. Aaron Kaplan" <(spam-protected)>
>> Cc: FunkFeuer Admin <(spam-protected)>, FunkFeuer Admin <(spam-protected)>
>> Reply-To: <(spam-protected)>
>>
>>
>>
>> Dear L. Aaron Kaplan,
>>
>> We have allocated the following prefix of IPv6 address space
>> to your registry at.funkfeuer:
>>
>> 		2a02:60::/29
>>
>> The RIPE database shows the following information:
>>
>> inet6num:       2a02:60::/29
>> netname:        AT-FUNKFEUER-20080218
>> descr:          FunkFeuer - Verein zur Foerderung freier Netze (ZVR: 814804682)
>> country:        AT
>> org:            ORG-FVzF1-RIPE
>> admin-c:        FA1767-RIPE
>> tech-c:         FA1767-RIPE
>> status:         ALLOCATED-BY-RIR
>> notify:         (spam-protected)
>> mnt-by:         RIPE-NCC-HM-MNT
>> mnt-lower:      FUNKFEUER-MNT
>> mnt-routes:     FUNKFEUER-MNT
>> changed:        (spam-protected) 20080218
>> changed:        (spam-protected) 20080218
>> changed:        (spam-protected) 20110905
>> changed:        (spam-protected) 20130408
>> source:         RIPE
>>
>> You may announce this prefix to your BGP peers and request reverse
>> delegation.
>>
>> You can allocate and assign from this range according to policies
>> described in "IPv6 Address Allocation and Assignment Policy" document,
>> http://www.ripe.net/ripe/docs/ipv6policy.html
>>
>> LIRs are required to register all IPv6 space in use as assignments in
>> the RIPE Database.
>>
>> To register these assignments in the RIPE database, you can use:
>> https://www.ripe.net/webupdates
>>
>> For more details on this and how to document these IPv6 assignments, please
>> see:
>>
>> http://www.ripe.net/ripe/docs/ipv6policy.html#assignments_shorter
>> http://www.ripe.net/ripe/docs/ipv6policy.html#registration_assignment
>> http://www.ripe.net/data-tools/support/documentation/documenting-ipv6-assignments-in-the-ripe-database
>>
>> If you have any questions regarding this matter, please do not hesitate to
>> contact <(spam-protected)>.
>>
>>
>> Kind Regards,
>>
>> Radha Ramphul
>> RIPE NCC IP Resource Analyst
>>
>> Join us in Skopje, Macedonia for SEE 2/RIPE NCC Regional Meeting, 22-23 April!
>> Register now:
>> https://www.ripe.net/ripe/meetings/regional-meetings/see-2
>>
>> Practice with the RIPE Database in our brand new RIPE Database Training Course:
>> https://www.ripe.net/lir-services/training/courses/rdb
>>
>> https://www.ripe.net/lir-services/resource-management
>
>
> _______________________________________________
> IPv6-wien mailing list
> (spam-protected)
> https://lists.funkfeuer.at/mailman/listinfo/ipv6-wien

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.funkfeuer.at/pipermail/ipv6-wien/attachments/20130408/0dd5b0c1/attachment.html>


More information about the IPv6-wien mailing list