[LACNIC/Politicas] LAC-2023-6 revision

[Hernan Arcidiacono]

+1

Hernán Arcidiácono
CTIO

Directo: 5411 5031 6411


<https://www.youtube.com/channel/UCyYudfbUubvOjuFBTYJCOeg>
<https://www.linkedin.com/company/iplan-telecommunications/>


On Tue, Dec 19, 2023 at 5:44 PM Fernando Frediani <fhfrediani at gmail.com>
wrote:

> Hello Robert
>
> I personally don't like the text in that way as it leaves room for other
> possibilities when it mentions on "eg". As I mentioned on my previous
> message in order to avoid multiple interpretation it is better it to be
> specific and thinking in a more practical scenario there are no much
> other possibilities that should be allowed under these exceptions (like
> gTLDs, specially those known as sTLDs), ccTLDs in the region are fine,
> out of the region I don't think is necessary. IXPs don't change anything
> from what is already, so why allow an IXP operating our of the region to
> request which leave us with the main propose of this proposal which are
> Root DNS Servers.
>
> Therefore name the only exception specifically: "/Se podrán otorgar
> excepciones a organizaciones fuera de la región que sean servidores raíz
> DNS como proveedores de infraestructura de Internet crítica global./"
>
> Regarding Option 2 I think one detail that is lacking is to mention that
> even in a Anycast scenario services must be provided also in the region.
>
> I think I got lost on the rest of your email and options, but so far
> Option 1 seems the simplest with the comments about if I didn't miss
> anything important.
>
> Best regards
> Fernando Frediani
>
> On 29/11/2023 16:30, Robert Story wrote:
> > Hello all,
> >
> > First, thank you to everyone who commented on the initial proposal. I am
> > going to start on V2 of LAC-2023-6, and I would like some input on how
> > you think I should proceed.
> >
> > # Options for updating the current proposal
> >
> > * Option 1: A simple tweak to the original proposal.
> >
> > The original language added to the second paragraph of 1.2 was:
> > "*Exceptions may be granted to organizations outside the region which
> > provide global critical internet infrastructure (eg. DNS Root
> > Servers).*"
> >
> > We could simply make the exception apply to Root Server Operators
> > (RSOs): "*Exceptions may be granted to organizations outside the region
> which
> > are Root Server Operators for the purpose of providing global anycast
> > DNS root service.*
> >
> > * Option 2: Add the exception under the "Anycast" paragraph in 1.2.
> >
> > The fourth paragraph of 1.2 already lists exceptions for anycast
> > service, but still specifies organizations must be in the region. A
> > new paragraph could be added for DNS Root Server Operators:
> >
> > "DNS Root Server Operators" that are legally constituted outside the
> > service region may be granted an exception for numbering resources as
> > long as they are used for providing global anycast DNS root service."
> >
> > * Option 3: Add the exception in v4/v6 micro assignments (2.3.3.2 and
> >    4.4.5)
> >
> > These 2 sections are the ones that talk about critical infrastructure
> > assignments, which are the types of assignments that should be used for
> > DNS root service. This requires adding text in two places, but adds
> > clarity about the type of resources to be assigned.
> >
> > * Option 4: Option 1 or 2 + specifying micro assignments
> >
> > Alternatively, the text in options 1 and 2 could specifically mention
> > micro assignments, but it feels odd putting such specific details in an
> > early and otherwise very general section of the policy.
> >
> > # Additional changes
> >
> > * Addition 1: Add text to also allow ASN assignments
> >
> > Some Root Server Operators use unique ASN numbers for each of their
> > instances, so that should be considered as well. Section 3 doesn't have
> > detailed sub-sections like the micro assignment policies do, so I'm
> > open to suggestions on where to add text and how to word it.
> >
> > Perhaps the easiest way would be to use Option 4 above, and mention
> > ASNs as well as micro assignments in section 1.2.
> >
> > # Conclusion
> >
> > I hope that one of the ideas I've proposed covers the concerns that
> > were expressed with version 1. If not, please let me know so that I can
> > try and address those concerns.
> >
> > Apologies for the English. When the discussion seems to have consensus
> > on the best way forward (or if there is no discussion!), I'll start a
> > new thread in Spanish for a broader reach.
> >
> > Regards,
> > Robert
> >
> > --
> > USC Information Sciences Institute<http://www.isi.edu/>
> > Networking and Cybersecurity Division
> > _______________________________________________
> > Politicas mailing list
> > Politicas at lacnic.net
> > https://mail.lacnic.net/mailman/listinfo/politicas
> > Desuscribirse/Descadastre-se/Unsubscribe:
> https://mail.lacnic.net/mailman/options/politicas
> >
> > El Codigo de Conducta de la Comunidad de LACNIC (
> https://rir.la/codigoconducta-SP) aplica a las listas de discusion de
> LACNIC.
> > O Codigo de Conduta da Comunidade do LACNIC (
> https://rir.la/codigoconducta-PT) se aplica as listas de discussao do
> LACNIC.
> > LACNIC's Community Code of Conduct (https://rir.la/codigoconducta-EN)
> applies to LACNIC's discussion lists.
> >
> _______________________________________________
> Politicas mailing list
> Politicas at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/politicas
> Desuscribirse/Descadastre-se/Unsubscribe
> <https://mail.lacnic.net/mailman/listinfo/politicasDesuscribirse/Descadastre-se/Unsubscribe>:
> https://mail.lacnic.net/mailman/options/politicas
>
> El Codigo de Conducta de la Comunidad de LACNIC (
> https://rir.la/codigoconducta-SP) aplica a las listas de discusion de
> LACNIC.
> O Codigo de Conduta da Comunidade do LACNIC (
> https://rir.la/codigoconducta-PT) se aplica as listas de discussao do
> LACNIC.
> LACNIC's Community Code of Conduct (https://rir.la/codigoconducta-EN)
> applies to LACNIC's discussion lists.
>
>

-- 
*No Imprimas Digitalizá*ESTE MENSAJE ES CONFIDENCIAL. Puede contener 
información amparada por el secreto profesional. Si usted ha recibido este 
e-mail por error, por favor comuníquenoslo inmediatamente vía e-mail y 
tenga la amabilidad de eliminarlo de su sistema; no deberá copiar el 
mensaje ni divulgar su contenido a ninguna persona. Muchas gracias.

THIS 
MESSAGE IS CONFIDENTIAL. It may also contain information that is privileged 
or otherwise legally exempt from disclosure. If you have received it by 
mistake please let us know by e-mail immediately and delete it from your 
system; should also not copy the message nor disclose its contents to 
anyone. Many thanks.


NSS S.A. – IPLAN | CUIT: 30-70265297-5 | IVA 
Responsable Inscripto | Ingr. Brutos: 901-033512-0 Inscripción I.G.J.: 
24/02/1999, N° 2588, libro 4, tomo - Sociedades por Acciones | Sede Social: 
Reconquista 865 2° Piso, CABA 
<https://maps.google.com/?q=Reconquista+865+2%C2%B0+Piso,+CABA&entry=gmail&source=g> 
C1003ABQ

 

Ley 25326 - art.27. - inc. 3. El titular podrá en cualquier 
momento solicitar el retiro o bloqueo de su nombre de los bancos de datos a 
los que se refiere el presente artículo.


Decreto 1558/01 - art. 27. - 
3er. párrafo. En toda comunicación con fines de publicidad que se realice 
por correo, teléfono, correo electrónico, Internet u otro medio a distancia 
a conocer, se deberá indicar, en forma expresa y destacada, la posibilidad 
del titular del dato de solicitar el retiro o bloqueo, total o parcial, de 
su nombre de la base de datos. A pedido del interesado, se deberá informar 
el nombre del responsable o usuario del banco de datos que proveyó la 
información.

 

El titular de los datos personales tiene la facultad de 
ejercer el derecho de acceso a los mismos en forma gratuita y a intervalos 
no inferiores a 6 meses, salvo que se acredite un interés legítimo al 
efecto conforme lo establecido por el artículo 14, inciso 3 de la ley 
25326.-



La Agencia de Acceso a la Información Pública , órgano de 
control de la ley Nº 25.326, tiene la atribución de atender las denuncias y 
reclamos que se interpongan con relación al incumplimiento de las normas 
sobre protección de datos personales.