- NZNOG - lists.nznog.org

APNIC proposal to remove multihoming requirement for IPv6 portable assignments - prop-101
by Dean Pemberton 31 May '12

31 May '12

Evening; Q: What now? A: At the APNIC meeing in New Delhi a proposal to remove the multihoming requirement for IPv6 portable assignments did not reach consensus. It's likely to come back again at the meeting in August and I'd like to explain a bit about it and get some feedback from the NZ community. Q: Ok what's this one all about? A; Right... Current APNIC policy only permits portable assignments of IPv6 addresses to be made if a member is currently multihomed or plans to be multihomed within three months. That can mean that people feel they can't apply for IPv6 space, or that they have to wait until they are multihomed in order to apply to APNIC for address space. Prop-101 looks to remove the requirement for multihoming and would let non-multihomed APNIC members apply for a portable IPv6 assignment. The full text is here: http://www.apnic.net/policy/proposals/prop-101/prop-101-v004.txt Q: What is a portable assignment and why would I want one anyway? A: A portable assignment of IPv6 addresses is independent of any particular ISP or network provider. It means that you can take those addresses and have them routed by anyone. Non-portable assignments are addresses which you might get from your ISP. Those addresses are taken from the ISPs block of IPv6 addresses and can only be used while you are their customer. If you were using non-portable addresses and wanted to move ISPs then you would have to renumber your network. Q: That sounds terrible! Why would anyone want anything else? A: Well for a lot of organisations they don't need anything else. Think about IPv4, most people operate with addresses given to them by their ISP just fine. Portable addresses are also only allocated by RIR organisations like APNIC. They don't come free, there is a yearly cost to be an APNIC member, and keep those addresses. Q: Are there any downsides? A: Objectors to this proposal suggest that if everyone was granted portable address space that the routing table would grow unnecessarily. Q: What does everyone else in the world do? A: APNIC is the only one for the 5 global registries which requires multihoming for portable IPv6 assignments. Q: So what do you want from me? A: If you have an opinion then let me know. If you think it's relevant to others then post it to the list. Don't hesitate to join the APNIC policy SIG list and have your say directly. Regards, Dean

2 1

New APNIC policy to increase transparency in IPv6 allocations
by Dean Pemberton 30 May '12

30 May '12

Evening all, Q: Why are you interrupting my evening? A; I just wanted to let everyone know about a new APNIC policy which has just passed through the Policy Development Process Q: Huh? A: The APNIC Executive council has just ratified a new policy called prop-102 which will increase transparency in IPv6 allocations. Q: Well what does it say then? A: Well prop-102 is a hellish boring name a new APNIC proposal which says that details of any sparse allocation algorithm used for the allocation by APNIC of IPv6 resources be published on their the website, and any revisions should be communicated back to the community. You can read the full text here: http://www.apnic.net/policy/proposals/prop-102/prop-102-v003.txt Q: Why do I care? A: When people are allocated IP addresses, they are sometimes under the impression that if they request more at a later date that they will get allocated a completly different area of the address space. That's not true. For some time now APNIC has been employing a system called 'Sparse Allocation' to try and make sure that when you came back, you stood a good chance of getting the IP address block just next-door. The problem up until now has been no one knew the details of this system. How soon did you have to come back? How large was the block they were reserving for you? If you wanted too long did they allocate it to someone else? All those details were hidden. Now they will be published. Q: What are you telling me this? A: I'm doing my bit to keep the community across what is happening at APNIC in a way that hopefully people can find accessible. I'll summarise some of the other policies shortly Q: What if I have more questions? A: Feel free to email me and I'll try and answer any APNIC policy related questions. Or feel free to participate in APNIC discussion directly via their Policy SIG (http://www.apnic.net/community/participate/join-discussions/sigs/policy-sig) Regards, Dean

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 May '12

