Re: [multrans] Issues charts for presentation at the BoF

hi Tom,

Some comments,

Page 8:
Issue: translation of a given address tends to happen
at multiple nodes, and at different stages within the
same node.
● Need the same mapping or its inverse, as applicable, to be
used each time a given address is translated. Implies inter-
nodal coordination in some form.

Jacni>: The coordination is probably required in the stateful
translation. While in some stateless cases, maybe not.

Page 9:
Jacni>: I do agree with that the original design of DS-Lite or 6rd
(unicast-based tunnel)
should not be used for multicast delivery, but that can NOT lead to the
conclusion stated in the second bullet ("Possible to use encapsulation in
the form of a softwire mesh between multicast routers.").
Mesh is a different use case, the mesh approaches do not apply to DS-Lite or
6rd cases either.

Page 10:
Jacni>: The discussions about dual-stack network are a little confusing. The
network may be dual-stack enabled from the device connected to headends, to
the IGMP/MLD Querier.
Or the network may be partially dual-stack enabled. The latter one is
"native transport + translation", and can be simplified as a translation
case.
Please refer to the -01 of the PS draft, maybe some text in the Section 3.3
can be reused:
http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-01#page-8

Cheers,
Jacni

On Tue, Jun 28, 2011 at 4:13 AM, Tom Taylor <tom111.taylor@bell.net> wrote:

> Attached are the charts I propose should be presented on the "issues" topic
> at the MULTRANS BoF. Comments in advance are welcome.
>
> Tom Taylor
>
> _______________________________________________
> multrans mailing list
> multrans@ietf.org
> https://www.ietf.org/mailman/listinfo/multrans
>
>