[sig-policy]Re: APNIC Fees for IXP assignments - Proposal

  • To: sig-policy at apnic dot net
  • Subject: [sig-policy]Re: APNIC Fees for IXP assignments - Proposal
  • From: Anne Lord <anne at apnic dot net>
  • Date: Sat, 26 Jul 2003 10:57:57 +1000 (EST)
  • Cc: sig-policy-chair at apnic dot net
  • List-archive: <http://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: <http://mailman.apnic.net/mailman/listinfo/sig-policy>,<mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
  • List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>,<mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
  • Sender: sig-policy-admin@lists.apnic.net
    • 
      I am forwarding the proposal below received by the APNIC Secretariat, 
      for the upcoming APNIC Open Policy Meeting in Korea. 
      
      Discussion and feedback on this list prior to Korea, is invited.
      
      regards,
      Anne
      --
      
      A modified policy for Internet Exchange Point (IXP) assignments 
      
      Proposed by: Bill Woodcock, PCH
      
      Version: 1.2
      
      Date: 25 July 2003
      
      
      
      1. Summary
      
         A revised policy for Internet Exchange Point (IXP) assignments is
         proposed which replaces the existing policy described in
         "Policies for Managing Internet Resources in the Asia Pacific"
         sections 4.2 and 11.2.
      
      2. Background and Problem
      
         The current definition of an Internet Exchange Point taken from
         section 4.2 above is:
      
           "An Internet Exchange Point (IXP) is a physical network
            infrastructure operated to facilitate the exchange of Internet
            traffic between independent ISPs.  The number of ISPs
            connected should be at least three, and there must be a clear
            and open policy for others to join.  An IXP is generally not
            considered as an Internet Registry, but rather as an end user
            of address space."
      
         The definition above should be updated in light of subsequent
         developments in international "best practices" surrounding the
         implementation and operation of IXPs.  Namely, the scope of
         operation of IXPs has become clearer and more focused in the
         intervening years, and the definition can consequently be
         correspondingly clarified.
      
         One problem which has also emerged during that time is that the
         membership fees associated with obtaining address space and
         services from APNIC required to operate an IXP are prohibitive
         for the majority of IXPs, which are typically non-profit
         organisations and often do not charge fees or have revenue.
      
      
      3. Proposal
      
      3.1 Revised Definition
      
         An amended definition for an IXP is proposed as follows:
      
           "An Internet Exchange Point (IX or IXP) is a layer 1 and layer
            2 network interstitial between and interconnecting three or
            more Autonomous Systems (ASNs) in contiguous IPv4 and IPv6
            subnets for the purpose of exchange of Internet traffic."
      
      3.2 Characteristics
      
         An IXP must have the following characteristics:
      
         * Offer membership on a non-discriminatory basis in accordance
           with a published process
      
         * Not provide, or be provided by, an operator of any layer 3
           transit or transport services
      
         * Is an end-user of address space.
      
      3.3 Eligibility for a portable assignment
      
         An IXP who meets the definitions and characterstics described
         above is eligible for IPv4 and IPv6 portable assignments. The
         following conditions must be met:
      
         * The address space must be used exclusively as the switch-fabric
           subnet interconnecting the Internet Protocol devices of IXP
           participants,
      
         * Documentation of three or more initial IXP participant
           Autonomous Systems must be provided
      
      3.4 Assignment Details
      
         * In accordance with established best-practice, both IPv4 and
           IPv6 blocks shall be assigned simultaneously, and the last tuple
           of the network portion of the assigned IPv4 and IPv6 blocks shall
           be matching values.
      
         * Because of the infeasibility of IXPs renumbering their exchange
           switch-fabric subnets, it is recommended that some form of sparse
           assignments is practiced by APNIC.
      
      3.5 Routing
      
         It is proposed that the restriction upon routability of the
         assigned block is lifted, and this matter is left to the
         discretion of the IXP and its participants.
      
      3.6 Fees
      
         It is proposed that qualifying not-for-profit IXP organisations,
         whether incorporated or not, which do not charge fees to their
         IXP participants have APNIC membership fees waived.
      
         If, at any time, an IXP is operated by a for-profit corporation,
         or fees of any sort are charged to the IXP participants, normal
         membership or non-member fees will apply.
      
      4. Implementation
      
         This policy will be implemented 3 months after acceptance by the
         community.
      
      
      -end-