Last Call Review of draft-ietf-mboned-deprecate-interdomain-asm-05
review-ietf-mboned-deprecate-interdomain-asm-05-secdir-lc-mandelberg-2019-12-24-00
| Request | Review of | draft-ietf-mboned-deprecate-interdomain-asm |
|---|---|---|
| Requested revision | No specific revision (document currently at 07) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2019-12-23 | |
| Requested | 2019-12-09 | |
| Authors | Mikael Abrahamsson , Tim Chown , Lenny Giuliano , Toerless Eckert | |
| I-D last updated | 2019-12-24 | |
| Completed reviews |
Rtgdir Last Call review of -05
by Loa Andersson
(diff)
Secdir Last Call review of -05 by David Mandelberg (diff) Genart Last Call review of -05 by Dale R. Worley (diff) Opsdir Last Call review of -05 by Carlos Pignataro (diff) |
|
| Assignment | Reviewer | David Mandelberg |
| State | Completed | |
| Request | Last Call review on draft-ietf-mboned-deprecate-interdomain-asm by Security Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/secdir/6tUV814_zM-0lhksko2WKy8MBGo | |
| Reviewed revision | 05 (document currently at 07) | |
| Result | Has issues | |
| Completed | 2019-12-15 |
review-ietf-mboned-deprecate-interdomain-asm-05-secdir-lc-mandelberg-2019-12-24-00
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. The summary of the review is Ready with issues. Section 3.2.3 talks about using source addresses for security. Doesn't that security rely on adoption of BCP38? (Or does the multicast destination address make BCP38 irrelevant here?)