Re: [CCAMP] bidir LSP in rfc4803
Attila Takacs <Attila.Takacs@ericsson.com> Mon, 28 February 2011 14:48 UTC
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E9963A6C19 for <ccamp@core3.amsl.com>; Mon, 28 Feb 2011 06:48:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 E7IBE7K8Na-h for <ccamp@core3.amsl.com>; Mon, 28 Feb 2011 06:48:31 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 09CA43A6C15 for <ccamp@ietf.org>; Mon, 28 Feb 2011 06:48:30 -0800 (PST)
X-AuditID: c1b4fb39-b7c6dae0000023f2-8f-4d6bb5fa9999
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id FD.FB.09202.AF5BB6D4; Mon, 28 Feb 2011 15:49:30 +0100 (CET)
Received: from ESESSCMS0365.eemea.ericsson.se ([169.254.1.161]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Mon, 28 Feb 2011 15:49:30 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: "Vijayanand C - ERS, HCL Tech" <vijayc@hcl.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Mon, 28 Feb 2011 15:49:29 +0100
Thread-Topic: bidir LSP in rfc4803
Thread-Index: AcvXGXlU6/zpjV+LR4e5csqlwu092AAOKXfA
Message-ID: <6477E10CC7D76444A479B9AC31F262A9DD9D0C93@ESESSCMS0365.eemea.ericsson.se>
References: <66E3DDEEA70F0D469D1FFE238526B6ED3E446EE6D1@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
In-Reply-To: <66E3DDEEA70F0D469D1FFE238526B6ED3E446EE6D1@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6477E10CC7D76444A479B9AC31F262A9DD9D0C93ESESSCMS0365eem_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [CCAMP] bidir LSP in rfc4803
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 14:48:33 -0000
Hi Vijay, Thanks for pointing out the MIB aspects, this is indeed a bit lagging behind. However, initial work on TP specific MIB has been started recently: http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt discusses bidirectional LSPs and I think the asymmetric bandwidth option should be addressed in that document as it goes along. Attila ________________________________ From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of Vijayanand C - ERS, HCL Tech Sent: Monday, February 28, 2011 8:31 AM To: ccamp@ietf.org Subject: [CCAMP] bidir LSP in rfc4803 Hello All, How are the two directions of the cross connect of the bidirectional LSP correlated It is not clear in RFC 4803. As per section 5, the cross connects will have the same XC index. " The GMPLS-LSR-STD-MIB module supports bidirectional LSPs as required for GMPLS. A single value of mplsXCIndex is shared by all of the segments for the entire bidirectional LSP. This facilitates a simple reference from [RFC3812<http://tools.ietf.org/html/rfc3812>] and [RFC4802<http://tools.ietf.org/html/rfc4802>] and makes fate-sharing more obvious. " But as per the example in section 6, the xcindex can be different but the mplsXCLSPId must be same " In mplsXCTable: { mplsXCIndex = 0x01, mplsXCInSegmentIndex = 0x00000015, mplsXCOutSegmentIndex = 0x00000012, mplsXCLspId = 0x0102 -- unique ID mplsXCLabelStackIndex = 0x00, -- only a single outgoing label mplsXCRowStatus = createAndGo(4) } In mplsXCTable: { mplsXCIndex = 0x02, mplsXCInSegmentIndex = 0x00000016, mplsXCOutSegmentIndex = 0x00000013, mplsXCLspId = 0x0102 -- unique ID mplsXCLabelStackIndex = 0x00, -- only a single outgoing label mplsXCRowStatus = createAndGo(4) } " Will the mplsXCindex be same or different, please clarify. Regards Vijay ________________________________ ::DISCLAIMER:: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. -----------------------------------------------------------------------------------------------------------------------
- [CCAMP] bidir LSP in rfc4803 Vijayanand C - ERS, HCL Tech
- Re: [CCAMP] bidir LSP in rfc4803 Attila Takacs
- Re: [CCAMP] bidir LSP in rfc4803 Vijayanand C - ERS, HCL Tech