"supporting IPv6" <--- what it means exactly?
Is there any clear understanding of what "supporting IPv6" means? I recently was told by a vendor that they "supported IPv6", and then when I went to go configure an IPv6 address, it was, of course, IPv4. I asked how they supported that, and they said that they "supported it" because they could "pass IPv6" traffic. Well...duh!
Is there any clear understanding of what "supporting IPv6" means?
I recently was told by a vendor that they "supported IPv6", and then when I went >to go configure an IPv6 address, it was, of course, IPv4. I asked how they >supported that, and they said that they "supported it" because they could "pass >IPv6" traffic.
Well...duh!
Yeah this seems to be a common problem. Vendors who have equipment that does not support a full IPv6 feature set comparable to the IPv4 functionality usually do the "it'll pass Ipv6" in which case my 10Mb/s hub from 1996 is IPv6 ready... Then there are vendors who offer a good IPv6 feature set but who only have IPv4 for the management. Some DPI vendors spring to mind for this. So.. caveat emptor! -- Leigh Porter UK Broadband ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Apr 23, 2011, at 7:45 AM, Rogelio wrote:
Is there any clear understanding of what "supporting IPv6" means?
If you actually want to know what they do or don't support, you could ask the vendor for a "Supplier's Declaration of Conformity" (SDOC) to the US Government IPv4 profile - <http://w3.antd.nist.gov/usgv6/testing.html> That profile may not include the particular features that you are most interested in, but it's probably a good start to building your own list. /John
i think jan zorz, over in slovenia has developed a good check list with the gang there which is being used more and more generally in the ripe region. randy
On Apr 23, 2011, at 7:45 AM, Rogelio wrote:
Is there any clear understanding of what "supporting IPv6" means?
I recently was told by a vendor that they "supported IPv6", and then when I went to go configure an IPv6 address, it was, of course, IPv4. I asked how they supported that, and they said that they "supported it" because they could "pass IPv6" traffic.
Look for things like: * IPv6 NDP support (RA, ND, NS, etc) * IPv6 native transport to the control-plane + in-band management * Support for IPv6 on bundled interfaces (with RA, ND, NS working) These are the types of things you need to look for. Some of these items depend on what your use case is. Some places you may want to talk about RA-Guard, others may not matter as much. Same for DHCPv6. I don't need this in my core network, but at the edge it's possibly important depending on the device(s). - Jared
there's a organization out there that has a logo compliance exercise... http://www.ipv6forum.com/ it's not perfect. when dealing with a vendor as with ipv4 there's generally a list of protocols and features you are looking to have support for, if these are encapsulated in RFCs they're fairly easy to point the finger as and say "do you support that ->" On 4/23/11 4:45 AM, Rogelio wrote:
Is there any clear understanding of what "supporting IPv6" means?
I recently was told by a vendor that they "supported IPv6", and then when I went to go configure an IPv6 address, it was, of course, IPv4. I asked how they supported that, and they said that they "supported it" because they could "pass IPv6" traffic.
Well...duh!
Is there any clear understanding of what "supporting IPv6" means?
ripe-501 may be helpful, jan zorz's docco enshrined in ripeness and overwebification. http://www.ripe.net/ripe/docs/ripe-501 randy
From: Rogelio Sent: Saturday, April 23, 2011 4:46 AM To: nanog@nanog.org Subject: "supporting IPv6" <--- what it means exactly?
Is there any clear understanding of what "supporting IPv6" means?
I recently was told by a vendor that they "supported IPv6", and then when I went to go configure an IPv6 address, it was, of course, IPv4. I asked how they supported that, and they said that they "supported it" because they could "pass IPv6" traffic.
Well...duh!
I recently ran into a case where the device can be programmed with an IPv6 address, will use v6 for management, etc. (you can use the v6 IP for SNMP and login and stuff), but it won't route v6 even with static routes (not even in using CPU). It will switch v6 traffic, though.
This may be helpful from a cpe perspective http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-cpe-router-09
participants (9)
-
Cameron Byrne -
George Bonser -
Jared Mauch -
Joel Jaeggli -
John Curran -
Jorge Amodio -
Leigh Porter -
Randy Bush -
Rogelio