HTTP/2 200
date: Sun, 13 Jul 2025 16:26:18 GMT
content-type: text/html; charset=UTF-8
content-length: 20148
x-xss-protection: 1; mode=block
referrer-policy: no-referrer, same-origin, strict-origin-when-cross-origin
x-frame-options: SAMEORIGIN
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
cf-edge-cache: cache,platform=wordpress
cache-control: public, max-age=300
link:
; rel="https://api.w.org/"
link:
; rel="alternate"; title="JSON"; type="application/json"
link: ; rel=shortlink
vary: Accept-Encoding
content-encoding: gzip
x-envoy-upstream-service-time: 434
strict-transport-security: max-age=15552000; preload
last-modified: Sun, 13 Jul 2025 16:26:18 GMT
cf-cache-status: MISS
accept-ranges: bytes
content-security-policy: frame-ancestors 'self' https://rex.apnic.net https://rex.stg.xyz.apnic.net
server: cloudflare
cf-ray: 95ea24280b3e1712-BLR
prop-064: Change to assignment policy for AS numbers – APNIC
Skip to content
prop-064: Change to assignment policy for AS numbers
Proposal text
prop-064-v002
Synopsis
The policy seeks to create awareness earlier within the community for the need to support 4-byte AS numbers without mandating an absolute final adoption of 4-byte AS numbers.
Current status
Implemented on 16 February 2009.
Authors
James Spenceley
Relevant forum
Policy SIG
Previous versions
prop-064-v001
Status at other RIRs
N/A
Proposal history
22 July 2008
Version 1 submitted to the Policy SIG mailing list for discussion.
25 July 2008
Version 2 submitted to the Policy SIG mailing list for discussion:
Version 2 adds a specific date for the interim step described in section 4.3 of the proposal.
28 August 2008
Reached consensus at APNIC 26 Policy SIG and AMM in Christchurch, New Zealand.
29 August – 24 October 2008
Eight-week call for final comments. No objections received.
20 November 2008
Endorsed by APNIC Executive Council (EC)
12 January – 9 February 2009
Draft policy document available for comments. See:
16 February 2009
Implemented