Last Call Review of draft-ietf-softwire-map-t-05
review-ietf-softwire-map-t-05-opsdir-lc-kuarsingh-2014-10-17-00
Request | Review of | draft-ietf-softwire-map-t |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | IETF Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2014-10-28 | |
Requested | 2014-09-29 | |
Authors | Xing Li , Congxiao Bao , Wojciech Dec , Ole Trøan , Satoru Matsushima , Tetsuya Murakami | |
I-D last updated | 2020-01-21 (Latest revision 2014-12-02) | |
Completed reviews |
Genart IETF Last Call review of -05
by Dan Romascanu
(diff)
Genart IETF Last Call review of -05 by Dan Romascanu (diff) Genart Telechat review of -06 by Dan Romascanu (diff) Genart IETF Last Call review of -08 by Dan Romascanu Secdir IETF Last Call review of -05 by Taylor Yu (diff) Opsdir IETF Last Call review of -05 by Victor Kuarsingh (diff) |
|
Assignment | Reviewer | Victor Kuarsingh |
State | Completed | |
Request | IETF Last Call review on draft-ietf-softwire-map-t by Ops Directorate Assigned | |
Reviewed revision | 05 (document currently at 08) | |
Result | Has nits | |
Completed | 2014-10-17 |
review-ietf-softwire-map-t-05-opsdir-lc-kuarsingh-2014-10-17-00
Hello, I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the operational area directors. Document editors and WG chairs should treat these comments just like any other last call comments. Reviewed Draft: draft-ietf-softwire-map-t-06 for its operational impact. Intended status: Experimental Review Status: Ready with text nits Summary: This is a document which outlines the MAP-T (Mapping of Address and Port) stateless IPv6-IPv4 NAT64 based solution. Text Input: Section 7.1 Paragraph 2: old text “.. a CE requires an the IPv6 prefix to be assigned to the CE” new text “.. a CE requires an IPv6 prefix to be assigned to the CE.” Section 7.2 Paragraph 3: old text “.. no specific routes need to be advertised externally for MAP to operate, neither in IPv6 nor IPv4 BGP.” new text “.. no specific IPv6 or IPv4 routes need to be advertised externally outside the service provider’s network for MAP to operate.” I added this version of the sentence since it makes more sense to me. Also, you technically don’t need BGP on the ISP side (although I can’t a modern network which does not use it). Ops Related Comments and review This document is well thought out and has addressed the major items I would be looking at from an operational standpoint. Areas of focus for these types of technologies include ICMP handling (addressed in section 9), DoS and Spoofing attacks (addressed in section 14) and overall deployment guidance (provided throughout the document). The only item I did not see mentioned specifically was QoS. This is not a major issue given the Experimental status of the draft, and is likely easily addressed (perhaps there was discussion on this that I missed). Given the prevalence of video services in operator networks today, video propagation leveraging QoS may to be supported for end sites (in this case the MAP-T CE side). Regards, Victor K