Version 9 (modified by jouni.nospam@…, 8 years ago) (diff)



DMM had two meeting slots this IETF. The WG has completed its current charter and delivered all milestones. The WG is about to recharter any time soon, since there is interest to continue into the solution space in distributed mobility management. Considerable amount of meeting time was spent to discuss about the rechartering and _how_ to continue from here, specifically after we have rechartered. As usual we got a set of presentations of DMM solutions, an update of 3GPP progress on CSIPTO (which relates closely what DMM has been doing), BBF progress in RGs with combined multiple WAN link technologies (LTE being the other one) and about AERO.

The next step is completing the charter text and move ship that to the approval process. There is already a consensus among the WG members on the identified initial work areas. The WG also approved for the next steps on organizing the work, which will involve periodic interim meetings and possibly smaller interest groups (or design teams) to work on the document skeletons.


The 6TiSCH group is using bitbucket to store drafts, agendas, minutes and meeting materials: ​

In particular the report from the Toronto meeting at IETF 90 is can be found at ​

The wiki page for the plugfest can be found at


DHC WG met on Wednesday morning. The session was attended by 44 people and lasted the full 150 minutes allocated.

The chairs provided an update ince IETF 89. There were two RFCs published, RFC 7227 and RFC 7283, and one document is in the RFC editor queue. 5 internet-drafts were last called, with 4 passing and 1 failing. 2 of the passed documents have since been sent back to the WG by the AD and the other 2 are shortly due to go to the AD. 1 call for adoption was issued (draft-csf-dhc-dynamic-shared-v4allocation) and it was adopted.

Nine presentations were given during the session:

Tomek Mrugalski gave an update on the RFC-3315bis work status and also discussed several issues to gain input.

Bernie Volz gave an update on draft-ietf-dhc-dhcpv6-stateful-issues and also discussed the outstanding issues to gain input.

Dacheng Zhang updated on the group on draft-ietf-dhc-sedhcpv6 and discussed an open issue that was raised after WGLC.

Tomek Mrugalski updated the group on the status of draft-ietf-dhc-topo-conf and to confirm that the WG feels this is ready for last call.

Qi Sun presented draft-ietf-dhc-dynamic-shared-v4allocation.

Kim Kinnear discussed what has happened with draft-ietf-dhc-dhcpv6-failover-design after the AD sent the work back to the WG. The failover-design document is being revised and some of the material is moving to a new failover-protocol document.

Tomek Mrugalski asked whether the WG should work on a DHCP Privacy Considerations document. There was interest and a half dozen volunteered to contribute and co-author.

Li Xue presented draft-xue-dhc-dynamic-gre and there was a discussion as to where this work should occur.

Suresh Krishnan was asked by the chairs to update the group on the Multiple Provisioning Domains work being done in MIF. This was informational only as issues should be discussed in MIF.


The TRILL WG met in the first meeting slot Monday morning. Its three major efforts currently are OAM, active-active, and directory assist in approximate order of decreasing priority. After a review of document and milestone status, Sue Hares reminded people of the survey to gather information for the TRILL implementation report for which Sue is editor.

On TRILL OAM: The two main TRILL OAM drafts, draft-ietf-trill-oam-fm and draft-ietf-trill-loss-delay, are through IETF Last Call and being considered by the IESG. RFC 7319, that sets up the IANA registries for the IEEE 802.1 CFM code points used by trill-oam-fm, was issued last Friday. There was a presentation on YANG and a TRILL OAM FM YANG module as part of an overall OAM model that would then be augmented for TRILL or other efforts such as NVO3. There was considerable discussion of this concept and of the TRILL FM OAM YANG module including whether it should include performance or that should be a separate document. The chairs started a three-week call for WG adoption of trill-yang-oam.

The next topic was Active-Active with presentations on the two main active-active drafts: draft-hu-trill-pseudonode-nickname and draft-zhang-trill-aa-multi-attach. There was a comment that some hardware might have difficulty using a pseudonode nickname when ingressing some frames but not others. It was pointed out that both drafts have a common mechanism to avoid multiple delivery of multi-destination traffic to a CE and this could be factored out into a separate draft. Both of these documents were in call for WG adoption ending at this TRILL WG meeting. There had been good support on the mailing list and, without objection in the room, the chairs adopted them.

A presentation on TRILL Link Protocols and then one on the changes in draft-ietf-trill-over-ip from version -00 to version -01 were given. One comment was that direct use of TRILL over UDP is not supported by current hardware but that other possibilities, such as TRILL over Ethernet over VXLAN, would be supported by current hardware. There were questions on congestion control with a sense in the room that the current provisions in the draft are inadequate.

An update on Directory Assisted Edge was presented including the status and possible next steps on the four related drafts. Presentations were given on two drafts on improving Layer 3 gateway (gateway at the IP level between VLANs or the like) access in the TRILL campus: draft-hao-trill-irb and draft-hao-trill-anycast-gw.

Finally, there was a presentation on a proposed RFC 7180bis (TRILL Clarifications, Corrections, and Updates) listing proposed additions and deletions from the current RFC 7180. There were no objections to the suggested changes.