Skip to main content

Last Call Review of draft-ietf-softwire-map-10
review-ietf-softwire-map-10-genart-lc-dupont-2014-10-10-00

Request Review of draft-ietf-softwire-map
Requested revision No specific revision (document currently at 13)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-10-10
Requested 2014-09-27
Authors Ole Trøan , Wojciech Dec , Xing Li , Congxiao Bao , Satoru Matsushima , Tetsuya Murakami , Tom Taylor
I-D last updated 2014-10-10
Completed reviews Genart Last Call review of -10 by Francis Dupont (diff)
Genart Last Call review of -11 by Francis Dupont (diff)
Secdir Last Call review of -10 by Brian Weis (diff)
Opsdir Last Call review of -10 by Fred Baker (diff)
Opsdir Last Call review of -10 by Nevil Brownlee (diff)
Assignment Reviewer Francis Dupont
State Completed
Request Last Call review on draft-ietf-softwire-map by General Area Review Team (Gen-ART) Assigned
Reviewed revision 10 (document currently at 13)
Result Ready
Completed 2014-10-10
review-ietf-softwire-map-10-genart-lc-dupont-2014-10-10-00
I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-softwire-map-10.txt
Reviewer: Francis Dupont
Review Date: 20141009
IETF LC End Date: 20141010
IESG Telechat date: 20141016

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 First please note I participated to Softwire WG work so it is possible
the document is not understantable by someone who has no knowledge
about the topic. I'll ask another member of the gen-art team to look
at it to check this particular point.
Other comments:
 - there are more than 5 authors. RFC 7322 (the new RFC Style Guide)
  provides an accurate (i.e., more than previously) indication
  about this problem.

 - ToC page 2 and 13 page 20: Acknowledgements -> Acknowledgments

 - 1 page 3: (FYI comment): RFC 1933 automatic tunneling was
  historically the first way to run IPv6 (end of March 1995
  when IPv6 over Ethernet ran only at the July IETF meeting
  the same year). So in fact the RFC was published in 1996
  but the mechanism itself was implemented a year before...

 - 1 page 4: IMHO there is no need to expand the MAP abbrev
  at its first use because it is in the title (note this would
  not apply if it was in the Abstract).

 - 1 page 4: provider's(SP) -> provider's (SP)

 - 3 page 5: NAPT should be in the terminology, in particular
  because the standard abbrev is more NAT-PT

 - 3 page 5 and many other places: e.g. -> e.g., and i.e. -> i.e.,

 - 4 page 6: encapsulation/ -> encapsulation /

 - 4 page 7: figure 1 should be in one page (the RFC Editor should
  take care of this in his final editing).

 - 5 page 8: a missing closing parenthesis in "MAP BR (see Section 5.4."

 - 5.1 page 8: minimise -> minimize

 - 5.2 page 10: /prefix -> / prefix

 - 6 page 13: figure 8 in one page (cf figure 1)

 - 11 page 19: glitch in the text version:
  "Attacks facilitated by restricted port           set:"

 - 12 page 19 and 20, and Authors' Addresses page 32:
  CN is not a valid Country in a postal address, I suggest China
  or better P.R. China

 - A Example 3 page 25: please expand FMR in the example title.

 - A Example 5 page 26: avoid page break after a title

 - A Example 5 page 27 (twice): DHCP. -> DHCP

 - A Example 5 page 27: please expand BMR abbrev (i.e., make the text
  easier and more pleasant to read).

Regards

Francis.Dupont at fdupont.fr