IETF 85 Atlanta
MBONED WG
Mon, Nov 5, 2012
9:00-11:30AM 
Salon B 
scribe: dino@cisco.com

Audio archive:
http://www.ietf.org/audio/ietf85/ietf85-salonb-20121105-0900-am1.mp3
Jabber log:
http://www.ietf.org/jabber/logs/mboned/2012-11-05.html

Status of WG Docs
-----------------
- AMT has taken a lot of time but mostly done
- Multrans work, 2 drafts adpoted:
  draft-ietf-multtrans-addr-acquistion-00
  draft-ietf-mmboned-v4v6-mcast-ps-00
  Overall, little to no activity for Multrans since Vancouver.
- draft-ietf-mboned-mcaddrdoc-04 is now RFC 6676.
- multicast-cdni, authors could not make WG due to Hurricane Sandy

Multrans
---------
Comment from Axel (from DT):
- DT needs 4-to-6-to-4, which means a tunneling solution can be used
versus a translation solution.

Jie (China Telecom):
- Need IPv4 at customer to IPv6 at the service provider.

Lenny: Should we keep translation services in WG charter?
- Toerless, restrict to the solutions that unicast has for transition.
So don't listen to multicast only requirements.
- Stig, don't have to work on them, but just have a need for them.
- Tom Taylor: consider the Map solution. Address+port solution.
- Ron: agree with Toerless, but ... look at uincast transition
mechanisms and see how they break multicast solutions.
- Dino: listen to providers that are deploying v6 cores and will be
doing unicast and multicast service at the same time.
- Toerless: agrees with Dino but look at all solutions and throw out
  what is not needed.
- Raise of hands vote: 75% says keep it.

Mrace Version 2: Hitoshi and WeeSan
-----------------------------------

- Reworded the draft per AD's request.
- Added example how mtrace2 works.
- Change authorship keeping Hitoshi as main author.
- mtrace2's client's location - queries can come from non-adjacent
clients.

Security concern:
- Stig: should default behavior to not have last-hop routers accept
query?
- Hitoshi: this was the behavior in last version of design, but change
  for this one.
- Stig: mtrace1 is liberal, but should be configurable.
- Gory: let people do what they want to do.
- Toerless: prefer last-hop to forward upstream when it doesn't know
where it comes in.
- Dino: make it plug-and-play, the queries don't create any state so it
  is as harmless as a ping.

- Added Extended Query to allow multiple paths for mtrace to take.
- New types can be extended and a transitive bit has been added.
- Similar draft draft-hout-dp-mtrace-00. May work together.
- Should this be WGLC? Take to list. Not enough reviewers of the draft.
  Sounds like no objection. But taking to the list.

Multicast in the Data Center Overview: Mike McBride and Helen Lui
-----------------------------------------------------------------

- Motivation was from the ARMD WG.
- Multicast vital in the data center. And others said wouldn't consider
  multicast at all in the data center.
- Draft gives no recommendations, just says where it stands in the data
center.
- Multicast apps: Windows Media Servers,  Publish and Subscribe,  Market
Data, IP Broker, VRRP,  Overlay, Compute System Monitoring (Ganglia),
Windows Server Cluster Node, Others?
- Dino: add an item for "extending subnets".
- Request the draft to be a WG document.
- 3 people read either first or second drafts.
- 5 yays, 0 nays to accept WG draft. Take to list for final vote.

AMT Multicast Production Implementation: Scott Brown (Octoshape)
----------------------------------------------------------------

- Streaming 2mbps to 2 million receivers. Hard to do with CDNs.
- Even more difficult outside of US.
- TV sized audiences are coming, high quality to 2-5mbps.
- IPTV deployments have provisioned for QOS Multicast. Trying to bring
  to multiple screens, now how to you bring to 3G/4G that is not
  provisioned like the traditional wired network.
- Multicast Design Goals:
  Provisioning and configuring each hop is a non-starter.
  Need an over-the-top solution to allow a simpler way.
  Don't require peering relationships. Too complicated.
  Needs to work over best-effort networks.
  Support adaptive bitrate technologies.
  Don't require telco/operator to install proprietary software in their
  network.
- Major League Gaming (MLG):
  Octoshape and AT&T worked together, March 2011 success event.
  April 2012 went production.
- AMT relays are public so anyone can use them. Events:
  CNN.live (US), NBA League Pass (US), Eurivision Song Contest (EMEA),
  Digturi Ieft Fooball (Turkey), TV Erocr Olympics (Brazil), IPC/ATOS
  Paraolympics (London).
- What is Octoshape .... (IPR on this so no notes)
- AT&T and Juniper AMT Relay used.
- Toerless: asks question, phone rings, he leaves room.  ;-)
- AMT Discovery Technique, uses reverse DNS to find sources and AMT
  Relay, uses internal mechanism to find multicast group.
- Lenny: did you have to write one implementation and ported multiple
  times?
  Answer is yes.
- Scott demoed a CCN app on Firefox, with a Octoshape plugin on MacOS.
  The AMT Relay is the AT&T Relay implementation.