Skip to main content

Policy Proposals

  • Community / Policy Development
    Global Policy State in RIPE PDP

    2010-03: This proposal would have modified the RIPE Policy Development Process to create a new state that is specific to global policies. This state was "Accepted pending consensus in other RIR communities." This would have allowed a global policy to be further discussed in the event that modifications are made in other RIR communities after acceptance in RIPE

    PolicyProposal PDP
  • Community / Policy Development
    Global Policy for the Allocation of IPv4 blocks to Regional Internet Registries

    2009-01: With the depletion of the IANA free pool of IPv4 address space, the current policy regarding the allocation of IPv4 address space to the RIRs will become moot. The RIRs may, according to their individual policies and procedures, recover IPv4 address space. This policy provides a mechanism for the RIRs to retro allocate the recovered IPv4 address space to the IANA and provides the IANA the policy by which it can allocate it back to the RIRs on a needs basis. This policy creates a new global pool of IPv4 address space that can be allocated where it is needed on a global basis without a transfer of address space between the RIRs.

    PolicyProposal
  • Community / Policy Development
    Using the Resource Public Key Infrastructure to Construct Validated IRR Data

    2008-04: This is a proposal to introduce a new registry that augments IRR data with the formally verifiable trust model of the Resource Public Key Infrastructure (RPKI) and provide ISPs with the tools to generate an overlay to the IRR which is much more strongly trustable.

    PolicyProposal
  • Community / Policy Development
    Use of final /8

    2008-06: This proposal describes how RIPE NCC should make allocations from its last /8 worth of address space at the time of total depletion of the IANA free pool.

    PolicyProposal IPV4 IPV4 depletion
  • Community / Policy Development
    IPv4 Allocation and Assignments to Facilitate IPv6 Deployment

    2009-04: The last IPv4 /8 that the RIPE NCC will hold is proposed to be dedicated to facilitate deployment of IPv6. Allocations and assignments from this block will be made based on demonstrated need, but the size will be downscaled taking into account existing transition technologies (for example dual-stack lite, NAT464, successors of NAT-PT). The proposed minimum allocation size is to be a /27 for such allocations and assignments.

    PolicyProposal
  • Community / Policy Development
    IPv6 Provider Independent (PI) Assignments for LIRs

    2009-08: This proposal is to allow LIRs to receive IPv6 PI assignments in addition to an IPv6 allocation.

    PolicyProposal IPV6
  • Community / Policy Development
    Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries

    2009-07: According to the current global policy (ripe-416), 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

    PolicyProposal as numbers
  • Community / Policy Development
    Multiple IPv6 /32 Allocations for LIRs

    2009-05: This is a proposal to allow an LIR operating separate networks in unconnected geographical areas to receive multiple /32 IPv6 allocations.

    PolicyProposal
  • Community / Policy Development
    Provider Independent (PI) IPv6 Assignments for End User Organisations

    2006-01: This proposal introduced a solution for organisations that needed IPv6 Provider Independent (PI) address space.

    PolicyProposal
  • Community / Policy Development
    ASPLAIN Format for the Registration of 4-byte ASNs

    2008-09: This proposal seeks to modify the current policy document 'Autonomous System (AS) Number Assignment Policies and Procedures' to adopt the use of ASPLAIN for recording and representation of 4-byte AS Numbers.

    PolicyProposal as numbers