[mpls] Mail regarding draft-chen-mpls-p2mp-egress-protection

Gregory Mirsky <gregory.mirsky@ericsson.com> Wed, 12 February 2014 23:26 UTC

Return-Path: <gregory.mirsky@ericsson.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 82E9D1A0022 for <mpls@ietfa.amsl.com>; Wed, 12 Feb 2014 15:26:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 lPvyswoqII6j for <mpls@ietfa.amsl.com>; Wed, 12 Feb 2014 15:26:15 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE751A002A for <mpls@ietf.org>; Wed, 12 Feb 2014 15:26:15 -0800 (PST)
X-AuditID: c618062d-b7f858e0000031c7-a8-52fc031225d4
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id C4.9E.12743.2130CF25; Thu, 13 Feb 2014 00:26:10 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0387.000; Wed, 12 Feb 2014 18:26:13 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "draft-chen-mpls-p2mp-egress-protection@tools.ietf.org" <draft-chen-mpls-p2mp-egress-protection@tools.ietf.org>
Thread-Topic: Mail regarding draft-chen-mpls-p2mp-egress-protection
Thread-Index: Ac8oSA4xaJC4UUoKSO2rSotsniXi5w==
Date: Wed, 12 Feb 2014 23:26:12 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B7619A2@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B7619A2eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUyuXRPrK4Q858gg8t7tS16Z29ntLi1dCWr A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJWxbqZmwSvTiplvr7E0MDbrdzFyckgImEjs +nyLEcIWk7hwbz1bFyMXh5DAEUaJVQtPMkE4yxkllt8+xg5SxSZgJPFiYw+YLSJQKvFi/Srm LkYODmYBZYlTd2VAwsICdhLHTu9lgihxlvj3/woLhK0n8bD1INgyFgFViU1/pzCBtPIK+Epc mJYFEmYEuuH7qTVgrcwC4hK3nsxngrhNQGLJnvPMELaoxMvH/1ghbEWJff3T2SHq8yU2/d8J FucVEJQ4OfMJywRG4VlIRs1CUjYLSRlEXEdiwe5PbBC2tsSyha+ZYewzBx4zIYsvYGRfxchR WpxalptuZLCJERghxyTYdHcw7nlpeYhRmoNFSZz3y1vnICGB9MSS1OzU1ILUovii0pzU4kOM TBycUg2M2y1yypINijktOL+9mX6r/JrD0x9HVVmSt9syZ4noPLMr/NGxrU5ur7mVcqT1oqXP vkcYm5mwcm1WEJb06z2x/MJnhVkXK0p7xYzuxFzXeDJ93fHb17rD0lrjClZMWn+69XRi9MOw r6eNeM9Fm1kxqBx+JRmcZ6Xl+LBPRzPZobLl7be/DHJKLMUZiYZazEXFiQCDrMWpXgIAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] Mail regarding draft-chen-mpls-p2mp-egress-protection
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 Feb 2014 23:26:18 -0000

Dear Authors,
I have couple comments to changes made in version 11 of the document:

*         Introduction. A statement that e2e may "provide slow fault recovery" been added. Of course, if an operator to use slower fault detection and opt for service restoration rather than protection, then fault recovery will be slow. But if we to compare apples to apples, then I find this assumption unsubstantiated and hence don't see enough motivation for the proposed solution.

*         Section 1.1 "Exactly how the failure is detected is out of scope for this document." I agree with this as long as you can demonstrate that egress failure can be detected and clearly identified specifically as egress failure in reasonable time.

Regards,
        Greg