[Idr] Rtgdir early review of draft-ietf-idr-capabilities-registry-change-05

Christian Hopps via Datatracker <noreply@ietf.org> Wed, 12 June 2019 02:27 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 367851200EF; Tue, 11 Jun 2019 19:27:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Christian Hopps via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
Cc: idr@ietf.org, ietf@ietf.org, draft-ietf-idr-capabilities-registry-change.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Christian Hopps <chopps@chopps.org>
Message-ID: <156030646312.23122.13759790091066171911@ietfa.amsl.com>
Date: Tue, 11 Jun 2019 19:27:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VKRKzX-mArttzQ9sQB2Td3m2HBA>
Subject: [Idr] Rtgdir early review of draft-ietf-idr-capabilities-registry-change-05
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: Wed, 12 Jun 2019 02:27:43 -0000

Reviewer: Christian Hopps
Review result: Ready


I have been selected to do a routing directorate “early” review of this draft.


The routing directorate will, on request from the working group chair, perform
an “early” review of a draft before it is submitted for publication to the
IESG. The early review can be performed at any time during the draft’s lifetime
as a working group document. The purpose of the early review depends on the
stage that the document has reached.

As this document is in working group last call, my focus for the review was to
determine whether the document is ready to be published. Please consider my
comments along with the other working group last call comments.

For more information about the Routing Directorate, please see

Document: draft-ietf-idr-capabilities-registry-change-05.txt
Reviewer: Christian Hopps
Review Date: June 11, 2019
Intended Status: Standards Track


No issues found. This documents is ready to proceed to the IESG.


The draft is very readable, and ready for publication.

For my own curiosity: while perusing the per revision changes, I saw "0 -
Reserved" was added then removed from the registration procedures table, but
"255 - Reserved" was left in. I figure "0" was removed b/c it's not a range and
it is reserved in the actual capability registry; however, why wouldn't this
logic then also apply to "255"?