IETF 100 (Singapore) DHC WG Agenda
This is a working page for developing the IETF-100 (Singapore) DHC WG Agenda & Status Update.
** DRAFT ** 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 & Bernie Volz
Secretary: <open - contact chairs if interested>
Presentations materials: https://datatracker.ietf.org/meeting/100/materials.html#wg-dhc
1. Administrativia (Agenda Bashing, WG Status, ...), Chairs - 10 minutes
2. Future of DHC WG - recharter?, Chairs - 15 minutes
3. DHCPv6 Yang Model, Ian Farrer - 15 minutes
draft-ietf-dhc-dhcpv6-yang
4. DHCP/DHCPv6 options for LWM2M bootstrapping, Srinivasa Rao Nallurim - 10 minutes
draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options
5. DHCPv6 options for MQTT client configuration, Srinivasa Rao Nallurim - 10 minutes
draft-nalluri-dhc-dhcpv6-mqtt-config-options
Note: Subject to change.
Session length: 60 minutes
Last Updated: November 2, 2017
- Title of Session: DHCP/DHCPv6 options for LWM2M bootstrapping
- Presenter: Srinivasa Rao Nalluri
- Related Drafts: draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options
- Time Required: 10 min
- Purpose of Session: To advance the draft
Note: There are IPR claims - see https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options.
The draft has been resurrected after long inactivity. -04 published on Oct. 28 is a substantial update (diff is 3,5k lines). The major outstanding item is a question about how best to represent new options. This received some feedback from Yang doctors. The question to the co-authors is whether they still have interest in the work. The question to the WG is whether the WG still has interest in this work; and if so how is willing to work on it (either in place of or in addition to one or more of the existing co-authors).
Topics to be reviewed:
- Discuss level of interest
- If interest:
-
- Discuss document authors (add or delete)
-
- Discuss open issues needing work
Added by Bernie Volz.
We are close to finishing much of the work on our charter.
Remaining items are to advance RFC 3315 Bis; which would likely occur 6 or more months after bis document is published. And, a few documents currently being worked on, such as the Yang model.
RFC 2418 (BCP 25) says in section 4. Working Group Termination:
"Working groups are typically chartered to accomplish a specific task or tasks. After the tasks are complete, the group will be disbanded. However, if a WG produces a Proposed or Draft Standard, the WG will frequently become dormant rather than disband (i.e., the WG will no longer conduct formal activities, but the mailing list will remain available to review the work as it moves to Draft Standard and Standard status.)"
A start at a rechartering draft is:
The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP
for automated allocation, configuration and management of IP addresses
and TCP/IP protocol stack parameters. DHCPv4 is currently a Draft
Standard and is documented in RFC 2131 and RFC 2132. DHCPv6 is currently
a Proposed Standard and is being updated and the WG plans to advance the
protocol to full standard.
The DHC WG is responsible for defining DHCP protocol extensions.
Definitions of new DHCP options that are delivered using standard
mechanisms with documented semantics are not considered a protocol
extension and thus are generally outside of scope for the DHC WG. Such
options should be defined within their respective WGs and reviewed by
DHCP experts in the Internet Area Directorate. However, if such options
require protocol extensions or new semantics, the protocol extension
work must be done in the DHC WG. Or, when no respective WG exists, the
DHC WG may take on the option definitions work with approval from the
responsible Area Director.
The DHC WG has the following main objectives:
1. Issue updated version of the DHCPv6 base specification, and after an
appropriate interval after publication as an RFC advance the to full
standard.
2. Develop documents that help explain operational considerations for
the wider community if and as needed.
3. Assist other WGs and independent submissions in defining options
(that follow RFC 7227 guidelines) and to assure DHCP operational
considerations are properly documented.
4. Additional topics and any option definition work may only be added
with approval from the responsible Area Director or by re-chartering.
- Title of Session: DHCPv6 options for MQTT client configuration
- Presenter: Srinivasa Rao Nalluri
- Related Drafts: draft-nalluri-dhc-dhcpv6-mqtt-config-options-00
- Time Required: 15 min
- Purpose of Session: To introduce the draft to the DHC WG
Note: See datatracker!
Published:
In RFC-Editor Queue:
Publication Requested:
Pending: