The minimum TTL (for IPv4) or Hop Limit (for IPv6) that must be set in a BGP packet received from this peer. This field is used to enable the Generalized TTL Security Mechanism (GTSM), as defined in RFC 5082. If set to 0, then no restriction is applied to received packets (that is, GTSM is not enabled). If set to any other value, then packets received from a peer with a TTL or Hop Limit less than the specified value will be dropped. A non-zero value also means that DC-BGP will send packets to this peer with TTL set to 255, as specified in RFC 5082. This overrides the TTL value specified in bgpPeerTtl or bgpPeergrTttl. Note that the typical use case for GTSM is for directly connected peers, where this field should be set to 254. Non-directly connected peers may still use this feature, with a lower value for this field, but the value must be chosen such that changes in the network topology do not cause packets to be dropped incorrectly. This field can be changed at any time. However, if the field is changed while the peer is admin_status UP, the change will only take effect after the peer has been cycled admin_status DOWN and then UP, thus forcing the peer session to be restarted. In this case, until the peer is set admin_status DOWN, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer).