Re: [mpls] MPLS-RT review of draft-cheng-mpls-tp-shared-ring-protection-05

Yimin Shen <yshen@juniper.net> Mon, 13 July 2015 16:44 UTC

Return-Path: <yshen@juniper.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D801A1BF5; Mon, 13 Jul 2015 09:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YzxRLLGyF66E; Mon, 13 Jul 2015 09:44:10 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0752.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::752]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EC5D1A1B7F; Mon, 13 Jul 2015 09:44:10 -0700 (PDT)
Received: from BY2PR0501MB1813.namprd05.prod.outlook.com (10.163.155.143) by BY2PR0501MB1813.namprd05.prod.outlook.com (10.163.155.143) with Microsoft SMTP Server (TLS) id 15.1.213.14; Mon, 13 Jul 2015 16:43:49 +0000
Received: from BY2PR0501MB1813.namprd05.prod.outlook.com ([10.163.155.143]) by BY2PR0501MB1813.namprd05.prod.outlook.com ([10.163.155.143]) with mapi id 15.01.0213.000; Mon, 13 Jul 2015 16:43:49 +0000
From: Yimin Shen <yshen@juniper.net>
To: "huubatwork@gmail.com" <huubatwork@gmail.com>, "draft-cheng-mpls-tp-shared-ring-protection@tools.ietf.org" <draft-cheng-mpls-tp-shared-ring-protection@tools.ietf.org>
Thread-Topic: [mpls] MPLS-RT review of draft-cheng-mpls-tp-shared-ring-protection-05
Thread-Index: AdCulDikA5WgvcQnQCSiWQCAAJNPcwMGNlygAHk56gAAPh0cQA==
Date: Mon, 13 Jul 2015 16:43:49 +0000
Message-ID: <BY2PR0501MB1813CBD233287BFAB1E700C2BD9C0@BY2PR0501MB1813.namprd05.prod.outlook.com>
References: <BY1PR0501MB1430819702B9DCE681281393A5AF0@BY1PR0501MB1430.namprd05.prod.outlook.com> <BY2PR0501MB181356DF5C6A742BC629A5BBBD9F0@BY2PR0501MB1813.namprd05.prod.outlook.com> <55A248D2.1010001@gmail.com>
In-Reply-To: <55A248D2.1010001@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-originating-ip: [66.129.241.13]
x-microsoft-exchange-diagnostics: 1; BY2PR0501MB1813; 5:C5ij+wXodDdeP12diWlqMT/YBo5dCfpOzUjlbOAX4wTN54a74dEtU4JiS9l4eOMzR97Z2wJpWxXxu9AivNBbBeyplf1R/N3egZSf0pO1Reso0RT1JIn96oMQmPi2bOhfDb7UkLfaK8MfxmOL91UyWw==; 24:0Fo1UE3K9dpiZgWaklrzZ6jV1HvSZwLrmCxbpXg/LDUBP+FUYMptsSs0sE/jjVwcLUSRlD7/pkBhoZnYl+6cGCSTGFzI32Z3GJo7ZDNdaAE=; 20:/AfSBPYOYQS9nijHMTz6fS2cNg28EiK0y2afPocwxXgUDfytZD9XSbuqMFGtqU0lStXDetdQZzZT/cIt3DhZiA==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0501MB1813;
by2pr0501mb1813: X-MS-Exchange-Organization-RulesExecuted
x-microsoft-antispam-prvs: <BY2PR0501MB1813A6D79358EE9B3CE9834ABD9C0@BY2PR0501MB1813.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:BY2PR0501MB1813; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0501MB1813;
x-forefront-prvs: 0636271852
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(43544003)(377424004)(164054003)(377454003)(51914003)(24454002)(2950100001)(122556002)(66066001)(50986999)(2501003)(74316001)(62966003)(16236675004)(230783001)(92566002)(2900100001)(19300405004)(86362001)(46102003)(2656002)(87936001)(189998001)(5001960100002)(19625215002)(99286002)(77156002)(40100003)(19580405001)(5003600100002)(102836002)(76176999)(19580395003)(5002640100001)(15975445007)(77096005)(54356999)(76576001)(18717965001)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0501MB1813; H:BY2PR0501MB1813.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/alternative; boundary="_000_BY2PR0501MB1813CBD233287BFAB1E700C2BD9C0BY2PR0501MB1813_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jul 2015 16:43:49.5697 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0501MB1813
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/4lgsFC-BJ-LWdkEM1JQPnr1rsZQ>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Subject: Re: [mpls] MPLS-RT review of draft-cheng-mpls-tp-shared-ring-protection-05
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Jul 2015 16:44:14 -0000

Hi Huub,

Thanks for the response.

Yes, the ring tunnel layer should deserve a greater level of detail in this draft.

Regarding the “ring-map”… You mentioned it in answering  a few of my top questions, but didn’t elaborate to support your anwers. IMO, the ring map is an important piece of your solution as well, and should not be pushed out of scope (below). I’d like to suggest to decribe what information it contains, how it is built, how  the information is distributed and synchronized between nodes, etc.


“Each node SHOULD have a ring map containing information about the sequence of the nodes around the ring.  The method of configuring the nodes with the ring maps is out of scope of this document.”


