Thanks Adrian for your comment. How about changing the paragraph to something like:
"The application can be routed based on specific performance criteria (e.g. packets delay, packet lose, jitter) to provide a better experience by choosing a tunnel over an underlay that meets or exceeds the specified performance criteria threshold for that application" Regards; Basil -----Original Message----- From: Adrian Farrel <[email protected]> Sent: July-28-20 8:01 AM To: [email protected] Cc: [email protected] Subject: [EXT]Thought about "Application Routing" in draft-dunbar-bess-bgp-sdwan-usage Hi, As Linda noted in her agenda slot today, draft-dunbar-bess-bgp-sdwan-usage version 08 introduced a new paragraph in the Introduction that says: - The Application Routing can also be based on specific performance criteria (e.g. packets delay, packet loos, jitter) to provide better application performance by choosing the right underlay that meets or exceeds the specified criteria. Firstly, s/loos/loss/ 😊 But I am concerned by the concept of "application routing" and I note that the term is not used elsewhere in the document nor is the concept expanded upon. As will be seen from the Application Aware Networking (APN) effort, the concept of traffic flows being routed according to the identity of the application is made complicated by various privacy and security concerns, not to mention issues of registering application identities. Fortunately, I suspect that this draft wants to do something similar to APN: that is, to classify the service that a particular application-sourced flow wants to receive from the network. This may be considerably more complex than DSCP, but the concept is the same that either a tunnel/pipe/flow is negotiated and established for use by the application, or the packets are 'coloured' for routing and treatment in the network. I would suggest two things: 1. Be a lot more clear about what is meant by "application routing" possibly even using a different term 2. Have a look at the APN work - side meeting on Thursday; see https://github.com/APN-Community/IETF108-Side-Meeting-APN for all the details Best, Adrian ------------------------------------------------------------------------------ External Email: Please use caution when opening links and attachments / Courriel externe: Soyez prudent avec les liens et documents joints _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
