Last Call Review of draft-nottingham-how-did-that-get-into-the-repo-01

Request Review of draft-nottingham-how-did-that-get-into-the-repo
Requested rev. no specific revision (document currently at 01)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2020-03-12
Requested 2020-02-13
Authors Mark Nottingham
Draft last updated 2020-03-08
Completed reviews Genart Last Call review of -01 by Jouni Korhonen
Assignment Reviewer Jouni Korhonen
State Completed
Review review-nottingham-how-did-that-get-into-the-repo-01-genart-lc-korhonen-2020-03-08
Posted at
Reviewed rev. 01
Review result Ready with Nits
Review completed: 2020-03-08


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


Document: draft-nottingham-how-did-that-get-into-the-repo-??
Reviewer: Jouni Korhonen
Review Date: 2020-03-08
IETF LC End Date: 2020-03-12
IESG Telechat date: Not scheduled for a telechat

This very needed document is ready for publication as an Informational RFC with few minor nits.

Major issues:

Minor issues:
1) Line 116-117 states "This document uses ABNF [RFC5234], including by reference the  following rules: ALPHA, DIGIT."
Why RFC5234 APLHA and DIGIT rules need to be specifically called out?

Nits/editorial comments:
1) Line 106   s/ike/like
2) Line 106  Expand CSRF on the first use (and possibly give an informative reference to it).