Telechat Review of draft-ietf-pim-explicit-tracking-09
review-ietf-pim-explicit-tracking-09-genart-telechat-moriarty-2013-12-18-00
| Request | Review of | draft-ietf-pim-explicit-tracking |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | Telechat Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2013-12-17 | |
| Requested | 2013-12-12 | |
| Authors | Hitoshi Asaeda | |
| Draft last updated | 2013-12-18 | |
| Completed reviews |
Genart Telechat review of -09
by
Kathleen Moriarty
(diff)
Secdir Last Call review of -08 by Magnus Nystrom (diff) Secdir Telechat review of -09 by Magnus Nystrom (diff) Opsdir Telechat review of -09 by Sarah Banks (diff) |
|
| Assignment | Reviewer | Kathleen Moriarty |
| State | Completed Snapshot | |
| Review |
review-ietf-pim-explicit-tracking-09-genart-telechat-moriarty-2013-12-18
|
|
| Reviewed revision | 09 (document currently at 13) | |
| Result | Ready with Nits | |
| Completed | 2013-12-18 |
review-ietf-pim-explicit-tracking-09-genart-telechat-moriarty-2013-12-18-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-pim-explicit-tracking-09 Reviewer: Kathleen Moriarty Review Date: December 18, 2013 IETF LC End Date: ? IESG Telechat date: December 19, 2013 Summary: The document is ready with nits. It is well written and did a nice job of providing refernces throughout the document where needed. Major issues: Minor issues: Nits/editorial comments: In the second to last paragraph of section 6, the word “loose” should be “lose”: However, the downstream hosts may loose the data packets until the routing path is reestablished and the data forwarding is restarted. In the security consideration section, no comma is necessary in the following sentence as there are only two items in the list: In order to mitigate such threats, a router enabling the explicit tracking function may limit a total amount of membership information the router can store, or may rate-limit State-Change Report messages per host.