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 rev. no specific revision (document currently at 06)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2019-12-23
Requested 2019-12-09
Authors Mikael Abrahamsson, Tim Chown, Leonard Giuliano, Toerless Eckert
Draft 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 Worley (diff)
Opsdir Last Call review of -05 by Carlos Pignataro (diff)
Assignment Reviewer David Mandelberg
State Completed
Review review-ietf-mboned-deprecate-interdomain-asm-05-secdir-lc-mandelberg-2019-12-24
Posted at https://mailarchive.ietf.org/arch/msg/secdir/6tUV814_zM-0lhksko2WKy8MBGo
Reviewed rev. 05 (document currently at 06)
Review result Has Issues
Review completed: 2019-12-15

Review
review-ietf-mboned-deprecate-interdomain-asm-05-secdir-lc-mandelberg-2019-12-24

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?)