Re: [mpls] Fwd: New Version Notification for draft-kompella-mpls-rmr-00.txt

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 13 November 2014 08:12 UTC

Return-Path: <jie.dong@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 90AAC1A3BA5 for <mpls@ietfa.amsl.com>; Thu, 13 Nov 2014 00:12:37 -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 sB1SpoAoUIez for <mpls@ietfa.amsl.com>; Thu, 13 Nov 2014 00:12:35 -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 293D51A1B8B for <mpls@ietf.org>; Thu, 13 Nov 2014 00:12:34 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLO76041; Thu, 13 Nov 2014 08:12:32 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 13 Nov 2014 08:12:31 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 13 Nov 2014 16:12:28 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Kireeti Kompella <kireeti.kompella@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] Fwd: New Version Notification for draft-kompella-mpls-rmr-00.txt
Thread-Index: AQHP85+BXc8zMxj8Ik2Mr1vArzJdO5xeOwQw
Date: Thu, 13 Nov 2014 08:12:27 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C92733766A54@nkgeml512-mbx.china.huawei.com>
References: <20141027041512.4465.43044.idtracker@ietfa.amsl.com> <CABRz93X_dDkHNE_bRGGUZgs=BA7BcpFkBRtvL0UUDz-rSLOh8Q@mail.gmail.com>
In-Reply-To: <CABRz93X_dDkHNE_bRGGUZgs=BA7BcpFkBRtvL0UUDz-rSLOh8Q@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.96.76]
Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C92733766A54nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/E8zsVMgcsqEC9HUZBAoOCz0UpkQ
Subject: Re: [mpls] Fwd: New Version Notification for draft-kompella-mpls-rmr-00.txt
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: Thu, 13 Nov 2014 08:12:38 -0000
X-List-Received-Date: Thu, 13 Nov 2014 08:12:38 -0000

Hi Kireeti,

I see the definition section of this draft briefly describes the architecture of ring LSP, and section 3.3, 3.4  specify the installation of primary and protection labels.  Since section 2.1 of draft-cheng-mpls-tp-shared-ring-protection specified the architecture of ring tunnels and the label distribution on rings, maybe we can build the ring LSP architecture based on that work.

Section 3.6 Protection describes the general protection mechanism used for ring LSPs, while the details of several protection mechanisms, like wrapping, short-wrapping and steering in ring topology were specified in section 2.2~2.4 of draft-cheng-mpls-tp-shared-ring-protection. IMO it would be helpful if the applicability of these protection mechanisms can be discussed or reused.

Regarding configuration and signaling, both are interesting topics for MPLS in ring topology, and I’d appreciate hearing your thoughts on them.

Best regards,
Jie

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Kireeti Kompella
Sent: Thursday, October 30, 2014 1:41 AM
To: mpls@ietf.org
Subject: [mpls] Fwd: New Version Notification for draft-kompella-mpls-rmr-00.txt

Hi Folks,

This is a draft on making MPLS more efficient in ring networks.  I have come around to understanding that:
a) rings are a special topology (there was a time that I didn't appreciate that);
b) MPLS is pretty inefficient in rings (that is/was quite obvious).

This draft attempts to fix that, both by making protection much more efficient, and by making configuration much easier.

Your comments are highly welcome!

Cheers,
Kireeti.

---------- Forwarded message ----------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Sun, Oct 26, 2014 at 9:15 PM
Subject: New Version Notification for draft-kompella-mpls-rmr-00.txt
To: Kireeti Kompella <kireeti.kompella@gmail.com<mailto:kireeti.kompella@gmail.com>>



A new version of I-D, draft-kompella-mpls-rmr-00.txt
has been successfully submitted by Kireeti Kompella and posted to the
IETF repository.

Name:           draft-kompella-mpls-rmr
Revision:       00
Title:          Resilient MPLS Rings
Document date:  2014-10-26
Group:          Individual Submission
Pages:          7
URL:            http://www.ietf.org/internet-drafts/draft-kompella-mpls-rmr-00.txt
Status:         https://datatracker.ietf.org/doc/draft-kompella-mpls-rmr/
Htmlized:       http://tools.ietf.org/html/draft-kompella-mpls-rmr-00


Abstract:
   This document describes the use of the MPLS control and data planes
   on ring topologies.  It describes the special nature of rings, and
   proceeds to show how MPLS can be effectively used in such topologies.
   It describes how MPLS rings are configured, auto-discovered and
   signaled, as well as how the data plane works.  Companion documents
   describe the details of discovery and signaling for specific
   protocols.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat



--
Kireeti