- NZNOG - lists.nznog.org

Re: [nznog] NZ prefix list
by Richard Hulse 02 Sep '09

02 Sep '09

>>> Matthew Moyle-Croft <mmc(a)internode.com.au> 3/09/2009 15:36:41 >>> > We'll be rich. > (Don't fall into the mistake of taking me seriously here). Someone will... Time for beer.

1 0

NZ prefix list
by Donald Gordon 02 Sep '09

02 Sep '09

Hi I'm in need of a view of what IP prefixes are local to NZ (ideally, what FX considers domestic, but I'm not too picky) for a personal project. My upstream can't provide me with a BGP feed, alas. Is there anyone here who could provide me with a multihop BGP view of their domestic routing table, or a looking glass I could screen-scrape? thanks (and beer?) in advance donald

6 6

FWD: Programme for IEEE NZ Wireless Workshop 2009 - Friday 4 September
by Clark Mills 01 Sep '09

01 Sep '09

Hi all. Forwarded message FYI. Might be of interest to someone out there. Kind regards... Clark ===================================================== *Subject:* Programme for IEEE NZ Wireless Workshop 2009 - (4 September) Dear colleagues This is a reminder that the *2009 IEEE New Zealand Wireless Workshop* is to be held 9:30am - 5pm, Friday, 4 September, 2009 Conference Centre Auditorium The University of Auckland 24 Symonds Street Auckland Registration: None (This is a free-of-charge event) *The programme for the Wireless Workshop is now on-line at: *http://www.ece.auckland.ac.nz/~pgrad/ieeenzwws.pdf <http://www.ece.auckland.ac.nz/%7Epgrad/ieeenzwws.pdf> The Conference Centre Auditorium on Symonds Street is physically connected to the Engineering School on Level 4 (street level). Car parking is available (for a fee) in a large university public access carpark under the huge new Business School on Grafton Road, near the intersection with Symonds Street). http://www.auckland.ac.nz/uoa/home/tm-visitor-parking There is also pay-and-display parking on the surrounding streets (but not on Symonds Street). Attached is a City Campus map showing the locations of the Conference Centre and the public parking building. Thank you to those who have already indicated your attendance (or otherwise). Planning was assisted by your responses. Please note that there is no requirement to register for this event. You are welcome to attend as much, or as little, of the day as suits you. IEEE membership is not a requirement. Best regards Kevin Sowerby IEEE ComSoc NZ Chapter

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 111.69.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, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.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, 202.27.186.0/23^23-29, 202.36.178.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.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 111.69.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, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.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, 202.27.186.0/23^23-29, 202.36.178.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.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.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.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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 Ltd - AS23655 members: 111.69.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, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.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, 202.27.186.0/23^23-29, 202.36.178.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.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 111.69.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, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.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, 202.27.186.0/23^23-29, 202.36.178.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.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.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.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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 Ltd - AS23655 members: 111.69.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, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.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, 202.27.186.0/23^23-29, 202.36.178.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.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 111.69.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, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.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, 202.27.186.0/23^23-29, 202.36.178.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.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.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.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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: AS9560:RS-ROUTES:AS9245 descr: advertised to AS9560 by COMPASS NZ - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 120.136.0.0/21^21-29, 123.108.144.0/21^21-29, 202.174.6.0/23^23-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080702 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9245 descr: advertised to AS9560 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 202.174.6.0/23^23-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.198.0/24^24-29, 202.37.234.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: antonio.pavletich(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

[AusNOG] Future IPv6 allocation policies
by Andy Linton 28 Aug '09

28 Aug '09

Hi All, I thought I would post to the list and highlight something that I think you will find important regarding IPv6 future deployment. This week at the APNIC Open Policy Meeting in Beijing (which concluded yesterday) the policy proposal "prop-073-v004: Simplifying allocation/ assignment of IPv6 to APNIC members with existing IPv4 addresses" reached consensus in both the policy SIG (Special Interest Group) and the APNIC Member Meeting. Provided this proposal makes it through the 8 week comment period with consensus intact and the APNIC Executive Council deems the proposal has reached community consensus it will be endorsed, this policy change means: * Any APNIC member organisation that has IPv4, requires no further justification to receive IPv6. - A member that has an IPv4 allocation would be eligible for an IPv6 /32 - A member that has an IPv4 assignment would be eligible for an IPv6 /48 * The APNIC secretariat is directed to implement a simple online request for IPv6 resources under this policy * The policy proposal authors recommend that the APNIC Secretariat communicate to members and others that the criteria for receiving an initial IPv6 block has been reduced and that the process of obtaining IPv6 address space has been made simpler to show that there is no effective barrier to members obtaining IPv6 addresses. Details can be found here: http://www.apnic.net/policy/proposals/prop-073 I'm sure we all recognise that there are many barriers and issues on the road to IPv6 deployment, this policy proposal makes that first step, of getting IPv6 address space, as easy as possible especially in the APNIC region. Cheers, Andy (Prop-073 Co-Author)

1 0

APNIC 28 meeting report
by Srinivas (Sunny) Chendi 27 Aug '09

27 Aug '09

________________________________________________________________________ APNIC 28 25-28 August 2009, Beijing, China ________________________________________________________________________ Thank you to everyone who contributed to APNIC 28. The preliminary event participation statistics are: Total number of delegates 272 Delegates at APNIC Member Meeting: 101 Economies represented: 25 APNIC member organizations represented: 51 APNIC held remote participation events via video conference in Kuala Lumpur, Malaysia and Dhaka, Bangaladesh. Attendance figures for these events were: Kuala Lumpur, Malaysia 12 Dhaka, Bangaladesh 86 (TBC) Web-based online participation options included a choice of video, audio and text chat. Participation figures for online remote delegates based on unique IP address were: Online remote participation feeds 288 To read, watch or listen to archives from the meeting, go to: http://meetings.apnic.net/28 Elections --------- During the APNIC Member Meeting (AMM) in Beijing on Friday, 28 August 2009, the following candidate was elected to the NRO NC. - Dr Kenny Huang Elections were held for NIR SIG Chair positions NIR SIG Chair - Izumi Okutani NIR SIG Co-chair - Wei Zhao An election was held for Policy SIG Co-Chair Policy SIG Co-chair - Terence Zhang Congratulations to the successful candidates: Election details are available at: http://meetings.apnic.net/28/elections Meeting decisions ----------------- Policy SIG Seven policy proposals were discussed. The following proposals reached consensus: prop-050: IPv4 address transfers prop-073: Simplifying allocation/assignment of IPv6 to APNIC members with existing IPv4 addresses prop-074: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries prop-075: Ensuring efficient use of historical AS numbers The following proposal was returned to the mailing list for further discussion: prop-076: Requiring aggregation for IPv6 subsequent allocations The following proposals were returned to their authors for further consideration: prop-077: Proposal to supplement transfer policy of historical IPv4 addresses prop-078: Reserving /10 IPv4 address space to facilitate IPv6 deployment http://www.apnic.net/policy/proposals MoU Signed ----------- APNIC signed a Memorandum of Understanding with the following organization: CNNIC (China Internet Network Information Center) Meeting sponsors ---------------- APNIC offers its deepest thanks to the sponsors of APNIC 28, whose invaluable contributions allowed APNIC to offer a meeting program of a very high standard: http://meetings.apnic.net/28/sponsorship Upcoming APNIC meetings ----------------------- APNIC 29 1-5 March 2010 Kuala Lumpur, Malaysia (with APRICOT 2010) http://meetings.apnic.net/29 APNIC 30 Four Seasons Hotel, Bangkok 23-27 August 2010 Bangkok, Thailand Thanks Sunny -- -------------------------------------------------------------------- Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3189/99 ____________________________________________________________________

1 0

Report on APNIC 28 policy proposals
by Elly Tawhai 27 Aug '09

27 Aug '09

Hi NZNOG Community, Below is a summary report of the status of policy proposals following discussion at APNIC 28. The following proposals reached consensus: prop-050: IPv4 address transfers prop-073: Simplifying allocation/assignment of IPv6 to APNIC members with existing IPv4 addresses prop-074: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries prop-075: Ensuring efficient use of historical AS numbers The following proposal was returned to mailing list for further discussion: prop-076: Requiring aggregation for IPv6 subsequent allocations The following proposals were returned to their authors for further consideration: prop-077: Proposal to supplement transfer policy of historical IPv4 addresses prop-078: Reserving /10 IPv4 address space to facilitate IPv6 deployment Next steps ---------- 1. Proposals that reached consensus will be returned to the Policy SIG mailing list for an eight-week comment period. 2. If no substantial objections are received during the final comment period, the proposals are deemed to have reached consensus at each stage of the policy development process. At this point, the SIG Chairs forward the proposals to the APNIC Executive Council (EC) for endorsement. 3. If the APNIC EC endorses the proposals, the APNIC Secretariat begins work on implementation of the proposals. Implementation usually takes a minimum of three months, but may take more depending on the implementation complexity. For more information on the proposals, please see: http://www.apnic.net/policy/proposals For more information on the APNIC policy development process, see: http://www.apnic.net/community/policy/process Kind regards, Elly APNIC

1 0