Haibo,
Thank you very much for the suggestion.
How about using "Color Extended Community"? i.e. Client UPDATE recursive to the
node address with "Color Extended Community" attached. And the UPDATE for the
Node describes the detailed IPsec attributes with the matching Color Extended
Community value.
UPDATE #1:
- MP-NLRI Path Attribute: to indicate multiple routes attached to
the C-PE2:
NextHop: C-PE2
Prefix:
10.1.x.x/16
VLAN #15
12.1.1.x/24
Color Extended community: RED
UPDATE #2:
* MP-NLRI Path Attribute:
* Tunnel-Encap Path Attribute: to describe the IPsec attributes
* Color Extended Community: RED
Thank you,
Linda
From: Wanghaibo (Rainsword) <[email protected]>
Sent: Sunday, November 1, 2020 9:32 PM
To: [email protected]; [email protected]
Subject: Mail regarding draft-ietf-bess-bgp-sdwan-usage
Hi authors,
About the section 4.1 BGP Walk Through for Homogeneous SDWAN.
It shows an example that:
- MP-NLRI Path Attribute: to indicate multiple routes attached to
the C-PE2:
10.1.x.x/16
VLAN #15
12.1.1.x/24
- Tunnel-Encap Path Attribute: to describe the IPsec attributes
This is a way of associating routea with tunnels, but each route has a large
amount of information.
However, there is another way to advertise routes with Tunnel Encapsulation
Extend Community attributes, like draft-ietf-idr-segment-routing-te-policy.
In this method, tunnel information is advertised using independent SAFIs.
Routes are associated with tunnels based on the Tunnel Encap EC.
Regards,
Haibo
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess
