Skip to main content

Minutes IETF100: dhc
minutes-100-dhc-01

The information below is for an old version of the document.
Meeting Minutes Dynamic Host Configuration (dhc) WG Snapshot
Date and time 2017-11-16 10:10
Title Minutes IETF100: dhc
State Active
Other versions plain text
Last updated 2017-12-05

minutes-100-dhc-01
DHC WG Agenda for IETF-100 (Singapore)

Date: Thursday, November 16, 2017, 18:10-19:10 (UT + 8), Afternoon session III
Location: Collyer
Chairs: Tomek Mrugalski (TM) & Bernie Volz (BV)
Secretary: none (open)
Presentations materials: https://datatracker.ietf.org/meeting/100/materials.html#wg-dhc

 1. Administrativia (Agenda Bashing, WG Status, ...), Chairs

  - BV and TM presented the Adminstrativia slides
  - Eliot Lear (EL) Please move item 2 to the bottom
  - BV - I'd prefer to leave it
  - TM - These aren't the only items


 2. Future of DHC WG - recharter?, Chairs

  - TM presented the Future of the slides
  - A request was made to move item 1 to the end (less important)

  - Chairs will update charter text and send it to the WG for review before submitting
    it


 3. DHCPv6 Yang Model, Ian Farrer (IF)
    draft-ietf-dhc-dhcpv6-yang

  - EL volunteered. Happy to contribute and review. EL added: would like to get
    involved because of the long term implications, how to deploy configuration
    after the device is capable of sending packets, how to protect the information
    being deployed.
  - IF - we could do 7227 equivalent for yang extensions
  - IF - asked for volunteers to review and potentially co-auther document
  - volunteers: Tim Winter, Bernie Volz, Eliot Lear, Robert Nagy, Tomek Mgrugalski


 4. DHCP/DHCPv6 options for LWM2M bootstrapping, Srinivasa Rao Nallurim (SN)
    draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options

  - SN presented the slides


 5. DHCPv6 options for MQTT client configuration, Srinivasa Rao Nallurim (SN)
    draft-nalluri-dhc-dhcpv6-mqtt-config-options

  - SN presented the slides

  - SN is looking for more WG feedback on both documents; BV provided some comments
    to the mailing list earlier in the week
  - There was a discussion about how many of these IoT related options there might be
    and is the the best way to go for these options? If there are other standards
    organizations, perhaps they should use the Vendor-Identifying options (DHCPv6
    options 16 & 17, DHCPv4 RFC 3925) that these organizations could use - similar to
    the CableLabs DOCSIS options (mostly for V6). That would be a far better way to
    go and the standards organization then as control of the options and can publish
    themselves.


The session ended at 19:10.

Minutes prepared by Bernie Volz from etherpad notes by Tomek Mrugalski (and others).

Last updated: December 5, 2017