[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Idr] draft-chavali-bgp-prefixlimit-02.txt as an IDR WG document
- To: <erosen at cisco.com>, "Fang, Luyuan, ALABS" <luyuanfang at att.com>
- Subject: RE: [Idr] draft-chavali-bgp-prefixlimit-02.txt as an IDR WG document
- From: "Susan Hares" <shares at nexthop.com>
- Date: Mon, 17 May 2004 13:57:29 -0400
- Cc: "Ash, Gerald R (Jerry), ALABS" <gash at att.com>, "Yakov Rekhter" <yakov at juniper.net>, <idr at ietf.org>
- List-archive: <https://www1.ietf.org/mail-archive/working-groups/idr/>
- List-help: <mailto:idr-request@ietf.org?subject=help>
- List-id: Inter-Domain Routing <idr.ietf.org>
- List-post: <mailto:idr@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/idr>,<mailto:idr-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>,<mailto:idr-request@ietf.org?subject=unsubscribe>
- Sender: idr-admin at ietf.org
- Thread-index: AcQ8M4R1yuHFYUSIQWuHPDiteEiyQAAAbryg
- Thread-topic: [Idr] draft-chavali-bgp-prefixlimit-02.txt as an IDR WG document
Eric:
Could you clarify for me a few things in
your last paragraph
"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 be specific on what other thresholds?
Sue
-----Original Message-----
From: Eric Rosen [mailto:erosen@cisco.com]
Sent: Monday, May 17, 2004 1:01 PM
To: Fang, Luyuan, ALABS
Cc: Ash, Gerald R (Jerry), ALABS; Yakov Rekhter; idr@ietf.org
Subject: Re: [Idr] draft-chavali-bgp-prefixlimit-02.txt as an IDR WG
document
> 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.
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr