Last Call Review of draft-halpern-gendispatch-antitrust-08
review-halpern-gendispatch-antitrust-08-secdir-lc-roca-2024-05-30-00
Request | Review of | draft-halpern-gendispatch-antitrust |
---|---|---|
Requested revision | No specific revision (document currently at 09) | |
Type | IETF Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2024-06-14 | |
Requested | 2024-05-17 | |
Authors | Joel M. Halpern , Jay Daley | |
I-D last updated | 2024-10-30 (Latest revision 2024-06-20) | |
Completed reviews |
Genart IETF Last Call review of -08
by Susan Hares
(diff)
Artart IETF Last Call review of -08 by Julian Reschke (diff) Secdir IETF Last Call review of -08 by Vincent Roca (diff) Dnsdir IETF Last Call review of -08 by Geoff Huston (diff) Dnsdir Telechat review of -09 by Geoff Huston |
|
Assignment | Reviewer | Vincent Roca |
State | Completed | |
Request | IETF Last Call review on draft-halpern-gendispatch-antitrust by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/2MveC1g1Fw2ldUv5wj9EoxQVWq4 | |
Reviewed revision | 08 (document currently at 09) | |
Result | Ready | |
Completed | 2024-05-30 |
review-halpern-gendispatch-antitrust-08-secdir-lc-roca-2024-05-30-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. Summary: Ready This document has no security implication. <secdir cap off> However, as a chairman of an IRTF RG (NWCRG) previously confronted with hostile behavior through late IPR declarations (i.e., once RFCs have been published) from longstanding active group participants, I came to the conclusion that a player can easily block a whole domain by means of FUD strategies and a portfolio of patents of dubious solidity and manifestly misused. And there's not much we can do at IETF level, unfortunately. </secdir cap off> Regards, Vincent