| CARVIEW |
Select Language
HTTP/2 200
date: Sun, 13 Jul 2025 14:17:22 GMT
content-type: text/html; charset=utf-8
cf-ray: 95e967482814755c-BLR
cf-cache-status: DYNAMIC
last-modified: Tue, 30 Jul 2024 05:42:25 GMT
vary: Accept-Encoding
x-content-type-options: nosniff
strict-transport-security: max-age=15552000; preload
server: cloudflare
content-encoding: gzip
[sig-policy] New APNIC policies now active
[sig-policy] New APNIC policies now active
- To: Policy SIG <sig-policy at apnic dot net>
- Subject: [sig-policy] New APNIC policies now active
- From: Sam Dickinson <sam at apnic dot net>
- Date: Mon, 05 Jul 2010 13:46:04 +1000
- Delivered-to: sig-policy at mailman dot apnic dot net
- List-archive: <https://mailman.apnic.net/mailing-lists/sig-policy>
- List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
- List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
- List-post: <mailto:sig-policy@lists.apnic.net>
- List-subscribe: <https://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
- List-unsubscribe: <https://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
- User-agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
_______________________________________________________________________
New APNIC policies now active
_______________________________________________________________________
Today, the APNIC Secretariat has implemented two policy proposals that
reached consensus during APNIC 29 in Kuala Lumpur, Malaysia in February
2010.
The APNIC Executive Council (EC) endorsed the proposals during its May
2010 meeting.
The two policies implemented are:
- prop-080: Removal of IPv4 prefix exchange policy
The policy that previously permitted resource holders to
return three or more non-contiguous IPv4 address blocks and
have the prefixes replaced with a single, larger, contiguous
block has been removed.
- prop-082: Removing aggregation criteria for IPv6 initial
allocations
The initial allocation criteria that required an LIR to
advertise its IPv6 connectivity as a single aggregated
address allocation has been removed and replaced by a
stronger recommendation with regard to the aggregation of
IPv6 routes.
A third proposal that reached consensus at APNIC 29 will not be
implemented until November 2010 due to its complexity:
- prop-079: Abuse contact information
Updated policy documents
------------------------
The comment period for the draft documents incorporating these policies
ended on 21 June 2010. The updated documents are now officially active:
- Policies for IPv4 address space management in the Asia Pacific
region
https://www.apnic.net/policy/add-manage-policy
- IPv6 address allocation and assignment policy
https://www.apnic.net/policy/ipv6-address-policy
- Policies for historical Internet resources in the APNIC Whois
Database
https://www.apnic.net/policy/historical-resource-policies
For more information, see the history of these policy proposals at:
https://www.apnic.net/policy/proposals
Regards
--
_____________________________________________________________________
Samantha Dickinson email: sam at apnic dot net
Senior Policy Specialist, APNIC sip: sam at voip dot apnic dot net
https://www.apnic.net phone: +61 7 3858 3100
- Prev by Date: Re: [sig-policy] prop-084: Frequent whois information update request
- Next by Date: Re: [sig-policy] Question on difference between v4 and v6 policy
- Previous by thread: [sig-policy] prop-084: Frequent whois information update request
- Next by thread: Re: [sig-policy] Question on difference between v4 and v6 policy
- Index(es):