 1 0) is received by the source from the sink, the bandwidth of the new member is made available to the VCG. Removing a member is also initiated by the NMS and achieved by sending a CTRL = IDLE for the member(s) that are to be removed. The sequence number of the remain- ing members is updated accordingly, and when an RS-Ack is received from the sink, the payload size of the VCG is decreased and distributed over the remaining active members. If required, the NMS can then remove each member's path through the network. In addition to the planned increase or decrease of the payload capacity of a VCG, LCAS offers the ability to automatically decrease the provisioned capacity in the event of network failure. Routing members of a VCG across different paths in the network is a resilience strategy known as diversification. An example of splitting a VCG into two diverse paths is shown in Figure 11.16. Y VC-ns on Working Path (X-Y) VC-ns on Protection Path Working Path Protection SDH Transport Network Fig. 11.16 LCAS used for resilience. End-to-End Traffic: VC-n-Xv Generic Framing Procedure In a network failure scenario that affects one or more members of a VCG (but not all members), the contents of the VCG will be in error for a short duration of time because the reassembled payload at the sink will be missing the data being transported by the affected members. LCAS coordination requires the removal of these members from the VCG, and this is achieved by changing the member status to failure mode (MST = FAIL, CTRL = DNU). The VCG payload is therefore reduced and uses only the remaining members, sending the CTRL code NORM or EOS. A message reporting the failed member is sent to the NMS. Because the sequence numbering is not changed, the RS-Ack bit is not toggled. The NMS could reprovision replacement members via an alternative path in the network and reestab- lish the full VCG payload in a hitless manner as described before. Clearly, LCAS allows a VCG to continue to carry reduced amounts of traffic even when constituent memb