- From: Holland, Jake <jholland@akamai.com>
- Date: Wed, 2 Feb 2022 21:46:35 +0000
- To: Gavin Henry <ghenry@suretec.co.uk>
- CC: "public-multicast@w3.org" <public-multicast@w3.org>
No, that was the less-preferred of 2 alternatives some time ago. RFC 8777 is the one that went forward, and there's an implementation available at: https://github.com/GrumpyOldTroll/multicast-ingest-platform That can import my traffic, we're still working on standing up the same capability for Internet2 and GEANT, both for ingest and export. (I do put the records in my own local bind9 server running in my local setup of the multicast-ingest-platform/sample-network, so it works to ingest their traffic from my place except when they change something, but it would be better if those were in the real reverse ip tree properly. However, they do have some AMT relays running.) -Jake On 02-02, 1:32 PM, "Gavin Henry" <ghenry@suretec.co.uk> wrote: > Internet2 and GEANT both have some capability on these, plus I’ve got some traffic sources with AMT reachability, but more interconnections here (especially if there’s useful traffic) would be cool. https://datatracker.ietf.org/doc/html/draft-jholland-idr-mcast-source-nexthop-over-amt-00 right?
Received on Wednesday, 2 February 2022 21:47:23 UTC