[mpls] question on draft-cui-mpls-tp-mfp-use-case-and-requirements

Loa Andersson <loa@pi.nu> Sat, 26 July 2014 12:28 UTC

Return-Path: <loa@pi.nu>
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 A48C91B27A0 for <mpls@ietfa.amsl.com>; Sat, 26 Jul 2014 05:28:55 -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, RP_MATCHES_RCVD=-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 5KU1ya8ZyHBi for <mpls@ietfa.amsl.com>; Sat, 26 Jul 2014 05:28:53 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A34661B2794 for <mpls@ietf.org>; Sat, 26 Jul 2014 05:28:53 -0700 (PDT)
Received: from [172.16.57.142] (unknown [206.47.221.210]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id BBC5B1802B19; Sat, 26 Jul 2014 14:28:51 +0200 (CEST)
Message-ID: <53D39F0D.6050209@pi.nu>
Date: Sat, 26 Jul 2014 14:29:01 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: draft-cui-mpls-tp-mfp-use-case-and-requirements@tools.ietf.org, "mpls@ietf.org" <mpls@ietf.org>, c-sai@bx.jp.nec.com
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/qyQTY7WQVWjs3wfnTn4PCe8UMEQ
Subject: [mpls] question on draft-cui-mpls-tp-mfp-use-case-and-requirements
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: Sat, 26 Jul 2014 12:28:55 -0000

Zhenlong,

draft-cui-mpls-tp-mfp-use-case-and-requirements in the mpls wg
yesterday. I had a question that was not very clear, I try to repeat it
here.

In slide 3 you say hat that:


"In the m:n architecture, the m backup paths(p1,p2)
  are sharing backup resource for n working paths, as
  shown in the following example(modeling)."

In slide 5 you say:

" The m backup paths should be sharing backup
   resource for n working paths, where n>=m."

It is not entirely clear if you say that n being a lower number is an
cost optimization or if it is part of the architecture.

 From a strictly architectural could n be lower, equal or higher than m,
i.e. you can protect m working paths with m+x protecting paths. Where
x can be any positive or negative number (as long as it give you at
least some resources for protection).

/Loa



-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64