A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.
Title : BGP Usage for SDWAN Overlay Networks
Authors : Linda Dunbar
James Guichard
This wording is better.
there are still two aspects where I think we can be clearer.
First, referring to generic packet forwarding and only later saying "we
mean tunnel selection" is still prone to confusing readers and prone to
confusing discussions of our intent later when folks use this
Joel,
How about this statement?
-Some traffic flows can be forwarded based on their application
identifiers instead of based on destination IP addresses, by the edge nodes
placing the traffic flows onto specific overlay paths based on their
application requirement.
It is more
The way you are wording that third bullet, it looks like it is expecting
the network (past the SD-WAN edges) to be looking for application
identifiers in making the packet forwarding decisions.
Is what you are looking for:
Selection of tunnels to be used for traffic subsets based on
Adrian and Joel,
Thank you very much for the suggestions.
I have updated the description per your suggested wording:
Here are some key characteristics of “SDWAN” networks:
- Augment of transport, which refers to utilizing overlay paths over
different underlay networks. Very often
Sue and authors,
To be clear, and John/Ali can chime in too, what I think we are saying is:
* people use RFC8365 as the reference to implement EVPN for VXLAN, VXLAN
GPE, NVGRE and MPLS-in-GRE.
* RFC8365 uses the encapsulation extended community described in section
4.1 of the
