Re: [mpls] Doubts on draft-helvoort-mpls-tp-ring-protection-switching-03

Naveen T <naveen.thanikachalam@yahoo.in> Mon, 04 February 2013 13:48 UTC

Return-Path: <naveen.thanikachalam@yahoo.in>
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 0894121F8667 for <mpls@ietfa.amsl.com>; Mon, 4 Feb 2013 05:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.794
X-Spam-Level:
X-Spam-Status: No, score=-1.794 tagged_above=-999 required=5 tests=[AWL=0.805, BAYES_00=-2.599]
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 r39VImCUQBX2 for <mpls@ietfa.amsl.com>; Mon, 4 Feb 2013 05:48:56 -0800 (PST)
Received: from nm7-vm4.bullet.mail.sg3.yahoo.com (nm7-vm4.bullet.mail.sg3.yahoo.com [106.10.148.179]) by ietfa.amsl.com (Postfix) with ESMTP id CBAF821F8605 for <mpls@ietf.org>; Mon, 4 Feb 2013 05:48:54 -0800 (PST)
Received: from [106.10.166.125] by nm7.bullet.mail.sg3.yahoo.com with NNFMP; 04 Feb 2013 13:48:48 -0000
Received: from [106.10.151.203] by tm14.bullet.mail.sg3.yahoo.com with NNFMP; 04 Feb 2013 13:48:47 -0000
Received: from [127.0.0.1] by omp1015.mail.sg3.yahoo.com with NNFMP; 04 Feb 2013 13:48:47 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 899661.5494.bm@omp1015.mail.sg3.yahoo.com
Received: (qmail 15971 invoked by uid 60001); 4 Feb 2013 13:48:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.in; s=s1024; t=1359985727; bh=objv9EXNZV1jUzqjGQ0c8TsuZsVYMgIBQrNZZIuEDeY=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=B/IV83FYyTnBHDiAxBefQLrQRw1xqeLslxXYfGJH38DF+opYb9hH95KRSNGsZMWqyoB2StZCVDua4TjpqYKoIku9fMzkBX19ClLxsRBkWQg75QPrlQoT4diiDrBxoZ+ru4GQcapUTdsO0UpHR8JlrbqBLWVchnrkZxQmSWcK+G8=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.in; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=gpHkh2/iEPiemnsVeoRqKKEA5SXKTPrb6PJikBy/X/C/Mi8DMEPq+LbqL5aVA5jZ53rCzrxO1epgApeZv9yI1Qb60PJbU1NFL5sF2jLx2QqtHGONIoY96wEBsP/NJxmVRIUbM8X0VbjsBWPWIE7AIX4OkaQqy4/HpD1mSKIiY2Q=;
X-YMail-OSG: ez34e9UVM1mQfkRJLH0mBFj6qpc517232qyEiI20mwOi6WH dhBgbjxoXbGQjPKLlVVKjpo_fQ5nl7BnD29V8XVSfCXX2iisHFWPE0TbR8Nl F2LXYYnzy819vZu_sht4FM.Dk66ZXW9GNN0gppbfkSQ8J7T6YDGD6c1Si7Xp s5dieT1Olyb9uK7nQBvOzkCz4t4O2yL_Bt739FY.oCp.X0fHF.hQtkw_l9pI APlu8v16OJ.J68nrGDyR3gR8IJJ8PufmRHuzLTUQ.Lrf6oTjpkoNkY7q8RBw qKuY.ZY7qDc9gqrjx6bCsbX7ypKdErYqQNzROWtzze9EZeYb6S3h4J0xG9Se _bLJVb9NzPzAneZi0pxzWBw0muH13z4Ih5fxEMDiqov_GPZbOTdrwzNGZSYS 63IeOfhnW2sqa9cPpoUf2ca6ZC6S_QKwNFfJ8Om6jO__7hwSWJHeskyoJwpw A.K0-
Received: from [115.112.61.194] by web190902.mail.sg3.yahoo.com via HTTP; Mon, 04 Feb 2013 21:48:47 SGT
X-Rocket-MIMEInfo: 001.001, RGVhciBIdXViLAoKVGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgY2xlYXJpbmcgdXAgbXkgZG91YnRzLiBZb3VyIGFuc3dlcnMgYWRkcmVzc2VkIG15IGNvbmNlcm5zLgoKSSBoYXZlIHR3byBtb3JlIHF1ZXN0aW9ucy7CoAoKVGhpcyBpcyB3aXRoIHJlc3BlY3QgdG8gdGhlIGxpbmsgZmFpbHVyZSBleGFtcGxlIGluIHRoZSBXcmFwcGluZyBzb2x1dGlvbiBhcyBkZXNjcmliZWQgaW4gc2VjdGlvbiAzLjEuMi4xLiBBcyBwcm9wb3NlZCBieSB0aGUgc29sdXRpb24sIHdoZW4gYSBmYWlsdXJlIG9jY3VycyBvbiB0aGUBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.131.499
References: <1359970168.93490.YahooMailNeo@web190901.mail.sg3.yahoo.com>, <1359975401.56110.YahooMailNeo@web190906.mail.sg3.yahoo.com> <73E555AA235F3846B8051DB38C8776272E5ACF9A@lhreml509-mbx>
Message-ID: <1359985727.14648.YahooMailNeo@web190902.mail.sg3.yahoo.com>
Date: Mon, 04 Feb 2013 21:48:47 +0800
From: Naveen T <naveen.thanikachalam@yahoo.in>
To: Huub helvoort <huub.van.helvoort@huawei.com>, MRPS Helvoort <draft-helvoort-mpls-tp-ring-protection-switching@tools.ietf.org>, MPLS <mpls@ietf.org>
In-Reply-To: <73E555AA235F3846B8051DB38C8776272E5ACF9A@lhreml509-mbx>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 04 Feb 2013 11:20:54 -0800
Subject: Re: [mpls] Doubts on draft-helvoort-mpls-tp-ring-protection-switching-03
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Naveen T <naveen.thanikachalam@yahoo.in>
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: Mon, 04 Feb 2013 13:48:57 -0000

