[mpls] Rtgdir last call review of draft-ietf-mpls-rmr-11

Susan Hares via Datatracker <noreply@ietf.org> Thu, 29 August 2019 09:15 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 15A8B120273; Thu, 29 Aug 2019 02:15:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Susan Hares via Datatracker <noreply@ietf.org>
To: <rtg-dir@ietf.org>
Cc: draft-ietf-mpls-rmr.all@ietf.org, mpls@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Susan Hares <shares@ndzh.com>
Message-ID: <156707010100.21081.6369578151637642112@ietfa.amsl.com>
Date: Thu, 29 Aug 2019 02:15:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/WJzSCraEoczQskQMmJZ9algKwes>
Subject: [mpls] Rtgdir last call review of draft-ietf-mpls-rmr-11
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Aug 2019 09:15:01 -0000

Reviewer: Susan Hares
Review result: Has Nits

Authors: Thank you for continuing to refine this document.  
Status: editorial nits:  

#1 - Section 3.3 paragraph 1, last sentence 
old/RMR is primarly intended for operation at the packet layer; 
       however, parallel links at hte lambda or fiber layer result in 
      parallel links at the packet layer./

question:  Did you want to say /may result/ intead of /result/

#2 - Section 3.7 - Would be easier to read if you included a diagram.
#3 - Section 4.4 - Would be easier to read if you included a diagram

Rational for requesting diagram: You are explaining the technology
that requires additional TLVs in other protocols (IGPS)

#4 - Section 5 - (editorial only)  This one section jars the reader 
to ask "why am I bothered with this section."   

I understand why you want to make this clear that this point. 
However, in section 1 you lay out the protocols. Do you also want to 
do this here?   Either choice works technically.  However this 
document is dually focused: summary of RMR concepts to 
those writing future specifications and RMR to those
desiring to install these solutions.   Does this section help 
those desiring to install these solutions to find the other document?