1. Summary of the Problem being addressed by this proposal

This policy reserves IPv4 resources for public Internet Exchange Points (IXPs) in the African region, ensuring that there would be discrete IPv4 resources to allow the establishment and growth of future IXPs.

2. Resumo de como esta proposta aborda o problema

Esta política solicita que o AFRINIC reserve e publique IPv4 resources, and 2-byte ASNs para uso somente por IXPs.

3.0 Proposta

3.1 Introdução

Considera-se amplamente que os Internet Exchange Points (IXPs) são um dos elementos críticos necessários para o desenvolvimento das economias da Internet. A África ainda está em processo de desenvolvê-las e, ao mesmo tempo, enfrenta o esgotamento iminente de suas IPv4 Recursos.

Não tendo IPv4 addresses to grow, or start new, IXPs would create unnecessary and unneeded routing complexity for Internet connected networks, looking to peer at IXPs to further their network scope.

A AFRINIC já tem uma política existente para fazer alocações aos IXPs ^[1]but that policy does not specifically reserve IPV4 space to ensure that there will be such, for future IXPs to grow and develop.Additionally, this policy reserves a set of 2-byte ASNs para uso por IXPs para uso em servidores de rota IXP BGP.

3.2 Distinction between IXP peering and management networks

We distinguish between two kinds of IP address resources needed and used at IXPs.

An IXP peering LAN is the contiguous network address block that the IXP would use to assign unique IP addresses to each peering member, for each peering participant to exchange network traffic across the shared peering infrastructure. Best practice has the IXP peering LAN não being visible in a view of the global routing table, among other things to reduce the attack vectors for ISP border routers via the IXP.

From a network identification, monitoring and analysis perspective, it is thus desirable, that the "peering LAN" space be provided from a contiguous block.The IXP management LAN is the management network that the IXP uses to provision services at the IXP, like monitoring, statistics, mail, ticket systems, provisioning of transit to DNS Roots, etc. Management networks, are meant to be reachable globally, for instance to publish data and allow remote access for common good network infrastructure (such as root and TLD DNS servers) and research projects.

3.3 BGP Route Servers use

Typically IXPs use BGP route servers to help manage peering sessions between different participants. The route servers implement IXP routing policy in the form of BGP communities, typically in the form of A:B, whereA,B represent A=IXP BGP route server and B=participant ASN.

Current BGP implementations utilise 6 bytes for the extended community attribute [RFC5668]. Therefore, an IXP with a 4-byte ASN em uso no servidor de rota não seria capaz de implementar com êxito o mapeamento da comunidade A: B BGP, se um participante do IXP tiver um byte de 4 bytes ASN. É provável que essa situação seja vivenciada por mais IXPs, como adicional de 4 bytes ASNs são alocados através do processo AFRINIC atual.

If, IXP route server communities include the IXP ASN e o par ASN (espera-se que seja de 4 bytes) e um total de apenas 6 bytes esteja disponível, segue que os servidores de rota IXP ASN could not be longer than a 2-byte ASN.

3.4 Proposta

Para garantir que haja recursos suficientes para o desenvolvimento de IXPs, essa política propõe que a AFRINIC reserve IPv4 endereços para LANs emparelhando IXP a partir de um bloco de endereços marcado particularmente e exclusivamente para uso em LAN emparelhando IXP.

Assignments for IXP peering LANs must be from one dedicated block, published as such by AFRINIC. The Peering LAN assignments for each IXP should ensure that the adjacent /24 IP block is reserved (based on the minimum end-user assignment policy size of /24) to support future growth of the IXP. This will enable an IXP to increase its peeringLAN resources to /23 without having to renumber to a new contiguous IP block allocation.

As atribuições para endereços de gerenciamento IXP NÃO devem ser fornecidas no mesmo bloco que as LANs emparelhamento IXP.

It is proposed that a /16 block be reserved for future requirements for IXP peering LANs in the AFRINIC service region, and that AFRINIC publish this block as such. In addition, the assignments for the IXP peering LAN should reserve the adjacent contiguous /24 IP block to the requesting IXP for future growth. These reservations shall be upheld until such a time that the available pool of the /16 can no longer allocate /23 assignments. Thereafter, new requests may be assigned from the reserved space held for future IXP growth.

It is further proposed to reserve the equivalent of an additional /16 block for IXP management prefixes, separate from the peering LANs.

Propõe-se que AFRINIC reserve um bloco de 2 bytes ASNs para uso em servidores de rota BGP em IXPs na região de serviço AFRINIC. O número de ASNs a serem reservados devem ser maiores de 114, ou metade dos 2 bytes restantes ASNs within AFRINIC block at the date of ratification of this policy.AFRINIC will allocate these resources on a first come first served basis.

3.5 Critério de avaliação

Esta política não sugere novos critérios de avaliação para o que determina um IXP válido.

4. Histórico de Revisões

23 Oct 2014             AFPUB-2014-GEN-004-DRAFT-01 posted on rpd list.

05 Nov 2014            AFPUB-2014-GEN-004-DRAFT-02 posted on rpd list. 

Referências

[1] AFRINIC Policy for End User Assignments - AFPUB-2006-GEN-001, http://afrinic.net/library/policies/127-afpub-2006-gen-001

Sections 5) and 6)