The document says:
scop <= 2. The value of this multicast address is necessary to
distinguish between an Interface ID-based multicast address and a
unicast-prefix-based multicast address. If scop <= 2, the former MUST
be used. That is, this document updates the [RFC 3306], which
describes the latter.
I'm trying to understand why the RFC 3306 are so broken for scope <=2
that they can not be used.
While using the new address format for scope <= 2 would presumably be
preferred I don't see why prohibiting (as the "MUST" above does)
the use of RFC 3306 for those scopes.
If prohibiting them is the right thing I think the document should state why.
The example says:
This is an example of an interface ID-based multicast address with
link-local scope. For example in an Ethernet environment, if the
link-local unicast address is FE80::12:34:56:78:90:AB, the multicast
prefix of the host is FF32:0:1234:56FF:FE78:90AB::/96. For SSM,
multicast address will be FF32::/96.
Typo (I think): FE80::12:34:56:78:90:AB should be FE80::1234:5678:90AB
and a better example would have a 64 bit iid (the above one has 16 leading
zeros). Such as
FE80::a12:34ff:fe56:7890
resulting in
FF32:0:a12:34ff:fe56:7890::/96
Erik
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
