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

["Susan Hares" <[e-mail]>]

Shitanshu: 

 

Please address Ron's comment about widely deployed.  I believe this was part
of Alvaro's comments. 

 

Sue 

 

From: rtg-dir [mailto:[e-mail]] On Behalf Of Ron Bonica
Sent: Thursday, February 23, 2017 12:07 PM
To: Shitanshu Shah; [e-mail];
[e-mail]; [e-mail]
Subject: Re: [RTG-DIR] 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.