Early Review of draft-ietf-trill-rfc7180bis-04
review-ietf-trill-rfc7180bis-04-rtgdir-early-white-2015-05-13-00

Request Review of draft-ietf-trill-rfc7180bis
Requested rev. no specific revision (document currently at 07)
Type Early Review
Team Routing Area Directorate (rtgdir)
Deadline 2015-05-13
Requested 2015-05-13
Other Reviews Genart Last Call review of -06 by Meral Shirazipour (diff)
Secdir Telechat review of -05 by Catherine Meadows (diff)
Opsdir Last Call review of -06 by Susan Hares (diff)
Review State Completed
Reviewer Russ White
Review review-ietf-trill-rfc7180bis-04-rtgdir-early-white-2015-05-13
Posted at http://www.ietf.org/mail-archive/web/rtg-dir/current/msg02580.html
Reviewed rev. 04 (document currently at 07)
Review result Has Nits
Draft last updated 2015-05-13
Review completed: 2015-05-13

Review
review-ietf-trill-rfc7180bis-04-rtgdir-early-white-2015-05-13

Hello,

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 ‚Äč

http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir



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-trill-rfc7180bis-04
Reviewer: Russ White
Review Date: 10 April 2015
Intended Status: Proposed Standard

Summary: 

This document is basically ready for publication, but has nits that should be considered prior to publication-- (I found one very minor nit, see below). 

Comments:

This document is difficult to understand, as it modifies several other documents that must be examined in parallel to understand the modifications being made. However, given that the TRILL documents are complex on their own, and this document "sweeps up" various changes across multiple documents while replacing another document, it is readable and serves the purpose for which it is intended well. Overall, this document is complex but readable; someone who understands a TRILL implementation should find it fairly navigable. 

I did check the IANA registries, references, and modifications proposed in this document; I could find no problems with the references, modifications, or registry information as described in the document.

Major Issues:

No major issues found.

Minor Issues:

No minor issues found.

Nits:

10. TRILL Header Update (New)
The TRILL header has been updated from its original specification in
[RFC6325] by [RFC7455] and [RFC7179] and is further updated by this
document. The TRILL header is now as show in the figure below which
is followed by references for all of the fields.

show/shown

==

Russ