Re: [mpls] [AHMPLS-TP] R: Working group last call ondraft-ietf-mpls-tp-ring-protection

"Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> Tue, 02 October 2012 14:50 UTC

Return-Path: <nurit.sprecher@nsn.com>
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 2AA4E21F844F for <mpls@ietfa.amsl.com>; Tue, 2 Oct 2012 07:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 uPI0Fax6b-+A for <mpls@ietfa.amsl.com>; Tue, 2 Oct 2012 07:50:25 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 3E30421F84FF for <mpls@ietf.org>; Tue, 2 Oct 2012 07:50:24 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q92EoJYO002588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Oct 2012 16:50:19 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q92EoImE029399; Tue, 2 Oct 2012 16:50:19 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 2 Oct 2012 16:50:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CDA0AD.3D8439F4"
Date: Tue, 02 Oct 2012 16:50:17 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C027A2CC2@DEMUEXC013.nsn-intra.net>
In-Reply-To: <1349174488.11140.YahooMailClassic@web15602.mail.cnb.yahoo.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls] [AHMPLS-TP] R: Working group last call ondraft-ietf-mpls-tp-ring-protection
Thread-Index: Ac2gioV6N4xSKVO0TLymJnGaGxJxhgAIbTdA
References: <506AADC0.2090802@gmail.com> <1349174488.11140.YahooMailClassic@web15602.mail.cnb.yahoo.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: ext Larry <larryli888@yahoo.com.cn>, D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>, huubatwork@gmail.com
X-OriginalArrivalTime: 02 Oct 2012 14:50:18.0111 (UTC) FILETIME=[3D41A0F0:01CDA0AD]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 68194
X-purgate-ID: 151667::1349189422-00003184-51392D6D/0-0/0-0
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, draft-ietf-mpls-tp-ring-protection@tools.ietf.org
Subject: Re: [mpls] [AHMPLS-TP] R: Working group last call ondraft-ietf-mpls-tp-ring-protection
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: Tue, 02 Oct 2012 14:50:56 -0000

Dear Han Li,
Thanks for your comment. 
·         Can you please explain why do you think there are risks that protection switch time exceeds 50ms ("from the moment of fault detection in a         network with a 16-node ring with less than 1200 km of fiber" as required in RFC 5654)? What in the proposed solution make you think there are risks? 
·         Can you please indicate why do you think the configuration is too complex and why it requires too many labels and OAM sessions...and how do you think this could be better optimized? 
In order to refer to this as a LC comment, the technical arguments should be presented and elaborated. 
Thanks and best regards,
Nurit
 
-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ext Larry
Sent: Tuesday, October 02, 2012 12:41 PM
To: D'Alessandro Alessandro Gerardo; huubatwork@gmail.com
Cc: mpls@ietf.org; mpls-chairs@tools.ietf.org; MPLS-TP ad hoc team; draft-ietf-mpls-tp-ring-protection@tools.ietf.org
Subject: Re: [mpls] [AHMPLS-TP] R: Working group last call ondraft-ietf-mpls-tp-ring-protection
 
not support!
It doesn't satisfy some requirements of the operators. The configuration is too complex and needs too many labels and OAM sessions. There are risks that protection switch time exceed 50ms.
 
*************************************************************************
Han Li, Ph.D 
China Mobile Research Institute
32 Xuanwumen West Street, Xicheng District, Beijing 100053, China 
Fax: +86 10 63135159 
MOBILE: 13501093385 
*************************************************************************
 
 
--- 12年10月2日,周二, Huub van Helvoort <huubatwork@gmail.com <mailto:huubatwork@gmail.com> > 写道:
 
