[DNSOP] service binding mapping for service levels

[Joe Abley <[e-mail]>]

Hi Gautam!

Regarding draft-gakiwate-dnsop-svcb-sla-parameter:

At the mic just now in Madrid I asked what incentive a client had to ever choose background priority if there's a better performance option. Your answer was that the use case here is when the application and the service are operated by the same people, like a weather forecasting service supplying data to a weather forecast widget on a phone.

If the client and server are operated by the same people, you could just use different names for the foreground and background traffic classes -- it's not obvious why you need to use a single name for both. You could use api-widget.weather.example.com for the phone widget that operates in the background and api-user.weather.example.com for use when an impatient user is asking the application to do things, or something like that.

Something like what you are suggesting could of course be done, but I am not sure why it's more useful than what we can already do. Is there an advantage?

I would have asked this follow-up question at the mic but we were short on time, so I'm asking it here.


Joe