[mpls] draft-kompella-mpls-rmr-00

Xuxiaohu <xuxiaohu@huawei.com> Wed, 12 November 2014 21:33 UTC

Return-Path: <xuxiaohu@huawei.com>
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 1BB631AD3B4 for <mpls@ietfa.amsl.com>; Wed, 12 Nov 2014 13:33:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.794
X-Spam-Level:
X-Spam-Status: No, score=-4.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, 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 dFjkmfbJJEU2 for <mpls@ietfa.amsl.com>; Wed, 12 Nov 2014 13:33:45 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE6971AD3D6 for <mpls@ietf.org>; Wed, 12 Nov 2014 13:33:44 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLO36183; Wed, 12 Nov 2014 21:33:42 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 12 Nov 2014 21:33:42 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.18]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 13 Nov 2014 05:33:38 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "kireeti.kompella@gmail.com" <kireeti.kompella@gmail.com>
Thread-Topic: draft-kompella-mpls-rmr-00
Thread-Index: Ac/+wJTiNhLCDCTzRbWTojN86D41Fg==
Date: Wed, 12 Nov 2014 21:33:37 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082CCD68@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.155.168]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082CCD68NKGEML512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/f72gPM9BWDXzQpqGXuOWpZkpltE
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] draft-kompella-mpls-rmr-00
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: <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: Wed, 12 Nov 2014 21:33:50 -0000

Hi Kireeti,

I have read your draft and found it's very interesting.

I wonder whether it's possible to introduce the idea of the RPR (Resilient Packet Ring) technology into the MPLS-enabled ring networks. For instance, for a given node on a ring, it has two types of interfaces, one is ring-interface and the other is non-ring-interface. In addition, the ring-interface is either eastward or westward. When receiving an MPLS packet from a non-ring interface, if the next-hop of that MPLS packet is one of its adjacent peers on the ring, it would impose a label indicating clock-wise forwarding or count-clock-wise forwarding accordingly. When receiving an MPLS packet with the top label being the label indicating clock-wise or counter-clock-wise forwarding, unless the next-hop of the FEC which is indicated by the label below that top label is itself or a peer which is connected via a non-ring interface (i.e., the packet would pop off the ring), that packet should be forwarding according to the top label, e.g., if the top label indicates clock-wise forwarding, it would be forwarded in the clock-wise direction.

The label indicating clock-wise or count-clock-wise forwarding could be an SPL or a local label which is advertised by each ring node. If that label is a local label, it should be swapped accordingly on each hop of the ring. When the packet received from a adjacent peer on the ring should pop off that ring, the top label indicating clock-wise or count-clock-wise forwarding should be stripped before performing the further MPLS forwarding process.

Best regards,
Xiaohu