Minutes from DHC meeting in Berlin (IETF87) ============================================= The joint Sunset4/DHC session minutes (for Thursday 1620-1720 CSET) can be found with the Sunset4 minutes at http://tools.ietf.org/wg/sunset4/minutes. The DHC session minutes (for Thursday 0900-1130 CSET) will be posted after the session. Presentation materials - https://datatracker.ietf.org/meeting/87/materials.html#wg-dhc WG Status & Agenda Bashing - Tomek Mrugalski -------------------------------------------- Suzanne Woolf as minute-taker, any others? Reminder that wg chairs don't need to be doing all of the shepherding Status read-out: Failover-design needs last call review! Drop or pursue prefix-pool draft? nobody offers to do the work, will ratify on the mailing list Draft container-opt went to IESG in 2010; DISCUSS from them needs to be resolved, then Last Call Draft stateful-issues is on today's agenda Draft option-guidelines is on today's agenda Draft addr-registration: IETF86 decided that author would report back from v6ops whether this made sense; no response yet Draft v4configuration on today's agenda Draft dhcpv4-over-dhcp6 waiting Draft dhc-dns-pd related to draft in HOMENET, which is probably a better place to do it (Ted Lemon at the mic) Side-comment: can we get it done without worrying too much about where? Is it ready to publish? Maybe keep it out of the more complex DNS issues in HOMENET WGLC and decide from there Draft unknown-message is on today's agenda Draft topo-conf needs upload as WG draft (missed comment on last draft on this slide) Happy Birthday DHCPV6! It's 10 years old already. Suggestion that RFC 3315 invoke the new process (per the plenary) to move to IS (Ted Lemon) Suggestion that RFC 3315bis be undertaken (Ralph Droms) DHC Re-Charter and DHCP Directorate ----------------------------------- (Bernie presents) Charter: Proposed revision sent to the list June 25 Minor wordsmithing Scope discussion addr-registration draft added back in, per Suresh, he will send text other possible drafts; "send text" re adding work items Bernie notes the list is a snapshot, and new stuff can be added per AD or if it's in scope for charter in general DHC Directorate Ted as AD can do this Proposal sent to the list June 25th Wordsmithing (Ralph Droms, Suresh Krishnan) re: duration of WG and Directorate Purpose is to provide review and advise the ADs, in a transparent and timely way Appeal/challenge regarding these reviews is also fine and welcome, noting the IESG feels it doesn't get *enough* appeals. Suggestion for explanation to share that mitigates "secrecy" concern; Suresh will send text Joint Sunset4/DHC recap ----------------------- Recap problem statement (slides) Recap presentations; see slides for outcomes Ted reminds people there are serious issues here and to try the IETF v6-only network for clarification Most presentations will be repeated here this morning draft-ietf-dhc-option-guidelines - Tomek Mrugalski -------------------------------------------------- See slides for issues/changes recap for this version (Post-WGLC, -13) Bernie is working on the writeup, going to IESG shortly Base document for the DHC Directorate draft-ietf-dhc-dhcpv6-stateful-issues - Bernie Volz --------------------------------------------------- See slides for issues/changes for current version (-04) Major open issue: rebind 3315bis will have to deal with multiple bindings somehow there are other holes to be addressed request for discussion of draft editor's recommendations on the mailing list WGLC in September draft-ietf-dhc-dhcpv4-over-dhcpv6 - Qi Sun ------------------------------------------ See slides for overall summary-- new draft (-01) Discussion of issues raised triggering reconfiguration of v4 RFC 4361 support? already in there option 82 handling may need refinement/clarification dhcpv6 relay has to actually open dhcpv4 packets to map? seems not discussion to go to mailing list; at least some clarification of the scenarios needed draft-ietf-dhc-dhcpv6-unknown-msg - Qi Sun ------------------------------------------ See slides for overall summary-- new draft (-01) Discussion of clarifying potential interoperability issues Clarity re: when a message is suitable for forwarding is critical draft-ietf-dhc-v4configuration - Branimir Rajtar ------------------------------------------------ See slides for overall summary-- new draft (-01) Open issues More thoughtful review of existing softwire mechanisms before deciding if this is needed? As proposed, this is bound to softwire rather than DHCP generically (Ian Farrer) Some discussion of complexity of tunnels in underlying scenario? Specifics of use cases that do or don't assume softwire Adding requirement not to require or assume softwire This is an issue of documenting a previous consensus in the doc, not revisiting the decision (Ted as AD) Meta-argument about previous consensus. Decision was to not reopen the issue, WG made a decision and we plan to stick with it. WG has previously determined that new dhcpv6 functionality not depend on transition mechanisms that will go away when v4 does Dependency issue on softwire is a subset; the consensus is generic draft-farrer-dhc-shared-address-lease - Ian Farrer -------------------------------------------------- See slides for overall summary-- new draft, anyone interested? Softwires or DHC work? includes new DHCP options & changes client and server behavior Marcin agrees to review End of Session - The remaining presentations were not presented. draft-wing-dhc-dns-reconfigure - Prashanth Patil ------------------------------------------------ draft-jiang-dhc-sedhcpv6 - Shang Jiang -------------------------------------- draft-bhandari-dhc-class-based-prefix - Shwetha Bhandari -------------------------------------------------------- draft-mglt-dhc-public-authoritative-server-option - Daniel Migault ------------------------------------------------------------------ draft-xue-dhc-dynamic-gre - Li Xue ---------------------------------- draft-sarikaya-dhc-vxlan-multicast - Behcet Sarikaya ----------------------------------------------------