All things related to multicast

[Scott Brown <>]

Title: FW: AMT questions

This is correct, Octoshape has client side code that is deployed on the end user device be that a PC, set top, phone or tablet. The Octoshape client also has implemented an AMT Gateway, that manages the connection to the AMT Relay which would be implemented in a server or as in the diagram an AMT enabled router. 

We have demonstrable implementations for Android, IOS, Linux, PC and OSX.

Best,
Scott

On 3/10/11 7:02 PM, "Zenon Mousmoulas" <> wrote:

> Actually, if you look at the diagram, the caption above the little box in "LAST MILE #1" reads "AMT ENABLED ROUTER" and its' uplink is also marked with "AMT TUNNEL". This is how I reached the conclusion that the CPE (rather than the "customer computer") runs the AMT gateway in the depicted topology, and also why I reused the specific wording in that diagram. Other than that, I think the difference between the AMT gateway and relay is clear.
>
> Apologies for any confusion this may have caused.
>
> -----?????? ??????-----
> ?π?: Curtis, Bruce []
> ?π??????: ??? 10/3/2011 8:43 ??
> ????: wg-multicast
> ????.: Zenon Mousmoulas
> ????: Re: AMT questions
>
>
> On Mar 9, 2011, at 3:25 AM, Zenon Mousmoulas wrote:
>
> > Hi Richard,
> >
> > thanks for relaying this information. In the tech note mentioned below, the last figure shows that Octoshape relies on AMT-enabled routers, while the following text implies that Octoshape client itself performs the AMT gateway function:
>
>   The AMT-enabled router in the diagram is on the network that doesn't have multicast enabled on the last mile (to the customer computer).  So AMT on the customer computer talks to an AMT relay (which in the diagram is the router providing the AMT relay function) and the router talks native multicast to the world.
>
> http://www.juniper.net/techpubs/en_US/junos10.3/topics/concept/amt-operation.html

------ End of Forwarded Message