1 / 8

RFC 7180bis: Further TRILL Clarifications, Corrections, and Updates

RFC 7180bis: Further TRILL Clarifications, Corrections, and Updates. Donald Eastlake Huawei Technologies <d3e3e3@gmail.com>. RFC 7180 bis.

erasto
Télécharger la présentation

RFC 7180bis: Further TRILL Clarifications, Corrections, and Updates

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RFC 7180bis: Further TRILL Clarifications, Corrections, and Updates Donald Eastlake Huawei Technologies <d3e3e3@gmail.com> rfc7180bis

  2. RFC 7180 bis • RFC 7180TRILL: Clarifications, Corrections, and Updates, covers a variety of topics; however, because of RFC publishing delays due to normative dependencies, it was already a bit out of date when it was published. • At some point we may wish to revise the base protocol specification, RFC 6325, but for now, I believe an rfc7180bis document is the way to go. rfc7180bis

  3. RFC 7180 bis • The remainder of this presentation lists • Topics I think should be added • Topics I think should be deleted • Topics I think should retained rfc7180bis

  4. RFC 7180 bis • Material I think should be added: • Add support for E-L1FS extended level 1 LSP/CSNP/PSNPs. Increases number of fragments and maximum TLV size from 2**8 to 2**16. See draft-ietf-isis-fs-lsp. • Each future specific use would be required to address backwards compatibility. • Advice to silently ignore unknown TRILL IS-IS PDUs. • The universe of IS-IS PDUs used to be very stable but TRILL added MTU-probe and MTU-ack while draft-ietf-isis-fs-lsp is adding Flooding Scope versions of LSP, CSNP, and PSNP. rfc7180bis

  5. RFC 7180 bis • More material I think should be added: • Optional alternative Reverse Path Forwarding Check as discussed on the mailing list. See http://www.ietf.org/mail-archive/web/trill/current/msg01852.htmland subsequent messages. • Deprecate extending the TRILL Header beyond the one word extension in RFC 7179. Make all but the lowest bit of the Op-Length field in the TRILL Header Reserved. rfc7180bis

  6. RFC 7180 bis • More material I think should be added: • Generally provide addition details where questions have arisen. For example, there was a discussion on the mailing list about the Appointed Forwarder Status Lost Counter, and whether you need to pay attention to it, that would be more accessible if put in an RFC. rfc7180bis

  7. RFC 7180 bis • Material to be removed: • Changes to Adjacency RFC 6327. These were rolled into Adjacency RFC 7177 which obsoleted RFC 6327 and so can be removed from an rfc7180bis. • Changes to Appointed Forwarder RFC 6439. This material should be moved into an rfc6439bis or all that material should be rolled into an rfc6235bis effort. rfc7180bis

  8. RFC 7180 bis • Other material from RFC 7180 would be retained in rfc7180bis with any minor updates that are warranted. rfc7180bis

More Related