Last Call Review of draft-ietf-dccp-udpencap-
review-ietf-dccp-udpencap-secdir-lc-tsou-2012-06-19-00
| Request | Review of | draft-ietf-dccp-udpencap |
|---|---|---|
| Requested revision | No specific revision (document currently at 11) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2012-06-01 | |
| Requested | 2012-05-18 | |
| Authors | Thomas R. Phelan , Gorry Fairhurst , Colin Perkins | |
| I-D last updated | 2020-01-21 (Latest revision 2012-06-25) | |
| Completed reviews |
Secdir IETF Last Call review of -??
by Tina Tsou (Ting ZOU)
|
|
| Assignment | Reviewer | Tina Tsou (Ting ZOU) |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-dccp-udpencap by Security Area Directorate Assigned | |
| Result | Ready | |
| Completed | 2012-06-19 |
review-ietf-dccp-udpencap-secdir-lc-tsou-2012-06-19-00
Hi, 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. I find one case which can be a small disadvantage: both sides have to be updated to use tunneling, even if only one side is blocked by NAT. Can we handle this case? Tina Sent from my IPv6 address 2001:0:4137:9e76:20f1:518:f56e:f6a5