1 / 9

draft-nadeau-pwe3-vccv-00.txt IETF #56 San Francisco, CA USA

Thomas D. Nadeau tnadeau@cisco.com Monique Morrow Mmorrow@cisco.com George Swallow Swallow@cisco.com ftp://ftp-eng.cisco.com/tnadeau/oam/draft-nadeau-pwe3-vccv-00.txt. draft-nadeau-pwe3-vccv-00.txt IETF #56 San Francisco, CA USA. Based on MPLS OAM and Customer Requirements.

badu
Download Presentation

draft-nadeau-pwe3-vccv-00.txt IETF #56 San Francisco, CA USA

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. Thomas D. Nadeautnadeau@cisco.com Monique Morrow Mmorrow@cisco.com George Swallow Swallow@cisco.comftp://ftp-eng.cisco.com/tnadeau/oam/draft-nadeau-pwe3-vccv-00.txt draft-nadeau-pwe3-vccv-00.txtIETF #56 San Francisco, CA USA

  2. Based on MPLS OAM and Customer Requirements • Driven by a need to provide a common means of testing PWEs using an in-band diagnostic mechanism. • ftp://ftp-eng.cisco.com/tnadeau/oam/draft-nadeau-mpls-oam-requirements-00.txt • Soon to be draft-ietf-mpls-oam-requirements-00.txt

  3. Motivation • One transport tunnel can serve many pseudo-wires and we can verify that path with existing tools… • (e.g.: MPLS ping is sufficient to monitor the PSN tunnel for PE-PE connectivity, but not VCs inside of tunnel.) • But…we cannot verify the PWs themselves using existing tools.

  4. VCCV Key Points • Provides extensible foundation for PW OAM CV/trace functions. • Will work with supported transport tunnels • MPLS and L2TPv3 (soon) • Different CV types to support different PWs when appropriate • LSP Ping, IP Ping, VPLS (future)

  5. VCCV Key Points (2) • Modify PWE Encapsulation Header • Some reserved bit for OAM indication. • Current bit in draft is already assigned; need to choose a new one. • Capability Signaled During VC setup as a bit mask of allowable VCCV types. • Carry multiple TLVs as payload to allow for different types of OAM operations. • Support MPLS and L2TPv3 transports • Support p2p and VPLS applications • Straight-forward to implement. • Reference • ftp://ftp-eng.cisco.com/tnadeau/oam/draft-nadeau-pwe3-vccv-00.txt

  6. NMS/mgr Triggers LSP ping trace when failure detected VCCV Packet Is lost Example of OperationCV/Trace Using VCCV and LSP Ping NMS/mgr Triggers VCCV Attachment VC Attachment VC

  7. Open Issues • As currently defined VCCV parameter does NOT need to be identical in both directions of a circuit, so no cases where the signaling MUST be rejected • In order to support certain functions in future one might want to reject a setup (e.g. the far end did not indicate Ping, but I'm configured to do CV with Ping). • The description of signaling is incorrect.  • Needs to be single sided (downstream unsolicited). • Need to add VCCV type for L2TPv3 • Current bit in draft is already assigned; need to choose a new one

  8. Next Steps • Refinements • Support L2TPv3 transport. • Editorial enhancements. • Accept as a PWE3 WG document.

  9. Thank You

More Related