Connected: An Internet Encyclopedia
Appendix 4. Comparison with RFC 1105

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1771
Prev: Appendix 3. Comparison with RFC 1163
Next: Appendix 5. TCP options that may be used with BGP

Appendix 4. Comparison with RFC 1105

Appendix 4. Comparison with RFC 1105

All of the changes listed in Appendices 2 and 3, plus the following.

Minor changes to the RFC1105 Finite State Machine were necessary to accommodate the TCP user interface provided by 4.3 BSD.

The notion of Up/Down/Horizontal relations present in RFC1105 has been removed from the protocol.

The changes in the message format from RFC1105 are as follows:

  1. The Hold Time field has been removed from the BGP header and added to the OPEN message.

  2. The version field has been removed from the BGP header and added to the OPEN message.

  3. The Link Type field has been removed from the OPEN message.

  4. The OPEN CONFIRM message has been eliminated and replaced with implicit confirmation provided by the KEEPALIVE message.

  5. The format of the UPDATE message has been changed significantly. New fields were added to the UPDATE message to support multiple path attributes.

  6. The Marker field has been expanded and its role broadened to support authentication.

Note that quite often BGP, as specified in RFC 1105, is referred to as BGP-1, BGP, as specified in RFC 1163, is referred to as BGP-2, BGP, as specified in RFC1267 is referred to as BGP-3, and BGP, as specified in this document is referred to as BGP-4.


Next: Appendix 5. TCP options that may be used with BGP

Connected: An Internet Encyclopedia
Appendix 4. Comparison with RFC 1105