Philippe Guibert

Actually, when configuring `redirect-to-nexthop-ietf 33::2`, I was happy to see an ipv6 ext comunity forged. However I have a doubt on which type and subtype to apply when looking at...

which draft overrides the other one : draft-ietf-idr-flow-spec-v6-09 or draft-ietf-idr-flowspec-redirect-ip ?

I can however see a 20 byte ipv6 ext community forged, but with wrong type and subtype. I am on head of exabgp. I would be happy to know the...

Thanks @elindsey for the comments; actually the draft from `https://www.iana.org/assignments/bgp-extended-communities/bgp-extended-communities.xhtml` was not explicitly mentioning the usage of ext ipv6 community. Thanks for clarification. I would be ok to specify the...

I have to admit that the format is equal to me, provided that the feature can be put into exabgp. so your counter proposal would suit me. thanks.

Hi @thomas-mangin , so previously, I made a patch to replace the route ttarget redirect IP with route target redirect VRF like that one: ``` class TrafficNextHopIPv6IETF (ExtendedCommunityIPv6): - COMMUNITY_TYPE...

adding to this, currently it is possible to have the following as for simpson draft: ``` redirect IPV6; ``` My expectation is that redirect either takes an IP (v4 or...

Hi Thomas, use case 1 : simpson way: nexthop IPV6 added in NLRI IPv6 : NOK ( it was working fine before patches). ``` route { match { source 1001::2/128;...

Hi Thomas, please give me a bit more time to clarify better the need.

ci:rerun