30 May '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 118.148.0.0/15^15-29, 111.69.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 140.200.0.0/16^16-29, 150.206.0.0/16^16-29, 153.111.0.0/16^16-29, 159.117.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 14.1.32.0/19^19-29, 49.50.192.0/19^19-29, 180.189.192.0/19^19-29, 202.124.96.0/19^19-29, 202.154.128.0/19^19-29, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 210.7.32.0/20^20-29, 27.110.120.0/21^21-29, 49.50.224.0/21^21-29, 120.136.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 103.4.136.0/22^22-29, 103.4.152.0/22^22-29, 103.247.152.0/22^22-29, 110.92.16.0/22^22-29, 113.197.96.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 103.22.234.0/23^23-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.204.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.106.0/23^23-29, 202.49.80.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 103.10.233.0/24^24-29, 143.96.13.0/24^24-29, 192.100.53.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.14.217.0/24^24-29, 202.36.29.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.0/24^24-29, 202.36.245.0/24^24-29, 202.37.114.0/24^24-29, 202.37.127.0/24^24-29, 202.37.179.0/24^24-29, 202.37.194.0/24^24-29, 202.37.220.0/24^24-29, 202.46.187.0/24^24-29, 202.49.59.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.50.176.0/24^24-29, 202.74.38.0/24^24-29, 203.6.246.0/24^24-29, 203.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 205.233.128.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)snap.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120329 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 118.148.0.0/15^15-29, 111.69.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 140.200.0.0/16^16-29, 150.206.0.0/16^16-29, 153.111.0.0/16^16-29, 159.117.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 14.1.32.0/19^19-29, 49.50.192.0/19^19-29, 180.189.192.0/19^19-29, 202.124.96.0/19^19-29, 202.154.128.0/19^19-29, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 210.7.32.0/20^20-29, 27.110.120.0/21^21-29, 49.50.224.0/21^21-29, 120.136.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.50.144.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 103.4.136.0/22^22-29, 103.4.152.0/22^22-29, 103.247.152.0/22^22-29, 110.92.16.0/22^22-29, 113.197.96.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 103.22.234.0/23^23-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.204.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.106.0/23^23-29, 202.49.80.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 103.10.233.0/24^24-29, 143.96.13.0/24^24-29, 159.172.204.0/24^24-29, 192.100.53.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.14.217.0/24^24-29, 202.36.29.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.0/24^24-29, 202.36.245.0/24^24-29, 202.37.114.0/24^24-29, 202.37.127.0/24^24-29, 202.37.179.0/24^24-29, 202.37.194.0/24^24-29, 202.37.220.0/24^24-29, 202.46.187.0/24^24-29, 202.49.59.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.50.176.0/24^24-29, 202.74.38.0/24^24-29, 203.6.246.0/24^24-29, 203.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 205.233.128.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: perrin(a)snap.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 May '12

30 May '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 103.5.80.0/22^22-29, 202.36.192.0/22^22-29, 32.114.24.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.36.68.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 32.234.81.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.64.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120314 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by at&t - AS2687 members: 103.5.80.0/22^22-29, 202.36.192.0/22^22-29, 32.114.24.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.36.68.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 32.234.81.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.0/24^24-29, 202.27.160.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.64.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 May '12

30 May '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet - AS23655 members: 118.148.0.0/15^15-29, 111.69.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 140.200.0.0/16^16-29, 150.206.0.0/16^16-29, 153.111.0.0/16^16-29, 159.117.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 14.1.32.0/19^19-29, 49.50.192.0/19^19-29, 180.189.192.0/19^19-29, 202.124.96.0/19^19-29, 202.154.128.0/19^19-29, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 210.7.32.0/20^20-29, 27.110.120.0/21^21-29, 49.50.224.0/21^21-29, 120.136.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 103.4.136.0/22^22-29, 103.4.152.0/22^22-29, 103.247.152.0/22^22-29, 110.92.16.0/22^22-29, 113.197.96.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 103.22.234.0/23^23-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.204.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.106.0/23^23-29, 202.49.80.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 103.10.233.0/24^24-29, 143.96.13.0/24^24-29, 192.100.53.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.14.217.0/24^24-29, 202.36.29.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.0/24^24-29, 202.36.245.0/24^24-29, 202.37.114.0/24^24-29, 202.37.127.0/24^24-29, 202.37.179.0/24^24-29, 202.37.194.0/24^24-29, 202.37.220.0/24^24-29, 202.46.187.0/24^24-29, 202.49.59.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.50.176.0/24^24-29, 202.74.38.0/24^24-29, 203.6.246.0/24^24-29, 203.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 205.233.128.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)snap.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120329 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet - AS23655 members: 118.148.0.0/15^15-29, 111.69.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 140.200.0.0/16^16-29, 150.206.0.0/16^16-29, 153.111.0.0/16^16-29, 159.117.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 14.1.32.0/19^19-29, 49.50.192.0/19^19-29, 180.189.192.0/19^19-29, 202.124.96.0/19^19-29, 202.154.128.0/19^19-29, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 210.7.32.0/20^20-29, 27.110.120.0/21^21-29, 49.50.224.0/21^21-29, 120.136.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.50.144.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 103.4.136.0/22^22-29, 103.4.152.0/22^22-29, 103.247.152.0/22^22-29, 110.92.16.0/22^22-29, 113.197.96.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 103.22.234.0/23^23-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.204.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.106.0/23^23-29, 202.49.80.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 103.10.233.0/24^24-29, 143.96.13.0/24^24-29, 159.172.204.0/24^24-29, 192.100.53.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.14.217.0/24^24-29, 202.36.29.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.0/24^24-29, 202.36.245.0/24^24-29, 202.37.114.0/24^24-29, 202.37.127.0/24^24-29, 202.37.179.0/24^24-29, 202.37.194.0/24^24-29, 202.37.220.0/24^24-29, 202.46.187.0/24^24-29, 202.49.59.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.50.176.0/24^24-29, 202.74.38.0/24^24-29, 203.6.246.0/24^24-29, 203.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 205.233.128.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: perrin(a)snap.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 May '12

