Subject: [BEHAVE] Comments on draft-venaas-behave-v4v6mc-framework-00.txt

From: Dave Thaler <[email-masked]>
Date: Tue, 21 Jul 2009 23:00:34 +0000

Attached is a marked up copy with my full comments.

Some high level points/questions:

1)      Is there anything special you could do with certain types of IPv6 addresses such as Unicast-Prefix-Based Multicast addresses (RFC 3306), Embedded-RP addresses, or link-scoped RFC 4489, to allow a simple stateless translation for scenarios that would otherwise be hard?

2)      Make sure you consider the case of multiple parallel translators (especially if they're stateless ones).  For example, switching to SPT may go through a different translator in this case.

3)      Having logic be application-independent whenever possible is a good thing.  You finally mention this at the end of 3.2, but until then the draft seems to assume application changes.

4)      Don't forget the cases where there's no middlebox, such as an IPv4-only app on a dual-stack node wanting to join a group sourced on the same link.  These are generally scenarios for in-host translation.

-Dave