<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><title>Enriched by Impactia Enterprise</title><style></style></head><body bgcolor=white lang=EN-US link=blue vlink=purple id="EFRAMER_MAIN_TABLE"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Inline: GV><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] <b>On Behalf Of </b>Elad Hefetz<br><b>Sent:</b> 26 May 2011 10:19<br><b>To:</b> Jasper Jans; ipv6-wg@ripe.net<br><b>Subject:</b> RE: [ipv6-wg] IPv6 on P2P links<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="95%" style='width:95.0%'><tr><td width="100%" style='width:100.0%;padding:0cm 0cm 0cm 0cm'><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%'><tr><td width="100%" style='width:100.0%;padding:1.5pt 1.5pt 1.5pt 1.5pt'><p align=center style='text-align:center'><a href="http://impactia.bezeqint.co.il/redirect.ASP?id=777&data=CzKhoCXrD8jQJitd8tSkHt5ZcZSwGdvpM15XhlxVXYF%2BerrLMudEVXXGgj7%2FOnfO&url=https:%2F%2Fonline.bezeqint.net%2Fupagegateway%2F569%2F66%2FNDZydW5hZklrTjcwNXZJNjBZMzdiQmFjcVNOSFpBU3RjWDdqWm9LSjlCcGVac3VaYS9SUDN4R3NQQWFNR0hFUitqSDMwWVV2S0R4TwpkTVVySGZhdjIrd3R6NXh4LzJvR1J1ZmVsZzBpdFlWcHR3aXFQZmdDQVExd3c3YTJ2aDlm"><span style='text-decoration:none'><img border=0 width=647 height=76 id="_x0000_i1032" src="cid:image001.jpg@01CC1B8F.F56286D0"></span></a><o:p></o:p></p></td></tr></table></td></tr><tr><td width="100%" valign=top style='width:100.0%;padding:7.5pt 7.5pt 7.5pt 7.5pt'><div id=emailtext><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p>The major problem I can assume happen when using only link local is the issue of replacing hardware.<br>When you replace the cards on the routers it will require you to change the internal routing protocol (IS-IS \ OSPF). <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>GV> this is incorrect, not? ISIS runs over CLNS and OSPFv3 just detects its neighbor by sending hello’s. If you replace HW, then there is no impact on these protocols at all.<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p>Another issue is debugging - when using trace route - all you will see is link-local addresses which make it very difficult to debug issues. <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>GV> depending on the vendor used it may actually give you a loopback address… because, how can a LL be the source of a ICMP unreachable reply? (the return packet would not be able to pass the link actually)<o:p></o:p></span></p><p>We are configuring all our P2P links with /64 prefix on each link. This is not idle and very wasteful way, but it's the only solution to not interfere with RFCs and standards.<br><br><span style='color:#1F497D'><o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>GV> /127 is now ok also, and doesn’t suffer from the well known ping-pong problem.<o:p></o:p></span></p><p>Also - this is the only way to be multi vendors prepared, be ready for future to come with new IPv6 applications and products. <o:p></o:p></p><p>MHO,<br>Elad <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>G/<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p>-----Original Message-----<br><br><o:p></o:p></p><pre><o:p> </o:p></pre><pre>From: <a href="mailto:ipv6-wg-admin@ripe.net">ipv6-wg-admin@ripe.net</a> mailto:[<a href="mailto:ipv6-wg-admin@ripe.net">ipv6-wg-admin@ripe.net</a>] On Behalf<o:p></o:p></pre><pre>Of Jasper Jans<o:p></o:p></pre><pre>Sent: Thursday, May 26, 2011 11:08 AM<o:p></o:p></pre><pre>To: <a href="mailto:ipv6-wg@ripe.net">ipv6-wg@ripe.net</a><o:p></o:p></pre><pre>Subject: [ipv6-wg] IPv6 on P2P links<o:p></o:p></pre><p>Can anyone give me some real world experience with IPv6 numbering on P2P links in their network?<o:p></o:p></p><p>I've seen the recommendations swing from '/64' to '/127 if your equipment can handle it' and even to 'do not assign anything at all just use link-local' and access your devices over the loopback which your IGP will distribute.<o:p></o:p></p><p>The last option seems interesting to me from a IP assignment point of few. It safes me having to allocate a block for this part of the infrastructure. I'm just wondering if in the long run it will not make life harder.<o:p></o:p></p><p>Jasper<o:p></o:p></p><p><br>Op dit e-mailbericht is een disclaimer van toepassing, welke te vinden is op <a href="http://www.espritxb.nl/disclaimer">http://www.espritxb.nl/disclaimer</a><o:p></o:p></p></div></td></tr></table><div id=footer><div class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif"'><hr size=1 width="100%" noshade style='color:#A0A0A0' align=left></span></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif"'>This message was enriched by Impactia Technologies Ltd. <a href="http://www.impactia.com" id="footer_url1">www.impactia.com</a><br>Please <a href="http://impactia.bezeqint.co.il/exclude.ASP?email=ipv6-wg@ripe.net&domain=bezeqint.co.il&id=777" id="footer_url2">do not enrich</a> emails sent to me.<br><br><o:p></o:p></span></p></div></div></div></body></html>