Francis,
I actually was implementing the scoped routing draft at
my previous place of employment. But, since they no longer
sell routers, the code is unavailable. The mechanism I used
was to add an additional field to the forwarding table to indicate
the scope id. The route lookups were done using the address and
the id as the key to the lookup.
Regards,
Brian
Francis Dupont wrote:
>
> In your previous mail you wrote:
>
> > PS: my concern is about the routing table (both size and organization).
>
> The added complexity of scoped routing has been known for awhile
> now. My original scoped routing document pointed it out in all
> its messy details.
>
> => my concern is not how to do it but the price to pay to have it,
> ie. it is not a technical concern (as many concerns in this thread).
>
> Thanks
>
> [EMAIL PROTECTED]
>
> PS: is the scope routing table implemented by a router vendor?
> (I'd like to get opinion from router vendors)
--
Brian Haberman
Nortel Networks
[EMAIL PROTECTED]
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
