Re: Reserved addresses in the SSM range

[zaid <zalbanna@MCI.NET>]

Is there a plan to use the GLOB mechanism
for SSM address allocation ?

Zaid
-----Original Message-----
From: Doron Rajwan <Doron@bandwiz.com>
To: ssm-interest@external.cisco.com <ssm-interest@external.cisco.com>
Date: Friday, August 04, 2000 11:03 PM
Subject: Reserved addresses in the SSM range



Regarding Hugh question about reserving addresses in the SSM address
space,
I would suggest to reserve at least 255 addresses, or even more.

First, we have nothing to loose.

Second, we all know that UDP and TCP reserved ports is proven to be
helpful.

Third, especially if my suggestion about "Multicast on-demand" will be
accepted, a multicast server will have the ability to know if it has
at
least one connected client to any given multicast address. In this
case, we
can think of the following services, each given in a different,
predefined,
multicast address:

1. Time service. The server's local time and time zone every second.
   Support packet-loss rate detection.
   Support "ping" for multicast.
   I suggest address 232.0.0.1 for this one.

2. CA service. Send certification about the server every 5 seconds.

3. Quote of the day service. Actually, quote of the minute.

4. Directory service. Send some information regarding the current
server.
   Probably the most important service.

5. ...


Doron.