[59064] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: IPv6

daemon@ATHENA.MIT.EDU (Daryl G. Jurbala)
Fri Jun 13 10:22:47 2003

Date: Fri, 13 Jun 2003 10:20:10 -0400
From: "Daryl G. Jurbala" <daryl@introspect.net>
To: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu


This is a multi-part message in MIME format.

--Boundary_(ID_xfBFJdS/SVAmVcfejkmDlg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

I guess that means vendor C has no excuse on the 7200 VXR series (and I
believe a few of the newer models).  But I still don't see anthing
fantastically IPv6 happening there.
 
Daryl G. Jurbala
Introspect.net Consulting
Tel: +1 215 825 8401
Fax: +1 508 526 8500
http://www.introspect.net <http://www.introspect.net/> 

PGP Key: http://www.introspect.net/pgp <http://www.introspect.net/pgp>


	-----Original Message-----
	From: stephen@sprunk.org [mailto:stephen@sprunk.org] 
	Sent: Friday, June 13, 2003 12:48 AM
	To: eddy+public+spam@noc.everquick.net
	Cc: nanog@merit.edu
	Subject: Re: IPv6
	
	
	 [.....]  

	Most L3 switches shipping today (e.g. the product in question)
have 
	particular ethertypes and destination address offsets hardcoded
into their 
	ASICs.  It's not a matter of supporting 128-bit addresses --
they simply 
	doesn't understand IPv6's header any more than they do DECnet or
AppleTalk. 

	While allocation policies may have an effect on how IPv6 FIBs
are most 
	efficiently stored, address length is a fairly small part of the
problem 
	when you're talking about redesigning every ASIC to handle both
IPv4 and 
	IPv6. 

	 [....]


--Boundary_(ID_xfBFJdS/SVAmVcfejkmDlg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D827521714-13062003><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
guess that means vendor C has no excuse on the 7200 VXR series (and I =
believe a=20
few of the newer models).&nbsp; But I still don't see anthing =
fantastically IPv6=20
happening there.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><SPAN class=3D827521714-13062003>D</SPAN>aryl G.=20
Jurbala<BR>Introspect.net Consulting<BR>Tel: +1 215 825 8401<BR>Fax: +1 =
508 526=20
8500<BR></FONT><A href=3D"http://www.introspect.net/"><FONT=20
size=3D2>http://www.introspect.net</FONT></A><BR><BR><FONT size=3D2>PGP =
Key:=20
</FONT><A href=3D"http://www.introspect.net/pgp"><FONT=20
size=3D2>http://www.introspect.net/pgp</FONT></A><FONT size=3D2>&nbsp; =
</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  stephen@sprunk.org [mailto:stephen@sprunk.org] <BR><B>Sent:</B> =
Friday, June=20
  13, 2003 12:48 AM<BR><B>To:</B>=20
  eddy+public+spam@noc.everquick.net<BR><B>Cc:</B>=20
  nanog@merit.edu<BR><B>Subject:</B> Re: IPv6<BR><BR></FONT></DIV><SPAN=20
  class=3D827521714-13062003><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;<FONT=20
  face=3DTahoma color=3D#000000>[.....]</FONT>&nbsp;</FONT></SPAN>
  <P><FONT size=3D2>Most L3 switches shipping today (e.g. the product in =
question)=20
  have</FONT> <BR><FONT size=3D2>particular ethertypes and destination =
address=20
  offsets hardcoded into their</FONT> <BR><FONT size=3D2>ASICs.&nbsp; =
It's not a=20
  matter of supporting 128-bit addresses -- they simply</FONT> <BR><FONT =

  size=3D2>doesn't understand IPv6's header any more than they do DECnet =
or=20
  AppleTalk.</FONT> </P>
  <P><FONT size=3D2>While allocation policies may have an effect on how =
IPv6 FIBs=20
  are most</FONT> <BR><FONT size=3D2>efficiently stored, address length =
is a=20
  fairly small part of the problem</FONT> <BR><FONT size=3D2>when you're =
talking=20
  about redesigning every ASIC to handle both IPv4 and</FONT> <BR><FONT=20
  size=3D2>IPv6.</FONT> </P>
  <P><FONT size=3D2><SPAN class=3D827521714-13062003><FONT face=3DArial=20
  =
color=3D#0000ff>&nbsp;[....]</FONT></SPAN></FONT></P></BLOCKQUOTE></BODY>=
</HTML>
=00=

--Boundary_(ID_xfBFJdS/SVAmVcfejkmDlg)--

home help back first fref pref prev next nref lref last post