October 2012 - NZNOG - lists.nznog.org

If you are using APNIC as an RPKI trust anchor, please update your Trust Anchor Set.
by George Michaelson 14 Oct '12

14 Oct '12

If you are using APNIC as an RPKI trust anchor, please update your Trust Anchor Set. APNIC will be switching to a new RPKI 'split' trust anchor system on the 25th of October. This change is needed to align APNIC administered resources with their allocation hierarchy. These resources will also be certified under each responsible parent registry at the appropriate time. In accordance with RFC6490 the old APNIC Trust Anchor Locator, associated certificate and repository will be removed, when the certificate expires on the 28th of October. 5 new Trust Anchor Locator (TAL) have been published. These will be kept up to date as an independent trust anchor set for resources maintained by APNIC. The production cycle will start on the 25th of October. Relying parties must add these new TAL by the 25th of October in order to maintain continuity of validation. If you have any questions please contact me. George Michaelson (ggm(a)apnic.net) Please add the following to your trust anchor set: rsync://rpki.apnic.net/repository/apnic-rpki-root-afrinic-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuMLL96YV9pf0rZ4Ow/bk cgpoPfsRzkcgmisyCuMUdotHwrp8pepujhohatScRK09ILRrZYCdpX4121MJhqXC P3u3hy9fF0CeARKX/Q82nJccD4dtUp23UcFys8hwJgNYZI910ajkAxwNT//H/TFw oUYbzZGBR7o2awMc7GdQl/j6dgOkV6AfYy5DyDEgOUNHnUxED2rreefL/E2Fr2ST Esar6bTR4Tg4+nVF1PjAkgN0tKZYe4wZ6VmtqV/VTngSLysim6av7ki+JR3cVgVU OqXeh1vPjH2tNu6u9bX37ZrdVb6NBRer9I99IDbKvyhELb6nzo8+Q74zga9HI+Pf QwIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-arin-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAp6vscYtzhe0CfFk5Ro44 llPhsInXtfAxqfYmK7m9V3khkqK3d3/ZAW6pcJm7qW8XhEGl+F5mUeeLIm5JoIhr kT5B5M6uL0VlCCkZJH4h76ybOa83vWITNZEDy9L3c3nK4S+Basu3vYoE4ICXGG+J 7zg5Iw9saV+p03E2w1g16pt1QI3Cnggp6edkeWClEz3aPw/ULOIHb7YmatWwdERl tL9LsuMSKszQLUY7F4XVpxey/rJYAZgzDUh+b6813WAClCkkydNjsbviuekAWJbx sW7Mcw53u30K4g8MP03CjkDOubyoR4Qo99R1UQJCdrRsFKbSSfN/fOA4y7ikc3xs jQIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-iana-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx9RWSL61YAAYumEiU8z8 qH2ETVIL01ilxZlzIL9JYSORMN5Cmtf8V2JblIealSqgOTGjvSjEsiV73s67zYQI 7C/iSOb96uf3/s86NqbxDiFQGN8qG7RNcdgVuUlAidl8WxvLNI8VhqbAB5uSg/Mr LeSOvXRja041VptAxIhcGzDMvlAJRwkrYK/Mo8P4E2rSQgwqCgae0ebY1CsJ3Cjf i67C1nw7oXqJJovvXJ4apGmEv8az23OLC6Ki54Ul/E6xk227BFttqFV3YMtKx42H cCcDVZZy01n7JjzvO8ccaXmHIgR7utnqhBRNNq5Xc5ZhbkrUsNtiJmrZzVlgU6Ou 0wIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-lacnic-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyoYPp3l3DWyPtLWrmRn4 Oux9hQ5bxd0SX/f6ygHxik+I3eMJP5J0Pr2e500tyXb2uKsX9kDqu/kckr+TUMhV BHd5yAv8OAE3YYEvpz/7uTX7cYy2yUeA76OEP75Y88OIQEzGpPLNpIzDxMggxuDh IhkA5xMiUJgVoEgmWSzR+MuRBjv2422wAGB5GpLgYsOjpwvG0VPmhnE+39+10ucQ CLt0Ny5kOR4an2tkvHjm7rzKDnFm8MWxPzAWESdf+8g7ITzSglqxDNiK5E5rdzNt h1Kvp+9RwaFArw6Ky1A4HhnoplN4EfKwxq0YamuKV0ZTTpWyT2+qDuE6sOfHRbJ0 5QIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-ripe-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwsQlXmEklLYApoDo7GEa NNTEGFPU5wJpi04iXuga2xn+g/TMLOlyJbjuPYRtRm/7VbRnN3m9Ta+WETy03+Fm EbXzB4xxhJKVik/ARHBnrBWhLyURy8Q5/XplE9cJein37IE1mIsbKM7o/90S225w 7GuvW7T4kjPWYmBFOywHWsfQO1EdsgiJrkz+Ab67ZkdSIiKHkf2UE6/MrbDEj+QK 9+s/vKH8BtDhaLmTWY+bVvfJ3+AWDH6roo1ozbl5yamQFbLOl3ns30f3yOJcNSNu /qgMQRRyp2sXXQovhTy8yqm3LFspaCWnTmQtBieWZwibuOa4Z27A1FzTMst2T4wY /wIDAQAB

