Re: [mpls] working group last call on draft-ietf-mpls-tp-li-lb-01.txt

[Sami Boutros <[e-mail]>]

Agreed Yaacov, during the period of loopback the 
cc-cv function can't be performed, and yes the 
main benefit is of loopback is to measure 
loss/delay on a segment of a path as you stated.

Thanks,

Sami
At 10:36 PM 5/11/2011, Weingarten, Yaacov (NSN - IL/Hod HaSharon) wrote:
>Sami, hi
>
>My understanding is that the question that was 
>asked is how do you use the cc-cv function to 
>check for mis-connectivity if it is being looped-back.
>
>Truth be told that during the period of loopback 
>you apparently cannot check the e2e path for 
>mis-connectivity, and the operator needs to take 
>this into consideration.  But since the path is 
>not transferring data e2e (it is looping 
>everything back) it is by definition not connected e2e.
>
>What is true is what Sami states this 
>functionality should be used to setup a 
>loss/delay measurement on a segment of a path, 
>and it should be used only for limited periods.
>
>Just my 2cents,
>yaacov
>
>From: [e-mail] 
>[mailto:[e-mail]] On Behalf Of ext Sami Boutros
>Sent: Thursday, May 12, 2011 8:03 AM
>To: [e-mail]; Loa Andersson
>Cc: Ross Callon; [e-mail]; MPLS-TP ad hoc 
>team; [e-mail]
>Subject: Re: [mpls] working group last call on draft-ietf-mpls-tp-li-lb-01.txt
>
>To check for mis-connectivity/mis-configuration, 
>you need a cc-cv function not a loopback function.
>
>The loopback function can be used for loss/delay 
>measurements, and this will be addressed in the delay/loss draft.
>
>Thanks,
>
>Sami
>At 07:11 PM 5/10/2011, [e-mail] wrote:
>
>
>hi, all
>for this draft, I have a question for Loopback function.
>in last ietf meeting, IMO, the author sami said this
>Loopback function is to loopback anything. for MEP point of
>a LSP, if it is set to Loopback state, it will loopback all received
>packets including any OAM packet. if so, how to detect mis-connectivity or
>mis-configuration for the LSP?
>in addtion, if it happen mis-connectivity, maybe 
>other LSP packet be transported to
>the MEP , and the mep point will still Loopback 
>the wrong packet to peer mep point,
>can it affect<app:ds:performance> performance 
><app:ds:statistics>statistics or measurement on the peer mep point?
>
>B.R.
>liu
>
>
>
>
>
>
>Loa Andersson <[e-mail]>
>·¢¼þÈË:  [e-mail]
>
>2011-05-10 23:43
>ÊÕ¼þÈË
>"[e-mail]" <[e-mail]>
>³­ËÍ
>Ross Callon <[e-mail]>, MPLS-TP ad 
>hoc team <[e-mail]>, [e-mail]
>Ö÷Ìâ
>[mpls] working group last call on draft-ietf-mpls-tp-li-lb-01.txt
>
>
>
>
>Working Group,
>
>this is to start a two week working group last call on
>
>draft-ietf-mpls-tp-li-lb-01.txt
>
>Please send your comments to the [e-mail] mailing list.
>
>This working group last call ends on May 25th.
>
>/Loa
>
>for the mpls wg co-chairs
>
>--
>
>
>Loa Andersson                         email: [e-mail]
>Sr Strategy and Standards Manager            [e-mail]
>Ericsson Inc                          phone: [phone]
>                                              [phone]
>_______________________________________________
>mpls mailing list
>[e-mail]
><https://www.ietf.org/mailman/listinfo/mpls>https://www.ietf.org/mailman/listinfo/mpls
>
>
>
>
>
>
>
>--------------------------------------------------------
>
>ZTE Information Security Notice: The information contained in this mail
>
>is solely property of the sender's organization. This mail communication
>
>is confidential. Recipients named above are obligated to maintain secrecy
>
>and are not permitted to disclose the contents of this communication to
>
>others.
>
>This email and any files transmitted with it are confidential and
>
>intended solely for the use of the individual or entity to whom they are
>
>addressed. If you have received this email in error please notify the
>
>originator of the message. Any views expressed in this message are those
>
>of the individual sender.
>
>This message has been scanned for viruses and Spam by ZTE Anti-Spam
>
>system.