The entire section 4.4 still remains as a problem for me. IMO, the ingress node and the egress node of a service LSP has a forwarding adjacency at the service LSP level, across the entire ring (or inter-connected rings). The LSP’s label should be transparent to intermediate ring nodes, and no intermediate ring nodes should perform forwarding based this label. Does this match the goals/requirements of this draft? There would be some problems if you want an intermediate ring node (ring interconnection node in this case) to understand a service LSP label. Also, I’m not sure how the ring map could help in this case. Therefore, until I see some clarification, I still don’t understand how section 4.4 would work in both normal forwarding and protection mode.


Thanks,

/Yimin


From: Huub van Helvoort [mailto:huubatwork@gmail.com]
Sent: Sunday, July 12, 2015 7:01 AM
To: Yimin Shen; draft-cheng-mpls-tp-shared-ring-protection@tools.ietf.org
Cc: mpls@ietf.org; mpls-chairs@ietf.org
Subject: Re: [mpls] MPLS-RT review of draft-cheng-mpls-tp-shared-ring-protection-05

Hello Yimin,

Thank you for your review.
Here is our response: in-line [Huub] on behalf of the authors.

Best regards. Huub.

======
On 10-07-15 03:37, Yimin Shen wrote:
Dear authors, chairs, and WG

I’ve been asked by the WG chairs to review draft-cheng-mpls-tp-shared-ring-protection-05 for WG adoption. Overall, I think the draft is trying to address a valid MPLS-TP scenario by using a promising solution. However, I have the following comments and questions  for sections 1 to 4, which I would like to request the authors to answer and clarify.

1.       Section 2.1 – Recovery of multiple failures
·         This is misleading to me. The draft seems to only be able to handle a single failure per ring, rather than multiple failures per ring. This may need some clarification.
[Huub] Multiple failures means that more than one link or node in the ring can fail. Protection can still be performed
in the "islands" created in this way. A node failure is in fact the same as adjacent link failures.
We can provide more clarification.


2.       I’d like to suggest to change term “exit node” to “egress node”.
[Huub] OK.


3.       Section 4.1 - The ring tunnel layer.

·         Given a ring of N nodes, this layer would consist of 4xN ring tunnels. The draft is a little light on the provisioning and management aspects of this layer, while pushing a lot of complexity to this layer.
[Huub] clarifying text can be added. We can add a section describing provisioning the ring-nodes.

·         Each node is traversed by many tunnels. How does it know whether a tunnel is working or protecting,  and whether a tunnel is CW or AW ? How does it associate a working tunnel with a protecting tunnel (to the same egress node, but opposite in direction) ?
[Huub] each node knows this because of the ring-map which contains this information.

·         When an ingress node needs a working tunnel to a particular egress node, how does choose between the CW  tunnel and the AW tunnel, especially when one is significantly longer  (i.e. of higher cost) than the other ?
[Huub] from the ring-map the ingress node knows what the shortest path is and then decides to take the CW or the AW tunnel.


4.       The draft describes 4 tunnels (CW, AW, CP, AP) per egress node ? Is it possible to use only 2 tunnels (i.e. CW and AW) and have them protect each other ?
[Huub] mixing working and protecting traffic in a single tunnel would make the RPS protocol more complex.
An egress node cannot make the distinction.


5.       Section 4.3.2 -- Short wrapping vs. “traditional wrapping”

·         Does “traditional wrapping” refer to the scenario in section 4.3.1 ?
[Huub] No it doesn't, section 4.3.1 explains wrapping for link failure and node failure.
[Huub] the description of traditional wrapping is in the first paragraph of section 4.3.2, more clarification can be added.

·         The 4.3.2 mode seems superior to the 4.3.1 mode in all aspects. If so, would there be any value to keep 4.3.1 mode.
[Huub] 4.3.1 explains wrapping methodology, its application is described in 4.3.2.

·         In 4.3.2 mode, CW tunnel ==CP tunnel and AW tunnel == AP tunnel in path topology, correct ? If so, you could reduce the number of tunnels per egress node from 4 to 2 (as comment [4] above), correct ?
[Huub] No, not correct. During a protection switch CW tunnel ==> AP tunnel and AW tunnel ==> CP tunnel.


6.       Section 4.3.3

·         This is equivalent to “global repair” in MPLS. However, why does the ingress node switch traffic from CW tunnel to AP tunnel instead of AW tunnel ? A working tunnel should be “better” than a protecting tunnel to permanently carry traffic.
[Huub] to operate properly ring protection switching has to be revertive, after repair the traffic should be switched back to working (shortest path)

7.       Section 4.4

·         I’m not sure how label swap would work on an interconnection node, as the draft describes it. In Fig-12, in normal state, F receives a packet from ring-1; The top label X is a tunnel to the node group; The next label Y is the service LSP. So, F pops label X, and “ the label used for working ring tunnel R2cW_I will be pushed based on the inner label” (i.e. label Y). How could F have the knowledge about the service LSP, its label Y, and its egress node, etc ?
[Huub] the ring-map has to take care of this.

·         I may have more questions to follow after the above…

Regards,

Yimin Shen
Juniper Networks



--

*****************************************************************

              请记住,你是独一无二的,就像其他每一个人一样