Skip to Content.
Sympa Menu

wg-multicast - Re: MSDP Storm

Subject: All things related to multicast

List archive

Re: MSDP Storm


Chronological Thread 
  • From: Jared Mauch <>
  • To: Marshall Eubanks <>
  • Cc: Magnus Danielson <>, , , , , , , ,
  • Subject: Re: MSDP Storm
  • Date: Fri, 19 Jan 2001 10:55:29 -0500

On Fri, Jan 19, 2001 at 10:50:15AM -0500, Marshall Eubanks wrote:
> Dear Magnus;
>
> Magnus Danielson wrote:
> >
> > From: Marshall Eubanks
> > <>
> > Subject: Re: MSDP Storm
> > Date: Fri, 19 Jan 2001 10:00:33 -0500
> >
> > > Hello Magnus;
> >
> > Dear Marshall,
> >
> > > 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.
> >
> > IMHO Mboned is the correct IETF WG for such a BCP. I just didn't imply
> > the WG
> > to do the BCP in question.
> >
>
> My guess is that the numbers will be the hard part. It is easy, after
> all, to say
>
> MSDP neighbors SHALL limit the number of Session Announcements flooded out.
>
> But it is not transparent (to me, at least) what that limit should be.
> Most people running a RP with MSDP will want guidance as to what limit
> should be
> used and/or what limits are reasonable. The same can be said for IGMP
> and PIM.

Rate-limiting MSDP messages or doing a per-peer SA limit
would be good.. Similar to the way we in the operational world can limit
the number of prefixes received, we should be able to limit the maximum
number of SA's that we receive from a peer.

I can determine that currently there are about 1200 SA's
so I can limit each of my eMSDP peers to have only 1200 SA's from them
to avoid the 12k SA's I was seeing earlier this week from port scans
of 227/8

- Jared

--
Jared Mauch | pgp key available via finger from

clue++; | http://puck.nether.net/~jared/ My statements are only mine.
END OF LINE | Manager of IP networks built within my own home




Archive powered by MHonArc 2.6.16.

Top of Page