> 发件人: Huub van Helvoort <huubatwork@gmail.com <mailto:huubatwork@gmail.com> >
> 主题: Re: [mpls] [AHMPLS-TP] R: Working group last call on draft-ietf-mpls-tp-ring-protection
> 收件人: "D'Alessandro Alessandro Gerardo" <alessandro.dalessandro@telecomitalia.it <mailto:alessandro.dalessandro@telecomitalia.it> >
> 抄送: "mpls@ietf.org <mailto:mpls@ietf.org> " <mpls@ietf.org <mailto:mpls@ietf.org> >, "mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org> " <mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org> >, "MPLS-TP ad hoc team" <ahmpls-tp@lists.itu.int <mailto:ahmpls-tp@lists.itu.int> >, "draft-ietf-mpls-tp-ring-protection@tools.ietf.org <mailto:draft-ietf-mpls-tp-ring-protection@tools.ietf.org> " <draft-ietf-mpls-tp-ring-protection@tools.ietf.org <mailto:draft-ietf-mpls-tp-ring-protection@tools.ietf.org> >
> 日期: 2012年10月2日,周二,下午5:02
> Do not support.
> 
> Same reasons as mentioned below.
> 
> Regards, Huub.
> 
> On 01-10-12 14:27, D'Alessandro Alessandro Gerardo wrote:
> > Do not support
> >
> > According to the optimization criteria for ring
> protection specified in Section 2.5.6.1 in RFC5654, the
> MPLS-TP ring protection should be optimized for
> simplification of the ring operation and the resources
> consumption around the ring. It is not the case of the
> proposed solution.
> > It is actually simply an applicability statement of a
> linear protection mechanism but it cannot be consider a
> solution that addresses the requirements for protection of
> ring topologies for Multi-Protocol Label Switching Transport
> Profile (MPLS-TP) as specified in RFC5654.
> >
> > Best regards,
> > Alessandro
> >
> >
> ------------------------------------------------------------------
> > Telecom Italia
> > Alessandro Gerardo D'Alessandro
> > Transport Innovation
> > Via Reiss Romoli, 274 - 10148 Torino
> > phone:  +39 011 228 5887
> > mobile: +39 335 766 9607
> > fax: +39 06 418 639 07
> >
> >
> > -----Messaggio originale-----
> > Da: mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org> 
> [mailto:mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org> ]
> Per conto di Hejia
> > Inviato: sabato 29 settembre 2012 12:53
> > A: Loa Andersson
> > Cc: mpls@ietf.org <mailto:mpls@ietf.org> ; mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org> ;
> MPLS-TP ad hoc team; draft-ietf-mpls-tp-ring-protection@tools.ietf.org <mailto:draft-ietf-mpls-tp-ring-protection@tools.ietf.org> 
> > Oggetto: Re: [mpls] Working group last call on
> draft-ietf-mpls-tp-ring-protection
> >
> > Do not support.
> >
> > Based on the analysis in Section 2.4 of
> draft-ietf-mpls-tp-ring-protection-02, the ring protection
> scheme using SPME as described, either wrapping or steering,
> does have deficiencies, which IMHO should be better
> reconsidered and solved if possible.
> >
> >
> > B.R.
> > Jia
> >
> > -----邮件原件-----
> > 发件人: mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org> 
> [mailto:mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org> ]
> 代表 Loa Andersson
> > 发送时间: 2012年9月19日 18:49
> > 抄送: mpls@ietf.org <mailto:mpls@ietf.org> ;
> MPLS-TP ad hoc team; draft-ietf-mpls-tp-ring-protection@tools.ietf.org <mailto:draft-ietf-mpls-tp-ring-protection@tools.ietf.org> ;
> mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org> 
> > 主题: [mpls] Working group last call on
> draft-ietf-mpls-tp-ring-protection
> >
> > Working Group,
> >
> > this is to start a two week working group last call on
> > draft-ietf-mpls-tp-ring-protection-02-txt.
> >
> > Please note that there are two IPR disclosures # 1462
> and  # 1872
> > related to this document.
> >
> > Please send your comments to the mpls working group
> mailing lists
> > (mpls@ietf.org <mailto:mpls@ietf.org> ).
> >
> > The working group last call ends October 3, 2012.
> >
> > /Loa
> > for the mpls wg co-chairs
> >
> >
> > --
> >
> >
> > Loa Andersson           
>              email:
> loa.andersson@ericsson.com <mailto:loa.andersson@ericsson.com> 
> > Sr Strategy and Standards Manager     
>       loa@pi.nu <mailto:loa@pi.nu> 
> > Ericsson Inc           
>               phone: +46
> 10 717 52 13
> >               
>                
>                 +46
> 767 72 92 13
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org <mailto:mpls@ietf.org> 
> > https://www.ietf.org/mailman/listinfo/mpls <https://www.ietf.org/mailman/listinfo/mpls> 
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org <mailto:mpls@ietf.org> 
> > https://www.ietf.org/mailman/listinfo/mpls <https://www.ietf.org/mailman/listinfo/mpls> 
> 
> -- 
> *****************************************************************
>            
>    请记住,你是独一无二的,就像其他每一个人一样
> _______________________________________________
> mpls mailing list
> mpls@ietf.org <mailto:mpls@ietf.org> 
> https://www.ietf.org/mailman/listinfo/mpls <https://www.ietf.org/mailman/listinfo/mpls> 
> 
_______________________________________________
mpls mailing list
mpls@ietf.org <mailto:mpls@ietf.org> 
https://www.ietf.org/mailman/listinfo/mpls <https://www.ietf.org/mailman/listinfo/mpls>