Skip to main content

Minutes IETF103: babel
minutes-103-babel-00

Meeting Minutes Babel routing protocol (babel) WG
Date and time 2018-11-07 08:40
Title Minutes IETF103: babel
State Active
Other versions plain text
Last updated 2018-11-27

minutes-103-babel-00
BABEL Working Group Meeting Minutes
Minutes: with assistance from Barbara Stark
Jabber: David Schinazi

Bangkok Marriott Marquis Queen's Park, Bangkok, Thailand
         Wednesday, 7 November 2018
         15:40 - 17:10, Boromphimarn Room

Chairs:  Russ White (LinkedIn)
         Donald Eastlake (Huawei)

Area Director: Martin Vigoureux (Nokia)

[times given are those originally scheduled, not the amount of time
actually taken.]

   5 min.  Administrativia (scribes), Agenda Bashing, Chairs
  ==========================================================
Introductions. Minutes takers and Jabber scribes (see above).
Some delay due to technical problems.
Chairs reviewed agenda and asked if there were any requests for
  additions or deletions. There were none.

David Schinazi: HMAC draft is in great shape.
Donald: OK. Will start WGLC on that.

   5 min.  Status, Review of Milestones, Chairs
  =============================================
slides: Agenda and Status
https://datatracker.ietf.org/meeting/103/materials/slides-103-babel-agenda-and-status-01
Donald Eastlake walked through the slides.

Donald: Late on some of the milestones but not too bad.

  15 min.  Babel Information Model, Barbara Stark
  ===============================================
              draft-ietf-babel-information-model-04
slides: Babel Information Model
https://datatracker.ietf.org/meeting/103/materials/slides-103-babel-babel-information-model-00

- slide 3: moved to github and .md because easier to edit. New html format,
everybody is going to migrate to that new format so get used to it ;-) - slide
4: closed issues. - slide 6: open issue #7, link types. will bring the issues
to the list as well but please have a look and comment. Juliusz: I'd be in
favour of adding link types as needed, not in bulk. From an implementation
point of view, I see no reason to add other link types. I'm afraid that you're
trying to export in the information model
  something that the implementation doesn't need to know. Cautious
  about adding so many different link types unless the implementation
  actually needs to know them

  10 min.  Babel YANG Model, Mahesh Jethanandani
  ======================================
              draft-mahesh-babel-yang-model-00
slides:  Babel YANG Model
https://datatracker.ietf.org/meeting/103/materials/slides-103-babel-babel-yang-model-01

Donald: Any objection to adopting this YANG draft as a WG draft? [No
   objections but rather support.] OK, we'll adopted it after
   confirmation on the mailing list.

   5 min.  Changes to the Babel DTLS Draft, David Schinzi
  =================================================
              draft-ietf-babel-dtls-01
slides:  Babel over DTLS
https://datatracker.ietf.org/meeting/103/materials/slides-103-babel-babel-over-dtls-00

Donald: Any objection to starting a WG Last Call on the DTLS
  draft. [No objection] OK, we'll start one after the meeting.

  15 min.  Babel Protocol Status, Juliusz Chroboczek
  ===============================================
              draft-ietf-babel-rfc6126bis-06
slides:  Recent Changes to RFC 6126bis
https://datatracker.ietf.org/meeting/103/materials/slides-103-babel-recent-changes-to-rfc-6126bis-00

   5 min.  Wrap-Up, Chairs
  ========================
Chairs: Thanks everyone, see you in Prague and/or on the mailing
  list.