>>>>> On Sat, 15 Mar 2003 18:15:25 +0200,
>>>>> Markku Savela <[EMAIL PROTECTED]> said:
>> to be clear: for outgoing packet, that should be enough. for incoming
>> packet, you will need to have a mapping table of
>> interface id -> link id
>> and translate id accordingly and use "fe80::1%linkX" as the identifier
>> for the peer.
> Such mapping is very simple: you just have each interface associated
> array of scope id's (16). For incoming packet, you just complete the
> source and destination addresses with: linkX =
> interface-> scopes[scope_of_addr]. Works also for multicast
> destinations, which may have almost any scope.
Yes, that's exactly what our current implementation does (except the
"fe80::1%linkX" notation). So, in some points, our implementation
have already prepared for the "links are larger than interfaces"
model.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[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]
--------------------------------------------------------------------
