Re: [mpls] Spencer Dawkins' Discuss on draft-ietf-mpls-tp-shared-ring-protection-05: (with DISCUSS and COMMENT)

"Alvaro Retana (aretana)" <aretana@cisco.com> Thu, 25 May 2017 13:38 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BD312778E; Thu, 25 May 2017 06:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 qgF8J8WYzgLF; Thu, 25 May 2017 06:38:38 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D284E126B72; Thu, 25 May 2017 06:38:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9014; q=dns/txt; s=iport; t=1495719517; x=1496929117; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gy8u9O2FKPLlMOpqgyhVChRzeKaFyKkSXLdcn6ow7dE=; b=YNI1VKg7iKdS3Il9R7EyZKQf7Ie8oZvVSsm7tdXDZyaK1hPKIll7CcDY q3Zb7d6UbBNaxbDyGq8A8ySgG1gAapjGs6S99/2i2USNTfQa34sWbd/Bo wOjPkFD2z+dI8bjz6o3640x5o9PajkEgh3FsVCRtINTTzCAkcqX41xo5q o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CnAABT3SZZ/4oNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm5nYoENB4NoihiaBYgYhTiCD4YkAhqCYz8YAQIBAQEBAQEBayi?= =?us-ascii?q?FGQYjVhACAQg7BAMCAgIfERQRAgQBDQWJRUwDFa8UgiYrhwYNhAcBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEdhl+CCYJxgleFIS+CMQWWeYZvOwGOT4RYkXeLMokbAR8?= =?us-ascii?q?4gQpzFVgBhR2BSnaIF4ENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,391,1491264000"; d="scan'208,217";a="431283279"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 May 2017 13:38:37 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v4PDca1O020010 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 25 May 2017 13:38:36 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 25 May 2017 08:38:36 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Thu, 25 May 2017 08:38:36 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, "huubatwork@gmail.com" <huubatwork@gmail.com>
CC: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-tp-shared-ring-protection@ietf.org" <draft-ietf-mpls-tp-shared-ring-protection@ietf.org>, The IESG <iesg@ietf.org>, Eric Gray <Eric.Gray@ericsson.com>
Thread-Topic: Spencer Dawkins' Discuss on draft-ietf-mpls-tp-shared-ring-protection-05: (with DISCUSS and COMMENT)
Thread-Index: AQHS1T4CyeG/Rethf0qxjjuT6S+0OaIFVpgA///Y3YA=
Date: Thu, 25 May 2017 13:38:35 +0000
Message-ID: <4203C4E8-7DE2-4BA5-A2BC-D31AA37FE9ED@cisco.com>
References: <149565660910.8641.739437988075507213.idtracker@ietfa.amsl.com> <b342ad77-1cd2-ebc9-4c84-337eeb4a00e8@gmail.com> <CAKKJt-ewdvUik3qhC3zsSAREUOtKfGUEjwa2-69jes1pma94Fw@mail.gmail.com>
In-Reply-To: <CAKKJt-ewdvUik3qhC3zsSAREUOtKfGUEjwa2-69jes1pma94Fw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.174.242]
Content-Type: multipart/alternative; boundary="_000_4203C4E87DE24BA5A2BCD31AA37FE9EDciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/DM8Tayhjt85g3CMKJovKDBVUhiM>
Subject: Re: [mpls] Spencer Dawkins' Discuss on draft-ietf-mpls-tp-shared-ring-protection-05: (with DISCUSS and COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 May 2017 13:38:40 -0000

Huub:

Hi!

I don’t think that just putting a paragraph in the Introduction would be enough operational guidance.  Ideally, I would like to see a separate Section on Operational Considerations explaining when/why each should be considered.

Also, rfc5706 offers good guidance – I realize not all sections there would apply in this case.

Thanks!

Alvaro.

On 5/25/17, 9:58 AM, "iesg on behalf of Spencer Dawkins at IETF" <iesg-bounces@ietf.org<mailto:iesg-bounces@ietf.org> on behalf of spencerdawkins.ietf@gmail.com<mailto:spencerdawkins.ietf@gmail.com>> wrote:


At a minimum, I'd like to see guidance for operators in choosing among
the three protection mechanisms. Why would they choose any one of the
three?

[Huub] more explanatory text can be added, it could be in the introduction
proposed by Alvaro.

I only saw Alvaro saying that he also wanted operational guidance included, but it's very likely that whatever you do to answer Alvaro's Comment would answer this part of my DIscuss. We were complaining about the same thing, it's just that I was more concerned about it ;-)