Jari Arkko wrote:

Christian Huitema wrote:

The routing or spanning tree solution is the most transparent to the
hosts, since it does not change any byte in the ND packets. However,
transparency may not be entirely desired, since SEND requires being
fairly explicit about relays.


Yes. In fact, an explicit marker telling that there indeed
was a proxy would be quite useful for SEND.


The concern here is that the explicit marker may need to be carried
in all packets (not just ND packets) if there are asymmetric paths,
or if paths can change dynamically after the initial  ND exchange.

Fred Templin wrote:

In other words, we need something like the experimental protocols
coming from the MANET wg (e.g., AODV, DSR, OLSR, TBRPF).
Even better would be a unified mechanism that combines the best
aspects of on-demand and reactive protocols.


Hmm.... I thought the idea of ND proxies was to avoid a complicated
L3 device. If we need something like a routing protocol, maybe
its time to pull out the proxy thing and replace it with a real
L3 device?


I did not say "L3 device", nor did I intend to imply such. While some of
the protocols I was referring to include extensions for passing around L3
prefix information, their primary function is to establish host routes based
on information learned from neighbors, and this can happen based on
either L3 addresses or L2 addresses as node IDs. In fact, the correct target
domain of application in this context would seem to be as a replacement
for the IEEE 802.1D spanning tree, so L2 addressing would seem to be
indicated.

Fred
[EMAIL PROTECTED]

--Jari


-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------




--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to