RFC 4271, "A Border Gateway Protocol 4 (BGP-4)", January 2006

Note: This RFC has been updated by RFC 6286, RFC 6608, RFC 6793, RFC 7606, RFC 7607, RFC 7705, RFC 8212, RFC 8654, RFC 9072

Errata ID: 5766
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alvaro Retana
Date Reported: 2019-06-28
Held for Document Update by: Alvaro Retana
Date Held: 2019-06-28

Section 9.2 says:

   If, due to the limits on the maximum size of an UPDATE message (see
   Section 4), a single route doesn't fit into the message, the BGP
   speaker MUST not advertise the route to its peers and MAY choose to
   log an error locally.

It should say:

   If, due to the limits on the maximum size of an UPDATE message (see
   Section 4), a single route doesn't fit into the message, the BGP
   speaker MUST NOT advertise the route to its peers and MAY choose to
   log an error locally.

Notes:

The Normative text should be "MUST NOT", and not "MUST not" -- both words should be capitalized.

Report New Errata