Last Call Review of draft-ietf-tsvwg-port-use-06
review-ietf-tsvwg-port-use-06-secdir-lc-harkins-2015-02-05-00
Request | Review of | draft-ietf-tsvwg-port-use |
---|---|---|
Requested revision | No specific revision (document currently at 11) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2015-02-17 | |
Requested | 2014-12-11 | |
Authors | Dr. Joseph D. Touch | |
I-D last updated | 2015-02-05 | |
Completed reviews |
Genart Last Call review of -06
by Dan Romascanu
(diff)
Genart Telechat review of -07 by Dan Romascanu (diff) Secdir Last Call review of -06 by Dan Harkins (diff) Opsdir Last Call review of -06 by Tim Wicinski (diff) |
|
Assignment | Reviewer | Dan Harkins |
State | Completed | |
Request | Last Call review on draft-ietf-tsvwg-port-use by Security Area Directorate Assigned | |
Reviewed revision | 06 (document currently at 11) | |
Result | Has nits | |
Completed | 2015-02-05 |
review-ietf-tsvwg-port-use-06-secdir-lc-harkins-2015-02-05-00
Hello, I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This draft provides some advice and recommendations on protocol port use to application and service designers. It has a nice, brief history of port usage and a nice list of guiding principles to help conserve port space. It will make a nice BCP. In my opinion it is Ready For Publication. With that said, I do have a small comment. In section 7.4 the draft says that TLS should be used to protect services that do not provide their own security directly. It might be worth while adding mention of DTLS and IPsec. And if the latter is not something that should be recommended then justification for that stance should be given. regards, Dan.