1 / 2

Multi-Hop Pseudo-Wire

Multi-Hop Pseudo-Wire. Requirement Team Outcome. Met this morning Discussion concerning where the document is going as no version submitted WG to help deliver service deployment scenarios. Intention to have a draft version by end November provide a concise definition of MH-PW

shoshana-gallagher
Download Presentation

Multi-Hop Pseudo-Wire

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. Multi-Hop Pseudo-Wire

  2. Requirement Team Outcome • Met this morning • Discussion concerning where the document is going as no version submitted • WG to help deliver service deployment scenarios. • Intention to have a draft version by end November • provide a concise definition of MH-PW • Start writing down the requirements in terms of capabilities (QoS, recovery, etc.), operations (manual, automated, etc.) and in scope/out of scope items. • Outcome of this work is to determine scope of the protocol work (next step, if any)

More Related