<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span> <a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-discard-prefix/">https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-discard-prefix/</a></div><div><br></div><div><div>"Remote triggered black hole filtering describes a method of</div><div> mitigating the effects of denial-of-service attacks by selectively</div><div> discarding traffic based on source or destination address. Remote</div><div> triggered black hole routing describes a method of selectively re-</div><div> routing traffic into a sinkhole router (for further analysis) based</div><div> on destination address. This document updates RFC5156 by explaining</div><div> why a unique IPv6 prefix should be formally assigned by IANA for the</div><div> purpose of facilitating IPv6 remote triggered black hole filtering</div><div> and routing."</div></div><div><br></div><div>Slds</div><div>as</div><br><div><div>On 13 Apr 2012, at 12:31, Carlos Martinez-Cagnazzo wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Si, ese es un topico relacionado excelente. Nosotros incluso podemos<br>alojar un wiki o una pagina web donde documentar esas cosas, y donde los<br>ISPs participantes se puedan anotar.<br><br>s2<br><br>Carlos<br><br>On 4/13/12 12:21 PM, Alejandro Acosta wrote:<br><blockquote type="cite">Hola,<br></blockquote><blockquote type="cite"> Esto tópicos serían excelentes.<br></blockquote><blockquote type="cite"> En estos días reunidos con un ISP (tipo Data Center) y conversando<br></blockquote><blockquote type="cite">con un upstream provider conversamos sobre otro uso de communities que<br></blockquote><blockquote type="cite">me pareció super interesante. Lo explico:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">1) Supongamos que yo tengo asignado un bloque /20, ahora bien me<br></blockquote><blockquote type="cite">estan atacando el host (o la red, no importa) ZZ.XX.CC.VV/24.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2) Cuando esto ocurra, le publico ZZ.XX.CC.VV/24 a mi upstream<br></blockquote><blockquote type="cite">provider con el community NNN que quiere decir, "enrutalo a<br></blockquote><blockquote type="cite">null/drop". De esa manera evito el ataque aguas abajo, ahorro mi<br></blockquote><blockquote type="cite">enlace internacional, etc, etc. L<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Saludos,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Alejandro,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 4/13/12, Carlos Martinez-Cagnazzo <<a href="mailto:carlosm3011@gmail.com">carlosm3011@gmail.com</a>> wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Creo que puede ser un muy buen topico para LACNOG el establecer<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">practicas regionales de uso de communities, ademas de las 'well-known'<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">como la NO_EXPORT.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On 4/13/12 11:58 AM, Arturo Servin wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Cambie de subject y solo pego esta parte del correo porque me parecio<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">adecuado comentarlo separado.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Aqui lo que se debe hacer es anunciar el agregado por todos los<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">enlaces, por ejemplo un /20. Por cada uno de los enlaces anunciar el<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">bloque desagregado (por ejemplo /21) con una comunidad de no-export.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">De esa forma puedes balancear tu tráfico sin llenar de rutas la tabla<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">de ruteo global.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Esto solo funciona si eres uni-homed, si eres multi-homed quiza si<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">tengas que partir tus bloques. Sin embargo, por lo que se ve en los<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">anuncios de ruteo, si la práctica de usar el "no-export" fuera más<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">usada podríamos reducir el número de rutas que generamos en la región.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Saludos,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">.as<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On 12 Apr 2012, at 10:51, Luis Carlos Solano wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Lo complicado de esto, sería un caso como este: supongamos que un ISP<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">tiene un cliente tan grande, que le llena totalmente uno de sus<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">enlaces de upstream de ahí que se deba anunciar a ese único cliente<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">por aparte. Quizá no sea una mala configuración del ISP.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">LACTF mailing list<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><br></blockquote></blockquote></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">LACTF mailing list<br></blockquote><blockquote type="cite"><a href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</a><br></blockquote><blockquote type="cite"><a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><br></blockquote>_______________________________________________<br>LACTF mailing list<br><a href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</a><br>https://mail.lacnic.net/mailman/listinfo/lactf<br></div></blockquote></div><br></body></html>