[secdir] Secdir review of draft-ietf-multimob-pmipv6-source

[Radia Perlman <[e-mail]>]

On Tue, Dec 17, 2013 at 7:11 PM, Radia Perlman <[e-mail]>wrote:

> 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 document combines mobile IPv6 with multicast.  It's unnecessarily
difficult to read.  There should be a section upfront expanding all the
acronyms, at the very least.  For instance, MLD, PMIPv6, PIM, MAG, HNP.
 Some of these (like MAG) are expanded in the text the first time they are
used, but most are not, and people aren't necessarily going to remember it
because of seeing it once, and there's no downside to having a section in
the introduction called "acronyms".

It also wouldn't hurt to explain "proxy mobile IPv6 domains"  (not just
expand the acronym PMIPv6).

I admit I don't completely understand this document, because I didn't want
to have to read all the other documents that this thing assumes you
understand, but I think I get the general idea.

I think the security considerations section covers most of the downsides,
but it doesn't talk about how multicast in general can amplify DOS packets.
 And with mobility, there are two problems with having a proxy sending the
multicast (unless it's tunneled, which would be OK).  If packets with an IP
source address can come from a different location, then loops won't be
detected (the security considerations section mentions that), but also,
it's harder for the infrastructure to filter out packets from forged IP
addresses.

Radia