On Tue, 4 Mar 2003, Quality Quorum wrote: > The problem here is software implementation of longest prefix match. > Up to this point it was limited to a few TLAs with 48 bits which was > quite doable in software, this draft expands it to 61
Note that "this" draft does not do it, it has been already done in addr-arch-v3, which has been approved by IESG/IAB for publication to Proposed Standard. > and you are > proposing 125, which is well beyond capabilities of software based > lookups. "well beyond capabilities of software based lookups" seems to be clearly false: I've run IPv6 test on Linux / BSD-based systems, which do have exactly that and have obtained gigabit-grade results, the same as with IPv4. Perhaps that applies in a very specific scenario of sw lookups only. Btw, it's 64 and 128, respectively: you seem to be doing exactly what's forbidden, glueing 2000::/3 in the implementation -- or do you do 48/64/128-bit lookup for non-2000::/3 routes? -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
