<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=328164522-15032011><FONT color=#0000ff
size=2 face=Arial>Harold, Lista,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=328164522-15032011><FONT color=#0000ff
size=2 face=Arial> Muy bueno el documento. El modo de redacción del
documento es excelente. Me agrada incluso para una charla.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=328164522-15032011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=328164522-15032011><FONT color=#0000ff
size=2 face=Arial>Saludos,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=328164522-15032011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=328164522-15032011><FONT color=#0000ff
size=2 face=Arial>Alejandro,</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=es class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>De:</B> lactf-bounces@lacnic.net
[mailto:lactf-bounces@lacnic.net] <B>En nombre de </B>Jorge
Villa<BR><B>Enviado el:</B> Martes, 15 de Marzo de 2011 03:41
p.m.<BR><B>Para:</B> lactf@lac.ipv6tf.org<BR><B>Asunto:</B> Re: [LAC-TF]
{Disarmed} Re: FW: Creating an IPv6 addressing plan for end
users(RIPE)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV><FONT size=2 face=Arial>Harold, muy buen aporte. Creo que como
complemento habria que agregar algunas herramientas para realizar el
direccionamiento y gestion de direcciones IPv6, tales como:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>IPplan (<A
href="">http://iptrack.sourceforge.net</A>)</FONT></DIV>
<DIV><FONT size=2 face=Arial>IPv6 Optimal Address Paln and Allocation Tool
[Marc Blanchet] (<A
href="http://www.ipv6book.ca/allocation.html">http://www.ipv6book.ca/allocation.html</A>)<BR></FONT></DIV>
<DIV><FONT size=2 face=Arial>Arturo, buena informacion complementaria de ese
trabajo de Owen y tambien es interesante la del Wiki de ARIN (<A
href="http://www.getipv6.info/index.php/IPv6_Addressing_Plans">http://www.getipv6.info/index.php/IPv6_Addressing_Plans</A>)</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Saludos,</FONT></DIV>
<DIV><FONT size=2 face=Arial>Jorge</DIV></FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV style="FONT: 10pt arial"> </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=aservin@lacnic.net href="mailto:aservin@lacnic.net">Arturo
Servin</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lactf@lac.ipv6tf.org
href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 15, 2011 3:37
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> {Disarmed} Re: [LAC-TF] FW:
Creating an IPv6 addressing plan for end users(RIPE)</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><SPAN style="WHITE-SPACE: pre" class=Apple-tab-span></SPAN>El documento
es bastante interesante.</DIV>
<DIV><BR></DIV>
<DIV><SPAN style="WHITE-SPACE: pre" class=Apple-tab-span></SPAN>Aquí hay una
presentación con otras recomendaciones de como hacer el plan de
direccionamiento.</DIV>
<DIV><FONT color=#0000ff size=2 face=Arial></FONT><BR></DIV>
<DIV><A
href="http://meetings.apnic.net/__data/assets/pdf_file/0008/23489/Half-Day-Intro.pdf">http://meetings.apnic.net/__data/assets/pdf_file/0008/23489/Half-Day-Intro.pdf</A></DIV>
<DIV><A
href="http://meetings.apnic.net/30/program/ipv6">http://meetings.apnic.net/30/program/ipv6</A></DIV>
<DIV><BR></DIV>
<DIV><SPAN style="WHITE-SPACE: pre" class=Apple-tab-span></SPAN>Sería
interesante saber si la gente está usando (o interesada más) en asignaciones
secuenciales o por bisección (no estoy seguro que esos sean los términos
correctos en castellano).</DIV>
<DIV><BR></DIV>
<DIV>Slds,</DIV>
<DIV>as</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV><BR>
<DIV>
<DIV>On 15 Mar 2011, at 16:11, Harold de Dios T. wrote:</DIV><BR
class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
<DIV><FONT size=2><FONT face="Consolas, Courier New, Courier"><SPAN
style="FONT-SIZE: 10pt">Les comparto un buen documento (abajo descrito en
URL) que a muchos de nosotros (directa o indirectamente) será de utilidad.
<BR><BR>Saludos,<BR>Harold.<BR></SPAN></FONT></FONT><FONT
face="Calibri, Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 11pt">------ Mensaje reenviado<BR><B>De: </B>Ray Soucy
<<A
href="x-msg://1067/rps@maine.edu">rps@maine.edu</A>><BR><B>Fecha:
</B>Tue, 15 Mar 2011 14:56:51 -0400<BR><B>Para: </B>Brent Sweeny <<A
href="x-msg://1067/sweeny@indiana.edu">sweeny@indiana.edu</A>><BR><B>CC:
</B>i2 ipv6 wg <<A
href="x-msg://1067/wg-ipv6@internet2.edu">wg-ipv6@internet2.edu</A>><BR><B>Asunto:
</B>Re: Creating an IPv6 addressing plan for end users (RIPE)<BR><BR>It's
a nice document.<BR><BR>RFC 3627 is worth mentioning. 126-bit
prefixes for point-to-point networks are just as easy to use, and with
IPv6 there isn't really a concern to save space.<BR><BR>In Maine we've
been looking into the ability to exploit very large address space for
subnets and neighbor discovery to perform denial of service attacks by
causing enough ND solicitations to fill the neighbor table for a router
(e.g. sweeping through every address in a 64-bit prefix)
as briefly mentioned in RFC
3756.<BR><BR>Initial results in the lab (if you can call a few
routers and a laptop a lab) are showing this could be a major problem and
become one of the most attractive denial of service attacks (I was
actually working on this last night).<BR><BR>Because of this, we're
updating our message to not only encourage, but also recommend the use of
126-bit prefixes for any point-to-point network.<BR><BR>We have also
adjusted our recommendation for LAN addressing to allocate 64-bit
prefixes, but if possible (e.g. SLAAC is not being used), use a subset of
the prefix with an appropriate size to limit the impact of such an attack
until better security controls are available.<BR><BR>For example, you
could allocate 2001:db8:0:1234::/64 for a network, but only define it on
the gateway as 2001:db8:0:1234::/120 (256). This helps
to mitigate the usefulness of the attack, but maintains the
flexibility to migrate to a 64-bit prefix once better controls are in
place.<BR><BR>We also position SLAAC as a less desirable option
for a corporate network. DHCPv6 was perceived to be "wrong" by
much of the IPv6 community, mainly due to lack of
client implementation; but for the enterprise this level of
control is highly desirable, especially for a phased deployment of
IPv6. <BR><BR>Thankfully, Windows (Vista), Mac OS X (Lion), and most
Linux distributions now have mature DHCPv6 client implementations,
making DHCPv6 a more than viable option for IPv6 deployment. It also
helps avoid IPv6 being used by hosts with
less-than-complete implementations as most systems that include
DHCPv6 have fairly stable and mature IPv6 implementations.<BR><BR>I
don't think anyone has written an RFC to describe how routers should
construct the neighbor table (would love to know if that is not the case),
but it would be nice to see something along the lines of not expiring
known entries if the table is full formalized as
an implementation guideline, or perhaps added as a security
feature.<BR><BR>On Tue, Mar 15, 2011 at 8:39 AM, Brent Sweeny <<A
href="x-msg://1067/sweeny@indiana.edu">sweeny@indiana.edu</A>>
wrote:<BR></SPAN></FONT>
<BLOCKQUOTE type="cite"><FONT
face="Calibri, Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 11pt">RIPE sent this to v6-ops, but I expect there's
interest in this group too:<BR>-------------------------------<BR>Date:
Tue, 15 Mar 2011 10:01:17 +0100<BR>From: Nathalie Trenaman <<A
href="x-msg://1067/nathalie@ripe.net"><FONT color=red><B>MailScanner ha
detectado un posible intento de fraude desde "x-msg:"
</B></FONT>nathalie@ripe.net</A>><BR>Subject: Creating an IPv6
addressing plan for end users<BR>To: <A
href="x-msg://1067/ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</A><BR><BR>Hi
all,<BR><BR>In our IPv6 courses, we often get the question: I give my
customers a<BR>/48 (or a /56 or a /52) but they have no idea how to
distribute that<BR>space in their network.<BR>In December Sander
Steffann and Surfnet wrote a manual explaining<BR>exactly that, in clear
language with nice graphics. A very useful<BR>document but it was in
Dutch,<BR>so RIPE NCC decided to translate that document to
English.<BR><BR>Today, we have published that document on our website
and we hope this<BR>document is able to take away some of the fear that
end users seem to<BR>have for these huge blocks.<BR>You can find this
document here:<BR><BR><A
href="http://www.ripe.net/training/material/IPv6-for-LIRs-Training-Course/IPv6_addr_plan4.pdf">http://www.ripe.net/training/material/IPv6-for-LIRs-Training-Course/IPv6_addr_plan4.pdf</A><BR>(PDF)<BR><BR>short
URL:<BR><A
href="http://bit.ly/IPv6addrplan">http://bit.ly/IPv6addrplan</A><BR><BR>We
look forward to your feedback, tips and comments.<BR><BR>With kind
regards,<BR><BR>Nathalie Trenaman<BR>RIPE NCC
Trainer<BR></SPAN></FONT></BLOCKQUOTE><FONT
face="Calibri, Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 11pt"><BR><BR><BR>-- <BR>Ray Soucy<BR><BR>Epic
Communications Specialist<BR><BR>Phone: +1 (207)
561-3526<BR><BR>Networkmaine, a Unit of the University of Maine
System<BR><A
href="http://www.networkmaine.net/">http://www.networkmaine.net/</A><BR><BR><BR>------
Fin del mensaje
reenviado<BR></SPAN></FONT></DIV>_______________________________________________<BR>LACTF
mailing list<BR><A
href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</A><BR><A
href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</A><BR></BLOCKQUOTE></DIV><BR>PREVENCIÓN
ES SALUD. TODOS PODEMOS LOGRARLO.
<P>
<HR>
<P></P>_______________________________________________<BR>LACTF mailing
list<BR>LACTF@lacnic.net<BR>https://mail.lacnic.net/mailman/listinfo/lactf<BR></BLOCKQUOTE>PREVENCIÓN
ES SALUD. TODOS PODEMOS LOGRARLO. </BLOCKQUOTE></BODY></HTML>