Dear Huub,

Thank you very much for clearing up my doubts. Your answers addressed my concerns.

I have two more questions. 

This is with respect to the link failure example in the Wrapping solution as described in section 3.1.2.1. As proposed by the solution, when a failure occurs on the link between B and C, the traffic flow and the label usage are as below:
A[W1]->B[P6]->A[P1]->F[P2]->E[P3]->D[P4]->C[W3]->D

Consider the case where the packet has traversed the ring on the protection path (...D[P4]->C) and is now at node C. At this point in time, if the link between B and C comes back up again, i.e., it is operational again, then;

1) Will the node C swap the label it receives (P4) with the protection label P3 and forward the packet to B? If so, there is a possibility that the packet continues to traverse the ring via the protection path in the loop, or;


2) Will the node C always swap the label it receives (P4) with the working label W3 and forward the packet to D irrespective of whether there is a failure on the link between C and B?

Thanks and Regards,
Naveen T

________________________________
From: Huub helvoort <huub.van.helvoort@huawei.com>
To: Naveen T <naveen.thanikachalam@yahoo.in>; MRPS Helvoort <draft-helvoort-mpls-tp-ring-protection-switching@tools.ietf.org> 
Sent: Monday, 4 February 2013 6:50 PM
Subject: RE: [mpls] Doubts on draft-helvoort-mpls-tp-ring-protection-switching-03



Dear Naveen,

Thank you very much for your patience.

The last two weeks I have been traveling, and email access was very limited.

Please find below the answers to your questions [Huub].

> The proposed solution recommends the usage of section layer OAM to find signal failures on a link. Since the two nodes will be able to detect failures at either end of a link using the link OAM, why would it be a necessity to send the APS payload to the adjacent node in the direction opposite to the failure?

[Huub] The nodes at each side of a section (e.g. Nodes A and B) can detect failures. However the failure may have occurred only in one direction, e.g node A --> B, the APS message s used to informA that B has detected a failure and will switch to protection, A will have to switch to protection too. 
[Huub] also if a node fails e.g. node B located between nodes A and C then both A and C will detect the failure of
the section connecting them to B, and they have to inform the other side C resp. A that they will perform a protectiuoin switch based on the detected failure.
[Huub] there may be more than a single section or node failure in the ring, all the nodes in the ring have to be aware of the failure and its location to take proper protection switch consequent actions.

> If the switching commands Lockout, Manual Switch and Forced Switch are taken out of the equation, and assuming that a signal failure will be the only reason considered for a switch-over, will it still be necessary to use the APS protocol at all? 

[Huub] also in this case the APS messages sent colockwise and counter-clockwise will be necessary to inform all the nodes in the ring of the fault location and the switch action. There may be point-to-multipoint connections on the ring, and each node has to decide wich signal should be used. 

I hope this addresses your concerns. 

Best regards, Huub.