Skip to main content

Minutes IETF113: mboned
minutes-113-mboned-00

Meeting Minutes MBONE Deployment (mboned) WG
Date and time 2022-03-22 13:30
Title Minutes IETF113: mboned
State Active
Other versions plain text
Last updated 2022-03-30

minutes-113-mboned-00
IETF 113 (Vienna/hybrid)
MBONED Agenda
Tues, Mar 22, 2022
14:30-16:30 CEST
Tuesday Afternoon session II, Mezzanine Park Suite 2

Note-taker: Max Franke
Jabber/Chat Log: https://jabber.ietf.org/jabber/logs/mboned/2022-03-22.html
Video log: https://www.youtube.com/watch?v=ItCG-TN-TwQ

Notes taken in etherpad at https://notes.ietf.org/notes-ietf-113-mboned

MBONED 113 notes
Chair Updates
- more reviews for YANG models required
- Telemetry draft update soon (by 114), waiting on other WGLCs (IPPM)
- No implementations for telemetry yet
- WG adoption for Sandy's draft decided until friday

Hackathon:
- Jake got IPv6 to work with the AMT gateway docker container
- Running against his relays
- Successfully streamed music (v4 in v4; v6 in v6; v4 in v6; v6 in v4)
- FreeRtr gateway also succesfully listened to all these combinations
- AMT gateway interop works with freertr
- No changes to FFMPEG or VLC, used external gateway not the one built in VLC
- Didn't try ASM

Ingress router failover:
- Added section about failure detection from Jake's comments
- More planned future updates: signaling between ingress and egrees routers,
RFC9026, language improvements - Some of the technologies in the draft have
been deployed (Ping but no BIER)

MTTB:
Feedback since 112:
- 112 comments are negative
- Multicast security dispacted to Msec, no discussion
- W3C webtransport rejected multicast as a use case
- uninterested unless browsers express interest and premature (needs IETF work
first) - Lenny: Seemingly circular dependency: Browsers say not enough demand,
but there seems to be IETF activity and interest - Warren: No suggestion for
actions - Jake: Not necessarily lack of IETF interest, but just missing work
for webtransport in IETF before work at W3C can occur - Aiming production
deployment pre-browser support, not abandoning effort - Setback but not
unexpected Future plan: - Out of R&D and into production team at Akamai, has a
real business case - In talks with a few partners - Aiming to get traffic
running in 1-2 years - Started work on QUIC, similar to QUIC multipath - Will
be transparent to applications, they dont need to do anything special - Early
version of draft on github - "Many things this could go wrong" - Server push
would be nice, but browsers are currently removing it, should still be possible
through webtransport unidirectional streams - Lucas Pardue will co-author -
Tentative target: July to QUICWG - Code contributions by some people to
libmcrx, trying to get windows support - MNAT needs more reviews
Lenny(regarding the idea about on how going forward): "Sounds good to me"
Warren: "It is an idea" Jake: "Interest will rise once ISPs are doing it"

Sandy: "Will AMT still be used if multicast implemented in QUIC"
Jake: "AMT will still be used for inter-domain connectivity"
Jake: "Dont know other way on how to cover demand for peak events"
- NFL will be streamed on Amazon this year (Thurs Night Football), Serie A was
streamed last year (used some multicast)