Changes between Version 3 and Version 4 of IETF90

25/07/14 04:45:36 (8 years ago)

add TRILL report


  • IETF90

    v3 v4  
    3939Suresh Krishnan was asked by the chairs to update the group on the Multiple Provisioning Domains
    4040work being done in MIF. This was informational only as issues should be discussed in MIF.
     42== TRILL ==
     44The 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.
     46On 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.
     48The 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.
     50A 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.
     52An 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.
     54Finally, 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.