<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.markdown { white-space: normal; }
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
div.plaintext h1 { font-size: 1.4em; }
div.plaintext h2 { font-size: 1.2em; }
div.plaintext h3 { font-size: 1.1em; }
blockquote.embedded,div.plaintext blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
div.plaintext a { color: #3983C4 }
blockquote.embedded,div.plaintext blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #BBBBBB; }
div.plaintext math[display="inline"] > mrow { padding:5px; }
div.plaintext div.footnotes li p { margin: 0.2em 0; }
body { font-family: sans-serif; }
div.markdown h1 { font-size: 1.4em; }
div.markdown h2 { font-size: 1.2em; }
div.markdown h3 { font-size: 1.1em; }
blockquote.embedded,div.markdown blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.markdown blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.markdown blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
div.markdown a { color: #3983C4 }
blockquote.embedded,div.markdown blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.markdown blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.markdown blockquote blockquote blockquote a { color: #BBBBBB; }
div.markdown math[display="inline"] > mrow { padding:5px; }
div.markdown div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="markdown">
<p dir="auto">Hay diferentes formas. Creo que lo mejor es:</p>
<ul>
<li>Utilizar PTRs individuales para los hosts que lo ameritan (servers, infraestructura)</li>
<li>Utilizar wildcards para rangos residenciales o redes de estaciones de trabajo. Digamos algo así como un “wildcard por VLAN”</li>
</ul>
<p dir="auto">s2</p>
<p dir="auto">Carlos</p>
<p dir="auto">On 30 Apr 2018, at 10:37, Amancio Mora Rodriguez wrote:</p>
</div>
<div class="plaintext"></div>
<blockquote class="embedded"><style scoped></style>
<div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Buenas tardes, <br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Ingenieros antes en Ipv4 se configuraba por cada Ipv4 un PTR, por ejemplo para un rango de red /24 configurabamos 255 PTR uno por cada Ipv4, para el caso de un rango /64 Ipv6 esto no sería escalable.
<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Cuál es la mejor forma y más correcta de configurar PTR en Ipv6? <br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Cordialmente, <br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Amancio Mora</div>
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
<b>Sent:</b> Thursday, April 26, 2018 10:00:00 AM<br>
<b>To:</b> lactf@lacnic.net<br>
<b>Subject:</b> LACTF Digest, Vol 169, Issue 30</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send LACTF mailing list submissions to<br>
lactf@lacnic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><br>
or, via email, send a message with subject or body 'help' to<br>
lactf-request@lacnic.net<br>
<br>
You can reach the person managing the list at<br>
lactf-owner@lacnic.net<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of LACTF digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. En 7 dias / In 7 days / Em 7 dias - FTL (ex-FLIP6)/ FTL<br>
(pre-FLIP6) / FTL (ex-FLIP6) (Azael Fernandez Alcantara)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 25 Apr 2018 10:57:55 -0500<br>
From: Azael Fernandez Alcantara <afaza@unam.mx><br>
To: GT IPv6 LAC / LAC IPv6 TF <lactf@lacnic.net><br>
Subject: [LAC-TF] En 7 dias / In 7 days / Em 7 dias - FTL (ex-FLIP6)/<br>
FTL (pre-FLIP6) / FTL (ex-FLIP6)<br>
Message-ID:<br>
<alpine.LFD.2.00.1804251053180.9467@pine.servidores.unam.mx><br>
Content-Type: text/plain; format=flowed; charset="US-ASCII"<br>
<br>
Buen Dia,<br>
<br>
Solo para recordarles y que esten al pendiente:<br>
<br>
En una semana (7 dias) sera el FTL (incluye ex-FLIP6), el miercoles 2 y <br>
jueves 3 de mayo, durante LACNIC29.<br>
+ Informacion :<br>
<a href="http://www.lacnic.net/2578/43/evento/foro-tecnico-de-lacnic">http://www.lacnic.net/2578/43/evento/foro-tecnico-de-lacnic</a><br>
<br>
In one week (7 days) will be the FTL (includes pre-FLIP6), on Wednesday <br>
and Thursday, May 2nd and 3rd, during LACNIC29.<br>
+ Information:<br>
<a href="http://www.lacnic.net/2579/44/evento/lacnic-technical-forum">http://www.lacnic.net/2579/44/evento/lacnic-technical-forum</a><br>
<br>
A Em uma semana (7 dias) sera o FTL (inclui ex-FLIP6), na quarta-feira, 2 <br>
de maio e quinta-feira 3 de maio LACNIC29.<br>
+ Informacoes:<br>
<a href="http://www.lacnic.net/2580/45/evento/forum-tecnico-de-lacnic">http://www.lacnic.net/2580/45/evento/forum-tecnico-de-lacnic</a><br>
<br>
Keynote: <br>
Bob Hinden <br>
"IPv6, Internet Security, and the Internet of Insecure Things"<br>
<br>
COORDIALES SALUDOS<br>
_________________________________________________________________<br>
Azael Fernandez Alcantara<br>
Moderador del ex-FLIP6 y de la lista LACTF de LACNIC<br>
@lactf<br>
_________________________________________________________________<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
LACTF mailing list<br>
LACTF@lacnic.net<br>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><br>
Cancelar suscripcion: lactf-unsubscribe@lacnic.net<br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 169, Issue 30<br>
**************************************<br>
</div>
</span></font></blockquote>
<div class="markdown">
<blockquote>
</blockquote><blockquote><p dir="auto">_______________________________________________<br>
LACTF mailing list<br>
LACTF@lacnic.net<br>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><br>
Cancelar suscripcion: lactf-unsubscribe@lacnic.net</p>
</blockquote></div>
<div class="markdown">
</div>
</body>
</html>