Telechat Review of draft-ietf-i2nsf-problem-and-use-cases-15
review-ietf-i2nsf-problem-and-use-cases-15-genart-telechat-worley-2017-05-09-00
Request | Review of | draft-ietf-i2nsf-problem-and-use-cases |
---|---|---|
Requested revision | No specific revision (document currently at 16) | |
Type | Telechat Review | |
Team | General Area Review Team (Gen-ART) (genart) | |
Deadline | 2017-05-09 | |
Requested | 2017-04-26 | |
Authors | Susan Hares , Diego Lopez , Myo Zarny , Christian Jacquenet , Rakesh Kumar , Jaehoon Paul Jeong | |
I-D last updated | 2017-05-09 | |
Completed reviews |
Secdir Last Call review of -12
by Derek Atkins
(diff)
Genart Last Call review of -11 by Dale R. Worley (diff) Genart Telechat review of -12 by Dale R. Worley (diff) Genart Telechat review of -15 by Dale R. Worley (diff) |
|
Assignment | Reviewer | Dale R. Worley |
State | Completed | |
Request | Telechat review on draft-ietf-i2nsf-problem-and-use-cases by General Area Review Team (Gen-ART) Assigned | |
Reviewed revision | 15 (document currently at 16) | |
Result | Ready w/nits | |
Completed | 2017-05-09 |
review-ietf-i2nsf-problem-and-use-cases-15-genart-telechat-worley-2017-05-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 wait for direction from your document shepherd or AD before posting a new version of the draft. Document: draft-ietf-i2nsf-problem-and-use-cases-15 Reviewer: Dale R. Worley Review Date: 2017-05-09 IETF LC End Date: 2017-03-22 IESG Telechat date: 2017-05-11 Summary: This draft is basically ready for publication, but has nits that should be fixed before publication. There is one remaining nit: 2. Terminology Security Service Provider: A provider of security services to the customers (end-users or enterprises) using NSF equipment purchased from vendors or created by the service provider. Per my discussion with the authors, the intended style is to not specifically capitalize the term "security service provider". Hence, this entry headword should be "Security service provider". [END]