CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 date: Sun, 13 Jul 2025 20:33:37 GMT content-type: text/html; charset=utf-8 cf-ray: 95eb8e6ec9b5c467-BLR cf-cache-status: DYNAMIC last-modified: Tue, 30 Jul 2024 05:41:24 GMT vary: Accept-Encoding x-content-type-options: nosniff strict-transport-security: max-age=15552000; preload server: cloudflare content-encoding: gzip [sig-policy] prop-074: IANA policy for allocation of ASN blocks to RIRs

[sig-policy] prop-074: IANA policy for allocation of ASN blocks to RIRs

To: "'sig-policy'" <sig-policy at apnic dot net>
Subject: [sig-policy] prop-074: IANA policy for allocation of ASN blocks to RIRs
From: "Ching-Heng" <chku at twnic dot net dot tw>
Date: Mon, 13 Jul 2009 14:38:50 +0800
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>

The proposal, 'Internet Assigned Numbers Authority (IANA) Policy for
Allocation of ASN Blocks (ASNs) to Regional Internet Registries', has
been sent to the Policy SIG for review. It will be presented at the
Policy SIG at APNIC 28 in Beijing, China, 25-28 August 2009. The
proposal's history can be found at:
         https://www.apnic.net/policy/prop-074
We invite you to review and comment on the proposal on the mailing list
before the meeting.
The comment period on the mailing list before an APNIC meeting is an
important part of the policy development process. We encourage you to
express your views on the proposal:
        - Do you support or oppose this proposal?
        - Does this proposal solve a problem you are experiencing? If
          so, tell the community about your situation.
        - Do you see any disadvantages in this proposal?
        - Is there anything in the proposal that is not clear?
        - What changes could be made to this proposal to make it more
          effective?
Randy, Jian and Ching-Heng
________________________________________________________________________
prop-074-v001: Internet Assigned Numbers Authority (IANA) Policy for
                Allocation of ASN Blocks (ASNs) to Regional Internet
                Registries
________________________________________________________________________
Authors:  Andrew de la Haye, RIPE NCC
           <andrew at ripe dot net>
           Stacy Hughes
           <ipgoddess.arin at gmail dot com>
Version:   1
Date:      13 July 2009
1.  Introduction
----------------
This is a global policy proposal.
According to the current Global Policy for Allocation of ASN Blocks to
Regional Internet Registries, IANA will cease to make any distinction
between 16-bit and 32-bit only ASN blocks by 31 December 2009, when
making allocations to RIRs. This proposal is to extend this date by one
year, to 31 December 2010.
2.  Summary of current problem
------------------------------
Due to operational issues external to the IANA/RIR policy process,
32-bit only ASNs are not being issued by the RIRs at the anticipated
rate.  As it stands, RIRs will likely not be able to justify a new block
of ASNs from the IANA after 31 December 2009 due to a glut of free 32
bit only ASNs in the RIR’s pool. This leaves available, essential 16-bit
ASNs stranded in the IANA free pool.  This proposal seeks to remedy the
potential problem by extending the deadline for differentiation by one
year.
With this proposal the policy will be aligned with the actual reality in
regards to 32-bit ASN deployment and usage.
The subject was raised during RIPE 58 and a presentation was made:
https://www.ripe.net/ripe/meetings/ripe-58/content/presentations/asn32-take-up-report.pdf
The feedback in this session suggested that a global policy proposal
should be developed and should be discussed.
3.   Situation in other RIRs
----------------------------
This is a global policy proposal and will be submitted to all RIRs.
- ARIN
   Submitted. Currently with the ARIN Address Council for development
   and evaluation
- RIPE
   2009-07: Internet Assigned Numbers Authority (IANA) Policy for
   Allocation of ASN Blocks (ASNs) to Regional Internet Registries
       https://www.ripe.net/ripe/policies/proposals/2009-07.html
- AfriNIC, LACNIC
   To be submitted
4.   Details of the proposal
----------------------------
This proposal suggests changing the "Allocation Principles" section of
the Global Policy for Allocation of ASN Blocks to Regional Internet
Registries [i] to:
     IANA allocates ASNs to RIRs in blocks of 1024 ASNs. In this document
     the term "ASN block" refers to a set of 1024 ASNs. Until 31 December
     2010, allocations of 16-bit and 32-bit only ASN blocks will be made
     separately and independent of each other [1].
     This means until 31 December 2010, RIRs can receive two separate ASN
     blocks, one for 16-bit ASNs and one for 32-bit only ASNs from the
     IANA under this policy. After this date, IANA and the RIRs will
     cease to make any distinction between 16-bit and 32-bit only ASNs,
     and will operate ASN allocations from an undifferentiated 32-bit ASN
     allocation pool.
     [1]
     16-bit ASNs are the AS Numbers in the range: 0 - 65535
     32-bit only ASNs are the AS Numbers in the range: 65536 - 4294967295
     32-bit ASNs are the AS Numbers in the range: 0 - 4294967295
5.   Advantages and disadvantages of the proposal
-------------------------------------------------
Advantages:
     See the section above, "2. Summary of current problem".
Disadvantages:
     Some may think that extending the previously set timeline can be
     perceived as some discouragement for the deployment of 32-bit ASNs.
     One counter argument to this is that RIRs and Internet community
     have some other mechanisms and activities to raise awareness for
     32-bit ASN pool (via public presentations and trainings). These
     activities will continue while 16-bit ASN blocks are still allocated
     to RIRs by the IANA as they are available and they are needed.
6.   Effect on APNIC members
----------------------------
Authors cannot think of any effect other than that if the proposal is
accepted, APNIC members will be able to keep receiving 16 bit ASNs if
they need to because APNIC will be able to receive 16 bit ASN blocks
from IANA.
7.   Effect on NIRs
-------------------
Same as above.
8.   References
---------------
[i] Global Policy for Allocation of ASN Blocks to Regional Internet
     Registries
     www.icann.org/en/general/global-policy-asn-blocks-31jul08-en.htm
_______________________________________________
Sig-policy-chair mailing list
Sig-policy-chair at apnic dot net
https://mailman.apnic.net/mailman/listinfo/sig-policy-chair

Original Source | Taken Source