Review of draft-ietf-kitten-rfc6112bis-03

Tim Wicinski <> Mon, 02 January 2017 08:39 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 359F91294EF; Mon, 2 Jan 2017 00:39:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tim Wicinski <>
To: <>
Subject: Review of draft-ietf-kitten-rfc6112bis-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 02 Jan 2017 00:39:10 -0800
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 Jan 2017 08:39:10 -0000

Reviewer: Tim Wicinski
Review result: Ready


I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written with the intent of improving the
operational aspects of the IETF drafts. Comments that are not
addressed in last call may be included in AD reviews during the IESG
review.  Document editors and WG chairs should treat these comments
just like any other last call comments. 

Document Reviewed: draft-ietf-kitten-rfc6112bis

Status: Ready

Summary: The -03 version addressed the minor issues I had found during