[mpls] RtgDir review: draft-ietf-mpls-lsp-ping-reply-mode-simple-03.txt

Dan Frost <frost@mm.st> Wed, 19 August 2015 16:50 UTC

Return-Path: <frost@mm.st>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id F0D5D1A1AA3 for <mpls@ietfa.amsl.com>; Wed, 19 Aug 2015 09:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 4t6p69Ux9l47 for <mpls@ietfa.amsl.com>; Wed, 19 Aug 2015 09:49:54 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B7B91A1AB6 for <mpls@ietf.org>; Wed, 19 Aug 2015 09:49:53 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 430B32071E for <mpls@ietf.org>; Wed, 19 Aug 2015 12:49:52 -0400 (EDT)
Received: from web4 ([]) by compute2.internal (MEProxy); Wed, 19 Aug 2015 12:49:52 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=mm.st; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=FO/ pagLMFmmO0yxfVj5Xss6R0OY=; b=mZVtuZgOL4yW0T0+ON8ds6YkpSQ1RrhPcoN mrpruwH+yHOdjaqKLqyreH8JR2PWABvCYGIZjG5H8mTk9mQ0S6+soBHn3mrqQ/Qs r88mISCjk9zgMAlJBYKYVUOI7lUJsxhU65fkzU7GzoNxpwQPChO55Rap3UCrMeEF LFhulhIE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=FO/pagLMFmmO0yxfVj5Xss6R0OY=; b=pLM2T ZyKmGW68UU3HnvkxZj2882v1A+hE4UBg370zhRKkIt705IkAt0WJRLVDzc0F5pLh GbKbiWV2LD60segatn4yA3u88pCWB6n1n5PPnzlPL1i8afA+dmwL3rSt5L/kfamp bgbRtAqqONhqVpZYHaMcJGXLMJ7Cu80NzUeoWs=
Received: by web4.nyi.internal (Postfix, from userid 99) id 17C0E1045E9; Wed, 19 Aug 2015 12:49:52 -0400 (EDT)
Message-Id: <1440002992.3391528.360465129.4D684834@webmail.messagingengine.com>
X-Sasl-Enc: U8tph645JKrQmcN+tJwKFTM3AFU9iceLTU2j2dQLw4VM 1440002992
From: Dan Frost <frost@mm.st>
To: rtg-ads@tools.ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-4fee8ba5
Date: Wed, 19 Aug 2015 17:49:52 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/sTlAjD7NrJQ98H9V2q5wt83p_2E>
Cc: rtg-dir@ietf.org, draft-ietf-mpls-lsp-ping-reply-mode-simple@tools.ietf.org, mpls@ietf.org
Subject: [mpls] RtgDir review: draft-ietf-mpls-lsp-ping-reply-mode-simple-03.txt
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: Wed, 19 Aug 2015 16:50:01 -0000


I have been selected as the Routing Directorate reviewer for this draft.
The Routing Directorate seeks to review all routing or routing-related
drafts as they pass through IETF last call and IESG review, and
sometimes on special request. The purpose of the review is to provide
assistance to the Routing ADs. For more information about the Routing
Directorate, please see

Although these comments are primarily for the use of the Routing ADs, it
would be helpful if you could consider them along with any other IETF
Last Call comments that you receive, and strive to resolve them through
discussion or by updating the draft.

Document: draft-ietf-mpls-lsp-ping-reply-mode-simple-03.txt
Reviewer: Dan Frost
Review Date: 19 Aug 2015
Intended Status: Standards Track


I have some minor concerns about this document that I think should be
resolved before publication.

This document addresses an important practical limitation affecting the
use of LSP Ping in deployed networks today.  It is for the most part
clearly written and complete, and contains helpful examples.

Major Issues:

No major issues found.

Minor Issues:

- Section 2, last paragraph: "This document adds one Reply Mode value to
describe the reverse LSP, ...".

This document does not appear to add a Reply Mode value, but rather to
modify the semantics of the "Reply via Specified Path (5)" Reply Mode,
as stated at the beginning of Section 3, so this sentence needs

- Section 3.1, first paragraph: Suggest adding RFC references for
associated LSPs, e.g. RFC 5960 for MPLS-TP.

- Section 3, general comment: This document is changing the semantics of
Reply Mode 5, and in particular changing the case of Mode 5 without a
Reply Path TLV from invalid to valid.  However, the document does not
appear to discuss interoperability issues in networks with a mix of
"old" and "new" LSRs.  This looks like something that should be
addressed explicitly.

- Section 3.1, last paragraph: This paragraph is very confusing and
either needs to be deleted or completely rewritten.  If, as it appears,
it is not changing existing requirements for IP addressing of LSP Ping
packets per RFCs 4379 and 7110, it should just be deleted.

- Section 4.1, preference ordering of reply options: The document
specifies that reply paths are to be preferred according to the order in
which they appear in the Reply Mode Order TLV.  However, it's not clear
from this document and RFC 7110 what the order semantics are of
including a Reply Path TLV with multiple sub-TLVs.  For instance, in
Section 4.1.1's example, FEC X and FEC Y are listed as different return
paths.  If they are different, what is their preference ordering and
where is this defined?

- General comment: It may be valuable for the authors to include a
Manageability Considerations or similar section to provide guidance to
implementors on configuration options, defaults, etc., particularly
given the operational difficulties that led to this document in the
first place.


There are a lot (too many to list here) of minor English grammar
problems, such as missing articles, throughout the text.  I would
suggest the editors do a grammatical review pass to clean these up as
much as possible before the RFC Editor stage.