Re: [mpls] working group last call on draft-ietf-mpls-tp-li-lb-01.txt
liu.guoman@zte.com.cn Fri, 13 May 2011 02:03 UTC
Return-Path: <liu.guoman@zte.com.cn>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B96113001F for <mpls@ietfa.amsl.com>; Thu, 12 May 2011 19:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.238
X-Spam-Level:
X-Spam-Status: No, score=-101.238 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, J_CHICKENPOX_62=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUI2ZED5P8fn for <mpls@ietfa.amsl.com>; Thu, 12 May 2011 19:03:28 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 593FC13001A for <mpls@ietf.org>; Thu, 12 May 2011 19:03:26 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 12520806486374; Fri, 13 May 2011 10:01:26 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 88213.806486374; Fri, 13 May 2011 10:03:24 +0800 (CST)
Received: (from root@localhost) by mse02.zte.com.cn id p4D23NQb065607 for <mpls@ietf.org>; Fri, 13 May 2011 10:03:23 +0800 (GMT-8) (envelope-from liu.guoman@zte.com.cn)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p4D1kbc1048163; Fri, 13 May 2011 09:46:38 +0800 (GMT-8) (envelope-from liu.guoman@zte.com.cn)
Message-Id: <201105130203.p4D23NQb065607@mse02.zte.com.cn>
In-Reply-To: <XFE-RCD-302agj5BbHk0000001a@xfe-rcd-302.cisco.com>
To: Sami Boutros <sboutros@cisco.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
From: liu.guoman@zte.com.cn
Date: Fri, 13 May 2011 09:46:48 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-05-13 09:46:38, Serialize complete at 2011-05-13 09:46:38
Content-Type: multipart/alternative; boundary="=_alternative 0009D5DC4825788F_="
X-MAIL: mse02.zte.com.cn p4D23NQb065607
X-MSS: AUDITRELEASE@mse02.zte.com.cn
Cc: Ross Callon <rcallon@juniper.net>, mpls@ietf.org, draft-ietf-mpls-tp-li-lb@tools.ietf.org
Subject: Re: [mpls] working group last call on draft-ietf-mpls-tp-li-lb-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2011 02:03:32 -0000
sami, yaccov,hi firstly i say sorry for not clearly describling my question. for the first question, maybe yaacov's understanding be right. if a mep is on loopback state, it can't check the e2e path for mis-connectivity because the mep point loopback everything including any OAM packet(cc&cv etc); for the second question, I know loss/delay measurement should use LM/DM fuction to implement it. but for loopback function, there are the following two application: 1 To verify bidirectional connectivity of a MEP with a MIP or a peer MEP ; 2 To perform a bidirectional in-service or out-of-service diagnostics test between a pair of peer MEPs. This includes verifying bandwidth throughput, detecting bit errors, etc; so for application 1, loopback anything will not affect verify bidirectional connectivity; but it may affect diagnostics test. for example, if mis-connectivity or mis-configuration happened on a LSP path, since the mep of the lsp is under loopback state, it can't check mis-connectivity, so the mep of the lsp maybe loopback other data packet of another lsp to the peer mep.or the data pkt of the LSP will be leaked to other LSP path, so it must affect the result of diagnostics test including bandwidth throughput, bit errors. maybe i miss something important? thank sami and yaacov for prompt replying it. B.R. Liu Sami Boutros <sboutros@cisco.com> 2011-05-13 05:05 收件人 "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>, <liu.guoman@zte.com.cn>, "Loa Andersson" <loa@pi.nu> 抄送 "Ross Callon" <rcallon@juniper.net>, <mpls@ietf.org>, "MPLS-TP ad hoc team" <ahmpls-tp@lists.itu.int>, <draft-ietf-mpls-tp-li-lb@tools.ietf.org> 主题 RE: [mpls] working group last call on draft-ietf-mpls-tp-li-lb-01.txt 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: mpls-bounces@ietf.org [ mailto:mpls-bounces@ietf.org] On Behalf Of ext Sami Boutros Sent: Thursday, May 12, 2011 8:03 AM To: liu.guoman@zte.com.cn; Loa Andersson Cc: Ross Callon; mpls@ietf.org; MPLS-TP ad hoc team; draft-ietf-mpls-tp-li-lb@tools.ietf.org 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, liu.guoman@zte.com.cn 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 performance statistics or measurement on the peer mep point? B.R. liu Loa Andersson <loa@pi.nu> ·¢¼þÈË: mpls-bounces@ietf.org 2011-05-10 23:43 ÊÕ¼þÈË "mpls@ietf.org" <mpls@ietf.org> ³ËÍ Ross Callon <rcallon@juniper.net>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, draft-ietf-mpls-tp-li-lb@tools.ietf.org Ö÷Ìâ [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 mpls@ietf.org mailing list. This working group last call ends on May 25th. /Loa for the mpls wg co-chairs -- Loa Andersson email: loa.andersson@ericsson.com Sr Strategy and Standards Manager loa@pi.nu Ericsson Inc phone: +46 10 717 52 13 +46 767 72 92 13 _______________________________________________ mpls mailing list mpls@ietf.org 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. -------------------------------------------------------- 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.
- [mpls] working group last call on draft-ietf-mpls… Loa Andersson
- Re: [mpls] working group last call on draft-ietf-… Stewart Bryant
- Re: [mpls] working group last call on draft-ietf-… Sami Boutros
- Re: [mpls] working group last call on draft-ietf-… liu.guoman
- Re: [mpls] working group last call on draft-ietf-… Stewart Bryant
- Re: [mpls] working group last call on draft-ietf-… Sami Boutros
- Re: [mpls] working group last call on draft-ietf-… Weingarten, Yaacov (NSN - IL/Hod HaSharon)
- Re: [mpls] working group last call on draft-ietf-… Stewart Bryant
- Re: [mpls] working group last call on draft-ietf-… Sami Boutros
- Re: [mpls] working group last call on draft-ietf-… liu.guoman
- Re: [mpls] working group last call on draft-ietf-… liu.guoman
- Re: [mpls] working group last call on draft-ietf-… Stewart Bryant
- Re: [mpls] working group last call on draft-ietf-… Weingarten, Yaacov (NSN - IL/Hod HaSharon)
- Re: [mpls] working group last call on draft-ietf-… Bocci, Matthew (Matthew)
- Re: [mpls] working group last call on draft-ietf-… Loa Andersson
- Re: [mpls] working group last call on draft-ietf-… Loa Andersson
- Re: [mpls] working group last call on draft-ietf-… Loa Andersson