All things related to multicast

[Marshall Eubanks <>]

Hello Magnus;

Magnus Danielson wrote:
> 
> From: Marshall Eubanks 
> <>
> Subject: Re: MSDP Storm
> Date: Thu, 18 Jan 2001 13:39:44 -0500
> 
> > I would agree. Mischievously, I would point out that there is an IGMP v3 
> > RFC grinding along :
> >  <draft-ietf-idmr-igmp-v3-05.txt>
> > AND a MSDP draft grinding along as well :
> > <draft-ietf-msdp-spec-06.txt>
> >
> 
> The actual numbers should never be put into that RFC. If specific numbers 
> are
> required, then you should have a separate RFC also running as a BCP to 
> detail
> it and updates can be made according to need.

Correct, although a mboned BCP might not be a bad idea.

> 
> Generic filters and adaptive functions may be directly specified.
> 
> > This might limit vast multiparty games or videoconferences a little, but 
> > would not hinder any SSM type aps I
> > can think of at all. The numbers I gave may be too lenient; I was just 
> > trying to get some thinking about this started.
> 
> Like allways, picking one single number is allways a tradeoff thing.
> 
> BTW. In this case of the worm... didn't the scanner try to connect to TCP?
> I mean, trying to do TCP on _ANY_ multicast address is just bound to be a
> looser. A simple filter could (and should) block that.
> 

I do not know, but this is a good point. I can see no reason not to
filter TCP.

> Cheers,
> Magnus

-- 


                                   Regards
                                   Marshall Eubanks

   Multicast Technologies, Inc.
   10301 Democracy Lane, Suite 201
   Fairfax, Virginia 22030
   Phone : 703-293-9624          Fax     : 703-293-9609     
   e-mail : 

     http://www.on-the-i.com