Last Call Review of draft-ietf-softwire-dslite-multicast-14
review-ietf-softwire-dslite-multicast-14-genart-lc-dupont-2017-01-09-00

Request Review of draft-ietf-softwire-dslite-multicast
Requested revision No specific revision (document currently at 18)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2017-01-12
Requested 2016-12-29
Authors Mohamed Boucadair , Jacni Qin , Christian Jacquenet , Yiu Lee , Qian Wang
I-D last updated 2017-01-09
Completed reviews Intdir Early review of -12 by Zhen Cao (diff)
Intdir Early review of -12 by Tim Chown (diff)
Opsdir Last Call review of -14 by Jouni Korhonen (diff)
Genart Last Call review of -14 by Francis Dupont (diff)
Rtgdir Telechat review of -14 by Stig Venaas (diff)
Genart Telechat review of -16 by Francis Dupont (diff)
Opsdir Telechat review of -16 by Tim Chown (diff)
Assignment Reviewer Francis Dupont
State Completed
Request Last Call review on draft-ietf-softwire-dslite-multicast by General Area Review Team (Gen-ART) Assigned
Reviewed revision 14 (document currently at 18)
Result Ready w/nits
Completed 2017-01-09
review-ietf-softwire-dslite-multicast-14-genart-lc-dupont-2017-01-09-00
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

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-softwire-dslite-multicast-14.txt
Reviewer: Francis Dupont
Review Date: 20170106
IETF LC End Date: 2017012
IESG Telechat date: unknown

Summary: Ready with Nits

Major issues: None

Minor issues: please consider to publish this as a BCP (vs standard track)?
I don't know if this question is new or already got an answer,
this is why I kept the Ready summary. BTW the IANA section is empty
so there is nothing requiring a standard track document.

Nits/editorial comments: 
 - ToC page 3 and 10 page 16: Acknowledgements -> Acknowledgments 

 - 4.2 page 7: RECOMMENDED inside an explicitly "not normative"
  section 4

 - 6.1 page 11: in "The mB4 may create": may -> MAY?

 - 6.3 page 11: in "decapsulate the IPv6 packet": IPv6 -> IPv4

 - 7.2 page 13 figure 3 and 8.1.1 page 15 figure 4:
   mPreifx64 -> mPrefix64

 - 7.2 page 13 last paragraph: (S6,G6) -> (S6, G6)
  (I am not strict about space or not but in this paragraph there is
   already a (S6, G6))

 - 7.5 page 14: Global scope;) -> Global scope)

 - 8.4 page 16: please use a non-breaking space so (S6, G6) stays
  on the same line in the text version (and hopefully (S4, G4) too).

 - Authors' Addresses page 20: China -> PR China (or any variant
  including CN (ISO IS 3166 2 letter code))

Regards

Francis.Dupont@fdupont.fr