Comments on draft-ietf-6man-multicast-scopes-02

[Jouni Korhonen <[e-mail]>]

Sorry for being late with my comments but here we go anyway.

I think this document is almost ready. Few comments/questions
though.

** In Section 3:

   NEW:

     o  The boundaries of zones of a scope are defined by the IPv6
        addressing architecture [RFC4291].

Ok.. this is confusing since it is *this* I-D that updates RFC4291
with a new Realm-scope aware boundary, thus RFC4291 would eventually
point back to this I-D. So while the above change is correct it
definitely is confusing.

Just like with draft-ietf-6man-multicast-addr-arch-update I see a
need for RFC4291bis, where Section 1 like enhancements would
belong to rather than stacking up I-Ds that patch things here and
there.  Again I recon it might be too late for this, though.

** Section 5

What would go under the other scopes than 3? Shouldn't we say at
least something about the possible future use of those? Will they
also list RFCs? 

** Section 7

I don't think it is sufficient just to refer to RFC4291 (almost non
existent) security considerations. For example there should be a
reference to RFC4007 which actually has text related to security
considerations of boundaries and scopes.

- JOuni