IPv6 in the enterprise

[Brandon Applegate]

On Tue, 19 Apr 2011, Mark Smith wrote:

> On Mon, 18 Apr 2011 17:45:36 -0400
> Matthew Huff <mhuff at ox.com> wrote:
>
>> So that when that ip address was discovered within monitoring systems we could do a reverse map back to the switch. Not possible with a link local.
>>
>
> I can see that might be useful for monitoring purposes, however I don't
> understand what the benefits are of then using a GUA a default gateway
> address on the end-nodes is. Wouldn't using link-locals for end-node
> default gateway addresses would make renumbering to a different GUA an
> easier task than the current efforts we have to go to in IPv4?
>

What about a routing protocol that carries the next-hop of a route in it 
unchanged ?  I believe this has been brought up before.  I'm trying to 
think of an example of where this could happen, I guess one would be:

-	'edge' between two orgs, side A running iBGP
-	side B presents to side A with hsrp
-	side A wishes to redist statics pointing at side B into their iBGP
-	assuming no 'next-hop-self', this address needs to be GUA

I am personally running GUA HSRP (cisco 6500 SXI5) on some segments but 
only have linux servers attached.  I am trying to keep up with the info 
folks are posting re: Windows 7 losing it's route after some time, very 
interesting.

Disclaimer: not trying to get religious on the subject, I like the fact 
that both GUA and LL are possible, and value folks input for both types of 
addresses being used.

--
Brandon Applegate - CCIE 10273
PGP Key fingerprint:
7407 DC86 AA7B A57F 62D1 A715 3C63 66A1 181E 6996
"SH1-0151.  This is the serial number, of our orbital gun."