BGP attribute for QoS SLA advertisement
draft-svshah-bgp-qos-sla-attribute-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shitanshu Shah , Keyur Patel , Sandeep Bajaj | ||
| Last updated | 2012-07-16 (Latest revision 2012-03-01) | ||
| Replaced by | draft-svshah-interdomain-sla-exchange | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-svshah-interdomain-sla-exchange | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Out-of-band manual learning of SLA details and provisioning them in general can be complex work for network administrators. For example, Enterprise network administrators not only have to know what is their SLA, for voice, video etc application traffic, with their Provider, but they also require translating application groups to Classifier groups as per provider's definition as well translate SLA to vendor specific provisioning language. An in-band method of QoS signaling can help to simplify some of the complexities. An optional transitive BGP attribute proposed in this document intends to signal SLA details in-band, across administrative boundaries (considered as Autonomous Systems (AS)), and thus simplify/speed-up some of the complex tasks. Though the use-case with the proposed attribute is explicitly defined in this document, purpose of this attribute is not limited to this use-case only.
Authors
Shitanshu Shah
Keyur Patel
Sandeep Bajaj
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)