HTTP/2 200
date: Sun, 13 Jul 2025 20:48:59 GMT
content-type: text/html; charset=UTF-8
content-length: 20083
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: 728
strict-transport-security: max-age=15552000; preload
last-modified: Sun, 13 Jul 2025 20:48:59 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: 95eba4eef87bc1b5-BLR
prop-065: Format for delegation and recording of 4-byte AS numbers – APNIC
Skip to content
prop-065: Format for delegation and recording of 4-byte AS numbers
Proposal text
prop-065-v001
Synopsis
This proposal recommends that APNIC changes its procedures to standardise on delegating 4-byte AS numbers in the ASPLAIN format rather than the current ASDOT format. This proposal extends to the data recorded in APNIC Whois Database records, with the proposal recommending that whois returns the same record for queries made in either format.
Current status
Published as an RFC
Authors
James Spenceley
Relevant forum
Policy SIG
Previous versions
N/A
Status at other RIRs
N/A
Proposal history
22 July 2008
Submitted to the Policy SIG mailing list for discussion.
28 August 2008
Reached consensus at the APNIC 26 Policy SIG and AMM in Christchurch, New Zealand.
29 August – 24 October 2008
Eight-week call for final comments.
22 September 2008
Submitted as an IETF Internet Draft:
27 October 2008
Policy SIG Chair formally announce that the Chairs will take no further action on the proposal, pending the publication of an RFC regarding format of 4-byte AS numbers.
12 December 2008
Published as an RFC (Standards Track):
RFC 5396 – Textual Representation of Autonomous System (AS) Numbers
