So, how would you propose that the system know that you are looking for an IPV6 config vs something else like a description or named acl/tunnel/etc?
On Wed, Jan 5, 2011 at 13:31, Nick Hilliard <[email protected]> wrote: > On 05/01/2011 16:01, Brandon Applegate wrote: > >> Is there a reason that ipv6 addresses are stored with uppercase letters >> in config ? >> > > yes. See rfc4291, section 2.2, where all of the examples are in upper > case. These examples caused people to prefer upper case notation for ipv6 > address representation, although there was actually nothing in the document > which actually mandated the use of upper case. > > These recommendations have been updated in rfc5952, which requires (i.e. > MUST) that all ipv6 addresses be represented in lower case. This document > is standards track, so I guess Cisco is going to have to change at some > stage. Given the current low levels of ipv6 deployment, sooner would be a > lot less painful than later. > > Nick > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
