Re: IPv6 w.g. Last Call on "Link Scoped IPv6 Multicast Addresses"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IPv6 w.g. Last Call on "Link Scoped IPv6 Multicast Addresses"
On Wed, 22 Oct 2003, Pekka Savola wrote:
> - put it in RFC3306 address, like FF32:40:fe80:<stuff>:<group-id> or
> FF32:A:fe80:<stuff>:<group-id>.
> this would leave 64 bits space to generate an address, assuming the
> group-id is 32.
> - the 64 bits (<stuff>) could be the interface ID of the link-local
> address, or something else completely, like a random number.
oops.. a miscalculation; this would leave (about) 48 bits for "stuff"
rather than 64.. assuming the group-id would be 32, which it wouldn't need
to be.
regardless of that, the point seems valid: there seem to be little need
for this spec.
of course, the simplest way would be use the about 48 bits or 80 bits to
randomly generate an address. The collision probability is insignificant.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.