Loop detection for imported routes Huawei
Huawei Bld., No.156 Beiqing Rd. Beijing 100095 China yuezhuo@huawei.com
Huawei
Huawei Bld., No. 156 Beiqing Rd. Beijing 100095 China xuguoqi@huawei.com
Huawei
Huawei Bld., No. 156 Beiqing Rd. Beijing 100095 China lichenxi1@huawei.com
Huawei
Huawei Bld., No.156 Beiqing Rd. Beijing 100095 China tide.li@huawei.com
Mutual route import between two IGP instances is often involved in networking solutions. However, routing loops may occur when route are imported to an instance from another and cause critical problem. This document provides a way to detect routing loop and introduces new sub-TLVs to support advertisement IPv4 and IPv6 prefix extended attribute flags and the source router ID of the router which import the route and redistribute the route. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
As dynamic routing protocols, IS-IS and OSPF are widely used on live networks. Mutual route import between two IGP instances is often involved in networking solutions. However, restricted routing policy need to be configred on the router, otherwise, routing loops may occur and cause critical problem. When a route is imported to an IGP instance, if the IGP instance can recognize the route has already been redistributed by itself and notice that there might be routing loops in the network, the router can take some actions to avoid or fix futher potential routing problems. Therefore, new sub-TLVs are introduced to support advertisement IPv4 and IPv6 prefix extended attribute flags and the source router ID of the router which has redistributed the prefix.
When a routing prefix is imported to an IGP instance and redistributed by the instance to other IGP areas, the router ID of this IGP instance will be added to the redistribute list of the prefix and advertised in IGP areas. The following sections describe how the redistribute list for a route prefix is advertised in IGP areas.
This document registers a new IS-IS sub-TLV in the "Sub-TLVs for TLVs 135, 235, 236 and 237" registry. This new sub-TLV provides ways to advertise IPv4 and IPv6 prefix extended attribute flags and the router ID of the router which redistributed the prefix.
Type: 10 Length: 1 + Router-ID length. Flags: 1 octet. The following flags are defined:
where: S-flag: If set, the prefix has be redistributed by the router that generate the current LSP. R-flag: If set, the prefix has be redistributed by the router other than the router that generate current LSP. Router ID: 6 octets. IS-IS System-ID as defined in [ISO10589]. This sub-TLV is optional. If the sub-Tlv length is equal to one, R-flag MUST be treated as if it is set to 0 on receipt. Undefined bits that are transmitted MUST be transmitted as 0 and MUST be ignored on receipt.
TBD.
Implementations MUST make it possible to enable or disable the sub-TLV based on configuration.
TBD.
This document requests that IANA allocates new sub-TLV types from the IS-IS "Sub-TLVs for TLVs 135, 235, 236 and 237)" registry as specified.
These extensions to IS-IS do not add any new security issues to the existing IGP.