Many of the products and features described herein remain in varying stages of development and will be offered on a when-and-if-available basis. This roadmap is subject to change at the sole discretion of Cisco, and Cisco will have no liability for delay in the delivery or failure to deliver any of the products or features set forth in this document. Any forward looking information within this document is subject to change by Cisco.

Many of the products and features described herein remain in varying stages of development and will be offered on a when-and-if-available basis. This roadmap is subject to change at the sole discretion of Cisco, and Cisco will have no liability for delay in the delivery or failure to deliver any of the products or features set forth in this document. Any forward looking information within this document is subject to change by Cisco.

The PfR Major/Minor Versions Rule

The _Minor Version_ of the BR must be Less Than or Equal To the _Minor Version_ of the MC for a connection to be established.

For Example:
If the Master Controller (MC) was at Version 3.3 and the Border Router was at Version 3.1 that would be OK as the BR Minor version number is less than the MC minor version number.

On the other hand, If the Master Controller (MC) was at Version 3.0 and the Border Router was at Version 3.2 that would NOT BE OK as the BR Minor Version Number is greater than the MC Minor Version Number.

The table below helps show the relationships between PfR MC and BR Minor Version Numbers.

Forward Looking Disclaimer

Many of the products and features described herein remain in varying stages of development and will be offered on a when-and-if-available basis. This roadmap is subject to change at the sole discretion of Cisco, and Cisco will have no liability for delay in the delivery or failure to deliver any of the products or features set forth in this document. Any forward looking information within this document is subject to change by Cisco.