NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

The whole site in one document for easy reference!
The TCP/IP Guide

Google
Web TCP/IP Guide






Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Internet Layer (OSI Network Layer) Protocols
           9  TCP/IP Routing Protocols (Gateway Protocols)
                9  TCP/IP Exterior Gateway/Routing Protocols (BGP and EGP)
                     9  TCP/IP Border Gateway Protocol (BGP/BGP-4)
                          9  BGP Detailed Messaging, Operation and Message Formats

Previous Topic/Section
BGP Detailed Messaging, Operation and Message Formats
Previous Page
Pages in Current Topic/Section
12
3
Next Page
BGP Connection Establishment: Open Messages
Next Topic/Section

BGP Message Generation and Transport, and General Message Format
(Page 3 of 3)

The Marker Field, Message Synchronization and Authentication

The Marker field is the most interesting one in the BGP message format, and as mentioned in the table is used for both synchronization and authentication. BGP uses a single TCP session to send many messages in a row. TCP is a stream-oriented transport protocol which just sends bytes across the link without any knowledge of what the bytes represent. This means that the protocol using TCP is responsible for deciding where the line is drawn between data units, in this case BGP messages.

Normally, the Length field tells each BGP device where to draw the line between the end of one message and the start of the next. However, it is possible that due to various conditions a device might lose track of where the message boundary is. The Marker field is filled with a recognizable pattern that clearly marks the start of each message, to keep BGP peers synchronized.

Before a BGP connection is established, the Marker field is just filled with all ones. Thus, this is the pattern used for Open messages. Once a BGP session is negotiated, if agreement is reached on an authentication method between the two devices, the Marker field takes on the additional role of authentication. Instead of looking for a Marker containing all ones, BGP devices look for a pattern generated using the agreed-upon authentication method. Detection of this pattern simultaneously synchronizes the devices and ensures that messages are authentic.

In extreme cases, BGP peers may be unable to maintain synchronization, and if so, a Notification message is generated and the session is closed. This will also happen if the Marker field contains the wrong data when authentication is enabled.

Key Concept: All four BGP message types use a general message format that contains three fixed header fields—Marker, Length and Type—and room for a message body that differs for each message type. The large Marker field is used to denote the start of a new BGP message, and is also used to facilitate the BGP authentication method.



Previous Topic/Section
BGP Detailed Messaging, Operation and Message Formats
Previous Page
Pages in Current Topic/Section
12
3
Next Page
BGP Connection Establishment: Open Messages
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.