[lacnog] Fwd: BGP Experiment

Lun Ene 7 22:13:01 -02 2019

Hola Edmundo,

  Muy buena pregunta, en realidad no sé. Voy a ver si averiguo algo.

Gracias, saludos

Alejandro,

El 7/1/19 a las 19:28, Edmundo Cázarez escribió:
>
> Hola,
>
>  
>
> ¿Hubo algún reporte de “hipo” por el experimento?
>
>  
>
> Saludos.
>
> -- Edmundo.
>
>  
>
> *From:*LACNOG [mailto:lacnog-bounces en lacnic.net] *On Behalf Of
> *Alejandro Acosta
> *Sent:* Thursday, December 20, 2018 12:53 PM
> *To:* Latin America and Caribbean Region Network Operators Group
> <lacnog en lacnic.net>
> *Subject:* [lacnog] Fwd: BGP Experiment
>
>  
>
> PSI.., para que estén informados, ojalá que no pase nada  (ufff.., de
> Pimpinela la canción)
>
>
>
> -------- Mensaje reenviado --------
>
> *Asunto: *
>
> 	
>
> BGP Experiment
>
> *Fecha: *
>
> 	
>
> Tue, 18 Dec 2018 10:05:26 -0500
>
> *De: *
>
> 	
>
> Italo Cunha <cunha en dcc.ufmg.br> <mailto:cunha en dcc.ufmg.br>
>
> *Para: *
>
> 	
>
> NANOG <nanog en nanog.org> <mailto:nanog en nanog.org>, DISCO experiment
> mailing list <disco-experiment en googlegroups.com>
> <mailto:disco-experiment en googlegroups.com>
>
>  
>
> NANOG,
>  
> We would like to inform you of an experiment to evaluate alternatives
> for speeding up adoption of BGP route origin validation (research
> paper with details [A]).
>  
> Our plan is to announce prefix 184.164.224.0/24 with a valid
> standards-compliant unassigned BGP attribute from routers operated by
> the PEERING testbed [B, C]. The attribute will have flags 0xe0
> (optional transitive [rfc4271, S4.3]), type 0xff (reserved for
> development), and size 0x20 (256bits).
>  
> Our collaborators recently ran an equivalent experiment with no
> complaints or known issues [A], and so we do not anticipate any
> arising. Back in 2010, an experiment using unassigned attributes by
> RIPE and Duke University caused disruption in Internet routing due to
> a bug in Cisco routers [D, CVE-2010-3035]. Since then, this and other
> similar bugs have been patched [e.g., CVE-2013-6051], and new BGP
> attributes have been assigned (BGPsec-path) and adopted (large
> communities). We have successfully tested propagation of the
> announcements on Cisco IOS-based routers running versions 12.2(33)SRA
> and 15.3(1)S, Quagga 0.99.23.1 and 1.1.1, as well as BIRD 1.4.5 and
> 1.6.3.
>  
> We plan to announce 184.164.224.0/24 from 8 PEERING locations for a
> predefined period of 15 minutes starting 14:30 GMT, from Monday to
> Thursday, between the 7th and 22nd of January, 2019 (full schedule and
> locations [E]). We will stop the experiment immediately in case any
> issues arise.
>  
> Although we do not expect the experiment to cause disruption, we
> welcome feedback on its safety and especially on how to make it safer.
> We can be reached at disco-experiment en googlegroups.com <mailto:disco-experiment en googlegroups.com>.
>  
> Amir Herzberg, University of Connecticut
> Ethan Katz-Bassett, Columbia University
> Haya Shulman, Fraunhofer SIT
> Ítalo Cunha, Universidade Federal de Minas Gerais
> Michael Schapira, Hebrew University of Jerusalem
> Tomas Hlavacek, Fraunhofer SIT
> Yossi Gilad, MIT
>  
> [A] https://conferences.sigcomm.org/hotnets/2018/program.html
> [B] http://peering.usc.edu
> [C] https://goo.gl/AFR1Cn
> [D] https://labs.ripe.net/Members/erik/ripe-ncc-and-duke-university-bgp-experiment
> [E] https://goo.gl/nJhmx1
>
> Este mensaje contiene información confidencial y se entiende dirigido
> y para uso exclusivo del destinatario. Si recibes este mensaje y no
> eres el destinatario por favor elimínalo, ya que difundir, revelar,
> copiar o tomar cualquier acción basada en el contenido está
> estrictamente prohibido. Network Information Center, S.A. de C.V.,
> ubicado en Ave. Eugenio Garza Sada 427 L4-6 Col. Altavista, Monterrey,
> México, C.P. 64840 recaba tus datos personales necesarios para: la
> prestación, estudio, análisis y mejora del servicio, la realización de
> comunicaciones y notificaciones; la transferencia y publicación en los
> casos aplicables; el cumplimiento de la relación existente; así como
> para la prevención o denuncia en la comisión de ilícitos. Si eres
> colaborador o candidato a colaborador de NIC México, tus datos serán
> utilizados para: la creación y administración de tu perfil como
> profesionista; el otorgamiento de herramientas de trabajo; la
> realización de estudios; el otorgamiento de programas y beneficios
> para mejorar tu desarrollo profesional; la gestión y administración de
> servicios de pago y/o nómina; así como para contacto y/o
> notificaciones. Si participas en promociones o en estudios podrás
> dejar de participar. Para mayor información revisa el Aviso de
> Privacidad <http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.
>
>
> This message contains confidential information and is intended only
> for the individual named. If you are not the named addressee please
> delete it, since the dissemination, distribuition, copy or taking any
> action in reliance on the contents is strictly prohibited. Network
> Information Center, S.A. de C.V., located on Av. Eugenio Garza Sada
> 427 L4-6, Col. Altavista, Monterrey, Mexico, CP 64840 collects your
> personal data which is necessary to: provide, research, analyze and
> improve the service; send communications and notices; transfer and
> publish your personal data when applicable; fulfill the existing
> relationship; prevent or inform in the commission of unlawful acts or
> events. If the data is processed in your quality of candidate or
> collaborator of NIC Mexico, the purpose of treatment is to: create and
> manage your profile as a professional; provide you with working tools;
> conduct studies; grant benefits and programs to enhance your
> professional development; manage and administrate payment services
> and/or payroll; as well as to contact you. If you participate in
> promotions or surveys you may stop or quit your participation at any
> time. For more information read the Privacy Note
> <http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.
>
>
> _______________________________________________
> LACNOG mailing list
> LACNOG en lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lacnog
> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20190107/86176db4/attachment.html>