30 May '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon - AS17746 members: 121.98.0.0/15^15-29, 60.234.0.0/16^16-29, 114.23.0.0/16^16-29, 156.62.0.0/16^16-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 180.189.192.0/19^19-29, 202.89.32.0/19^19-29, 202.150.96.0/19^19-29, 49.50.240.0/20^20-29, 112.109.64.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 112.109.80.0/21^21-29, 124.150.160.0/21^21-29, 182.23.176.0/21^21-29, 202.3.88.0/21^21-29, 202.49.64.0/21^21-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 103.3.232.0/22^22-29, 103.6.144.0/22^22-29, 110.44.16.0/22^22-29, 113.21.224.0/22^22-29, 116.193.144.0/22^22-29, 202.14.20.0/22^22-29, 202.36.8.0/22^22-29, 202.49.244.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 116.193.148.0/23^23-29, 120.138.22.0/23^23-29, 124.150.170.0/23^23-29, 143.96.2.0/23^23-29, 143.96.4.0/23^23-29, 182.236.122.0/23^23-29, 182.236.124.0/23^23-29, 202.14.82.0/23^23-29, 202.27.76.0/23^23-29, 202.36.198.0/23^23-29, 202.36.230.0/23^23-29, 202.175.142.0/23^23-29, 210.54.12.0/23^23-29, 210.54.142.0/23^23-29, 103.2.121.0/24^24-29, 103.6.212.0/24^24-29, 116.193.151.0/24^24-29, 120.138.31.0/24^24-29, 124.150.168.0/24^24-29, 124.150.172.0/24^24-29, 182.236.121.0/24^24-29, 192.88.190.0/24^24-29, 192.203.216.0/24^24-29, 202.6.5.0/24^24-29, 202.12.104.0/24^24-29, 202.14.84.0/24^24-29, 202.14.217.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.12.0/24^24-29, 202.36.70.0/24^24-29, 202.36.174.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.72.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.46.189.0/24^24-29, 202.49.59.0/24^24-29, 202.49.140.0/24^24-29, 202.49.216.0/24^24-29, 202.49.233.0/24^24-29, 202.50.164.0/24^24-29, 202.50.176.0/24^24-29, 202.50.246.0/24^24-29, 202.129.253.0/24^24-29, 202.175.137.0/24^24-29, 202.175.138.0/24^24-29, 203.6.246.0/24^24-29, 203.97.42.0/24^24-29, 210.55.5.0/24^24-29, 210.55.169.0/24^24-29, 210.55.199.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: robert.keightley(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120501 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon - AS17746 members: 121.98.0.0/15^15-29, 60.234.0.0/16^16-29, 114.23.0.0/16^16-29, 156.62.0.0/16^16-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 202.150.96.0/19^19-29, 49.50.240.0/20^20-29, 112.109.64.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 112.109.80.0/21^21-29, 182.23.176.0/21^21-29, 202.3.88.0/21^21-29, 202.49.64.0/21^21-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 103.3.232.0/22^22-29, 103.4.136.0/22^22-29, 103.6.144.0/22^22-29, 103.247.152.0/22^22-29, 113.21.224.0/22^22-29, 116.193.144.0/22^22-29, 202.14.20.0/22^22-29, 202.36.8.0/22^22-29, 202.49.244.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 116.193.148.0/23^23-29, 120.138.22.0/23^23-29, 143.96.2.0/23^23-29, 143.96.4.0/23^23-29, 202.14.82.0/23^23-29, 202.27.76.0/23^23-29, 202.36.198.0/23^23-29, 202.36.230.0/23^23-29, 202.175.142.0/23^23-29, 210.54.12.0/23^23-29, 210.54.142.0/23^23-29, 103.6.212.0/24^24-29, 116.193.151.0/24^24-29, 120.138.31.0/24^24-29, 124.150.172.0/24^24-29, 192.88.190.0/24^24-29, 192.203.216.0/24^24-29, 202.6.5.0/24^24-29, 202.12.104.0/24^24-29, 202.14.84.0/24^24-29, 202.14.217.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.12.0/24^24-29, 202.36.70.0/24^24-29, 202.36.174.0/24^24-29, 202.36.233.0/24^24-29, 202.37.72.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.46.189.0/24^24-29, 202.49.59.0/24^24-29, 202.49.140.0/24^24-29, 202.49.216.0/24^24-29, 202.49.233.0/24^24-29, 202.50.164.0/24^24-29, 202.50.176.0/24^24-29, 202.50.246.0/24^24-29, 202.175.137.0/24^24-29, 202.175.138.0/24^24-29, 203.6.246.0/24^24-29, 203.97.42.0/24^24-29, 210.55.5.0/24^24-29, 210.55.169.0/24^24-29, 210.55.199.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: robert.keightley(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR ------------------------------------------------------------

