RE: draft-ietf-v6ops-rfc3330-for-ipv6 WGLC

["Durand, Alain" <Alain_Durand@cable.comcast.com>]

Here is my review of  draft-ietf-v6ops-rfc3330-for-ipv6:

A) "...addresses should not be advertised and should be filtered out
when
   received"

I found this text a bit vague. It does not say advertised to whom
nor explain if such routes learned via a routing protocol
should be rejected (by default ?) or if special filters
should be put in place (by default ?) to reject any incoming
packets containing those addresses...
It does not say either if this applies to routers or hosts.

I'd rather like to see the sentence used in RFC3330:

"Addresses within this block should not appear on the public Internet"

B) The document should mention something about IPv4 compatible
addresses,
if only to say they were deprecated (are they really? I lost track).

C) What about addresses outside of 2::/3?

D) The document should have a normative reference to RFC3513

E) Actually, re-reading RFC3513, I found that most of the information
   is already there in much greater details.
   The value-added of this document is to talk about old 6bone, 6to4 &
Teredo.
   It is not obvious to *me* that this is enough to justify its
publication,
   but it may be for others.

F) Shouldn't this become an IANA registry? In that case, shouldn't this
   document have an IANA section?

    - Alain.