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– 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)