[afnog] subnet prefix length > 64 breaks IPv6?

[sylvain aboka baya]

 Hi, Jordi !

 Please, Receive my Best Wishes about the New Year 2012 !

 FYA, Please Look Below...


------------------------------

Message: 6
Date: Sat, 24 Dec 2011 11:02:35 +0530
From: Glen Kent <glen.kent at gmail.com>
To: nanog at nanog.org
Subject: subnet prefix length > 64 breaks IPv6?
Message-ID:
    <CAPLq3UPJqwrqeOJornSAEQjNa=b7BOB6r3XZWugHUGyLAsq9Wg at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am trying to understand why standards say that "using a subnet
prefix length other than a /64 will break many features of IPv6,
including Neighbor Discovery (ND), Secure Neighbor Discovery (SEND)
[RFC3971], .. " [reference RFC 5375]

Or "A number of other features currently in development, or being
proposed, also rely on /64 subnet prefixes."

Is it because the 128 bits are divided into two 64 bit halves, where
the latter identifies an Interface ID which is uniquely derived from
the 48bit MAC address.

I am not sure if this is the reason as this only applies to the link
local IP address. One could still assign a global IPv6 address. So,
why does basic IPv6 (ND process, etc) break if i use a netmask of say
/120?

I know that several operators use /120 as a /64 can be quite risky in
terms of ND attacks. So, how does that work? I tried googling but
couldnt find any references that explain how IPv6 breaks with using a
netmask other than 64.

Glen



------------------------------  


 Best Regards!                                                     
 
************************
Sylvain Baya
 CCNA
 (+237) 77005341                              

BP 13107 YAOUNDE / CAMEROUN
abscoco2001 at yahoo.fr
************************




________________________________
 De : JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
À : "ipv6cluster at ist-ipv6.org" <ipv6cluster at ist-ipv6.org> 
Envoyé le : Lundi 26 Décembre 2011 8h06
Objet : [ipv6cluster] IPv6 news - weekly summary {01}
 

IPv6 news - weekly summary 

Main News:


Other News:
Year in Review 2011: The stories that dominated the wireline industry
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8269>

It’s Time to get Jiggy with Active DDI
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8268>

New Internet protocol to undergo test
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8267>

China to speed up development of next-generation Internet industry: Cabinet
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8263>

IPv6 due for wide deployment in 2012, experts say
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8261>

I Want IPv6 for Christmas - Part II
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8258>

IP Address Space Covered by Certificates
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8257>

Rising Cybercrime Pushes African Governments to Take Action
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8256>

IPv6: Get ready for the transition…and avoid becoming obsolete
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8254>


Security:
Cyber threats in 2012: 5 pain points
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8266>


Corporate and Products:
2012: Year of warp speed, other innovations
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8265>

2012 Predictions: Networking part two
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8264>

D-Link Successfully Passes Second Round of IPv6 Interoperability Testing
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8262>

The RTC Group Announces "Internet of Things" Keynote in Santa Clara January Conference
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8260>

Stonesoft Firewall/VPN Receives VPN Consortium’s IPv6 IPsec Certification
<http://www.ipv6tf.org/index.php?page=news/newsroom&id=8259>




 
**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://afnog.org/pipermail/afnog/attachments/20111227/53657c5e/attachment.html>