Conrad Seould Hotel, Seoul, Korea. Friday, 18 November, 2016. 11:50-13:20 Park Ballroom 1-2 Chairs: Russ White (LinkedIn) Donald Eastlake (Huawei) Note taker: Barbara Stark 6 min. Administrativia (scribes), Agenda Bashing, Chairs ========================================================= https://www.ietf.org/proceedings/97/slides/slides-97-babel-status-review-of-milestones-03.pdf 6 min. Status, Review of Milestones, Chairs David Schinazi: I have implemented Babel per current RFC 6126. It was very easy. Was happy with the specification and with the performance of the implementation. 20 min. Suggested clarification and updates to the Babel TLV processing, ========================================================================= Denis Ovsienko (Custodian Data Centres) https://www.ietf.org/proceedings/97/slides/slides-97-babel-suggested-clarification-and-updates-to-the-babel-tlv-processing-00.pdf Denis presented remotely (via MeetEcho). Juliusz Chroboczek: Slide 7. This used to be part of the main doc, but Joel Halpern convince to put in separate doc. And think Joel was right. Believe strongly it needs to be informative, and not moved (first bullet). Made point on another bullet on the slide. Slide 18. Does not belong in the base spec. No problem having additional requirements in the security extension. Denis: Slide 7, first bullet. Key word was "some". Take discussion to list. John Dowdell: Seem to be having same issues as in MANET. Feel free to borrow from there anything you find useful. Denis: Will try to steal more. John: Yes try to work with people because we went through much pain. David S.: Expresses what option he likes from slide 19. Slide 7 points need to be discussed more on the list. There are some problems with what is proposed on Slide 7. 15 min. BIER in Babel, Sandy Zhang (ZTE) ========================================= https://www.ietf.org/proceedings/97/slides/slides-97-babel-bier-in-babel-01.pdf Sandy presented. Juliusz: That's cool. Happy to see that. Minor concerns. Technical concern is that there are elements that seem much like OSPF/IS-IS. Babel does not have transitional bit. This might be addressed/encoded in various ways. Need to discuss on list. Discuss sub-TLVs too, on the list. Non-technical issue is that elements of draft are hard to read. Final question is whether you have a prototype (runing code). Sandy: not yet, but willing to work on prototype. Juliusz: Good we can discuss on list. Alia Atlas: As AD: Some thoughts on how to do this and what scope is if there is interest. We need to understand if there are routers implementing Babel that could/would/should also do BIER. Since Babel is of interest to HOMENET WG, does HOMENET have a multicast architecture. Is there interest in using BIER to solve multicast architecture in HOMENET? Needs to be thought and discussion. AD hat off: Yes it's cool but we need to see if there is interest. AD hat on again: We do not seem to have multual understanding and agreement how to do extension. Not clear where draft would land. But cannot answer this until we answer Juliusz' questions (technical and prototype). 6 min. Wrap-Up, Chairs ======================= Barbara Stark: Will pursue information model for March.