1 0

Fwd: InTAC invite (for NZNOG)
by Andy Linton 30 May '12

30 May '12

---------- Forwarded message ---------- From: Campbell Gardiner <campbell(a)internetnz.net.nz> Date: Thu, May 31, 2012 at 10:00 AM Subject: InTAC invite (for NZNOG) To: Andy Linton <asjl(a)lpnz.org> Hi Andy, Attached is the invitation for InTAC (and text below). Are you able to send this to NZNOG please? Thanks, C -- On Tuesday 10 July, InternetNZ is holding a one-day conference in Auckland to discuss issues related to the technical architecture and technical policy of ultra-fast broadband and fibre networks. www.internetnz.net.nz/intac InternetNZ cordially invites yourself and colleagues to attend this event. Please see attached for the invitation and draft programme. Note that we are seeking further ideas for discussion topics, so please feel free to email me with any suggestions. What: The Internet Technical Architecture Conference (InTAC) When: Tuesday, 10th July 2012 Where: SkyCity Convention Centre, Auckland. Who should attend: Those involved in developing fibre policy, building the network, and using the network to talk to one another about its technical underpinnings. This includes people working for Local Fibre Companies, Chorus, Retail Service Providers, Telecommunications firms, Content Providers, Technologists, and Government. International keynote: Lev Gonick, the Chief Information Officer of Case Western Reserve University in Cleveland, USA How much: $60, inclusive of GST and lunch / networking drinks. To register: Email rsvp(a)internetnz.net.nz. Places are limited so we suggest interested people register at the earliest. Regards, Campbell -- Campbell Gardiner Communications Lead, Internet New Zealand Secretariat, New Zealand IPv6 Task Force Web: www.internetnz.net.nz & www.ipv6.org.nz Email: campbell(a)internetnz.net.nz DDI: + 64 4 495 2332 Mobile: + 64 21 506 004 Address: Level 9, Grand Arcade Tower, 16 Willis Street, Wellington 6011

1 0

APNIC Survey 2012 Extended to 8 June
by Elly Tawhai 29 May '12

29 May '12

Hi NZNOG Community, The APNIC Survey is still open for participation. This your time to have your say! Kind regards, Elly APNIC ________________________________________________________________________ APNIC Survey 2012 Extended to 8 June ________________________________________________________________________ There is still time to respond to the APNIC Survey 2012 and give a direct contribution to APNIC's operational planning and future direction. You do not have to be an APNIC Member to complete the Survey, and will only be asked questions that are relevant to you. Kindly take a few minutes to fill out the Survey, which is available until 8 June at: http://www.apnic.net/survey Kind regards, ________________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 3646 South Brisbane, QLD 4101 Australia Fax: +61 7 3858 3199 6 Cordelia Street, South Brisbane, QLD http://www.apnic.net ________________________________________________________________________ * Sent by email to save paper. Print only if necessary.

1 0

Re: [nznog] Fwd: DNCL Second Level Consultation and Submissions
by Blair Harrison 29 May '12

29 May '12

