Alex,

Alexandru Petrescu wrote:
one-interface routers and links (again)

Let me first describe one-interface routers as I understand are proposed in 6LoWPAN:

       +------------------------+---------------+
       |                        |               |
   2001:db8:1::1/128 2001:db8:1::2/128 2001:db8:1::3/128
      _|eth0                   _|eth0          _|eth0
     |R1 |                    |R2 |           |R3 |
      ---                      ---             ---

R1 sends an IP packet to R3 but this reaches only R2. R2 picks the packet, looks at the dst address, finds it's not for self, consults routing table, finds a host-based route and sends it to R3. This can work ok.

Exactly, you pictured this nicely. This is how LoWPAN Routing works. I'll get back to the definition of that in your other thread.

Now let me picture the same thing, but with The Link:

                           The Link
       +------------------------+---------------+
       |                        |               |
   2001:db8:1::1/128 2001:db8:1::2/128 2001:db8:1::3/128
      _|eth0                   _|eth0          _|eth0
     |R1 |                    |R2 |           |R3 |
      ---                      ---             ---

If there is a such link which links together all nodes then R1 would communicate directly to R3, by definition, no need to IP route. Could you please clarify why do IP routing then?

Then obviously, you don't need to perform LoWPAN Routing. This kind of (transitive) link occurs when all nodes are in radio range of each-other, or if the link technology is forming some kind of mesh underneath IP.

In the ND draft this is really all that "mesh-under" means. It means we don't need to do LoWPAN Routing, nor do we even need nodes playing a Router roll.

And picture the same with 2 links:
              link1                  link2
       +------------------------+---------------+
       |                        |               |
   2001:db8:1::1/128 2001:db8:1::2/128 2001:db8:1::3/128
      _|eth0                   _|eth0          _|eth0
     |R1 |                    |R2 |           |R3 |
      ---                      ---             ---

But in this figure R2 would need to have two MAC addresses on the same interface, because it is in two different links. I'm not aware of such interfaces with two MAC addresses. Could you please clarify?

This doesn't exist if links are defined as you have.

Alex

_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan

--
http://zachshelby.org - My blog “On the Internet of Things”
Mobile: +358 40 7796297

Zach Shelby
Head of Research
Sensinode Ltd.
Kidekuja 2
88610 Vuokatti, FINLAND

This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof.
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan

Reply via email to