[mpls-tp] 答复: draft-bao-mpls-tp-path-transfer-reqs
Bao.Yuanlin@zte.com.cn Wed, 31 March 2010 03:32 UTC
Return-Path: <bao.yuanlin@zte.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 720773A6882 for <mpls-tp@core3.amsl.com>; Tue, 30 Mar 2010 20:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -89.019
X-Spam-Level:
X-Spam-Status: No, score=-89.019 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, CHARSET_FARAWAY_HEADER=3.2, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bfbMd6+QuZB9 for <mpls-tp@core3.amsl.com>; Tue, 30 Mar 2010 20:32:47 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 1835C3A6782 for <mpls-tp@ietf.org>; Tue, 30 Mar 2010 20:32:46 -0700 (PDT)
Received: from [10.30.17.100] by mx6.zte.com.cn with surfront esmtp id 12864764009499; Wed, 31 Mar 2010 11:31:40 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 86863.2775887111; Wed, 31 Mar 2010 11:30:27 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o2V3WjsX082113; Wed, 31 Mar 2010 11:33:01 +0800 (CST) (envelope-from Bao.Yuanlin@zte.com.cn)
In-Reply-To: <77ead0ec1003282150g33c96946mbfbd443481885609@mail.gmail.com>
To: mpls-tp@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFE5A98B8E.D10BA197-ON482576F7.000EE33C-482576F7.00137D36@zte.com.cn>
From: Bao.Yuanlin@zte.com.cn
Date: Wed, 31 Mar 2010 11:35:05 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-03-31 11:32:58, Serialize complete at 2010-03-31 11:32:58
Content-Type: multipart/alternative; boundary="=_alternative 00137D35482576F7_="
X-MAIL: mse2.zte.com.cn o2V3WjsX082113
Subject: [mpls-tp] 答复: draft-bao-mpls-tp-path-transfer-reqs
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2010 03:32:48 -0000
Hi, Vishwas, The requirements listed in RFC5493 aply to unidirectional and co-routed LSPs in the ASON architecture of ITU-T G.8080. However, in MPLS-TP network, associated bidirectional LSP and PW defined in RFC5654 are included, which are not described in RFC5493. For associated bidirectional LSP, edge nodes and transit nodes should be aware about the pairing relationship of the forward and the backward directions belonging to the same associated bidirectional transport path, so, this pairing relationship must be created in CP when associated LSP transfer from MP to CP. This is not described in RFC5493. For PW including SS-PW and MS-PW, it's signaling procedures described in RFC4447, draft-ietf-pwe3-dynamic-ms-pw and draft-ietf-pwe3-segmented-pw are completely different from the LSP's. So, the PW transfer procedures are another big differences, which are not described in RFC5493. So, the above two aspects are the main MPLS-TP specific requirements. Others specific requirements maybe exist, but we aren't identified. And any new requirements identified are welcome to improve the document. Regards, Yuanlin Bao Vishwas Manral <vishwas.ietf@gmail.com> 写于 2010-03-29 12:50:46: > Hi, > > I am very happy to see new inputs from different people and vendors. > > I looked at the draft and was wondering what is not covered in RFC > 5493 which is for GMPLS control plane/ MP which is probably the > control plane for MPLS-TP. Is there any MPLS-TP specific requirement? > > Thanks, > Vishwas >
- [mpls-tp] 答复: Re: 答复: draft-bao-mpls-tp-path-tran… Bao.Yuanlin
- [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Vishwas Manral
- [mpls-tp] 答复: draft-bao-mpls-tp-path-transfer-reqs Bao.Yuanlin
- Re: [mpls-tp] 答复: draft-bao-mpls-tp-path-transfer… benjamin.niven-jenkins
- Re: [mpls-tp] 答复: draft-bao-mpls-tp-path-transfer… benjamin.niven-jenkins
- Re: [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Curtis Villamizar
- Re: [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Zhi-Wei Lin
- Re: [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Adrian Farrel
- Re: [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Zhi-Wei Lin
- Re: [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Vishwas Manral
- [mpls-tp] 答复: Re: draft-bao-mpls-tp-path-transfer… Bao.Yuanlin
- Re: [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Curtis Villamizar
- Re: [mpls-tp] draft-bao-mpls-tp-path-transfer-reqs Adrian Farrel