1 / 6

MPLS TP OAM Framework draft-ietf-mpls-tp-oam-framework-05

MPLS TP OAM Framework draft-ietf-mpls-tp-oam-framework-05. Editors Dave Allan Italo Busi Ben Niven-Jenkins. Changes Since Last Version. Current version Alignment with MPLS-TP-Framework Alignment with agreements out of Hiroshima & conference calls ITU-T early review comments addressed.

nam
Download Presentation

MPLS TP OAM Framework draft-ietf-mpls-tp-oam-framework-05

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. MPLS TP OAM Frameworkdraft-ietf-mpls-tp-oam-framework-05 Editors Dave Allan Italo Busi Ben Niven-Jenkins

  2. Changes Since Last Version • Current version • Alignment with MPLS-TP-Framework • Alignment with agreements out of Hiroshima & conference calls • ITU-T early review comments addressed

  3. Changes Since Last Version/2 Key issues resolved • Relationship between MEs and the various types of transport entities. • Genericizing the document for PSTs vs. TCM • TCM is simply a degenerate case • CV uses MEG ID, not ME ID • Clean up of various artifacts of this… • PST/TCM for PWs clarified • Relationship and capabilities of MIPs vs. ‘intermediate nodes’ clarified • MIPs only speak when spoken to…. • Text around ‘out of band’ return paths added

  4. Changes Since Last Version/3 • Dataplane loopback, lock report, lock indicate descriptions added • Known implications of p2mp documented • Layer/sub-layer aligned with framework draft • MPLS-TP is a “layer” network • Some clarification around ordered aggregates and Loss Measurement (LM) added • Meaningful measurement requires the obvious, it is just not actually documented anywhere else… • MEP/MIP location aligned with framework draft • TTL is the MIP addressing scheme in the framework draft… • Both per-node MIP and per-interface MIPs are possible • Text on measurement and control implications of proactive and on demand monitoring added

  5. Current Status • In last call & liaised to ITU-T… • A few comments received to date, no obvious show stoppers • Alignment with static pw status • Rephrasing of “minimum loss probability PHB” for some OAM flows

  6. Next Steps • LC Comment resolution • Editing to address comments received privately and on the TP list • Any comments liaised from ITU-T • Respin for a 2nd Last Call early April • If no “more substantial” comments received than we have gotten to date, declare victory

More Related