> From: Dae Young KIM <[email protected]>
> o I have one and only one number for my node.
That's what I was trying to find out. So even if you have a machine which is
connected to two networks, it only has one 'node address'.
Therefore, the 'mode address' cannot contain any information about the
'location' of the node (since a machine with two connections, i.e. two
'locations', has only one 'node address').
So you may have a different term ('node address'), but your 'node address'
acts, and is used, just like the 'identifier' that most of the rest of us
talk about.
Similarly, in this example, which shows a node we can call 'node D':
> node <- node addr (= IP addr)
> | \
> | \
> | \
> mac addr -> LAN 3G <- L2 addr
Let me also set the condition that the shortest path from the LAN to the 3G
network which does _not_ pass through node D is very long (say 10 AS's long).
Now, looking at another node a long way away (say, 10 AS's away from both the
LAN and the 3G network) - we can call this other node S: what node S puts in
an IP packet to get it to node D is not either the 'MAC address' or the 'L2
address' (which cannot be 'routed' on such a large scope), but some other
value (an AS number, it seems). Once the packet gets to that AS, the 'MAC
address'/'L2 address' is used to get it to the host.
Assuming such a design would work (since whether or not it will work is not
relevant to the point I want to make), the combination of AS number and 'MAC
address'/'L2 address' acts, and is used, just like the 'locator' that most of
the rest of us talk about.
So you have simply re-created the same basic design most of the rest of us
have, just with different terms, and slightly different engineering details.
Noel
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
