Routing Area Directorate (rtgdir)
|Directorate (with reviews)||Name||Routing Area Directorate|
|Area||Routing Area (rtg)|
|Personnel||Chairs||Haomian Zheng, Luc André Burdet|
|Area Director||John Scudder|
|Secretaries||Haomian Zheng, Luc André Burdet|
Donald E. Eastlake 3rd
Himanshu C. Shah
Joel M. Halpern
Zhaohui (Jeffrey) Zhang
The Routing Area Directorate is tasked to help the Routing Area Directors by performing specific tasks as set out below. Additional tasks may be added to this list over time.
Review all documents submitted to the IESG for publication that have routing significance
How is Review Triggered?
Triggered by request for early review (by any AD or by any Routing Area WG chair)
Triggered by document moving to 'publication requested' state (for routing area documents)
Triggered by IETF last call (for non-routing area documents that get IETF last call)
Triggered by entry on the IESG agenda (for other documents)
Who Reviews Each Document?
Each document is assigned to an individual member of the routing directorate
Assignments are made on a round-robin basis across the directorate. This ensures that we make full use of all the directorate members, and that each document gets a good cross-area review. This may mean that a reviewer will review a document that they do not have a deep background in. This is fine as the reviewer can always at least do a review for readability - and lack of readability is the number one issue that causes delays at the IESG stage of processing.
Reviewer responds rapidly with decision "yes, I will do it in appointed time", "yes, I will do it but need more time", "no, I cannot do it".
Routing Directorate review is not a substitute for the ADs reviewing documents that have major routing area implications.
Assist ADs with judgment issues when requestedThe ADs may send email to the routing directorate list when they have issues that they want help with.