Supported Features for Real BGP Payload Support

The following protocol features are supported for sending BGP payload between a simulation and a real router:

  • The serializations/deserializations of the BGP messages and associated fields listed in Table 26 are either fully or partially supported. Most of the supported features are based on RFC 4271.
  • Note that any limitation indicated by the BGP model will limit the real BGP payload support feature as well.

Table 26: Supported BGP Messages

BGP Message Field Subfield Comments
Common Message Header Marker
Length
Type
OPEN Version Always set to 4 during serialization
My Autonomous System
Hold Time
BGP Identifier
Optional Parameters Length Set to 0 (even if a real message indicates other value)
KEEPALIVE (Contains the same fields as the common Message Header) A KEEPALIVE message consists of only the message header and has a length of 19 octets
NOTIFICATION Error Code The BGP model supports only CEASE and HOLD TIMER EXPIRED Values for this field

Deserialization:
The value of the field is preserved, but any value other than CEASE and HOLD TIMER EXPIRED is ignored by the model during the processing of the received message
Error Subcode Serialization:
Not supported. Always set to 0 (zero)

Deserialization:
The value of the field is preserved, but it is ignored by the model during the processing of the received message
UPDATE Withdrawn Routes Length
Withdrawn Routes
Total Path Attribute Length
Path Attributes ORIGIN
AS_PATH • Only an AS number size of 16 bits is supported.
• Segment types related to confederations are supported [RFC 5065].
• When de-serializing, the path length will be computed by adding only the AS numbers in the segments of type AS_SET and AS_SEQUENCE.
NEXT_HOP
MULTI_EXIT_DISC
LOCAL_PREF
ORIGINATOR_ID From RFC 4456
CLUSTER_LIST From RFC 4456
Network Layer Reachability Information