On 09/03/2009, at 1:44 PM, Jasper Bryant-Greene wrote:
>
> How is that different from normal IP routing? The other end always
> decides which way to send packets back to you, and in the event that
> your customer is multihomed, the return path might not even transit
> your AS.
I control my outbound and inbound routing. People only send packets
via routes I advertise and I can show a contractual relationship
between me and my upstream or peer, my upstream and theirs or their
peer and then to the far end etc.
With using 6to4 the downside is that whilst I may have my own gateway,
the FAR end could be using a 3rd party 6to4 gateway. This means that
the return packets traverse links for which I have no contractual
relationship.
I guess in some way I'm agreeing with Joe that everyone SHOULD run
their own, especially if they offer up content over IPv6. (I wonder
if Google do with ipv6.google.com?).
MMC
--
Matthew Moyle-Croft Internode/Agile Peering and Core Networks
Level 5, 162 Grenfell Street, Adelaide, SA 5000 Australia
Email: mmc(a)internode.com.au Web: http://www.on.net
Direct: +61-8-8228-2909 Mobile: +61-419-900-366
Reception: +61-8-8228-2999 Fax: +61-8-8235-6909
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
------------------------------------------------------------
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
------------------------------------------------------------
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
------------------------------------------------------------
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
------------------------------------------------------------
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)
________________________________________________________________________
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
____________________________________________________________________
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
Hi NZNOG Community,
You may be aware that APNIC 28 is currently taking place,
and the Policy SIG has started. Don't forget you can participate
remotely in discussions, ask the presenter questions, and voice
your opinion. For more information on webcast, Jabber chat,
and live transcript services please see:
http://meetings.apnic.net/28
Some of the policy proposals up for discussion this time are:
* prop-050: IPv4 address transfers
* prop-073: Automatic allocation/assignment of IPv6
* 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 number
* prop-076: Requiring the aggregation of IPv6 subsequent allocations
* prop-077: Proposal to supplement transfer policy of historical IPv4
addresses
* prop-078: Reserving /10 IPv4 address space to facilitate IPv6 deployment
Kind regards,
Elly
APNIC
