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

Zhenlong Cui <c-sai@bx.jp.nec.com> Tue, 29 July 2014 00:31 UTC

Return-Path: <c-sai@bx.jp.nec.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 3F32B1A03DB for <mpls@ietfa.amsl.com>; Mon, 28 Jul 2014 17:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.693
X-Spam-Level:
X-Spam-Status: No, score=-1.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 z4aRs0deT14a for <mpls@ietfa.amsl.com>; Mon, 28 Jul 2014 17:31:00 -0700 (PDT)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [210.143.35.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C788C1A03CA for <mpls@ietf.org>; Mon, 28 Jul 2014 17:30:59 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.160]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id s6T0UvQi015138; Tue, 29 Jul 2014 09:30:57 +0900 (JST)
Received: from mailsv4.nec.co.jp (imss61.nec.co.jp [10.7.69.156]) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) with ESMTP id s6T0Uut11658; Tue, 29 Jul 2014 09:30:56 +0900 (JST)
Received: from mail02.kamome.nec.co.jp (mail02.kamome.nec.co.jp [10.25.43.5]) by mailsv4.nec.co.jp (8.13.8/8.13.4) with ESMTP id s6T0UuQX024302; Tue, 29 Jul 2014 09:30:56 +0900 (JST)
Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.145] [10.38.151.145]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-858461; Tue, 29 Jul 2014 09:29:55 +0900
Received: from BPXM18GP.gisp.nec.co.jp ([169.254.2.157]) by BPXC17GP.gisp.nec.co.jp ([10.38.151.145]) with mapi id 14.02.0328.011; Tue, 29 Jul 2014 09:29:54 +0900
From: Zhenlong Cui <c-sai@bx.jp.nec.com>
To: Loa Andersson <loa@pi.nu>, "draft-cui-mpls-tp-mfp-use-case-and-requirements@tools.ietf.org" <draft-cui-mpls-tp-mfp-use-case-and-requirements@tools.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] question on draft-cui-mpls-tp-mfp-use-case-and-requirements
Thread-Index: Ac+qbHJ5tXHiNxEaR9u2GgVZYwRxqA==
Date: Tue, 29 Jul 2014 00:29:54 +0000
Message-ID: <E703759D9A8E6446BEA7F57C9A91381A739DF8@BPXM18GP.gisp.nec.co.jp>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.38.126.83]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/Vc6OsqDcu6sTWud98B1kZ5sXlfc
Subject: Re: [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: Tue, 29 Jul 2014 00:31:01 -0000

Hi Loa,

Thank you for your question and repeating on the list.

"n>=m" - it's a typical use case of m:n protection, but isn't a limitation. I apologize for the confusion.
I agree with you that could n be lower, equal or higher than m in the m:n architecture.

We will incorporate your comments to the next version of this draft.

BR,
Zhenlong


> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: Saturday, July 26, 2014 9:29 PM
> To: draft-cui-mpls-tp-mfp-use-case-and-requirements@tools.ietf.org; mpls@ietf.org; Cui Zhenlong(崔 珍龍)
> Subject: question on draft-cui-mpls-tp-mfp-use-case-and-requirements
> 
> 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