Activity log for bug #1706726

Date Who What changed Old value New value Message
2017-07-26 17:37:49 Nischal Sheth bug added bug
2017-07-26 17:37:57 Nischal Sheth nominated for series juniperopenstack/trunk
2017-07-26 17:37:57 Nischal Sheth bug task added juniperopenstack/trunk
2017-07-26 17:38:03 Nischal Sheth information type Proprietary Public
2017-07-26 19:04:38 Nischal Sheth description TBD As part of ip-fabric forwarding support, CN needs the ability to indicate in the L3VPN route for an endpoint, that the endpoint has an IP address from the underlay and hence is capable of native forwarding i.e. without MPLS encapsulation. Proposal is to signal this by advertising a "native" encapsulation in XMPP and BGP.
2017-07-26 19:10:00 Nischal Sheth description As part of ip-fabric forwarding support, CN needs the ability to indicate in the L3VPN route for an endpoint, that the endpoint has an IP address from the underlay and hence is capable of native forwarding i.e. without MPLS encapsulation. Proposal is to signal this by advertising a "native" encapsulation in XMPP and BGP. As part of ip-fabric forwarding support, CN needs the ability to indicate in the L3VPN route for an endpoint that the endpoint has an IP address from the underlay and hence is capable of native forwarding i.e. without MPLS encapsulation. Proposal is to signal this by advertising a "native" encapsulation in XMPP and BGP. Note that "native" encapsulation can and will be advertised along with other encapsulations like udp and gre i.e. it need not be exclusive. The vRouter can determine whether to use overlay or native encapsulation based on the properties of the source VN and encapsulations signaled in the destination route.
2017-07-26 19:11:08 Nischal Sheth description As part of ip-fabric forwarding support, CN needs the ability to indicate in the L3VPN route for an endpoint that the endpoint has an IP address from the underlay and hence is capable of native forwarding i.e. without MPLS encapsulation. Proposal is to signal this by advertising a "native" encapsulation in XMPP and BGP. Note that "native" encapsulation can and will be advertised along with other encapsulations like udp and gre i.e. it need not be exclusive. The vRouter can determine whether to use overlay or native encapsulation based on the properties of the source VN and encapsulations signaled in the destination route. As part of ip-fabric forwarding support, CN needs the ability to indicate in the L3VPN route for an endpoint that the endpoint has an IP address from the underlay and hence is capable of native forwarding i.e. without MPLS encapsulation. Proposal is to signal this by advertising a "native" encapsulation in XMPP and BGP. Note that "native" encapsulation can and will be advertised along with other encapsulations like udp and gre i.e. it need not be exclusive. The vRouter can determine whether to use overlay or native encapsulation based on the properties of the source VN and encapsulations signaled in the destination route. Conceptually, we can think of native encapsulation as having the highest priority.
2017-07-26 23:39:18 OpenContrail Admin juniperopenstack/trunk: status New In Progress
2017-07-27 16:53:18 OpenContrail Admin juniperopenstack/trunk: status In Progress Fix Committed
2017-07-27 16:53:19 OpenContrail Admin juniperopenstack/trunk: milestone r4.1.0.0-fcs
2017-10-12 17:47:52 Nischal Sheth juniperopenstack/trunk: milestone r4.1.0.0-fcs r5.0.0
2017-10-12 18:06:16 OpenContrail Admin juniperopenstack/trunk: status Fix Committed In Progress
2017-10-12 18:06:21 OpenContrail Admin nominated for series juniperopenstack/r4.1
2017-10-12 18:06:21 OpenContrail Admin bug task added juniperopenstack/r4.1
2017-10-12 18:06:21 OpenContrail Admin bug task added juniperopenstack/r4.1
2017-10-12 18:43:41 Nischal Sheth juniperopenstack/r4.1: milestone r4.1.0.0-fcs
2017-10-15 21:53:38 OpenContrail Admin juniperopenstack/r4.1: status In Progress Fix Committed
2017-10-17 20:22:54 OpenContrail Admin juniperopenstack/trunk: status In Progress Fix Committed