Activity log for bug #1416551

Date Who What changed Old value New value Message
2015-01-30 21:32:09 Nischal Sheth bug added bug
2015-01-30 21:32:20 Nischal Sheth nominated for series juniperopenstack/trunk
2015-01-30 21:32:20 Nischal Sheth bug task added juniperopenstack/trunk
2015-01-30 21:33:13 Nischal Sheth information type Proprietary Public
2015-01-30 21:33:51 Nischal Sheth description It is typically not desirable to use public ASNs for contrail clusters. However there is a need to interoperate with an L3VPN core that uses a 4-byte AS. Hence the first phase of the implementation would be to handle received AS4_PATH attribute and prepend our AS to it.. Second phase would be to use a 4-byte AS as the local AS for the cluster. Note that 4 byte AS support is not necessary even if the underlay uses 4 byte ASes as described below. No interaction is required between the underlay and the overlay. https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-00#section-5.2 It is typically not desirable to use public ASN for a cluster. However there is a need to interoperate with an L3VPN core that uses a 4-byte AS. Hence the first phase of the implementation would be to handle received AS4_PATH attribute and prepend our AS to it.. Second phase would be to use a 4-byte AS as the local AS for the cluster. Note that 4 byte AS support is not necessary even if the underlay uses 4 byte ASes as described below. No interaction is required between the underlay and the overlay. https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-00#section-5.2
2015-01-30 21:34:13 Nischal Sheth description It is typically not desirable to use public ASN for a cluster. However there is a need to interoperate with an L3VPN core that uses a 4-byte AS. Hence the first phase of the implementation would be to handle received AS4_PATH attribute and prepend our AS to it.. Second phase would be to use a 4-byte AS as the local AS for the cluster. Note that 4 byte AS support is not necessary even if the underlay uses 4 byte ASes as described below. No interaction is required between the underlay and the overlay. https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-00#section-5.2 It is typically not desirable to use public ASN for a cluster. However there is a need to interoperate with an L3VPN core that uses a 4-byte AS. Hence the first phase of the implementation would be to handle received AS4_PATH attribute and prepend our AS to it. Second phase would be to allow a 4-byte AS as the local AS for cluster. Note that 4 byte AS support is not necessary even if the underlay uses 4 byte ASes as described below. No interaction is required between the underlay and the overlay. https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-00#section-5.2
2015-02-02 19:16:07 Nischal Sheth description It is typically not desirable to use public ASN for a cluster. However there is a need to interoperate with an L3VPN core that uses a 4-byte AS. Hence the first phase of the implementation would be to handle received AS4_PATH attribute and prepend our AS to it. Second phase would be to allow a 4-byte AS as the local AS for cluster. Note that 4 byte AS support is not necessary even if the underlay uses 4 byte ASes as described below. No interaction is required between the underlay and the overlay. https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-00#section-5.2 It is typically not desirable to use public ASN for a cluster. However there is a need to interoperate with an L3VPN core that uses a 4-byte AS. Hence the first phase of the implementation would be to handle received AS4_PATH attribute and prepend our AS to it. Second phase would be to allow a 4-byte AS as the local AS for cluster. https://tools.ietf.org/html/rfc6793 Note that 4 byte AS support is not necessary even if the underlay uses 4 byte ASes as described below. No interaction is required between the underlay and the overlay. https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-00#section-5.2
2015-04-29 22:52:42 Nischal Sheth juniperopenstack/trunk: milestone r2.30-fcs
2016-03-21 20:24:08 Nischal Sheth juniperopenstack/trunk: milestone r3.0-fcs
2018-05-02 23:39:28 Ananth Suryanarayana juniperopenstack/trunk: assignee Nischal Sheth (nsheth) Nikhil Bansal (nikhilb-u)
2018-07-31 01:54:17 OpenContrail Admin juniperopenstack/trunk: status New In Progress
2018-08-17 04:13:01 Nikhil Bansal juniperopenstack/trunk: status In Progress Fix Committed
2018-08-17 06:14:29 Jeba Paulaiyan juniperopenstack/trunk: milestone r5.1.0
2018-09-21 10:18:16 OpenContrail Admin juniperopenstack/trunk: status Fix Committed In Progress
2018-09-24 03:45:23 OpenContrail Admin juniperopenstack/trunk: status In Progress Fix Committed
2018-09-24 05:57:21 OpenContrail Admin juniperopenstack/trunk: status Fix Committed In Progress
2018-10-08 15:29:49 OpenContrail Admin juniperopenstack/trunk: status In Progress Fix Committed