1 / 8

draft-koike-mpls-tp-temporal-hitless-psm-02

draft-koike-mpls-tp-temporal-hitless-psm-02. Mar 31st, 2011 Prague Yoshinori Koike / NTT Alessandro D'Alessandro/ Telecom Italia. Updates. Mr. Alessandro D‘Alessandro of Telecom Italia joined as a co-author. Reflected comments from mailing-list discussion

duff
Télécharger la présentation

draft-koike-mpls-tp-temporal-hitless-psm-02

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. draft-koike-mpls-tp-temporal-hitless-psm-02 Mar 31st, 2011 Prague Yoshinori Koike / NTT Alessandro D'Alessandro/ Telecom Italia

  2. Updates • Mr. Alessandro D‘Alessandro of Telecom Italiajoined as a co-author. • Reflected comments from mailing-list discussion • Aligned the network objectives with the descriptions in 3.8 of mpls-tp-oam-framework • Added an example of Sub-path Maintenance Element (SPME) to clarify the necessity of the enhanced in-service segment monitoring • Added requirements for enhanced in-service segment monitoring

  3. (1) On-demand hitless segment monitoring at least in single layer • On-demand and in-service “single-layer” hitless segment monitoring is mandatory. It provides a method for a defect localization • On-demand and in-service “multi-layer” hitless segment monitoring is optional. Multi-layer measurements in parallel achieve a strict and efficient defect localization by using the results of the same time flame. A B C D E Transport path (MEP-MEP) Segment Layer 1 Segment Layer 2 Multi-layer monitoring Segment Layer 3

  4. (2) On-demand segment monitoring independent from proactive monitoring of ME • “On-demand and in-service” segment monitoring should be supported without disabling the pro-active monitoring of an original transport path. • Note: Bandwidth design for OAM packets used by the on-demand and in-service segment monitoring is operators’ design issue. A B C D E Transport Path (MEP-MEP) Proactive monitoring of original transport path Segment Layer 1 On-demand in-service segment monitoring Must be independent

  5. (3) Diagnostic procedures for defect localization • On-demand and in-service segment monitoring should be supported in an arbitrary segment of a transport path. A B C D E Transport Path (MEP-MEP) Flexible segment monitoring : proposed Segment monitoring On-demand segment monitoring in any segment Constrained segment monitoring :not reasnable Constraining one end point of on-demand segment monitoring is not desirable because it limits deployment scenarios

  6. Summary of additional requirements • On-demand and in-service “single-layer” segment monitoring is proposed. Multi-layer segment monitoring is optional. • “On-demand and in-service” single layer segment should be done independently from pro-active monitoring of an original ME of a transport path. • On-demand and in-service segment monitoring should be able to be set in an arbitrary segment of a transport path.

  7. Next Steps • Solicit feedbacks on the draft, particularly from operators • Update the drafts based on the comments • Reflect comments from Deutsche Telekom • Mr. Manuel Paul joins as a co-editor • Request to make this a WG draft

  8. Thank you

More Related