1 0

Xtra DNS
by Simon Lyall 14 Oct '12

14 Oct '12

Can somebody on the team that looks after Xtra's DNS servers please contact me. I'm seeing problems with a specific record that works okay with most/all other NZ ISPs ( the record has a short TTL but has been broken for days ). My work's site has a work-around in place but various other sites ( like some at Mozilla ) will be broken for Xtra customers. The servers I am talking about are: 202.27.184.3 alien 202.27.184.5 terminator 202.27.158.40 dnsc1 202.27.156.72 dnsc2 -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Added a new Range of IP addresses in NZ - Geolocation updates
by Greg Theron 09 Oct '12

09 Oct '12

Hi Guys We have setup an ISP in New Zealand and have allocated part of our Australian IP address space over here. Could I please ask everyone to update their Geolocation Databases to include the 180.222.160.0/20 as being based in Auckland? Thanks heaps Greg inetnum: 180.222.160.0 - 180.222.175.255 netname: TELCOINABOX-AP descr: Telcoinabox Pty Ltd descr: Telcoinabox NZ Limited descr: Level 4, 15 Huron Street, Takapuna, Auckland country: NZ admin-c: TNLN1-AP<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=TNLN1-AP&form_type=advanc…> tech-c: TNLN1-AP<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=%20TNLN1-AP&form_type=adv…> mnt-by: APNIC-HM<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=%20APNIC-HM&form_type=adv…> mnt-lower: MAINT-TELCOINABOX-AU<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=MAINT-TELCOINABOX-AU&form…> mnt-routes: MAINT-TELCOINABOX-AU<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=MAINT-TELCOINABOX-AU&form…> mnt-irt: IRT-TELCOINABOX-AU status: ALLOCATED PORTABLE remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ remarks: This object can only be updated by APNIC hostmasters. remarks: To update this object, please contact APNIC remarks: hostmasters and include your organisation's account remarks: name in the subject line. remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ changed: hm-changed(a)apnic.net 20091014 changed: hm-changed(a)apnic.net 20121009 source: APNIC Greg Theron [cid:image001.png(a)01CDA6D7.4DA3C3D0] Telcoinabox NZ Limited | Level 4, 15 Huron Street, Takapuna, Auckland D: +64 9 4880106 | M: +64 27 874 4783 | F: 0800 883 526 telcoinabox.co.nz Add us on social media: g [cid:image002.png(a)01CDA6D7.4DA3C3D0]<http://facebook.com/telcoinabox> [cid:image003.png(a)01CDA6D7.4DA3C3D0] <http://www.linkedin.com/company/419134?trk=tyah> [cid:image004.png(a)01CDA6D7.4DA3C3D0] <http://twitter.com/#!/telcoinabox_nz> ________________________________ The information contained in this electronic mail transmission is intended by Telcoinabox (NZ) Ltd for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission.

4 4

FW: ICANN News Alert -- Implementing the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA
by Leo Vegoda 08 Oct '12

08 Oct '12

Hi, The consultation described in the announcement below is being run to gather input on the best way to implement the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA, which was ratified in May. In particular, we are keen to gather input on the most useful registry format for the Recovered IPv4 Pool. If you have a particular preference, please provide input to the consultation. Many thanks, Leo Vegoda From: ICANN News Alert Sent: Thursday, October 04, 2012 1:37 PM Subject: ICANN News Alert -- Implementing the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA <http://www.icann.org/> Description: ICANN News Alert <http://www.icann.org/en/news/announcements/announcement-04oct12-en.htm> http://www.icann.org/en/news/announcements/announcement-04oct12-en.htm _____ Implementing the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA 4 October 2012 Forum Announcement: Comment Period Opens on Date: 4 October 2012 Categories/Tags: Internet Protocol Addressing Purpose (Brief): The Board ratified the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA in May. This public comment period is intended to gather input on options open for implementation. Public Comment Box Link: <http://www.icann.org/en/news/public-comment/implementing-ipv4-post-04oct12-…>http://www.icann.org/en/news/public-comment/implementing-ipv4-post-04oct12-… message was sent from:ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536Email Marketing by <http://www.icontact.com/a.pl/144186> Description:iContact - Try It Free! <http://app.icontact.com/icp/mmail-mprofile.pl?r=9828084&l=6333&s=FAC9&m=895…> Manage Your SubscriptionDescription:http://click.icptrack.com/icp/track.php?msgid=89518…

1 0

FW: APE MAC addresses
by Mark Frater 02 Oct '12

02 Oct '12

Anyone know what the rational is around the "official policy around APE" of only having a single MAC address per port? I would have thought that there was some technical merit in allowing at least 2 to cover rotuer replacement (without MAC address spoofing) and offer some peer router diversity options (e.g. either via separate peering sessions or VRRP implementation.) Regards Mark Frater

5 7