Re: [mpls-tp] poll on making draft-sprecher-mpls-tp-survive-fwk-01.txtaworking group document?

[Huub van Helvoort <[e-mail]>]

Hello, Liu,

You replied:

> xueqin and Huub:
>   1 IMO, make-b4-break means pre-planed path to protected working path. 
> but when the working path have not any fault, there isn't any traffic of 
> working path to be  transported through protected path, it means it 
> isn't necessary to duplicate in the source node.
> only the working path is wrong or fault, the traffic will be transported 
> through the protection path.

You removed too much text, the make-b4-break is applicable when
performing a manual switch MS or forced switch FS. Not for the case there
is a signal fail. For MS and FS both working and protection entity are
intact. Make-b4-break requires in case of 1:1 (and 1:N) protection that the
source sends traffic on both working and protection and THEN the sink
will switch (preferably after confirmation from the source). It is still
possible
that in this case PDUs are lost.
If merging is used at the sink side, duplication of PDUs is possible.

>   2 for 1:N protection,maybe 100%  is considered from the bandwidth of 
> every working path. IMO, even if the working path that need the most 
> bandwidth among N working path  is failed, the protection path also 
> ensure to provide the same bandwidth and QOS for the working traffic. It 
> may not mean all traffic of all failed working path must be restored 
> when more one working paths are failed.

This means that the requiremnt should be reworded: 100% of the first
failed path shall be protected (even though it is illogical to require that
100% of the N entities is protected by a single entity).

Xie xie, Huub.

-- 
================================================================
Always remember that you are unique...just like everyone else...