Re: [Idr] RtgDir review: draft-ietf-idr-sla-exchange-10

[Shitanshu Shah <[e-mail]>]

Hi Ron,


To break it down in two point response,


1) This draft is not changing how SLA is established at first place. The draft is providing a method to convey this a priori established SLA to help reduce lot of manual complexities and errors to admin. Thus given a knowledge of what SLA is established, in general devices should be capable to support that established SLA.



2) If there still are any issues in implementing exchanged SLA in forwarding, we think they either are implementation specific or of temporary nature where for example enough resources not available at any specific point of a time.


We feel that in current state of the draft, it can be largely useful in deployments.




One can imagine though even establishment of SLA also can be done via exchanging it over bgp. However, negotiation of SLA does not have to be clubbed with exchange of SLA. Negotiation of SLA is not in this scope.


Regards,
Shitanshu


________________________________
From: Ron Bonica <[e-mail]>
Sent: Thursday, February 23, 2017 10:06 AM
To: Shitanshu Shah; [e-mail]; [e-mail]; [e-mail]
Subject: RE: RtgDir review: draft-ietf-idr-sla-exchange-10


Hello,



The draft is internally consistent. But given what is left out of scope, I wonder if the new attributes will ever be widely deployed.



                                                                                Ron





This document might benefit from discussion of operational issues. I assume that when a BGP listener learns a route with the SLA Exchange Attribute, it provisions class of service forwarding classes on interfaces.



##svshah, though this is one desired use of exchanging SLA content, the draft focuses on transporting SLA content from the SLA Producer to the SLA Consumer. Processing of the QoS attribute content, at the SLA Consumer, is outside the scope of this document.



##svshah, Let me know if you have a suggestion to make description clearer in Section 1 and 2 to highlight this.





I also assume that a) it takes time to provision class of service forwarding classes and b) the number of forwarding classes that can be provisioned are finite. What does the BGP listener do when the number of forwarding classes requested exceeds its capacity to deliver?



##svshah, Since scope of the document is to transport SLA content from the SLA Producer to the SLA Consumer, the document considers error handling in the context of transporting data and thus any formating errors and semantics errors within that context. Any errors in the context of processing QoS attribute content at the SLA Consumer is outside the scope of the document.