[MBONED] AMT implementation/pointers

Toerless Eckert <tte@cs.fau.de> Tue, 28 March 2017 16:55 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885FF129405 for <mboned@ietfa.amsl.com>; Tue, 28 Mar 2017 09:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZNL6DNMvSz0s for <mboned@ietfa.amsl.com>; Tue, 28 Mar 2017 09:55:13 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1C0A1279EB for <mboned@ietf.org>; Tue, 28 Mar 2017 09:55:12 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id A789858C56D; Tue, 28 Mar 2017 18:55:08 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 8E8C6B0BB46; Tue, 28 Mar 2017 18:55:08 +0200 (CEST)
Date: Tue, 28 Mar 2017 18:55:08 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: mboned@ietf.org
Cc: thkernen@cisco.com
Message-ID: <20170328165508.GD15006@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/dd_XxGVgGXppCtazvxmT5BR4_6E>
Subject: [MBONED] AMT implementation/pointers
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 16:55:21 -0000

Jake/*:

Great work on the AMT SW during the hackathon during the weekend and reporting on it.

Wanted to remind folks here on the list of one open source implementation that was
done in 2014 from Cisco as part of a workshop with the EBU in Geneva:

https://tech.ebu.ch/events/multicast14

There are a bunch of good presentations also documenting in more detail the
functionality of the AMT gateway implementation. During the event the EBU told us that
these presentations should be accessible to anybody by just registering for free,
but i have not been able to get access to those presentations. Seems more like the
presentations are only accessible to EBU member orgs only (or else i am doing something
wrong). If the presentations are not available publically, maybe Greg could contribute them
to the github for the gateway implementation...

The implementation is an AMT gateway implementation that is meant to be linked into
receiver applications, it runs without daemon, it supports IPv4 (not IPv6 yet,
should be easy to add), and it does also automatically supports joining to (S,G) both
natively and via AMT - if the traffic is received natively, then the AMT tunnel will
be terminated automatically.

There was also work by some other workshop participants to integrate the
gateway library into example apps.

https://github.com/cisco/SSMAMTtools

What this achieves is the key automatic optimization possible with AMT:

        Relay -------------------------------------> Rcvr App

More folks join:
        Relay -------------------------------------> Rcvr1 App
        Relay -------------------------------------> Rcvr2 App
        Relay -------------------------------------> Rcvr3 App

Now your sites WAN link runs over, not enough bandwidth, so you install into your
site (eg: your home) a router that is garteway and relay:

                                     WAN-link
        Relay ----------------------------GW/Relay---------> Rcvr1 App
                                                  ---------> Rcvr2 App
                                                  ---------> Rcvr3 App
                                                  ---------> Rcvr4 App

And of course, if you dare to do, you could also enable native multicast in your
site and of course that should then also work. 

Of course, this concept requires a site router that supports GW/Relay,
so for homes it would be great therefore to get GW running in the open
source OpenWRT implementation.

Cheers
    Toerless