[Idr] Opsdir last call review of draft-ietf-idr-tunnel-encaps-19

Jouni Korhonen via Datatracker <noreply@ietf.org> Sun, 04 October 2020 19:38 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A203A09D1; Sun, 4 Oct 2020 12:38:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: last-call@ietf.org, idr@ietf.org, draft-ietf-idr-tunnel-encaps.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160184032571.6799.6133110818746519025@ietfa.amsl.com>
Reply-To: Jouni Korhonen <jouni.nospam@gmail.com>
Date: Sun, 04 Oct 2020 12:38:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/6U8ln1bCBIuFNW1tb4C855Z64Dc>
Subject: [Idr] Opsdir last call review of draft-ietf-idr-tunnel-encaps-19
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Oct 2020 19:38:46 -0000

Reviewer: Jouni Korhonen
Review result: Has Nits

I find this document ready for publication. Some editorial nits and generic
comments below:

Editorials:
* Lines 522-525: Using parenthesis around references is a bit odd looking.
However, the RFC editor can decide what to do with this kind of style. The same
style is used also in other places of the document, while the usual without
parenthesis is also used. * There are several cases where an acronym is used
before expanding it or never expanding it (such as AS). However, the RFC editor
will likely take care of these. * Line 1060 opens a parenthesis and text in it
but never closes it. * Line 1533 s/section/Section * Section 13 IANA
considerations:
  - There is a separate sub-Section for RFC556 and RFC5640. However, there is
  no sub-Section for RFC5512, which is handles in the abstract of Section 13.
  Consider adding an equivalent sub-Section for RFC5512 as well.

Comments:
* I believe the three downrefs reported by IDnits are required for this
document.