[NLNOG] feedback gezocht: maximum prefix limits (inbound / outbound) draft

[Martin Pels]

Hi,

Mooi werk! Hierbij mijn opmerkingen/suggesties:

3.1

> Adj-RIB-In stores routing information learned from inbound UPDATE
> messages that were received from another BGP speaker Section 3.2
> [RFC4271]

Adj-RIB-In stores routing information learned from inbound UPDATE
messages that were received from another BGP speaker (see [RFC4271]
Section 3.2).

> As example [..]

As an example [..]

3.2

Je geeft een voorbeeld van wanneer de sessie niet down gebracht wordt,
maar er ontbreekt een voorbeeld en RFC2119-tekst waarbij de sessie wel
down gebracht wordt. Iets als de volgende tekst:

"As an example, when an operator configures the Type B post-policy limit
for IPv4 Unicast to be 50 on a given EBGP session, and the other BGP
speaker announces a hundred IPv4 Unicast routes of which 75 are accepted
due to local policy (and thus considered for the Loc-RIB by the local
BGP speaker), the session MUST be torn down. On the other hand, if in
the same example no prefixes are accepted due to local policy, the
session is not torn down."

Ik zou nog expliciet noemen dat de Type-B prefix limit voor een peer
gelijk of lager dient te zijn dan de Type-A limit om effect te hebben.
Dit zou ook afgedwongen kunnen worden in de configuratie.

"In order to have effect, the Type-B prefix limit for a peer MUST be
equal or lower than the Type-A limit for this peer. Implementations
SHOULD/MAY(?) prevent configuration of a Type-B prefix limit that is
higher than the configured Type-A limit.

4.

De verwoording van de Error Subcode kan beter, zoals al eerder genoemd.
Ik sluit me aan bij Steven's suggesties.

> The routing information stored in the Adj-RIBs-Out will be carried in
> the local BGP speaker's UPDATE messages and advertised to its
> neighbors Section 3.2 [RFC4271]

The routing information stored in the Adj-RIBs-Out will be carried in
the local BGP speaker's UPDATE messages and advertised to its neighbors
(see [RFC4271] Section 3.2).

> [..] the BGP session MUST be torn down and send the neighbor a
> NOTIFICATION message [..]

[..] the BGP session MUST be torn down and a NOTIFICATION message must
be sent to the neighbor [..]

> Outbound Maximum Prefix Limits can be thought of as Dead Man's
> Switches.

Outbound Maximum Prefix Limits can be thought of as "dead man's
switches", preventing policy configuration accidents or malfunctioning
from causing harm to other BGP speakers.

Groet,
Martin