Last Call Review of draft-ietf-p2psip-rpr-10

Request Review of draft-ietf-p2psip-rpr
Requested rev. no specific revision (document currently at 11)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2013-09-30
Requested 2013-09-19
Authors Ning Zong, XingFeng Jiang, Roni Even, Yunfei Zhang
Draft last updated 2013-09-30
Completed reviews Genart Last Call review of -10 by Dan Romascanu (diff)
Genart Telechat review of -11 by Dan Romascanu
Opsdir Early review of -11 by Carlos Pignataro
Secdir Telechat review of -11 by Klaas Wierenga
Secdir Last Call review of -10 by Klaas Wierenga (diff)
Assignment Reviewer Dan Romascanu
State Completed
Review review-ietf-p2psip-rpr-10-genart-lc-romascanu-2013-09-30
Reviewed rev. 10 (document currently at 11)
Review result Ready with Issues
Review completed: 2013-09-30


I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at


Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-p2psip-rpr-10
Reviewer: Dan Romascanu
Review Date: 9/30/13
IETF LC End Date: 9/30/13
IESG Telechat date: 

Summary: Ready with minor and editorial issues

Major issues:

Minor issues:

[I-D.ietf-p2psip-drr] is an Informational Reference. It is mentioned in several places, out of which at least one makes reading the referred document mandatory for anybody who intends to write an implementation of this document. This place is Section 7 which states: 

> This document uses the new RELOAD overlay configuration element,
   "route-mode", inside each "configuration" element, as defined in DRR
   document [I-D.ietf-p2psip-drr].

Nits/editorial comments:

1. Section 3.1 RPR includes just one sub-section 3.1.1 with a similar title. It looks like the division of the text in a subsection is not needed. 

2. The title of Section 3.2 is 'Scenarios where RPR can be beneficial'. In fact only 3.2.3 describes such a scenario, while 3.2.1 and 3.2.2 describe cases which would ease deployment of RPR (managed environments, bootstrap nodes). In other words 3.2.1 and 3.2.2 describe cases when RPR could be deployed and 3.2.3 a case when RPR should be deployed. 

3. In Section 6.2.2: 

> The option value is illustrated in the following figure, defining the
   ExtensiveRoutingModeOption structure:

However no figure follows.