Hi Folks, I have a few thoughts on this, apologies if this seems a bit conflicted, just what I'm thinking at the moment. On Wed, May 30, 2012 at 3:39 PM, Simon Green <simon(a)simongreen.net> wrote: > To me this whole things seems like a way for Internet NZ to double > their income. Most entities that have a non conflicting .co.nz domain > will also want to register their .nz domain (even if they don't use > it), just to prevent domain hijacking at a future date. And that means > two payment of domain fees. (ala ICANN allowing arbitrary top level > domains) > How about the other way around, new registrants for .nz being compelled to register .co.nz as well? An interesting thought experiment, but I think people are overall lazy, and this just won't happen unless there is someone encouraging them to do so (their registrar or web developer, most likely). Frankly though, if your business will collapse under the pressure of another $24/yr domain you're probably doing it wrong anyway. > I can't see any benefit to domain owners or the general public in > opening up to 2LD registration. I will be replying to the proposal at > some stage. > > Probably not much benefit to existing domain owners, as someone discussed earlier, most people have invested all their branding in one particular version of their domain, and that's fine. I think it does provide an "in" for new players, whose name of choice might be taken already in the 3ld space but not yet camped out in .nz I haven't really seen much confusion in the past except where people try to guess the domain of a particular company, and get it wrong, this does probably leave things open for a little confusion. As also mentioned earlier, this isn't really so much an issue any more, as if people want to find you, they just type your company name into the search box. If you're not the first hit, then you've probably done your SEO wrong - or your name is just not very unique :) Lets take a look at the distribution of .nz 2ld registrations for last month. Apologies if this doesn't display well, but the numbers are all there. 2LD Apr-12 .co 417188 .net 27229 .org 26552 .school 3285 .ac 1929 .gen 1381 .geek 1148 .govt 1117 .maori 691 .health 147 .iwi 79 .mil 34 .cri 14 .parliament 9 Total 480803 So out of 480803 total registrations in .nz, we have 417188, or 86.7% of all total registrations being .co.nz, with the next two being 5.6% and 5.5%. Seems like some extra commercial type 2ld categories might be a good idea (tourism.nz, retail.nz, trade.nz?) Lumping the bulk of domains into .co.nz has already destroyed any semblance of hierarchy, so I don't really see much reason to argue about the sanctity of the old way of doing things. It's already well and truly gone. I do think that it's worth having a discussion about whether .nz should be opened up fully, or try to find some more 2lds which might be practical - I don't think there should necessarily have to be someone apply for these, historically the process has just taken too long and only industry people really are aware of it (a-la geek.nz, a paltry 1100 registrations after several years in operation) - InternetNZ could come up with some new ones all on their own - and they're the ones with the data on existing registrations already so may be able to further split out the .co.nzregistration data into rough categories. It's probably worth having a good think about further domains to lock out at the 2ld, eg wpad.nz, and isatap.nz (which have been dealt with already in the 3ld space), I'm sure there are others. All of the supported IDN variants of the locked out domains should also be prevented from being registered. Cheers, Blair

1 0

Discussion paper on opening .nz 2ld
by Andy Linton 29 May '12

29 May '12

Just following up on my earlier posting on this. By all means discuss this on the nznog list, in pubs and clubs and anywhere else you choose but let me remind you that if you want to be sure that your opinion is taken into account don't forget the formal process described here. andy ---------- Forwarded message ---------- From: Joy Liddicoat <joy(a)liddicoatlaw.co.nz> Date: Wed, May 30, 2012 at 10:21 AM Subject: Re: [members-discuss] Discussion paper on opening .nz 2ld To: InternetNZ Members Discussion List <members-discuss(a)mailman.internetnz.net.nz> The consultation relates to a proposal being considered by the Domain Name Commission to extend the .nz domain name space by allowing registrations at the second level. This has the potential to significantly alter New Zealand's domain name space, and it is important that we hear the views of a wide variety of people and organisations. For ease of reference the Consultation Paper and some FAQ information are attached – this is also available at http://dnc.org The Consultation Paper raises a number of questions including about the creation of new second level domains within the existing .nz structure and whether or not certain names should be prohibited at the second level if registrations at the second level are permitted. I’d like to encourage all members to participate and respond with their views along with any other points you wish to raise. All comments including those of the local Internet community will form the basis of the decision on whether or not to proceed. These comments must be sent to us at the DNC. Online submissions can be made at https://www.research.net/s/dnc_consultation1 or you can email to policies(a)dnc.org.nz or post to Domain Name Commission Ltd, PO Box 11-881, Manners St, Wellington 6142. Submissions will be published online as they are received at http://dnc.org.nz/second_level_proposal_c1. If you have any questions please feel free to contact me through the Domain Name Commission at policies(a)dnc.org.nz. Yours sincerely, Joy Liddicoat Chair Domain Name Commission Limited

1 0