Re: Maximum Prefix Limit

"Manav Bhatia" <mnvbhatia@yahoo.com> Thu, 17 January 2002 13:38 UTC

Message-ID: <014501c19f5c$5c8481c0$b4036c6b@Manav>
Reply-To: Manav Bhatia <mnvbhatia@yahoo.com>
From: Manav Bhatia <mnvbhatia@yahoo.com>
To: Jeffrey Haas <jhaas@nexthop.com>
Cc: idr@merit.edu
References: <03b001c19e4e$aa86e750$b4036c6b@Manav> <20020116103528.A18433@nexthop.com> <059c01c19f14$91b1de80$b4036c6b@Manav> <20020117082940.A20374@nexthop.com>
Subject: Re: Maximum Prefix Limit
Date: Thu, 17 Jan 2002 19:09:15 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-idr@merit.edu
Precedence: bulk

| > The session in any case will be torn even if the threshold for a single
| > SAFI crosses. Does it make much sense in saying that," i will accept x
SAFI
| > 1 routes, y SAFI 2 routes, etc"?
|
| No, but it may make sense to say "I'll accept X ipv4/unicast routes, but
| if I get > Y ipv4/multicast routes, drop the peer session, potentially
| removing the ipv4/multicast capability".

Does it mean that the next time the session comes up there is no
ipv4/multicast capability supported? Once again, this is implementation
specific and we could work both ways. The session comes up after idle timer
hoping that the sys admin would have looked into the matter OR we dont
support ipv4/multicast (or which ever SAFI limit exceeded).

Regards,
Manav


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com