[ietf85-tech] Addressing

[Tauber, Tony]

Hi Jim,

So far there only seem to be IRR objects for the two older prefixes.

ttauber-desktop-~ 19: whois -h whois.radb.net  -i origin AS56554
Warning: RIPE flags used with a traditional server.
route:      130.129.0.0/16
descr:      IETF meeting
origin:     AS56554
mnt-by:     MAINT-AS852
changed:    backbone at telus.com 20110628  #20:50:45Z
source:     RADB

route6:     2001:df8::/32
descr:      IETF meeting
origin:     AS56554
mnt-by:     MAINT-AS852
changed:    backbone at telus.com 20110628  #20:49:29Z
source:     RADB

And an aut-num object:

aut-num:        AS56554
as-name:        IETF-MEETING
descr:          Internet Society
descr:          IETF Meeting Network
org:            ORG-IS136-RIPE
import:         from AS3220 accept ANY
import:         from AS8674 accept ANY
export:         to AS3220 announce ANY
export:         to AS8674 announce ANY
admin-c:        DUMY-RIPE
tech-c:         DUMY-RIPE
notify:         jim at daedelus.com
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         netnod-mnt
mnt-routes:     netnod-mnt
changed:        hostmaster at ripe.net 20110316
source:         RIPE



But nothing for the new prefixes that I can find.

How do you want to handle these registrations?

Thanks,

Tony


On 10/10/12 1:51 PM, "Jim Martin" <jim at daedelus.com> wrote:

>Gentlepeople,
>	Ok, for addressing this time around, we'll use the usual blocks:
>
>	130.129.0.0/16
>	2001:df8::/32
>
>	Advertised out of AS56554.
>
>	We'll also advertise our new "legitimate" blocks from RIPE, and will
>figure out how to use these in the future:
>
>	31.130.224.0 - 31.130.239.255 (31.130.224.0/20)
>	31.133.128.0 - 31.133.191.255 (31.133.128.0/18)
>	2001:67c:1230::/46
>	2001:67c:370::/48
>
>	Thanks!
>
>	- Jim
>
>_______________________________________________
>ietf85-tech mailing list
>ietf85-tech at daedelus.com
>http://www.daedelus.com/mailman/listinfo/ietf85-tech