[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1

Thu Aug 20 11:04:52 GMT+3 2020

Hola Fernando,

Muy clara tu explicación, muchas gracias.

Si estoy entendiendo bien, tú asumes que al exigir este requisito (IPv6 
operativo en la red) a quienes necesiten transferir IPv4 y no lo 
quieran/puedan hacer, dejarán de realizar la transferencia de recursos?

Saludos,

Oscar

On 8/19/20 01:32, Fernando Frediani wrote:
> Hola Ricardo
> Gracias por tus comentarios.
>
> Un punto importante a destacar de esta propuesta es que *no obliga* a 
> ninguna organización a implementar IPv6.
> Si esta propuesta llega a un consenso y se ratifica cualquier 
> organización que desee permanecer sin IPv6 durante 20 años más, podrá 
> hacerlo respetando la autonomía de ese Sistema Autónomo. No existe 
> ningún mecanismo de coacción en la propuesta por parte del RIR/NIR o 
> cualquier otra organización para quienes deseen permanecer sin IPv6 en 
> sus redes.
>
> Sin embargo, si la organización necesita transferir más direcciones 
> IPv4 para continuar su operación, se entiende que este tipo de 
> actividad termina agravando el problema de escasez de IPv4.
> De esta forma, como la operación de transferencia es una operación que 
> concierne a toda la comunidad, se solicita una *justa consideración* 
> de esa organización al resto de la comunidad involucrada, que es 
> precisamente para demostrar que cuenta con IPv6 operativo en su red.
>
> La propuesta también es bastante razonable y ya establece que para una 
> nueva organización que no pueda mas obtener direcciones directamente 
> del RIR/NIR, estará exenta de este requisito para poder transferir un 
> /22 inicial. Asimismo, si la organización puede demostrar que los 
> Upstreams no son capaces de conectar con IPv6, está exenta de este 
> requisito.
>
> En resumen: este es un requisito adicional muy razonable y justo para 
> el resto de la comunidad dado el momento que estamos viviendo. Si 
> alguien realmente califica para transferir más y más direcciones IPv4, 
> se espera que al menos demuestre cierto compromiso con el ecosistema.
>
> Saludos
> Fernando Frediani
>
> On 18/08/2020 23:15, Ricardo Patara wrote:
>> Acerca de esa propuesta, tengo mis preocupaciones
>>
>> Si bien comprendo la motivación, la cual me parece muy nobre (el
>> despliegue de IPv6), no estoy seguro que se acelere el despliegue de
>> IPv6 si se implementa esa propuesta.
>>
>> Como el autor indica, aún hay necesidad de IPv4 y eso es comprensible.
>>
>> Los mecanismos para obtener más direcciones IPv4 es a través de la
>> transferencia, la cual demanda una inversión financiera bastante alta.
>>
>> Si a estas organizaciones aún no les ha tocado la necesidad de ipv6, no
>> creo que les forzando ha implementar de alguna manera para obtener ipv4
>> es lo mismo que desplegar una red ipv6 bien planeada para brindar
>> servicio a sus clientes con soporte a ese protocolo.
>>
>> Infelizmente, ellos ya deberían haber percibido la necesidad de
>> implementar ipv6.
>>
>> El costo por no hacerlo les tocará en el algun momento del futuro.
>>
>> Pienso que el camino es la informar, motivar y no "forzar".
>> LACNIC y los NIRs han hecho un buen trabajo en ese sentido (de difusión
>> y capacitación). La comunidad, en general, tiene también su papel en 
>> eso.
>>
>> -- 
>> ricardo
>>
>> Em 06/08/2020 15:17, info-politicas at lacnic.net escreveu:
>>> [Português abaixo]
>>> [English below]
>>>
>>> Estimados suscriptores de la lista de políticas de LACNIC,
>>>
>>> La propuesta LAC-2020-1 ha pasado de la versión 2 a la versión 3
>>>
>>> Título: Agregar IPv6 operativo como requisito para las 
>>> transferencias de IPv4
>>>
>>> Resumen: On 15th February 2017 LACNIC started IPv4 Exhaustion Phase 
>>> 3 meaning only new entrants can receive up to a single /22 of IPv4 
>>> space. Since then the amount of IPv4 Transfers between organizations 
>>> has increased reasonably as shown by the official LACNIC reports. 
>>> With the implementation of LAC-2019-1 and possibility of Inter-RIR 
>>> transfers these numbers have the potential to grow substantially.
>>>
>>> The objective of this proposal is to add as a requirement for 
>>> organizations in process of receiving transferred IPv4 space under 
>>> 2.3.2.18 to show they have an IPv6 allocation/assignment by LACNIC 
>>> or a provider and that is operational on their networks. Such 
>>> organization must be able to prove this IPv6 space is being used by 
>>> providing LACNIC the documented network deployment details to prove 
>>> IPv6 is operational in significant parts of the network.
>>>
>>> On 28th November 2019 LACNIC Board issued a statement 
>>> (https://www.lacnic.net/4283/2/lacnic/lacnic-board-calls-on-the-community-to-promote-ipv6-deployment) 
>>> reinforcing the issue about IPv4 exhaustion, mentioning IPv4 address 
>>> space will be exhausted by mid-2020 and calling the community to 
>>> promote IPv6 deployment.
>>> In its statement LACNIC Board “invite the community to work on 
>>> promoting the development of policies that will accelerate the 
>>> effective deployment of IPv6 above other policies that may be 
>>> discussed at a later date.”
>>>
>>> In the case the receiver provides a written statement from its 
>>> upstream that IPv6 connectivity is unavailable, the IPv6 requirement 
>>> may be waived. In the case LACNIC is not able to meet a new entrant 
>>> request for IPv4 space the IPv6 requirement may be waived for a 
>>> transfer up to a /22.
>>>
>>> Para ver el detalle ingrese en:
>>> https://politicas.lacnic.net/politicas/detail/id/LAC-2020-1/language/sp
>>>
>>> Los cambios respecto a la versión anterior se pueden visualizar aquí:
>>> https://politicas.lacnic.net/politicas/diff2?id=LAC-2020-1&v=3&v2=2&language=SP 
>>>
>>>
>>> Los comentarios y los puntos de vista aportados por la comunidad son 
>>> vitales para el correcto desarrollo del proceso de la propuestas
>>> - ¿Apoya usted o se opone a esta nueva versión de la propuesta?
>>> - ¿Ve alguna desventaja en esta nueva versión de la propuesta?
>>> - ¿Qué cambios podrían hacerse a esta nueva versión de la propuesta 
>>> para que sea más eficaz?
>>>
>>>
>>> Por más información contacte a info-politicas at lacnic.net
>>> Saludos cordiales,
>>> ______________________________________________________________________________________________________ 
>>>
>>> Prezados assinantes da lista de políticas de LACNIC,
>>>
>>> A proposta LAC-2020-1 tem passado da versão 2 para a versão 3
>>>
>>> Título: Adicionar IPv6 operacional como requisito para as 
>>> transferências do IPv4
>>>
>>> Resumo: On 15th February 2017 LACNIC started IPv4 Exhaustion Phase 3 
>>> meaning only new entrants can receive up to a single /22 of IPv4 
>>> space. Since then the amount of IPv4 Transfers between organizations 
>>> has increased reasonably as shown by the official LACNIC reports. 
>>> With the implementation of LAC-2019-1 and possibility of Inter-RIR 
>>> transfers these numbers have the potential to grow substantially.
>>>
>>> The objective of this proposal is to add as a requirement for 
>>> organizations in process of receiving transferred IPv4 space under 
>>> 2.3.2.18 to show they have an IPv6 allocation/assignment by LACNIC 
>>> or a provider and that is operational on their networks. Such 
>>> organization must be able to prove this IPv6 space is being used by 
>>> providing LACNIC the documented network deployment details to prove 
>>> IPv6 is operational in significant parts of the network.
>>>
>>> On 28th November 2019 LACNIC Board issued a statement 
>>> (https://www.lacnic.net/4283/2/lacnic/lacnic-board-calls-on-the-community-to-promote-ipv6-deployment) 
>>> reinforcing the issue about IPv4 exhaustion, mentioning IPv4 address 
>>> space will be exhausted by mid-2020 and calling the community to 
>>> promote IPv6 deployment.
>>> In its statement LACNIC Board “invite the community to work on 
>>> promoting the development of policies that will accelerate the 
>>> effective deployment of IPv6 above other policies that may be 
>>> discussed at a later date.”
>>>
>>> In the case the receiver provides a written statement from its 
>>> upstream that IPv6 connectivity is unavailable, the IPv6 requirement 
>>> may be waived. In the case LACNIC is not able to meet a new entrant 
>>> request for IPv4 space the IPv6 requirement may be waived for a 
>>> transfer up to a /22.
>>>
>>> Para ver o detalhe acesse:
>>> https://politicas.lacnic.net/politicas/detail/id/LAC-2020-1/language/pt
>>>
>>> As alterações da versão anterior podem ser vistas aqui:
>>> https://politicas.lacnic.net/politicas/diff2?id=LAC-2020-1&v=3&v2=2&language=PT 
>>>
>>>
>>>   Os comentários e os pontos de vista aportados pela comunidade são
>>> vitais para o bom desenvolvimento do processo das propostas
>>> - Você está a favor ou em contra desta nova versão
>>>   da proposta?- Vê alguma desvantagem nesta nova versão
>>>   da proposta?
>>>
>>> - Que mudanças poderiam ser feitas à esta nova versão
>>>   da proposta para que seja mais eficaz?
>>>
>>> Por mais informações entre em contato conosco através do e-mail:
>>> info-politicas at lacnic.net.
>>>
>>> Atenciosamente,
>>> ______________________________________________________________________________________________________ 
>>>
>>>
>>> Dear LACNIC Policy List subscribers,
>>>
>>> Proposal LAC-2020-1 has been updated from version 2 to version 3
>>>
>>> Title: Add IPv6 operational as a requirement for IPv4 transfers
>>>
>>> Summary: On 15th February 2017 LACNIC started IPv4 Exhaustion Phase 
>>> 3 meaning only new entrants can receive up to a single /22 of IPv4 
>>> space. Since then the amount of IPv4 Transfers between organizations 
>>> has increased reasonably as shown by the official LACNIC reports. 
>>> With the implementation of LAC-2019-1 and possibility of Inter-RIR 
>>> transfers these numbers have the potential to grow substantially.
>>>
>>> The objective of this proposal is to add as a requirement for 
>>> organizations in process of receiving transferred IPv4 space under 
>>> 2.3.2.18 to show they have an IPv6 allocation/assignment by LACNIC 
>>> or a provider and that is operational on their networks. Such 
>>> organization must be able to prove this IPv6 space is being used by 
>>> providing LACNIC the documented network deployment details to prove 
>>> IPv6 is operational in significant parts of the network.
>>>
>>> On 28th November 2019 LACNIC Board issued a statement 
>>> (https://www.lacnic.net/4283/2/lacnic/lacnic-board-calls-on-the-community-to-promote-ipv6-deployment) 
>>> reinforcing the issue about IPv4 exhaustion, mentioning IPv4 address 
>>> space will be exhausted by mid-2020 and calling the community to 
>>> promote IPv6 deployment.
>>> In its statement LACNIC Board “invite the community to work on 
>>> promoting the development of policies that will accelerate the 
>>> effective deployment of IPv6 above other policies that may be 
>>> discussed at a later date.”
>>>
>>> In the case the receiver provides a written statement from its 
>>> upstream that IPv6 connectivity is unavailable, the IPv6 requirement 
>>> may be waived. In the case LACNIC is not able to meet a new entrant 
>>> request for IPv4 space the IPv6 requirement may be waived for a 
>>> transfer up to a /22.
>>>
>>> To see the details, please click on:
>>> https://politicas.lacnic.net/politicas/detail/id/LAC-2020-1/language/en
>>>
>>> The changes from the previous version can be seen here:
>>> https://politicas.lacnic.net/politicas/diff2?id=LAC-2020-1&v=3&v2=2&language=EN 
>>>
>>>
>>> The community's comments and opinions are essential to the proper 
>>> functioning of the policy development process.
>>> - Do you support this new version of the proposal or are you against 
>>> it?
>>> - Do you think this new version of the proposal has any drawbacks?
>>> - What changes could be made to this new version of the proposal to 
>>> make it more effective?
>>>
>>> For further information, please contact info-politicas at lacnic.net
>>> Kind regards,
>>> -- 
>>> LACNIC - Registro de Direcciones de Internet para América Latina y 
>>> Caribe
>>> Rambla Rep. de México 6125, CP 11400
>>>
>>> Montevideo-Uruguay
>>>
>>> Teléfono: +598 2604 22 22
>>> www.lacnic.net
>>> _______________________________________________
>>> Politicas mailing list
>>> Politicas at lacnic.net
>>> https://mail.lacnic.net/mailman/listinfo/politicas
>>>
>> _______________________________________________
>> Politicas mailing list
>> Politicas at lacnic.net
>> https://mail.lacnic.net/mailman/listinfo/politicas
> _______________________________________________
> Politicas mailing list
> Politicas at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/politicas