Presentation on theme: "IP Policy in APNIC and What about TWNIC ? Kuo-Wei Wu."— Presentation transcript:
IP Policy in APNIC and What about TWNIC ? Kuo-Wei Wu
Agenda Introduction Hierarchy of address space distribution APNIC policy development process Address Space Management What about TWNIC?
Introduction APNIC is the Regional Internet Registry for the Asia Pacific region, responsible for distributing public Internet address space and related resources in the region and for coordinating the development and implementation of policies to manage those resources. The policies described in this document have been developed by the Internet community of the Asia Pacific region through a consensus process facilitated by APNIC. They are to be implemented by APNIC and by the National Internet Registries and the Local Internet Registries throughout the region.
APNIC policy development process 1. Introduction This document describes the process through which policy proposals are to be submitted, considered and adopted by APNIC. Policies are developed by the membership and the broader Internet community through a bottom- up process of consultation and consensus. The forums for policy development are twice-yearly APNIC Open Policy Meetings (OPMs) and discussions on Special Interest Group (SIG) mailing lists. Anyone may attend the meetings and participate in discussions and the decision making.
APNIC policy development process 2. Scope This document describes the process through which policy-related proposals may be submitted, considered, and adopted by the APNIC community, including a step-by-step explanation of the process. This process will be followed in the creation of any new policy, as well as any substantial or significant changes to existing policy. 3. Definitions 3.1 Policy proposal Policy proposals are proposals which have been officially submitted for the consideration of the APNIC community, and which propose either a new policy or a change to an existing policy. Upon adoption, these policies will apply to the operation of APNIC, the APNIC Secretariat, and the APNIC membership.
APNIC policy development process 4. Proposal process A policy proposal must go through the following chronological steps in order to be adopted by APNIC. Step 1. Discussion before the OPM A formal proposal paper must be submitted to the SIG mailing list and to the SIG Chair four weeks before the start of the OPM. The proposal must be in text which clearly expresses the proposal, with explicit mention of any changes being proposed to existing policies and the reasons for those changes. The APNIC Secretariat will recommend a preferred proposal format. If the four-week deadline is not met, proposals may still be submitted and presented for discussion at the meeting; however, no decision may be made by the meeting regarding the proposal. The proposal will need to be resubmitted in time for the following meeting if the author wishes to pursue the proposal.
APNIC policy development process Step 2: Consensus at the OPM Consensus is defined as "general agreement" as observed by the Chair of the meeting. Consensus must be reached first at the SIG session and afterwards at the Member Meeting for the process to continue. If there is no consensus on a proposal at either of these forums, the SIG (either on the mailing list or at a future OPM) will discuss whether to amend the proposal or to withdraw it. Step 3: Discussion after the OPM Proposals that have reached consensus at the OPM will be circulated on the appropriate SIG mailing list for a period of eight weeks. This is known as the "comment period".
APNIC policy development process Step 4: Confirming consensus Consensus is assumed to continue unless there are substantial objections raised during the "comment period". When the "comment period" has expired, the appropriate SIG Chair (and Co-chairs) will decide whether the discussions on the mailing list represent continued consensus. If the Chair (and Co-chairs) observe that there are no "substantial objections" to the proposed policy, consensus is confirmed and the process continues as outlined below in Step 5. If it is observed that there have been "substantial objections" raised to the proposed policy, consensus is not confirmed and the proposal will not be implemented. The SIG will then discuss (either on the mailing list or in the SIG) whether to pursue the proposal or withdraw it.
APNIC policy development process Step 5. Endorsement from the EC The EC, in their capacity as representatives of the membership, will be asked to endorse the consensus proposals arising from the OPM and the SIG mailing lists for implementation at the next EC meeting. In reviewing the proposals for implementation, the EC may refer proposals back to the SIG for further discussion with clearly stated reasons. As per the APNIC By-laws, the EC may, at its discretion, refer the endorsement to a formal vote of adoption by the APNIC members.
Goals of address space management Uniqueness Every assignment and allocation of address space must be guaranteed as globally unique. Registration All assignments and allocations made directly by APNIC to its members and customers must be registered in a publicly accessible database (Whois). Aggregation Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure. Conservation To maximize the lifetime of the available resource, address space must be distributed according to actual need and for immediate use. Fairness All policies and practices relating to the use of address space should apply fairly and equitably to all existing and potential members of the Internet community.
Policy environment (I) Routability : The routability of address space throughout the Internet can never be guaranteed by any single organisation. Internet growth rates : To manage address space in a way that will maximise future scaling of the Internet. Collective responsibility : Policies and procedures are developed by members and the Internet community, in the common interest of those communities. Impartiality : apply the policies fairly and equitably. Varying levels of expertise : For varying levels of assistance and monitoring, appropriate to ensure a consistent approach to address space management throughout the AP Internet community. Address ownership : Address space as a scarce, public resource, ISPs and other organisations and individuals that use address space are considered "custodians" rather than "owners" of the resource.
Policy environment (II) Address stockpiling : APNIC policies prevent stockpiling and ensure efficient deployment. Evaluations to be based on best practice : Adopt best practice in management with exist appropriate technologies to improve the management (APNIC will consults with its members and Internet community to define and develop best practice recommendations). Private address space : In general, private address space should be used for networks not connected to the Internet. Minimum practical allocations : The minimum practical allocation is /21 now Documentation : To properly evaluate requests, IRs must examine all relevant documentation relating to the networks. This documentation may include: network engineering plans; subnetting plans; equipment invoices and purchase orders……. Confidentiality : APNIC will protect all confidential information
General policy framework IRs to adopt consistent address space management policies All NIRs and LIRs that receive address space from APNIC must adopt allocation and assignment policies that are consistent with the policies described in this document. NIRs and LIRs must ensure that address space for which they are responsible is only allocated or assigned subject to agreements consistent with the license provisions. Also, NIRs must, wherever possible, apply slow start, assignment window, and second opinion policies to their own members in a manner consistent with the way APNIC applies such policies.
Address allocation Address space license Slow start mechanism Exceptions to slow start Criteria for initial allocation Criteria for subsequent allocations No guarantee of contiguous allocations Prior allocations to be used first : "eighty percent rule" Special circumstances - large assignments Reservations not supported Address aggregation Validity of allocations and assignments Transfer of address space
LIR address space management Assignment window for LIRs Assignment usage estimates Responsibility to maintain in-addr.arpa records Registration requirements Assignments and exchanges Small multihoming assignments Renumbering to promote aggregation Mergers, acquisitions, and takeovers of LIRs Updating registration details Effect on membership agreement Sub-allocations by LIRs Updating registration details Registering contact persons Effect of sub-allocations on LIR's usage rate Internet Exchange Points Critical infrastructure Consequences for allocations Closure of LIRs