Re: [Idr] draft-chavali-bgp-prefixlimit-02.txt as an IDR WG document

[Yakov Rekhter <yakov at juniper.net>]

Eric,

> > In the current implementation, the  prefix limit is only configured on the
> > BGP receiver (e.g., provider edge router), the BGP speaker (e.g. CPE) does
> > not  have   any  control.   Some  implementation  has   warning  threshold
> > option. When warning  limit is reached, the trap will only  show up on the
> > provider  side, the  operator  has to  contact  the customer  by phone  or
> > through some messaging systems.  
> 
> This suggests that it is useful for  a BGP speaker to know that a given peer
> will only be  able to receive n prefixes.  In that  case, it certainly makes
> sense for  the value  n to be  learned dynamically.   Both of the  drafts in
> question support that functionality. 
> 
> I don't see the argument  for dynamically learning multiple threshold levels
> from a peer.  Especially as there  are no real semantics associated with the
> other thresholds. 

Could you please clarify whether (a) you are in favor or against
accepting signalled prefix limit as an IDR WG item, and if yes,
then (b) which of the two approaches (draft-chavali-bgp-prefixlimit-02.txt
or draft-keyur-prefixlimit-orf-00.txt) would you favor.

Yakov.

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr