Re: [mpls] Ben Campbell's No Objection on draft-ietf-mpls-mldp-node-protection-05: (with COMMENT)

IJsbrand Wijnands <ice@cisco.com> Mon, 28 September 2015 19:40 UTC

Return-Path: <ice@cisco.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 2DA651B2C2C; Mon, 28 Sep 2015 12:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 7nzKZwwG4tbs; Mon, 28 Sep 2015 12:40:42 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2FF1B2C1C; Mon, 28 Sep 2015 12:40:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1221; q=dns/txt; s=iport; t=1443469241; x=1444678841; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=h5j4nFkMIHxVynUI8ZRrKxZDLklOhAJVzf331PSraD8=; b=d8BKvq596Dz/g1HgvoROwIJ2YAzBU63yFmYvZd5dubfsxqa7mzozi72U 2Vq2bBQ4YUPKpchVmqPBavrR5RQTkMf0TZe0q7nWRZ/aaI4YPmRs0FarT k3RPm0yWuuwddFCv1sF0SYQixZ+jBNNQu0wZ3hboGyhqspju2UaN+tDxF I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C/BABtlglW/xbLJq1drW4FAYENky2HdAKCBxIBAQEBAQEBgQqEJQEBBCNWEAsaAiYCAlcGLogTtxCUVQEBAQEBAQEBAQEBAQEBAQEBAQEZgSKFCoJWgm6EWjMHgmkvgRQBBJVwjQ+bPygIM4JDgUA8iVQBAQE
X-IronPort-AV: E=Sophos;i="5.17,604,1437436800"; d="scan'208";a="611899963"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 28 Sep 2015 19:40:39 +0000
Received: from ams-iwijnand-88111.cisco.com (ams-iwijnand-88111.cisco.com [10.60.202.92]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t8SJecOO022076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Sep 2015 19:40:38 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <64A18C22-B877-40A1-9C08-FFA3291658B1@nostrum.com>
Date: Mon, 28 Sep 2015 21:40:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <702FC7E4-4AEB-48EE-8053-066506130C7C@cisco.com>
References: <20150914220331.5981.89192.idtracker@ietfa.amsl.com> <7DD892A2-37EF-435E-A8F5-9167436DA808@cisco.com> <64A18C22-B877-40A1-9C08-FFA3291658B1@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/pL78BJmLSBreBC3mHAw7mGo95Qg>
Cc: mpls@ietf.org, mpls-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-mpls-mldp-node-protection.shepherd@ietf.org, draft-ietf-mpls-mldp-node-protection@ietf.org, draft-ietf-mpls-mldp-node-protection.ad@ietf.org
Subject: Re: [mpls] Ben Campbell's No Objection on draft-ietf-mpls-mldp-node-protection-05: (with COMMENT)
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: <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: Mon, 28 Sep 2015 19:40:46 -0000

Hi Ben,

>>> 
>> 
>> Both MUST be included.
> 
> Then I suggest something like "Both the PRL MP Status and an MP FEC TLV MUST…"

Ok, I’ll make that change.

> 
>> 
>>> 
>>> -- 4.1.3, last paragraph:
>>> Just “recommended”? Is link flapping a minor enough that it doesn't
>>> justify a MUST?
>> 
>> Well, its really an implementation choice to save resources being using in deleting and re-creating the tLDP session. If the implementation has means to deal with this or has other mechanism to solve this problem, that is fine too.
> 
> Okay, A few words to that effect might be helpful.

Well, in that section I’m already making the reader aware of the fact that a tLDP session may be flapping due to link flapping, and what solution can be applied to mitigate it. I don’t think more words are necessary here. Are you ok if we keep it like it is?

> 
> 
> [...]
> 
>>> 
>>> "MUST encode PLR Status Value Element": Missing article.
>> 
>> What do you mean here?
> 
> "MUST encode _the_ PLR Status Value Element". (or possibly _a_ PRL Status Value Element)

Got it ;-)

Thx,

Ice.