Inter-domain Traffic Conditioning Agreement (TCA) Exchange Attribute
draft-ietf-idr-sla-exchange-11
|
| Document |
Type |
|
Active Internet-Draft (idr WG)
|
|
Last updated |
|
2017-08-01
|
|
Replaces |
|
draft-svshah-interdomain-sla-exchange
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
Revised I-D Needed - Issue raised by AD
|
|
Document shepherd |
|
Susan Hares
|
|
Shepherd write-up |
|
Show
(last changed 2016-03-25)
|
| IESG |
IESG state |
|
AD is watching
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alvaro Retana
|
|
Send notices to |
|
aretana@cisco.com
|
IDR S. Shah
Internet-Draft
Intended status: Standards Track K. Patel
Expires: February 2, 2018 Arrcus, Inc
S. Bajaj
Viptela
L. Tomotaki
Verizon
M. Boucadair
Orange
August 1, 2017
Inter-domain Traffic Conditioning Agreement (TCA) Exchange Attribute
draft-ietf-idr-sla-exchange-11.txt
Abstract
Network administrators typically enforce Quality of Service (QoS)
policies according to Traffic Conditioning Agreement (TCA) with their
providers. The enforcement of such policies often relies upon
vendor-specific configuration language. Both learning of TCA, either
thru TCA documents or via some other out-of-band method, and
translating them to vendor specific configuration language is a
complex, often manual, process and prone to errors.
This document specifies an optional transitive attribute to signal
TCA parameters in-band, across administrative boundaries (considered
as Autonomous Systems (AS)), thus simplifying and facilitating some
of the complex provisioning tasks in situations where BGP is
available as a routing protocol.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 2, 2018.
Shah, et al. Expires February 2, 2018 [Page 1]
Internet-Draft Inter-domain TCA Exchange August 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. QoS Attribute Definition . . . . . . . . . . . . . . . . . . 5
3.1. QoS Attribute SubType . . . . . . . . . . . . . . . . . . 6
3.2. TCA SubType . . . . . . . . . . . . . . . . . . . . . . . 7
3.3. TCA Content for ADVERTISE TCA Event . . . . . . . . . . . 9
3.3.1. Supported IPFIX identifiers for Traffic Class
Elements . . . . . . . . . . . . . . . . . . . . . . 12
3.3.2. Traffic Class Service types and respective TLVs . . . 15
4. Originating TCA Notification . . . . . . . . . . . . . . . . 22
4.1. TCA Contexts . . . . . . . . . . . . . . . . . . . . . . 23
4.1.1. TCA Advertisement for Point-to-Point Connection . . . 23
4.1.2. TCA Advertisement for Destination AS Multiple Hops
Away . . . . . . . . . . . . . . . . . . . . . . . . 24
5. QoS Attribute Handling at Forwarding Nodes . . . . . . . . . 24
5.1. BGP Node Capable of Processing QoS Attribute . . . . . . 24
5.2. QoS Attribute Handling at Receiver . . . . . . . . . . . 25
6. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 25
7. Deployment Considerations . . . . . . . . . . . . . . . . . . 25
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
9. Security Considerations . . . . . . . . . . . . . . . . . . . 28
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29
Show full document text