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

"Ben Campbell" <ben@nostrum.com> Thu, 17 September 2015 00:43 UTC

Return-Path: <ben@nostrum.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 BBFDF1A9027; Wed, 16 Sep 2015 17:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 4TGgIP4uJIH6; Wed, 16 Sep 2015 17:43:11 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94D0B1A6FFB; Wed, 16 Sep 2015 17:43:11 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t8H0guOH099197 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 16 Sep 2015 19:43:06 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: IJsbrand Wijnands <ice@cisco.com>
Date: Wed, 16 Sep 2015 19:42:55 -0500
Message-ID: <64A18C22-B877-40A1-9C08-FFA3291658B1@nostrum.com>
In-Reply-To: <7DD892A2-37EF-435E-A8F5-9167436DA808@cisco.com>
References: <20150914220331.5981.89192.idtracker@ietfa.amsl.com> <7DD892A2-37EF-435E-A8F5-9167436DA808@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/3xqc1998XHJmDWbfuLDbi95KE6Q>
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: Thu, 17 Sep 2015 00:43:12 -0000

On 16 Sep 2015, at 5:04, IJsbrand Wijnands wrote:

> Hi Ben,
>
>> -- 2.3, last paragraph: "Along with the PLR MP Status a MP FEC TLV 
>> MUST
>> be included"
>> Does that mean that both MUST be included, or if the first is 
>> included,
>> the second MUST also be?
>
> Both MUST be included.

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

>
>>
>> -- 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.


[...]

>>
>> "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)

Thanks!

Ben.