Genart last call review of draft-nottingham-rfc5988bis-05

Stewart Bryant <stewart.bryant@gmail.com> Wed, 24 May 2017 16:49 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3389D129B6C; Wed, 24 May 2017 09:49:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: gen-art@ietf.org
Cc: draft-nottingham-rfc5988bis.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-nottingham-rfc5988bis-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149564456407.28435.714290542306024853@ietfa.amsl.com>
Date: Wed, 24 May 2017 09:49:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U6_pYfIU5jIQV5JmCikDTPQMM0M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 May 2017 16:49:24 -0000

Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-nottingham-rfc5988bis-??
Reviewer: Stewart Bryant
Review Date: 2017-05-24
IETF LC End Date: 2017-05-26
IESG Telechat date: 2017-06-08

Summary:
This is a well written document, and ready for publication.

I found an IANA consideration a little confusing, but I am sure that
either IANA understand it or will ask for clarification.

Major issues:

Minor issues:
I found the IANA considerations confusing. Specifically it looks like
Section 4.1 refers to 
https://www.iana.org/assignments/message-headers/message-headers.xhtml
although it does not say so in so many words.

Assuming that to be the case the IANA text in section 4.1 (which
copies the text from RFC5688)
does not line up column by column with the text in the registry. I
assume that 
[RFC&rfc.number;] means [This RFC], but do not see where Author/Change
control fits in the 
registry.

Nits/editorial comments: 

In the intro and the abstract the text "a model for indicate the
relationships" is not good grammar.