CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 04:48:45 GMT
content-type: text/html; charset=utf-8
cf-ray: 95ee63bcbb09c1b3-BLR
cf-cache-status: DYNAMIC
last-modified: Tue, 30 Jul 2024 05:38:21 GMT
vary: Accept-Encoding
x-content-type-options: nosniff
strict-transport-security: max-age=15552000; preload
server: cloudflare
content-encoding: gzip
[sig-policy] prop-041-v001: IPv6 assignment size to criticalinfrastructu
[sig-policy] prop-041-v001: IPv6 assignment size to criticalinfrastructu
- To: <sig-policy at apnic dot net>
- Subject: [sig-policy] prop-041-v001: IPv6 assignment size to criticalinfrastructure
- From: "Kenny Huang" <huangk at alum dot sinica dot edu>
- Date: Tue, 8 Aug 2006 19:48:36 +0800
- Cc:
- List-archive: <https://www.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>
- Thread-index: Aca6rkyrWOFm+kkwR1WKCoyxPVmJrwAMiLfw
Dear SIG members The proposal "IPv6 assignment size to critical infrastructure" was sent to the Policy SIG Chair and Co-chairs yesterday. We are now forwarding it to the Policy SIG for review. It will be presented at the Policy SIG at APNIC 22 in Kaohsiung, Taiwan, 4-8 September 2006. You are invited to review and comment on the proposal on the mailing list before the meeting. The proposal's history can be found at: https://www.apnic.net/docs/policy/proposals/prop-041-v001.html Regards Kenny Huang Policy SIG huangk at alum dot sinica dot edu ________________________________________________________________________ prop-041-v001: IPv6 assignment size to critical infrastructure ________________________________________________________________________ Author: APNIC Secretariat <secretariat at apnic dot net> Version: 1 Date: 7 August 2006 Introduction ------------ This policy proposes a clarification of the APNIC policy for IPv6 portable assignments to critical infrastructure networks operating in the Asia Pacific region. Summary of the current problem ------------------------------ The current policy for critical infrastructure assignments in section 5.8.2 of APNIC document, "IPv6 Address Allocation and Assignment Policy" (https://www.apnic.net/docs/policy/ipv6-address-policy.html#5.8.2) states: "The minimum assignment made under these terms is /32." Since this policy became active, requests have been received for multiple /32 assignments in cases where infrastructure operators have multiple POPs or servers providing secondary services. While the policy is ambiguous in this regard, the APNIC secretariat deemed that additional /32 assignments are not warranted in such cases, due to the large amount of address space involved and the potentially large number of such requests. Situation in other RIRs ----------------------- AfriNIC: no specific policy ARIN: /48 minimum assignment per POP LACNIC: /48 minimum, /32 maximum micro allocation to critical Internet infrastructure operators only RIPE NCC: minimum allocation size at time of request Proposal -------- It is proposed that section 5.8.2 of APNIC document "IPv6 Address Allocation and Assignment Policy" remains except to modify the last sentence to read: "The maximum assignment made under these terms is /32 per operator."
- Prev by Date: [sig-policy] prop-037-v001: Deprecation of email updates forAPNIC Registry and whois
- Next by Date: [sig-policy] prop-041-v001: IPv6 assignment size to critical infrastructure
- Previous by thread: [sig-policy] prop-037-v001: Deprecation of email updates forAPNIC Registry and whois
- Next by thread: [sig-policy] prop-041-v001: IPv6 assignment size to critical infrastructure
- Index(es):