1 / 5

MPLS Performance Measurement UDP Return Path draft-bryant-mpls-oam-udp- return -02

MPLS Performance Measurement UDP Return Path draft-bryant-mpls-oam-udp- return -02. { stbryant , msiva , sabsoni }@ cisco.com. WG Adoption Poll. There were two significant types of comments This incremental improvement to RFC6378 vs new OAM configuration protocol Error handling logic.

davina
Download Presentation

MPLS Performance Measurement UDP Return Path draft-bryant-mpls-oam-udp- return -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. MPLS Performance Measurement UDP Return Pathdraft-bryant-mpls-oam-udp-return-02 {stbryant, msiva, sabsoni}@cisco.com

  2. WG Adoption Poll • There were two significant types of comments • This incremental improvement to RFC6378 vs new OAM configuration protocol • Error handling logic

  3. Incremental Improvement • Proposal is simple and results in a self contained protocol. • It fixes an oversight in the original RFC6378 design • There is no defined and deployed OAM configuration protocol. If an OAM configuration protocol is defined it will complement this approach.

  4. Error Handling • Always the Cinderella, compared to normal operation  • Will take a further look at this after IETF and encourage others to do so as well. • Suggest that we will only fully understand whatthis when we have field experience.

  5. Completing the Work • It would be nice to pick up the pace to web speed on this work. • Propose: • Adopt as WG draft and publish as is • Fix the outstanding comment and publish -01 • Chairs request early allocation of the Return UDP Port TLV codepoint • Get some deployment experience on the error handling • Request RFC

More Related