Last Call Review of draft-ietf-iasa2-rfc4071bis-08

Request Review of draft-ietf-iasa2-rfc4071bis
Requested rev. no specific revision (document currently at 11)
Type Last Call Review
Team Routing Area Directorate (rtgdir)
Deadline 2019-03-18
Requested 2019-03-07
Requested by Alvaro Retana
Authors Brian Haberman, Joseph Hall, Jason Livingood
Draft last updated 2019-03-11
Completed reviews Secdir Last Call review of -08 by Christian Huitema (diff)
Rtgdir Last Call review of -08 by Ben Niven-Jenkins (diff)
Genart Last Call review of -08 by Paul Kyzivat (diff)
This document will be reviewed by the IESG after IETF 104, so there's time...

I'm looking for a non-technical review related to any potential effect on the general IETF process: WG operation, document publication, etc.  I don't think there's any, but an extra pair of eyes for a quick review would be great.
Assignment Reviewer Ben Niven-Jenkins
State Completed
Review review-ietf-iasa2-rfc4071bis-08-rtgdir-lc-niven-jenkins-2019-03-11
Reviewed rev. 08 (document currently at 11)
Review result Ready
Review completed: 2019-03-11



I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-iasa2-rfc4071bis-08.txt
Reviewer: Ben Niven-Jenkins
Review Date: 11th March 2019
IETF LC End Date: 18th March 2019
Intended Status:  
Best Current Practice

Summary: No issues found. This document is ready for publication.

Comments: The document describes the structure of IASA 2.0 and is well written and easy to read.

Major Issues: No major issues found.

Minor Issues: No minor issues found.

Nits: Section 1, Introduction, paragraph 6 uses “IETF Administration LLC Executive Director” when the terminology section (4.1) uses “IETF LLC Executive Director”.