1 / 6

Status and Updates TRILL OAM

Status and Updates TRILL OAM. March 2014 89 th IETF London. Made a formal presentation to IEEE 802.1 Interim committee meeting requesting formal allocation of block of CFM opcode code points and block of TLV types for the purpose of IETF OAM.

yamal
Télécharger la présentation

Status and Updates TRILL OAM

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. Status and Updates TRILL OAM March 2014 89th IETF London

  2. Made a formal presentation to IEEE 802.1 Interim committee meeting requesting formal allocation of block of CFM opcode code points and block of TLV types for the purpose of IETF OAM. • IEEE 802.1 committee is conducting a formal ballot on the above request Updates since last IETF

  3. Published RFC 6905: “Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)” • In RFC Editor’s queue: • “TRILL OAM Framework”, draft-ietf-trill-oam-framework-04 Updates since last IETF (condt..)

  4. Updates since last IETF (condt..) • Published -02 version of both Fault management and Loss and Delay drafts • Ready for WG Last Call (waiting for IEEE decision on Op-codes and TLV): • “TRILL Fault Management”, draft-ietf-trill-oam-fm-02 • “Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)”, draft-ietf-trill-loss-delay-02 • Work in Progress: “TRILL OAM MIB”, draft-ietf-trill-oam-mib-00

  5. + MEP addressed by RB nickname + They are placed at the TRILL OAM Layer + There is no Layer Violation + CFM framework is a generic mechanism and not tied to a Layer Recap of Placement of TRILL OAM

  6. Q&A

More Related