<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Super buena idea..... duraron mucho :-)<br>
</p>
<br>
<div class="moz-cite-prefix">El 21/2/17 a las 6:41 p.m., Tomas Lynch
escribió:<br>
</div>
<blockquote
cite="mid:CAGEujU_+8OY35R3FgnxivRtVHZ3iVqm5eviqkzedWXN8paaiqg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Coincide con las nuevas formas de configuración de Cisco
en IOS XR y las de siempre de Juniper donde tenés que
explicitar un filtro de entrada y salida. Desconozco otros
vendors.<br>
<br>
</div>
Me parece una muy buena idea.<br>
<br>
</div>
Tomás Lynch<br>
<div>
<div><br>
<br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Feb 21, 2017 at 5:25 PM,
Guillermo Cicileo <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:gcicileo@gmail.com"
target="_blank">gcicileo@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hola,
<div><br>
</div>
<div>No se si han visto este draft que se esta proponiendo
en el grupo grow de la IETF. La idea es cambiar la
política por default de BGP, que en muchas
implementaciones (IOS, Juniper) consiste en aceptar todo
lo que los neighbors publican y anunciar a todos los
neighbors.</div>
<div><br>
</div>
<div>Este draft propone cambiar ese comportamiento para
que, en caso de que no haya configurada explícitamente
una política de entrada o salida, no se acepten ni
anuncien rutas en las sesiones eBGP. </div>
<div><br>
</div>
<div>Este cambio es interesante porque nos protege de
errores involuntarios, pero su impacto sobre las
implementaciones y las redes en producción existentes
puede ser importante. </div>
<div><br>
</div>
<div>Creo que es interesante que le den una lectura, es
cortito :)</div>
<div><br clear="all">
<div>
<div class="m_-2943536147104445823gmail_signature">Saludos,<br>
<br>
Guillermo.<br>
</div>
</div>
<br>
<div class="gmail_quote">---------- Forwarded message
----------<br>
From: <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:internet-drafts@ietf.org"
target="_blank">internet-drafts@ietf.org</a>></span><br>
Date: Tue, Feb 21, 2017 at 5:37 PM<br>
Subject: [GROW] I-D Action:
draft-ietf-grow-bgp-reject-03.<wbr>txt<br>
To: <a moz-do-not-send="true"
href="mailto:i-d-announce@ietf.org" target="_blank">i-d-announce@ietf.org</a><br>
Cc: <a moz-do-not-send="true"
href="mailto:grow@ietf.org" target="_blank">grow@ietf.org</a><br>
<br>
<br>
<br>
A New Internet-Draft is available from the on-line
Internet-Drafts directories.<br>
This draft is a work item of the Global Routing
Operations of the IETF.<br>
<br>
Title : Default EBGP Route
Propagation Behavior Without Policies<br>
Authors : Jared Mauch<br>
Job Snijders<br>
Greg Hankins<br>
Filename :
draft-ietf-grow-bgp-reject-03.<wbr>txt<br>
Pages : 5<br>
Date : 2017-02-21<br>
<br>
Abstract:<br>
This document defines the default behavior of a BGP
speaker when<br>
there is no import or export policy associated with
an External BGP<br>
session.<br>
<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a moz-do-not-send="true"
href="https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-reject/"
rel="noreferrer" target="_blank">https://datatracker.ietf.org/d<wbr>oc/draft-ietf-grow-bgp-reject/</a><br>
<br>
There's also a htmlized version available at:<br>
<a moz-do-not-send="true"
href="https://tools.ietf.org/html/draft-ietf-grow-bgp-reject-03"
rel="noreferrer" target="_blank">https://tools.ietf.org/html/dr<wbr>aft-ietf-grow-bgp-reject-03</a><br>
<br>
A diff from the previous version is available at:<br>
<a moz-do-not-send="true"
href="https://www.ietf.org/rfcdiff?url2=draft-ietf-grow-bgp-reject-03"
rel="noreferrer" target="_blank">https://www.ietf.org/rfcdiff?u<wbr>rl2=draft-ietf-grow-bgp-reject<wbr>-03</a><br>
<br>
<br>
Please note that it may take a couple of minutes from
the time of submission<br>
until the htmlized version and diff are available at <a
moz-do-not-send="true" href="http://tools.ietf.org"
rel="noreferrer" target="_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP
at:<br>
<a moz-do-not-send="true"
href="ftp://ftp.ietf.org/internet-drafts/"
rel="noreferrer" target="_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
<br>
______________________________<wbr>_________________<br>
GROW mailing list<br>
<a moz-do-not-send="true" href="mailto:GROW@ietf.org"
target="_blank">GROW@ietf.org</a><br>
<a moz-do-not-send="true"
href="https://www.ietf.org/mailman/listinfo/grow"
rel="noreferrer" target="_blank">https://www.ietf.org/mailman/l<wbr>istinfo/grow</a><br>
</div>
<br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
LACNOG mailing list<br>
<a moz-do-not-send="true" href="mailto:LACNOG@lacnic.net">LACNOG@lacnic.net</a><br>
<a moz-do-not-send="true"
href="https://mail.lacnic.net/mailman/listinfo/lacnog"
rel="noreferrer" target="_blank">https://mail.lacnic.net/<wbr>mailman/listinfo/lacnog</a><br>
Cancelar suscripcion: <a moz-do-not-send="true"
href="https://mail.lacnic.net/mailman/options/lacnog"
rel="noreferrer" target="_blank">https://mail.lacnic.net/<wbr>mailman/options/lacnog</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
LACNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LACNOG@lacnic.net">LACNOG@lacnic.net</a>
<a class="moz-txt-link-freetext" href="https://mail.lacnic.net/mailman/listinfo/lacnog">https://mail.lacnic.net/mailman/listinfo/lacnog</a>
Cancelar suscripcion: <a class="moz-txt-link-freetext" href="https://mail.lacnic.net/mailman/options/lacnog">https://mail.lacnic.net/mailman/options/lacnog</a>
</pre>
</blockquote>
<br>
</body>
</html>